Unable to bringup etcd:v3.5.13 docker container. #19580
Unanswered
Mattavamsi
asked this question in
Q&A
Replies: 1 comment
-
Hi @Mattavamsi, starting v3.5 our container images are based on a distroless image. Therefore, they don't come installed with shell interpreters such as sh or bash. If you need to apply customization using your init shell script, I suggest building your own image. i.e.,: FROM quay.io/coreos/etcd:v3.5.19 as etcd
FROM debian:<some tag>
RUN mkdir -p /var/etcd/ /var/lib/etcd/
COPY --from=etcd /usr/local/bin/etcd /usr/local/bin/
COPY --from=etcd /usr/local/bin/etcdctl /usr/local/bin/
COPY --from=etcd /usr/local/bin/etcdutl /usr/local/bin/
... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug report criteria
What happened?
Hello Team,
We are trying to update etcd container version from v3.4.13 to v3.5.13. (We also upgraded k3s to newer version i.e, v1.30.4+k3s- ().
with v3.4.13 we are able to bring etcd docker container without any issues. But we are facing some problems with v3.5.13 version.
So upon investigating seems some changes are happened in v3.5.13 version base image.
--> docker run --rm -it -v /root/script.sh:/root/script.sh --entrypoint /bin/sh quay.io/coreos/etcd:v3.4.13
--> ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var
-->exit
-->docker run --rm -it -v /root/script.sh:/root/script.sh --entrypoint /bin/sh quay.io/coreos/etcd:v3.5.13
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown.
Logs:
-->docker inspect quay.io/coreos/etcd:v3.4.13 | grep -i image
"Image": "sha256:6a96e79e979340f0af0a6a0bb54c7c76bb3095553d6a4fa80ce02fa9d01e18f1",
"Image": "sha256:6a96e79e979340f0af0a6a0bb54c7c76bb3095553d6a4fa80ce02fa9d01e18f1",
--> docker inspect quay.io/coreos/etcd:v3.5.13 | grep -i image
"Image": "",
"Image": "",
-->k3s --version
k3s version v1.30.4+k3s- ()
go version go1.22.5
Hardware types are same for both versions.
-->docker inspect quay.io/coreos/etcd:v3.5.13 | grep -i Archit.
"Architecture": "amd64",
-->docker inspect quay.io/coreos/etcd:v3.4.13 | grep -i Archit.
"Architecture": "amd64",
We are trying to bringup the new etcd instance using the following command:
docker run -e SUBNET_PREFIX="$network_prefix" -p 2382:2382 -p 2380:2380 -e INITIAL_CLUSTER_MEMBERS="$ETCD_INITIAL_CLUSTER_MEMBERS" -v /etc/etcd/:/etc/etcd/ -v /etc/:/etc -v /root/etcd3mount:/root/etcd3mount -v /var/lib/rancher/k3s/server/tls/etcd/:/var/lib/rancher/k3s/server/tls/etcd/ --privileged --net=host --name etcd3 quay.io/coreos/etcd:v3.5.13 /etc/etcd/etcd.sh -d &
standard_init_linux.go:228: exec user process caused: no such file or directory
What did you expect to happen?
I should be able to open interactive session with version v3.5.13 like as shown below for v3.4.13
-->docker run --rm -it -v /root/script.sh:/root/script.sh --entrypoint /bin/sh quay.io/coreos/etcd:v3.4.13
--> ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var
-->exit
How can we reproduce it (as minimally and precisely as possible)?
docker pull quay.io/coreos/etcd:v3.5.13
docker run --rm -it -v /root/script.sh:/root/script.sh --entrypoint /bin/sh quay.io/coreos/etcd:v3.5.13
Anything else we need to know?
No response
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
paste your configuration here
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
Beta Was this translation helpful? Give feedback.
All reactions