杀死后的未知错误未成功终止:信号通知初始化过程导致“权限被拒绝" \ n:未知 [英] unknown error after kill did not terminate sucessfully: signaling init process caused "permission denied"\n: unknown'

问题描述

我正在尝试启动某些Docker容器，或者至少正忙于使用Docker容器.首次安装后，所有东西都可以正常工作.和dint所做的任何事情都不仅仅是docker-compose up down stop restart，还制作了一些wordpress容器以及PHPmyadmin和MariaDB.但是现在当我尝试关闭docker容器时，它给了我拒绝的权限.

I am trying to startup or some docker containers or at least busy with the docker containers. After first installation every thing whas working perfect. and dint do any thing different than just docker-compose up down stop restart and also making some wordpress containers and PHPmyadmin and MariaDB. But now when i try to shutdown the docker container it gives me permissions denied.

到目前为止，我已经在网络上搜索了所有内容，例如将www-data添加到组中，或者尝试使用sudo杀死它.删除容器和图像，没有任何结果.

I have search every thing so far on the web like adding www-data to the groups or try with sudo to kill it. Removet the containers and images with out any results.

david@david-Notebook-P14:~/Desktop/docker-projects$ docker-compose up
Starting mailhog                        ... done
Starting docker-projects_wordpress_db_1 ... done
Starting docker-projects_wordpress_1    ... done
Starting docker-projects_phpmyadmin_1   ... done
Attaching to docker-projects_wordpress_db_1, mailhog, docker-projects_wordpress_1, docker-projects_phpmyadmin_1
wordpress_db_1  | 2019-05-14  8:13:31 0 [Note] mysqld (mysqld 10.3.14-MariaDB-1:10.3.14+maria~bionic) starting as process 1 ...
mailhog         | 2019/05/14 08:13:30 Using in-memory storage
mailhog         | 2019/05/14 08:13:30 [SMTP] Binding to address: 
mailhog         | 2019/05/14 08:13:30 Serving under http://0.0.0.0:8025/
mailhog         | [HTTP] Binding to address: 0.0.0.0:8025
mailhog         | Creating API v1 with WebPath: 
mailhog         | Creating API v2 with WebPath: 
wordpress_1     | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message
wordpress_1     | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.4. Set the 'ServerName' directive globally to suppress this message
wordpress_1     | [Tue May 14 08:13:34.311188 2019] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.25 (Debian) PHP/7.2.18 configured -- resuming normal operations
wordpress_1     | [Tue May 14 08:13:34.345515 2019] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
^CGracefully stopping... (press Ctrl+C again to force)
Stopping docker-projects_wordpress_1    ... error
Stopping docker-projects_phpmyadmin_1   ... error
Stopping mailhog                        ... error
Stopping docker-projects_wordpress_db_1 ... error


ERROR: for docker-projects_phpmyadmin_1  b'cannot stop container: 6911429b36f56ed310c94b4fff91247abea44d9ce4524facd13409a2972df5f2: Cannot kill container 6911429b36f56ed310c94b4fff91247abea44d9ce4524facd13409a2972df5f2: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'

david@david-Notebook-P14:~/Desktop/docker-projects$ docker-compose down
Stopping docker-projects_wordpress_1    ... error
Stopping docker-projects_phpmyadmin_1   ... error
Stopping mailhog                        ... error
Stopping docker-projects_wordpress_db_1 ... error

ERROR: for mailhog  b'cannot stop container: 171cb796bfc6f72294dc66fc0d6277bedda358052db9a95fca6b05c5d0222959: Cannot kill container 171cb796bfc6f72294dc66fc0d6277bedda358052db9a95fca6b05c5d0222959: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'

ERROR: for docker-projects_wordpress_1  b'cannot stop container: 47f29abaf5027d626ea55c7bd4d24a4369f37207d8d723000daa65f6a3b330cf: Cannot kill container 47f29abaf5027d626ea55c7bd4d24a4369f37207d8d723000daa65f6a3b330cf: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'

ERROR: for docker-projects_phpmyadmin_1  b'cannot stop container: 6911429b36f56ed310c94b4fff91247abea44d9ce4524facd13409a2972df5f2: Cannot kill container 6911429b36f56ed310c94b4fff91247abea44d9ce4524facd13409a2972df5f2: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'
david@david-Notebook-P14:~/Desktop/docker-projects$ ps aux | grep dockerd
root      1120  0.3  1.8 493900 71232 ?        Ssl  09:32   0:08 dockerd -G docker --exec-root=/var/snap/docker/384/run/docker --data-root=/var/snap/docker/common/var-lib-docker --pidfile=/var/snap/docker/384/run/docker.pid --config-file=/var/snap/docker/384/config/daemon.json --debug
root      1559  0.0  1.0 781576 40784 ?        Ssl  09:32   0:01 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
david     6053  0.0  0.0  21540  1076 pts/0    S+   10:17   0:00 grep --color=auto dockerd
david@david-Notebook-P14:~/Desktop/docker-projects$ sudo docker-compose down
[sudo] password for david: 
Stopping docker-projects_wordpress_1    ... error
Stopping docker-projects_phpmyadmin_1   ... error
Stopping mailhog                        ... error
Stopping docker-projects_wordpress_db_1 ... error

ERROR: for docker-projects_phpmyadmin_1  b'cannot stop container: 6911429b36f56ed310c94b4fff91247abea44d9ce4524facd13409a2972df5f2: Cannot kill container 6911429b36f56ed310c94b4fff91247abea44d9ce4524facd13409a2972df5f2: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'

ERROR: for mailhog  b'cannot stop container: 171cb796bfc6f72294dc66fc0d6277bedda358052db9a95fca6b05c5d0222959: Cannot kill container 171cb796bfc6f72294dc66fc0d6277bedda358052db9a95fca6b05c5d0222959: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'

ERROR: for docker-projects_wordpress_1  b'cannot stop container: 47f29abaf5027d626ea55c7bd4d24a4369f37207d8d723000daa65f6a3b330cf: Cannot kill container 47f29abaf5027d626ea55c7bd4d24a4369f37207d8d723000daa65f6a3b330cf: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:393: signaling init process caused "permission denied"\n: unknown'

我希望解决此许可问题.到目前为止，我找不到任何解决方案，只是希望有人能帮助我解决这个问题.

I hope to get this permission problem solved. So far i cant find any solutions than hope some one could help me with this.

已经非常感谢

推荐答案

我得到了解决方案:

[可选] 只需使用sudo systemctl stop apparmor&& systemctl disable apparmor

[OPTIONAL] Just use sudo systemctl stop apparmor && systemctl disable apparmor

使用sudo service docker restart重新启动docker之后运行reboot

After restarting docker using sudo service docker restart and then run reboot

这将解决问题.

这篇关于杀死后的未知错误未成功终止:信号通知初始化过程导致“权限被拒绝" \ n:未知的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！