Hi, has anyone successfully run docker on Rock3a?

Hi, has anyone successfully run docker on Rock3a?
When I install docker on rock3a, it says that installation is not successful, because cgroup, and some other features that I don’t remember are not supported. I am using official OS whose kernel version is 4.19.
Is this because the kernel is too old, or because the rock-chip’s modification to the kernel is too buggy?
Thanks for replying.

I’ve fixed this issue by this pull request: https://github.com/radxa/kernel/pull/11, which has got merged on 21 March. You should check your kernel build date by command uname -a

why not???,maybe you need new Linux OS

Hi, my uname -a output is:

Linux rock-3a 4.19.193-51-rockchip-gb2c01b3d79f2 #rockchip SMP Tue Jul 19 14:07:
56 UTC 2022 aarch64 GNU/Linux

It is build after Mar.21.

But when I install docker.io, it still shows error:

Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693041631+08:00" level=warning msg="Your kernel does not support cgroup rt period"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693251051+08:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693322511+08:00" level=warning msg="Your kernel does not support cgroup blkio weight"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693375887+08:00" level=warning msg="Your kernel does not support cgroup blkio weight_device"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693431013+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.read_bps_device"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693485264+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.write_bps_device"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693539223+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.read_iops_device"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.693735518+08:00" level=warning msg="Your kernel does not support cgroup blkio throttle.write_iops_device"
Aug 29 23:33:12 rock-3a dockerd[2113]: time="2022-08-29T23:33:12.696203938+08:00" level=info msg="Loading containers: start."
Aug 29 23:33:13 rock-3a dockerd[2113]: time="2022-08-29T23:33:13.449530896+08:00" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
Aug 29 23:33:13 rock-3a dockerd[2113]: time="2022-08-29T23:33:13.451569974+08:00" level=info msg="stopping healthcheck following graceful shutdown" module=libcontainerd
Aug 29 23:33:13 rock-3a dockerd[2113]: time="2022-08-29T23:33:13.451765394+08:00" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugins.moby
Aug 29 23:33:13 rock-3a dockerd[2113]: time="2022-08-29T23:33:13.457505789+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x40007f4120, TRANSIENT_FAILURE" module=grpc
Aug 29 23:33:13 rock-3a dockerd[2113]: time="2022-08-29T23:33:13.458252469+08:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x40007f4120, CONNECTING" module=grpc
dpkg: error processing package docker.io (--configure):
 installed docker.io package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)

It says that my kernel does not support balabala features.
Where does the problem lie?
[/quote]

These kernel related logs are just warnings. But there is no useful info to locate the real root cause. Your kernel should be ok.

Finally I have found where the reason lies: docker uses iptables, but it can’t be compatible with iptables-nft, and it is only compatible with iptables-legacy.

所以,兄弟,你解决了这个问题了没有,我入手了SBC,同样发现这个问题了

can you help me

Purge docker

update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

run docker install again and that bit should be solved but may still be missing some cgroups