docker - 在其他分区上安装Docker时出错-6ren

docker - 在其他分区上安装Docker时出错

转载作者：行者123 更新时间：2023-12-02 19:02:31

我大约在三周前在Kubernetu 28G(sdb5)的分区上安装了Kubuntu 18，但是在安装docker之后，该空间似乎不足以容纳我的根分区
我发现/ var / lib / docker /需要11.1 GiB。

我找到了将sdb7分区用于docker的决定，该决定现在不使用。
因此，在将/ sdb7格式化为ext4并在/ etc / fstab中使用/ sdb7并重新启动OS之后，我运行:

cd /var/lib
sudo rsync -av docker /mnt/_work_sdb7
sudo mv docker docker.old
sudo ln -s /mnt/_work_sdb7/docker

接下来:

$ docker-compose up -d --build
ERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

我找到了解决这种错误的方法:

sudo  usermod -aG docker $USER
sudo  newgrp - docker

但这没有帮助。下一个 :

缺少某些配置/许可？

# docker-compose --version
docker-compose version 1.17.1, build unknown
# docker --version
Docker version 19.03.2, build 6a30dfc

MODIFIED:

我运行命令并在控制台中看到消息:

$ sudo dockerd --data-root=/mnt/_work_sdb7
INFO[2019-09-14T14:56:26.394402307+03:00] Starting up                                  
INFO[2019-09-14T14:56:26.395196810+03:00] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf 
INFO[2019-09-14T14:56:26.444127000+03:00] parsed scheme: "unix"                         module=grpc
INFO[2019-09-14T14:56:26.444152461+03:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2019-09-14T14:56:26.444179994+03:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <nil>}] }  module=grpc
INFO[2019-09-14T14:56:26.444193376+03:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2019-09-14T14:56:26.444651765+03:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000143020, CONNECTING  module=grpc
INFO[2019-09-14T14:56:26.444710232+03:00] blockingPicker: the picked transport is not ready, loop back to repick  module=grpc
INFO[2019-09-14T14:56:26.463935589+03:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000143020, READY  module=grpc
INFO[2019-09-14T14:56:26.503211493+03:00] parsed scheme: "unix"                         module=grpc
INFO[2019-09-14T14:56:26.503236499+03:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2019-09-14T14:56:26.503253831+03:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <nil>}] }  module=grpc
INFO[2019-09-14T14:56:26.503264403+03:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2019-09-14T14:56:26.503334016+03:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000143420, CONNECTING  module=grpc
INFO[2019-09-14T14:56:26.503354596+03:00] blockingPicker: the picked transport is not ready, loop back to repick  module=grpc
INFO[2019-09-14T14:56:26.503629147+03:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000143420, READY  module=grpc
WARN[2019-09-14T14:56:26.584401464+03:00] Your kernel does not support swap memory limit 
WARN[2019-09-14T14:56:26.584423249+03:00] Your kernel does not support cgroup rt period 
WARN[2019-09-14T14:56:26.584431948+03:00] Your kernel does not support cgroup rt runtime 
INFO[2019-09-14T14:56:26.584832727+03:00] Loading containers: start.                   
INFO[2019-09-14T14:56:26.861388365+03:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address 
INFO[2019-09-14T14:56:27.120567034+03:00] Loading containers: done.                    
INFO[2019-09-14T14:56:27.294102345+03:00] Docker daemon                                 commit=6a30dfc graphdriver(s)=overlay2 version=19.03.2
INFO[2019-09-14T14:56:27.294224407+03:00] Daemon has completed initialization          
INFO[2019-09-14T14:56:27.366695106+03:00] API listen on /var/run/docker.sock

上面的命令没有完成并且正在工作:

我在其他选项卡中打开控制台并运行:

$ sudo  usermod -aG docker $USER
$ sudo  newgrp - docker
# cd /mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker
# sudo systemctl enable docker
Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
# sudo systemctl start docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-09-14 15:00:34 EEST; 8s ago
     Docs: https://docs.docker.com
  Process: 14694 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 14694 (code=exited, status=1/FAILURE)

Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Stopped Docker Application Container Engine.
Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.service: Start request repeated too quickly.
Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Failed to start Docker Application Container Engine.
# journalctl -xe
-- Automatic restarting of the unit docker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.service has finished shutting down.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Closed Docker Socket for the API.
-- Subject: Unit docker.socket has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.socket has finished shutting down.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Stopping Docker Socket for the API.
-- Subject: Unit docker.socket has begun shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.socket has begun shutting down.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Starting Docker Socket for the API.
-- Subject: Unit docker.socket has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.socket has begun starting up.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Listening on Docker Socket for the API.
-- Subject: Unit docker.socket has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.socket has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.service: Start request repeated too quickly.
Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 14 15:00:34 serge-at-hoe systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.service has failed.
-- 
-- The result is RESULT.
Sep 14 15:00:34 serge-at-hoe systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Sep 14 15:00:42 serge-at-hoe systemd[1]: Started Run anacron jobs.
-- Subject: Unit anacron.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit anacron.service has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 14 15:00:42 serge-at-hoe anacron[14760]: Anacron 2.3 started on 2019-09-14
Sep 14 15:00:42 serge-at-hoe anacron[14760]: Normal exit (0 jobs run)

怎么了？

MODIFIED 2:
我找不到现有文件，因此创建了新文件/etc/docker/daemon.json
内容:

{
  "data-root": "/mnt/_work_sdb7/docker" ,
  "storage-driver": "overlay2"
}


/etc/docker# ls -la
total 24
drwxr-xr-x   2 root root  4096 вер 14 16:52 .
drwxr-xr-x 150 root root 12288 вер 14 16:05 ..
-rwxrwxrwx   1 root root    81 вер 14 16:52 daemon.json
-rw-------   1 root root   244 вер  6 18:12 key.json

在我的/ etc / fstab中:

/dev/sdb7 /mnt/_work_sdb7  ext4 defaults 0 0

并重新启动操作系统。
之后，在我的docker项目中，我运行:

$ sudo systemctl enable docker
[sudo] password for serge: 
Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
serge@serge-at-hoe:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker$ sudo systemctl start docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
serge@serge-at-hoe:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker$ systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-09-14 16:54:09 EEST; 2s ago
     Docs: https://docs.docker.com
  Process: 5199 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 5199 (code=exited, status=1/FAILURE)

вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Service hold-off time over, scheduling restart.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
вер 14 16:54:09 serge-at-hoe systemd[1]: Stopped Docker Application Container Engine.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Start request repeated too quickly.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Failed with result 'exit-code'.
вер 14 16:54:09 serge-at-hoe systemd[1]: Failed to start Docker Application Container Engine.
serge@serge-at-hoe:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker$ journalctl -xe
-- 
-- Automatic restarting of the unit docker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
вер 14 16:54:09 serge-at-hoe systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.service has finished shutting down.
вер 14 16:54:09 serge-at-hoe systemd[1]: Closed Docker Socket for the API.
-- Subject: Unit docker.socket has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.socket has finished shutting down.
вер 14 16:54:09 serge-at-hoe systemd[1]: Stopping Docker Socket for the API.
-- Subject: Unit docker.socket has begun shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support                                                                                                                                                                                                    
--                                                                                                                                                                                                                                           
-- Unit docker.socket has begun shutting down.                                                                                                                                                                                               
вер 14 16:54:09 serge-at-hoe systemd[1]: Starting Docker Socket for the API.                                                                                                                                                                 
-- Subject: Unit docker.socket has begun start-up                                                                                                                                                                                            
-- Defined-By: systemd                                                                                                                                                                                                                       
-- Support: http://www.ubuntu.com/support                                                                                                                                                                                                    
--                                                                                                                                                                                                                                           
-- Unit docker.socket has begun starting up.                                                                                                                                                                                                 
вер 14 16:54:09 serge-at-hoe systemd[1]: Listening on Docker Socket for the API.                                                                                                                                                             
-- Subject: Unit docker.socket has finished start-up                                                                                                                                                                                         
-- Defined-By: systemd                                                                                                                                                                                                                       
-- Support: http://www.ubuntu.com/support                                                                                                                                                                                                    
--                                                                                                                                                                                                                                           
-- Unit docker.socket has finished starting up.                                                                                                                                                                                              
--                                                                                                                                                                                                                                           
-- The start-up result is RESULT.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Start request repeated too quickly.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Failed with result 'exit-code'.
вер 14 16:54:09 serge-at-hoe systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.service has failed.
-- 
-- The result is RESULT.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
вер 14 16:54:10 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:c8:e7:f0:6e:fc:29:08:00 SRC=100.103.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=40300 PROTO=2 
вер 14 16:54:10 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=213.109.129.134 DST=213.109.234.130 LEN=44 TOS=0x00 PREC=0x00 TTL=250 ID=15541 DF PROTO=TCP SPT=35673 DPT=23 WINDOW=14600 R
вер 14 16:54:11 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=36.63.165.72 DST=213.109.234.130 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=901 DF PROTO=TCP SPT=44000 DPT=1433 WINDOW=8192 RES=0
вер 14 16:54:12 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=01:00:5e:00:00:01:c8:e7:f0:6e:fc:29:08:00 SRC=100.103.0.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=48963 PROTO=2 
вер 14 16:54:23 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=159.224.38.32 DST=213.109.234.130 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=26239 DF PROTO=TCP SPT=34959 DPT=6881 WINDOW=7300 RES
вер 14 16:54:23 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=185.222.211.54 DST=213.109.234.130 LEN=40 TOS=0x00 PREC=0x00 TTL=251 ID=1768 PROTO=TCP SPT=41109 DPT=8321 WINDOW=1024 RES=0
вер 14 16:54:23 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=87.122.153.155 DST=213.109.234.130 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=2867 DF PROTO=TCP SPT=47437 DPT=6881 WINDOW=7300 RES
вер 14 16:54:24 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=159.224.38.32 DST=213.109.234.130 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=26240 DF PROTO=TCP SPT=34959 DPT=6881 WINDOW=7300 RES
вер 14 16:54:24 serge-at-hoe kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC=44:8a:5b:ee:2a:dd:c8:e7:f0:6e:fc:29:08:00 SRC=87.122.153.155 DST=213.109.234.130 LEN=60 TOS=0x00 PREC=0x00 TTL=57 ID=2868 DF PROTO=TCP SPT=47437 DPT=6881 WINDOW=7300 RES
lines 2823-2877/2877 (END)

我看到错误:

вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Start request repeated too quickly.
вер 14 16:54:09 serge-at-hoe systemd[1]: docker.service: Failed with result 'exit-code'.
вер 14 16:54:09 serge-at-hoe systemd[1]: Failed to start Docker Application Container Engine.

？

MODIFIED 3:
我找到了/etc/systemd/system.conf，其中所有参数都已注释
我取消了注释或使用一些值添加了参数，使它们递增并重新启动操作系统。我做了几次，至少我有:

DefaultStartLimitIntervalSec=350s
DefaultStartLimitBurst=260
StartLimitInterval=350s
StartLimitBurst=260
StartLimitIntervalSec=260

虽然所有其他参数都已注释，但是无论如何我都会看到错误:

вер 14 18:05:44 serge-at-hoe systemd[1]: docker.service: Start request repeated too quickly.
вер 14 18:05:44 serge-at-hoe systemd[1]: docker.service: Failed with result 'exit-code'.
вер 14 18:05:44 serge-at-hoe systemd[1]: Failed to start Docker Application Container Engine.

哪些值必须具有这些(或其他一些)值？

MODIFIED＃4:
我在/etc/systemd/system.conf中尝试将某些值更改为零，因为我用谷歌搜索了这样的可能决定:

DefaultStartLimitIntervalSec=0
DefaultStartLimitBurst=260
StartLimitInterval=350
StartLimitBurst=260
StartLimitIntervalSec=0

但是重新启动操作系统后，我无法登录系统，并且屏幕上显示了许多刷新消息。
我用全0修改了文件:

DefaultStartLimitIntervalSec=0
DefaultStartLimitBurst=0
StartLimitInterval=0
StartLimitBurst=0
StartLimitIntervalSec=0

我重新加载好，但在运行docker时仍然出现“重复启动请求太快”错误:

$ sudo  usermod -aG docker $USER
#:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker$ sudo  newgrp - docker
#:/root# cd /mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker
#:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker# sudo systemctl start docker   
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
#:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker# sudo systemctl enable docker
Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
#:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker# sudo systemctl start docker   
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
#:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-09-16 14:30:07 EEST; 298ms ago
     Docs: https://docs.docker.com
  Process: 5183 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 5183 (code=exited, status=1/FAILURE)

Sep 16 14:30:07 s systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Sep 16 14:30:07 s systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Sep 16 14:30:07 s systemd[1]: Stopped Docker Application Container Engine.
Sep 16 14:30:07 s systemd[1]: docker.service: Start request repeated too quickly.
Sep 16 14:30:07 s systemd[1]: docker.service: Failed with result 'exit-code'.
Sep 16 14:30:07 s systemd[1]: Failed to start Docker Application Container Engine.
#:/mnt/_work_sdb8/wwwroot/lar/DockerApps/votes_docker# journalctl -xe
-- Support: http://www.ubuntu.com/support
-- 
-- Unit snapd.service has finished shutting down.
Sep 16 14:30:15 s systemd[1]: Starting Snappy daemon...
-- Subject: Unit snapd.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit snapd.service has begun starting up.
Sep 16 14:30:15 s snapd[6435]: AppArmor status: apparmor is enabled and all features are available
Sep 16 14:30:15 s snapd[6435]: cannot run daemon: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
Sep 16 14:30:15 s systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 14:30:15 s systemd[1]: snapd.service: Failed with result 'exit-code'.                                                                                                                                                      
Sep 16 14:30:15 s systemd[1]: Failed to start Snappy daemon.                                                                                                                                                                      
-- Subject: Unit snapd.service has failed                                                                                                                                                                                                    
-- Defined-By: systemd                                                                                                                                                                                                                       
-- Support: http://www.ubuntu.com/support                                                                                                                                                                                                    
--                                                                                                                                                                                                                                           
-- Unit snapd.service has failed.                                                                                                                                                                                                            
--                                                                                                                                                                                                                                           
-- The result is RESULT.                                                                                                                                                                                                                     
Sep 16 14:30:15 s systemd[1]: snapd.service: Triggering OnFailure= dependencies.                                                                                                                                                  
Sep 16 14:30:15 s systemd[1]: snapd.service: Service hold-off time over, scheduling restart.                                                                                                                                      
Sep 16 14:30:15 s systemd[1]: snapd.service: Scheduled restart job, restart counter is at 25663.                                                                                                                                  
-- Subject: Automatic restarting of a unit has been scheduled                                                                                                                                                                                
-- Defined-By: systemd                                                                                                                                                                                                                       
-- Support: http://www.ubuntu.com/support                                                                                                                                                                                                    
--                                                                                                                                                                                                                                           
-- Automatic restarting of the unit snapd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 16 14:30:15 s systemd[1]: Stopped Snappy daemon.
-- Subject: Unit snapd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit snapd.service has finished shutting down.
Sep 16 14:30:15 s systemd[1]: Starting Snappy daemon...
-- Subject: Unit snapd.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit snapd.service has begun starting up.
Sep 16 14:30:15 s snapd[6467]: AppArmor status: apparmor is enabled and all features are available
Sep 16 14:30:15 s snapd[6467]: cannot run daemon: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
Sep 16 14:30:15 s systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 14:30:15 s systemd[1]: snapd.service: Failed with result 'exit-code'.
Sep 16 14:30:15 s systemd[1]: Failed to start Snappy daemon.
-- Subject: Unit snapd.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit snapd.service has failed.
-- 
-- The result is RESULT.
Sep 16 14:30:15 s systemd[1]: snapd.service: Triggering OnFailure= dependencies.

我不确定/etc/systemd/system.conf中的有效选项还是其他问题？

最佳答案

您输入了:

sudo systemctl start docker
sudo systemctl enable docker

？

关于docker - 在其他分区上安装Docker时出错，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/57934900/

文章推荐： docker - 在docker run命令中传递动态路径

javascript - npm test 出错，但 mocha test node.js 出错
我正在使用 node.js 和 mocha 单元测试，并且希望能够通过 npm 运行测试命令。当我在测试文件夹中运行 Mocha 测试时，测试运行成功。但是，当我运行 npm test 时，测试给出了
java - java方法replaceAll()出错
我的文本区域中有这些标签 ..... 我正在尝试使用 replaceAll() String 方法替换它们 text.replaceAll("", ""); text.replaceAll("", "
java - ZXing 出错
早上好，我是 ZXing 的新手，当我运行我的应用程序时出现以下错误: 异常Ljava/lang/NoClassDefFoundError；初始化 ICOM/google/zxing/client/a
C - free() 出错？
我正在制作一些哈希函数。它的源代码是... #include #include #include int m_hash(char *input, size_t in_length, char
swift - SKPhysicsContactDelegate 出错？
我正在尝试使用 Spritekit 在 Swift 中编写游戏。目的是带着他的角色迎面而来的矩形逃跑。现在我在 SKPhysicsContactDelegate (didBegin ()) 方法中犯了
java - actionPerformed 出错？
我正在尝试创建一个用于导入 CSV 文件的按钮，但出现此错误: actionPerformed(java.awt.event.ActionEvent) in cannot implement
java - NULLIF() 出错？
请看下面的代码 public List getNames() { List names = new ArrayList(); try { createConnection(); Sta
创建计划事件时 MySQL 出错
我正在尝试添加一个事件以在“dealsArchive”表中创建一个条目，然后从“deals”表中删除该条目。它需要在特定时间执行。这是我正在尝试使用的: DELIMITER $$ CREATE EV
尝试将存储过程结果插入表时 PHPmyadmin 出错
我试图将两个存储过程的表结果存储到 phpmyadmin 例程窗口中的单个表中，这给了我 mariadb 语法错误。单独调用存储过程给出了结果。存储过程代码 BEGIN CREATE TABLE t
android - videoview的onpreparedlistener()出错
我想在 videoview 中加载视频之前有一个进度条。但是我收到以下错误。我还添加了所有必要的导入。我在 ANDROID 中使用 AIDE 这是我的代码 public class MainActi
android - AsyncTask 出错
我已经使用了 AsyncTask，但我不明白为什么在我的设备 (OS 4.0) 上测试时仍然出现错误。我的 apk 构建于 2.3.3 中。我想我把代码弄错了，但我不知道我的错误在哪里。任何人都请帮助
MySQL注入(inject)出错
我在测试 friend 网站的安全性时，通过在 URL 末尾添加 ' 发现了 SQL 注入(inject)漏洞该网站是用zend框架构建的我遇到的问题是 MySQL -- 中的注释语法不起作用，因此页
java - getMap() 出错？
我正在尝试使用堆栈溢出答案之一的交互式信息窗口。链接如下: interactive infowindow 但是我在代码中使用 getMap() 时遇到错误。虽然我尝试使用 getMapAsync 但
java - addMouseListener 出错
当我编译以下代码时出现错误: The method addMouseListener(Player) is undefined for the type Player 代码: import java.
mysql - Async_Http_Response_Handler 出错
我是 Android 开发的初学者。我正在开发一个接收 MySql 数据然后将其保存在 SQLite 中的应用程序。我将 Json 用于同步状态，以便我可以将未同步数据的数量显示为要同步的待处理数据
Java - 转换文件名 - 出错？
(这里是Hello world级别的自动化测试人员) 我正在尝试下载一个文件并将其重命名以便于查找。我收到一个错误....这是代码 @Test public void allDownload(
c++ - while(cin) 出错
我只是在写另一个程序。并使用: while (cin) words.push_back(s); words是string的vector，s是string。我的 RAM 使用量在 4 或 5
javascript - AngularJS 出错
我是 AngularJS 的新手，我遇到了一个问题。我有一个带有提交按钮的页面，当我单击提交模式时必须打开并且来自 URL 的数据必须存在于模式中。现在，模式打开但它是空的并且没有从 URL 获取数据
c++ - 尝试将文件写入数组时运算符 << 出错
我正在尝试读取一个文件(它可以包含任意数量的随机数字，但不会超过 500 个)并将其放入一个数组中。稍后我将需要使用数组来做很多事情。但到目前为止，这一小段代码给了我 no match for o
c++ - benderrmq 出错
有些人在使用 make 命令进行编译时遇到了问题，所以我想我应该在这里尝试一下，我已经在以下操作系统的 ubuntu 32 位和挤压 64 位上尝试过我克隆了 git 项目 https://gith

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

docker - 在其他分区上安装Docker时出错