在NUC9中安装ESXi8.0U2,安装黑群晖后，docker无法启动
通过SSH登录群晖查看docker运行信息xxx@DS920Plus:/$ sudo docker info
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
Client:
Context: default
Debug Mode: false
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 20.10.3
Storage Driver: btrfs
Build Version: Btrfs v4.0
Library Version: 101
Logging Driver: db
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs db fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3fa00912415f3e9c6f82dd72119179d599efd13b
runc version: 31cc25f16f5eba4d0f53e35374532873744f4b31
init version: ed96d00 (expected: de40ad0)
Security Options:
apparmor
Kernel Version: 4.4.180+
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.828GiB
Name: DS920Plus
ID: AULO:3NCA:Z4HQ:MHRZ:TT7W:3K72:GK5R:VBVR:MFTK:F3UN:ABLP:Q4X2
Docker Root Dir: /volume1/@docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio weight support
WARNING: No blkio weight_device support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
查看docker运行状态
xxx@DS920Plus:/$ sudo systemctl status docker
● docker.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
查看docker版本
xxx@DS920Plus:/$ sudo docker version
Client:
Version: 20.10.3
API version: 1.41
Go version: go1.17.1
Git commit: 55f0773
Built: Thu Jul 21 10:23:46 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Server:
Engine:
Version: 20.10.3
API version: 1.41 (minimum version 1.12)
Go version: go1.17.1
Git commit: b487c8f
Built: Thu Jul 21 10:21:56 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.4.3
GitCommit: 3fa00912415f3e9c6f82dd72119179d599efd13b
runc:
Version: v1.0.0-rc93
GitCommit: 31cc25f16f5eba4d0f53e35374532873744f4b31
docker-init:
Version: 0.19.0
GitCommit: ed96d00
我安装7.1和7.2两个版本，都是同样的问题，感觉已应该和硬件有关，请大佬指教，不胜感激！ 本帖最后由 angelshadow 于 2024-10-31 14:03 编辑
问题的原因找到了，docker镜像仓库的地址被封了，导致镜像拉来不下来，更换镜像源后问题解决，并且docker运行正常情况下，docker info 和systmctl status docker命令返回的状态和帖子内容是一样的。
群晖中docker守护进程配置文件位于/var/packages/ContainerManager/etc/dockerd.json镜像仓库的URL为"registry-mirrors"字段。
群晖中重启Docker服务的命令为：sudo synosystemctl restart pkgctl-ContainerManager
发一个我在用的镜像源：https://docker.fxxk.dedyn.io 无脑装SA6400 248100321 发表于 2024-10-22 15:08
无脑装SA6400
SA6400试了一下，问题依旧。 我也遇到这个情况了 qxiaoyu 发表于 2024-10-27 21:08
我也遇到这个情况了
使用NUC9直接安装SA6400，加载nvme插件，固态能用，但docker的问题依旧，今晚准备安装debain系统，在其中安装docker试试，感觉是BIOS设置的问题，我的BIOS是0077 angelshadow 发表于 2024-10-31 13:48
问题的原因找到了，docker镜像仓库的地址被封了，导致镜像拉来不下来，更换镜像源后问题解决，并且docker运 ...
我也发现很多docker镜像源被封了，我现在是直接下载docker的镜像tar文件，然后传上去添加，不然不好找镜像源。
页:
[1]