RZ/Five docker issue

Consider that VLP3.0.3 does not officially support rz/five yet, even if it is available from github, so some features may not fully work. Anyway:

systemctl start docker

Then wait, it takes a while. Then:

docker run hello-world

Hi MicBis,

it is still showing an error message,p_age.lease check the below error message in the attached image.

Thanks & Regards

Mahesh R

Then you did not build it correctly.

Hi MicBis,

but docker support have been enabled, let me know to test docker have been built properly or not.

Thanks & reagrds

Mahesh R

systemctl status docker.service

uname -a

Anyway if you follow carefully the build instructions it will work.

root@smarc-rzfive:~# docker run hello-world
[ 147.504256] IPv6: ADDRCONF(NETDEV_CHANGE): veth8ff7dc2: link becomes ready
[ 147.515872] IPv6: ADDRCONF(NETDEV_CHANGE): vethd59ae2c: link becomes ready
[ 147.576665] docker0: port 1(veth8ff7dc2) entered blocking state
[ 147.598815] docker0: port 1(veth8ff7dc2) entered disabled state
[ 147.612614] device veth8ff7dc2 entered promiscuous mode
[ 147.626568] kauditd_printk_skb: 29 callbacks suppressed
[ 147.626575] audit: type=1700 audit(1683221050.491:44): dev=veth8ff7dc2 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[ 147.648232] docker0: port 1(veth8ff7dc2) entered blocking state
[ 147.654254] docker0: port 1(veth8ff7dc2) entered forwarding state
[ 147.698097] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[ 149.275791] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[ 150.384996] docker0: port 1(veth8ff7dc2) entered disabled state
[ 150.412271] eth0: renamed from vethd59ae2c
[ 150.435560] docker0: port 1(veth8ff7dc2) entered blocking state
[ 150.441587] docker0: port 1(veth8ff7dc2) entered forwarding state

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(riscv64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
docs.docker.com/.../

Hi MicBis,

I have tried rebuilding the docker once again, but still getting the same issue, please find the below attached image for reference.

Thanks & Regards

Mahesh R

root@smarc-rzfive:~# dockerd
INFO[2023-05-05T12:04:19.626262483Z] Starting up
INFO[2023-05-05T12:04:19.637005067Z] parsed scheme: "unix" module=grpc
INFO[2023-05-05T12:04:19.637280233Z] scheme "unix" not registered, fallback to default scheme module=grpc
INFO[2023-05-05T12:04:19.637549317Z] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2023-05-05T12:04:19.637697317Z] ClientConn switching balancer to "pick_first" module=grpc
INFO[2023-05-05T12:04:19.659616233Z] parsed scheme: "unix" module=grpc
INFO[2023-05-05T12:04:19.659841150Z] scheme "unix" not registered, fallback to default scheme module=grpc
INFO[2023-05-05T12:04:19.660059067Z] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2023-05-05T12:04:19.660203567Z] ClientConn switching balancer to "pick_first" module=grpc
INFO[2023-05-05T12:04:19.931526483Z] [graphdriver] using prior storage driver: overlay2
WARN[2023-05-05T12:04:19.971334400Z] Your kernel does not support cgroup blkio weight
WARN[2023-05-05T12:04:19.971699650Z] Your kernel does not support cgroup blkio weight_device
INFO[2023-05-05T12:04:19.975056733Z] Loading containers: start.
[ 76.204822] kauditd_printk_skb: 29 callbacks suppressed
[ 76.204832] audit: type=1325 audit(1683288260.335:44): table=nat family=2 entries=11 op=xt_replace pid=376 comm="iptables"
[ 76.234825] audit: type=1325 audit(1683288260.363:45): table=nat family=2 entries=10 op=xt_replace pid=377 comm="iptables"
[ 76.283912] audit: type=1325 audit(1683288260.415:46): table=nat family=2 entries=9 op=xt_replace pid=381 comm="iptables"
[ 76.303638] audit: type=1325 audit(1683288260.435:47): table=nat family=2 entries=8 op=xt_replace pid=382 comm="iptables"
[ 76.325123] audit: type=1325 audit(1683288260.455:48): table=filter family=2 entries=23 op=xt_replace pid=383 comm="iptables"
[ 76.355129] audit: type=1325 audit(1683288260.483:49): table=filter family=2 entries=23 op=xt_replace pid=385 comm="iptables"
[ 76.385389] audit: type=1325 audit(1683288260.515:50): table=filter family=2 entries=21 op=xt_replace pid=387 comm="iptables"
[ 76.405465] audit: type=1325 audit(1683288260.535:51): table=filter family=2 entries=19 op=xt_replace pid=388 comm="iptables"
[ 76.452144] audit: type=1325 audit(1683288260.583:52): table=nat family=2 entries=6 op=xt_replace pid=392 comm="iptables"
[ 76.498243] audit: type=1325 audit(1683288260.627:53): table=filter family=2 entries=17 op=xt_replace pid=396 comm="iptables"
INFO[2023-05-05T12:04:21.175241400Z] 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[2023-05-05T12:04:21.565031900Z] Loading containers: done.
INFO[2023-05-05T12:04:21.861740733Z] Docker daemon commit=3949ff121e-unsupported graphdriver(s)=overlay2 version=20.10.17-ce
INFO[2023-05-05T12:04:21.862879400Z] Daemon has completed initialization
INFO[2023-05-05T12:04:22.046054649Z] API listen on /var/run/docker.sock

I'm afraid that if the problem is not reproducible, it would be difficult to help.

Hi MicBis,

What is missing in my build, is there an specific document to follow and build docker, please let me know

Thanks & Regards

Mahesh R

As already mentioned VLP3.0.3 is not an official release for RZ/Five.

I don't know what's missing in your build, however simply following the instructions that can be found on meta-renesas github you should be able to get it working. There's no secret recipe.

Hi Chris and MicBis.

We are using RZ/Five VLP3.0.4 to get the docker feature, but still we are facing the same issue as in VLP3.0.3.

we have faced some error while applying the docker patch.

please find the below screen shot of docker not starting error for reference.

Please help us ASAP.

Thanks & Regards

Mahesh R

Hello Mahesh,

I tried to recreate the issue but in my case, the patch is being applied without any issues as you can see below:

Dear sachin,

Thanks for the response, in my came i am not sure why the patch is not applying.

Thanks & Regards

Mahesh R

Hi sachin,

did you get docker working in RZ/Five using bsp 3.0.4.

Thanks & Regards

Mahesh R

Honestly docker support is one of the main changes of the 3.0.4 version:

It is not very likely that it is broken.

What you can try is the prebuilt image.