Docker Community Forums

Share and learn in the Docker community.

Cannot start any container because of missing entry point

(Blubadub) #1


I have a problem with running any container at the moment, always leading to an error even with containers that were running before.

I had a container running since 2 weeks with no problem (mysql:latest). Then I restarted the server PC and afterwards the same container wouldn’t start any more with the message:

Error response from daemon: Container command ‘’ not found or does not exist.

Also creating new containers from current images from docker hub are not running with the same error message. For example:

docker run -d --name owncloud_test-container \
-p 34567:80 \

Leads to:

docker: Error response from daemon: Container command '/' not found or does not exist..

I am using:
OpenSuse Leap 42 (64bit)
Docker: 1.11.1-106.1

First think I look at when I have strange behavior is apparmor, but this should not be a problem:

#/etc/init.d/boot.apparmor status
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/boot.apparmor)
   Active: inactive (dead)

Any Ideas?


Error when running privileged - problem mounting fuse
(Dvohra) #2

What is the Dockerfile? Does the Dockerfile include the ENTRYPOINT instruction?

(Blubadub) #3

The Dockerfiles for these two examples are:

Dockerfile MySQL

Dockerfile Owncloud

As said these are the Dockerfiles of the official images from MySQL and Owncloud on Docker Hub. And these are only examples, I have the same problem with all images and containers that I tested.
But most strange for me is, that at least for MySQL I had a container running for two weeks, so the entry point must be in there. I stopped the container, restart the server and start the container again and get the problem above and the container is not starting any more.

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                      PORTS               NAMES
54cf1e6071ca        mysql               ""   2 weeks ago         Exited (127) 46 hours ago                       mysql_wp-container

(Dvohra) #4

Docker seems to be not running properly. What is the output of the following commands:
sudo service docker start
sudo service docker status

(Blubadub) #5

Thanks for the help.
I restarted the service several times in the last days without any effect, but with the last restart now the problem suddenly is gone. I don’t know, that I changed something relevant. Will come back here, when the problem comes back.