About 99% of the time when I try to stop or rm a ddev project I get a 'permission denied' error, and then have to try a lot of different means to get ddev back to a healthy state so I can start working again. Then it happens all over again the next time I come to work on the project.
Can anyone suggest a) the quickest means to break out of this when I am unable to stop a docker container or ddev project b) a means to work out why it keeps happening and fix it?
To mitigate this I have tried:
ddev stop
ddev rm -a
ddev rm
ddev stop
Docker stop
Updating ddev
Upgrading docker
Restarting the machine (occasionally works)
Using the docker kill command
I am working on a linux machine Ubuntu 18.04
Ddev version is v1.8.0
Docker is 18.09.6, build 481bc77
Thank you!!
I would expect to be able to stop and start projects easily but seem to have been getting a permissions error about 99% of the time. I have not identified why it sometimes on the rare occasion works fine.
Stopping ddev-lpntheme-dba ... error
Stopping ddev-lpntheme-web ... error
Stopping ddev-lpntheme-db ... error
ERROR: for ddev-lpntheme-web cannot stop container: 761c2f876230df13267d3d2a7c5d92c869d796a41f1b45cf1c9831ee6673740f: Cannot kill container 761c2f876230df13267d3d2a7c5d92c869d796a41f1b45cf1c9831ee6673740f: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"
: unknown
ERROR: for ddev-lpntheme-dba cannot stop container: e5165f70b0b949aef305af013f4aae762968aa0afa99cf6f397c6960048a76bf: Cannot kill container e5165f70b0b949aef305af013f4aae762968aa0afa99cf6f397c6960048a76bf: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"
: unknown
Removing container: ddev-lpntheme-dba
Failed to remove project lpntheme:
could not remove container ddev-lpntheme-dba: API error (500): Could not kill running container e5165f70b0b949aef305af013f4aae762968aa0afa99cf6f397c6960048a76bf, cannot remove - Cannot kill container e5165f70b0b949aef305af013f4aae762968aa0afa99cf6f397c6960048a76bf: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"
: unknown
I've also managed to completely break the Docker daemon in the past trying to resolve this problem. (I was following this and didn't really know what I was doing How to stop running Container, if error response from daemon is: Cannot Kill Container [...] permission denied?)
Any help greatly appreciated!
More info from 7/6/19
crispin#sonic:~/dockerfolder/ToolLibraryProject$ ddev start
Starting ToolLibraryProject...
Recreating ddev-ssh-agent ... done
ssh-agent container is running: If you want to add authentication to the ssh-agent container, run 'ddev auth ssh' to enable your keys.
Running Command Command=ip address show dev docker0
Creating volume "ToolLibraryProject-mariadb" with default driver
Creating ddev-ToolLibraryProject-db ... done
Creating ddev-ToolLibraryProject-web ... done
Creating ddev-ToolLibraryProject-dba ... done
Recreating ddev-router ... done
Ensuring write permissions for ToolLibraryProject
Successfully started ToolLibraryProject
Project can be reached at https://ToolLibraryProject.ddev.local, http://ToolLibraryProject.ddev.local, https://127.0.0.1:32771, http://127.0.0.1:32772
crispin#sonic:~/dockerfolder/ToolLibraryProject$ ls
composer.json config LICENSE phpunit.xml.dist scripts web
composer.lock drush load.environment.php README.md vendor
crispin#sonic:~/dockerfolder/ToolLibraryProject$ ls
composer.json config LICENSE phpunit.xml.dist scripts web
composer.lock drush load.environment.php README.md vendor
crispin#sonic:~/dockerfolder/ToolLibraryProject$
crispin#sonic:~/dockerfolder/ToolLibraryProject$ ddev stop
Stopping ddev-ToolLibraryProject-web ... error
Stopping ddev-ToolLibraryProject-dba ... error
Stopping ddev-ToolLibraryProject-db ... error
ERROR: for ddev-ToolLibraryProject-web cannot stop container: 3485d615d2dfa46884493b91d7339b06834594fcb46f870cfe60a0486b87f1d3: Cannot kill container 3485d615d2dfa46884493b91d7339b06834594fcb46f870cfe60a0486b87f1d3: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"
: unknown
ERROR: for ddev-ToolLibraryProject-dba cannot stop container: cc2209064e0103fdab638445aeac2206217c83a17a7b97eea2216440bb5bb4e2: Cannot kill container cc2209064e0103fdab638445aeac2206217c83a17a7b97eea2216440bb5bb4e2: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"
: unknown
Removing container: ddev-ToolLibraryProject-web
Failed to remove project ToolLibraryProject:
could not remove container ddev-ToolLibraryProject-web: API error (500): Could not kill running container 3485d615d2dfa46884493b91d7339b06834594fcb46f870cfe60a0486b87f1d3, cannot remove - Cannot kill container 3485d615d2dfa46884493b91d7339b06834594fcb46f870cfe60a0486b87f1d3: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"
: unknown
And with docker logs ToolLibraryProject I get Error: No such container: ToolLibraryProject
Regarding file system I hope this makes sense:
/dev/sda2 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Related
when im trying to build an image with command docker build im getting this error
im using windows docker desktop
The command '/bin/sh -c yarn install --production' returned a non-zero code: 4294967295: failed to shutdown container: container 1842716825b498d7be9ed514a4839dfc528caafe8f906018c93842517f60635e encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110): subsequent terminate failed container 1842716825b498d7be9ed514a4839dfc528caafe8f906018c93842517f60635e encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110)
how this error be resolved
This must be due to windows host failure on docker call when try to shut down the container
Try by restarting docker demon
sudo service docker restart
Check the status of the Docker containers:
docker ps -a
stop and remove it:
docker stop <container-id>
docker rm <container-id>
Then try by building the image again. If the problem still persists, consider upgrading to the latest version of Docker or clear docker cache or
docker system prune
Error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.project%3Dkafka-waffle-stack%22%3Atrue%7D%7D": open //./pipe/docker_engine: The system cannot find the file specified
How can I fix this issue and get the docker-compose command to work?
I am trying to run a docker-compose command, but I am receiving the above error message. The error message seems to indicate that the Docker daemon is not running. I have tried starting the Docker daemon by running the command "dockerd" in the command prompt, but the issue persists.
I went through each step and followed the documentation here https://minikube.sigs.k8s.io/docs/drivers/docker/
When I try to run
minikube start --driver=docker
I get this error
X Exiting due to PROVIDER_DOCKER_NOT_RUNNING: "docker version --format -" exit status 1: error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified.
* Suggestion: Start the Docker service
* Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/
The documentation it references is the same one I used to set everything up to begin with. I also tried switching daemon using the command "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon
that didn't work and I tried reset the docker settings to default and I'm still getting this error.
When I start a DDEV-Local project, I get "Failed to start ddev-ssh-agent", and when I use docker logs ddev-ssh-agent I see
Running socat UNIX-LISTEN:/tmp/.ssh-agent/proxy-socket,perm=0666,fork UNIX-CONNECT:/tmp/.ssh-agent/socket
unix_listener: cannot bind to path /tmp/.ssh-agent/socket: Permission denied
2020/04/29 14:50:25 socat[16] E bind(5, {AF=1 "/tmp/.ssh-agent/proxy-socket"}, 30): Permission denied
How can I fix this?
Use this sequence to fix this exact problem:
ddev poweroff
docker volume rm ddev-ssh-agent_dot_ssh ddev-ssh-agent_socket_dir
ddev start
That will repair/replace the docker volumes that store the ssh-agent socket, and seems to resolve this problem.
If you know what sequence of events might have caused this, please comment or open an issue to explain. It is mostly likely caused by using root privileges with ddev, but ddev actively tries to prevent that.
I am running trying to run a docker build on windows 10:
D:\mds>docker-compose --file=docker-compose.yml up -d
Starting mds_data_1
Starting mds_memcached_1
Starting mds_mongo_1
Starting mds_mysql_1
Starting mds_fc_1
Starting mds_succeed_1
Starting mds_haproxy_1`
But fc_1 is not starting, and when I run: docker logs mds_fc_1, I see:
container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/D/~mds\\\" to rootfs \\\"/var/lib/docker/overlay2/f483546b2e19d0860971307b8cc813bad6ca683f3ebd90c36d89974444d7b75b/merged\\\" at \\\"/var/www/applications/mds\\\" caused \\\"stat /D/~mds: input/output error\\\"\""
container_linux.go:247: starting container process caused "process_linux.go:359: container init caused \"rootfs_linux.go:54: mounting \\\"/D/~mds\\\" to rootfs \\\"/var/lib/docker/overlay2/f483546b2e19d0860971307b8cc813bad6ca683f3ebd90c36d89974444d7b75b/merged\\\" at \\\"/var/www/applications/mds\\\" caused \\\"stat /D/~mds: input/output error\\\"\""
standard_init_linux.go:178: exec user process caused "no such file or directory"
standard_init_linux.go:178: exec user process caused "no such file or directory"
standard_init_linux.go:178: exec user process caused "no such file or directory"
standard_init_linux.go:178: exec user process caused "no such file or directory"
If you run docker ps -a, then you can see your docker container status.
I think fc_1 is in exited status, because it failed with error something like file not found error.
please find why this error happened, then you can fc_1 can run continuously.