arriven / db1000n

MIT License
1.18k stars 208 forks source link

can't connect to container #464

Closed industral closed 2 years ago

industral commented 2 years ago
root@xxx:~# docker exec -it root_db100_proxy_15_1 /bin/sh
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown
root@xxx:~# docker exec -it root_db100_proxy_15_1 sh
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "sh": executable file not found in $PATH: unknown
root@xxx:~# docker exec -it root_db100_proxy_15_1 which sh
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "which": executable file not found in $PATH: unknown
root@xxx:~# 

something is off. Just can't connect to check container. I've tried different containers, same behaviour.

Looks like issue with latest version of docker, since previous one worked fine

bitshape commented 2 years ago

Starting from v0.8.4 it’s using ko “distro-less” Docker builds so you can’t get into interactive mode as there’s no bin/sh anymore.

industral commented 2 years ago

thanks for reply! so how to check let's say if container has internet or to do something else?

arriven commented 2 years ago

you can, however, use db1000n-advanced for that, which is still based on alpine

industral commented 2 years ago

thanks @Arriven !