Kengo Seki created BIGTOP-3392:
----------------------------------

             Summary: All packaging jobs are failing on Fedora 31 for aarch64 
and ppc64le
                 Key: BIGTOP-3392
                 URL: https://issues.apache.org/jira/browse/BIGTOP-3392
             Project: Bigtop
          Issue Type: Bug
            Reporter: Kengo Seki
            Assignee: Kengo Seki


https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/611/

I tried to run docker containers manually in these machines, and found the 
following errors occurred.

{code}
jenkins@bigtop-docker-slave-arm4:~$ docker run -it -d 
bigtop/slaves:trunk-fedora-31-aarch64 /sbin/init
75adb48dbe8be1f98a114554aafe28446613629f02fbce076e7f91597f60cc25
jenkins@bigtop-docker-slave-arm4:~$ docker ps -a | grep 75adb48d
75adb48dbe8b        bigtop/slaves:trunk-fedora-31-aarch64   "/sbin/init"        
3 minutes ago       Exited (255) 3 minutes ago                       
nostalgic_swartz
jenkins@bigtop-docker-slave-arm4:~$ docker logs 
75adb48dbe8be1f98a114554aafe28446613629f02fbce076e7f91597f60cc25
Failed to mount tmpfs at /run: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
{code}

{code}
jenkins@bigtop1slave:~$ docker run -it -d bigtop/slaves:trunk-fedora-31-ppc64le 
/sbin/init
6729703b725c5e23d2ef860c0ab87f5f44d6a680427853517ad27a16f96d6064
jenkins@bigtop1slave:~$ docker ps -a | grep 6729703b
6729703b725c        bigtop/slaves:trunk-fedora-31-ppc64le      "/sbin/init"     
        24 seconds ago      Exited (255) 16 seconds ago                       
compassionate_morse
jenkins@bigtop1slave:~$ docker logs 
6729703b725c5e23d2ef860c0ab87f5f44d6a680427853517ad27a16f96d6064
Failed to mount tmpfs at /run: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
{code}

Though I'm not sure the root cause of this for now (docker version problem, 
something wrong in building image, or something else?), but as a workaround, 
specifying the {{\--privileged}} option (or {{\--cap-add SYS_ADMIN -v 
/sys/fs/cgroup:/sys/fs/cgroup:ro}} for stricter permission) when running 
container seems to resolve this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to