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 ‘docker-entrypoint.sh’ 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 \ owncloud:9-apache
e9ca24834ba2ad76c185033e267ce42d5722330d2a688141bf362d9a3c2f052f docker: Error response from daemon: Container command '/entrypoint.sh' not found or does not exist..
I am using:
OpenSuse Leap 42 (64bit)
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)