-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0.0 Does not work with Nats Operator #194
Comments
Right because there is no symlink for
|
Heh, I think it would work but currently there's no ARM build. |
I will take a look at pushing a version of the operator where this is fixed tomorrow. If you want to try to create your own arm image for now, this is the Dockerfile that can be used to generate an 2.0.0 compatible image: https://github.com/nats-io/nats-server/blob/master/docker/Dockerfile.alpine |
Thanks, I'll for sure take a look at it. Does the build system support cross-compilation? I could tackle getting this and the streaming operator working with ARM by emulating how the nats-server build and docker generation happens. |
hey @charles-d-burton, the dockerfile I shared does not support cross compilation, but also I am about to merge #195 and then push the image of the operator this morning that would support 2.0.0 image. I pushed my own image here for now |
Fixed via #195 |
Defects
You'll then see the following in the logs:
Events:
Type Reason Age From Message
Normal Scheduled 88s default-scheduler Successfully assigned default/nats-cluster-1 to kube-node3
Normal Pulling 87s kubelet, kube-node3 Pulling image "nats:2.0.0"
Normal Pulled 84s kubelet, kube-node3 Successfully pulled image "nats:2.0.0"
Normal Created 84s kubelet, kube-node3 Created container nats
Warning Failed 83s kubelet, kube-node3 Error: failed to create containerd task: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: "/gnatsd": stat /gnatsd: no such file or directory": unknown
Versions of
gnatsd
and affected client libraries used:2.0.0
OS/Container environment:
Kubernetes 1.14
Steps or code to reproduce the issue:
Ensure that you have a working version of the nats operator installed in a Kubernetes cluster
kubectl apply the following file
`apiVersion: nats.io/v1alpha2
kind: NatsCluster
metadata:
name: nats-cluster
spec:
size: 3
version: "2.0.0"
Expected result:
A running NATS Cluster
Actual result:
A not running NATS Cluster
The text was updated successfully, but these errors were encountered: