👀 Views: 99 💬 Answers: 1 📅 Created: 2025-06-08

docker ubuntu overlay2 bash

I'm trying to figure out I'm relatively new to this, so bear with me. I'm experiencing an scenario with Docker on Ubuntu 22.04 where my containers unexpected result to start, producing the behavior: `behavior: failed to start container: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "": executable file not found in $PATH: unknown`. I've tried various troubleshooting steps without success. My Docker setup uses the Overlay2 storage driver, and the behavior occurs when I attempt to run a container based on an image that worked previously. Here is the command I'm using to run the container: ```bash docker run -d --name my_container my_image:latest ``` I've checked the Docker daemon logs with `journalctl -u docker.service` and found entries that consistently show the same `OCI runtime create failed` message. I also verified that the image is indeed present using `docker images`, and it appears to be built correctly with the expected executable in the image. To further troubleshoot, I ran `docker inspect my_image:latest` and confirmed that the `Cmd` entry points to the correct executable location: `/usr/local/bin/my_app`. However, when I manually enter a shell in the image using `docker run -it my_image:latest /bin/sh`, I can see that the file is there but it gives a permissions scenario: `permission denied`. I checked the permissions and they are set correctly: ```bash ls -l /usr/local/bin/my_app -rwxr-xr-x 1 root root 123456 Jan 1 00:00 my_app ``` I also ensured that the underlying filesystem has enough space and inodes using `df -h` and `df -i`. Everything seems fine there. Additionally, I tried switching the storage driver to aufs by editing `/etc/docker/daemon.json`, but it didn't resolve the scenario. Is there something I might be missing regarding permissions or filesystem compatibility with Overlay2? Any insights or suggestions on how to further diagnose or resolve this scenario would be greatly appreciated. I'm working on a service that needs to handle this. Thanks in advance! My team is using Bash for this service. Any pointers in the right direction? I'm on Ubuntu 20.04 using the latest version of Bash. What's the best practice here?