猫盘(ARM) 群晖 docker 成功运行

This topic created in 2396 days ago, the information mentioned may be changed or developed.

目前可以执行一些简单的 container，还没有实现太多。
最明显的缺点是只能使用 host 模式，不能使用 bridge 模式。
主要是执行 brctl add 创建网桥失败提示 package not installed. 有谁能帮忙解决吗？解决了 arm 群晖下的 docker 就完美了~适用于其他各种 arm cpu 的群晖

sudo docker run -d --network=host portainer/portainer:linux-arm64
Password:
DEBU[2019-10-24T21:36:47.617296766+08:00] Calling GET /_ping
DEBU[2019-10-24T21:36:47.688275264+08:00] Calling POST /v1.32/containers/create
DEBU[2019-10-24T21:36:47.700661674+08:00] form data: {"AttachStderr":false,"AttachStdin":false,"AttachStdout":false,"Cmd":null,"Domainname":"","Entrypoint":null,"Env":[],"ExposedPorts":{"9000/tcp":{}},"HostConfig":{"AutoRemove":false,"Binds":null,"BlkioDeviceReadBps":null,"BlkioDeviceReadIOps":null,"BlkioDeviceWriteBps":null,"BlkioDeviceWriteIOps":null,"BlkioWeight":0,"BlkioWeightDevice":[],"CapAdd":null,"CapDrop":null,"Cgroup":"","CgroupParent":"","ConsoleSize":[0,0],"ContainerIDFile":"","CpuCount":0,"CpuPercent":0,"CpuPeriod":0,"CpuQuota":0,"CpuRealtimePeriod":0,"CpuRealtimeRuntime":0,"CpuShares":0,"CpusetCpus":"","CpusetMems":"","DeviceCgroupRules":null,"Devices":[],"DiskQuota":0,"Dns":[],"DnsOptions":[],"DnsSearch":[],"ExtraHosts":null,"GroupAdd":null,"IOMaximumBandwidth":0,"IOMaximumIOps":0,"IpcMode":"","Isolation":"","KernelMemory":0,"Links":null,"LogConfig":{"Config":{},"Type":""},"Memory":0,"MemoryReservation":0,"MemorySwap":0,"MemorySwappiness":-1,"NanoCpus":0,"NetworkMode":"host","OomKillDisable":false,"OomScoreAdj":0,"PidMode":"","PidsLimit":0,"PortBindings":{"9000/tcp":[{"HostIp":"","HostPort":"9000"}]},"Privileged":false,"PublishAllPorts":false,"ReadonlyRootfs":false,"RestartPolicy":{"MaximumRetryCount":0,"Name":"no"},"SecurityOpt":null,"ShmSize":0,"UTSMode":"","Ulimits":null,"UsernsMode":"","VolumeDriver":"","VolumesFrom":null},"Hostname":"","Image":"portainer/portainer:linux-arm64","Labels":{},"NetworkingConfig":{"EndpointsConfig":{}},"OnBuild":null,"OpenStdin":false,"StdinOnce":false,"Tty":false,"User":"","Volumes":{},"WorkingDir":""}
DEBU[2019-10-24T21:36:48.080861220+08:00] Creating dest directory: /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953-init
DEBU[2019-10-24T21:36:48.081006898+08:00] Calling TarUntar(/var/lib/docker/vfs/dir/ca576912ecf216d2458a342170e67436400630fb91779f56c8e591d5d03db4d6, /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953-init)
DEBU[2019-10-24T21:36:48.081053058+08:00] TarUntar(/var/lib/docker/vfs/dir/ca576912ecf216d2458a342170e67436400630fb91779f56c8e591d5d03db4d6 /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953-init)
DEBU[2019-10-24T21:36:50.218479838+08:00] Creating dest directory: /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953
DEBU[2019-10-24T21:36:50.218893193+08:00] Calling TarUntar(/var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953-init, /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953)
DEBU[2019-10-24T21:36:50.218981592+08:00] TarUntar(/var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953-init /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953)
DEBU[2019-10-24T21:36:58.273158564+08:00] container mounted via layerStore: /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953
DEBU[2019-10-24T21:36:58.279198411+08:00] Probing all drivers for volume with name: 95007d948dcac2ce59181ee64e31641a80c7db1bfce28b5c9c96bbd9ca7aba41
DEBU[2019-10-24T21:36:58.279602886+08:00] Registering new volume reference: driver "local", name "95007d948dcac2ce59181ee64e31641a80c7db1bfce28b5c9c96bbd9ca7aba41"
DEBU[2019-10-24T21:36:58.369027081+08:00] copying image data from 0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7:/data, to 95007d948dcac2ce59181ee64e31641a80c7db1bfce28b5c9c96bbd9ca7aba41
DEBU[2019-10-24T21:36:58.573514199+08:00] Calling POST /v1.32/containers/0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7/wait?condition=next-exit
0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7
DEBU[2019-10-24T21:36:58.595641210+08:00] Calling POST /v1.32/containers/0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7/start
DEBU[2019-10-24T21:36:58.597708865+08:00] container mounted via layerStore: /var/lib/docker/vfs/dir/786a73f997906bef0885777f0605cbfcd8b829b0bb5fd5ea5fb85de8e92a4953
DEBU[2019-10-24T21:36:58.985018485+08:00] EnableService 0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7 START
DEBU[2019-10-24T21:36:58.985131443+08:00] EnableService 0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7 DONE
WARN[2019-10-24T21:36:59.026778858+08:00] Seccomp is not enabled in your kernel, running container without default profile.
DEBU[2019-10-24T21:36:59.764840380+08:00] libcontainerd: received containerd event: &types.Event{Type:"start-container", Id:"0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7", Status:0x0, Pid:"", Timestamp:(*timestamp.Timestamp)(0x4421b32e50)}
DEBU[2019-10-24T21:37:00.250454966+08:00] libcontainerd: event unhandled: type:"start-container" id:"0287d59a753b7259d025ef6a422ed7f7cc7308a82c4285beaddca7c2798ddee7" timestamp:<seconds:1571924219 nanos:764203828 >

2019-10-24

debu

08:00

null

8 replies • 2019-11-02 14:45:34 +08:00

wanghuangjie

Oct 25, 2019

请问怎么实现的呢。
我把 docker 的储存模式改作了 vfs.
但还是卡在“iptable"这了。
iptables v1.6.0: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)

wanghuangjie

Oct 25, 2019

禁用了 iptable 还有 bridge 以后可以跑了。。。。

huluhulu

Oct 25, 2019 via iPhone

@wanghuangjie 是的，禁用 iptable 和 bridge，起 container 用 host 模式，试了几个跑起来都没问题

abmin521

Oct 26, 2019

为什么要禁用？我用 arm 的板子是可以跑的比如去广告某 DNS

huluhulu

Oct 26, 2019 via iPhone

@abmin521 因为群晖的 linux kernel 把 bridge 没有编译进去…

hanmiao

Oct 27, 2019

是大猫盘还是小猫盘

huluhulu

Nov 1, 2019

@hanmiao 小的那个

hanmiao

Nov 2, 2019

全涨价了 233