Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-3392

All packaging jobs are failing on Fedora 31 for aarch64 and ppc64le

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.5.0
    • None
    • None

    Description

      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.

      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...
      
      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...
      

      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.

      Attachments

        Activity

          People

            sekikn Kengo Seki
            sekikn Kengo Seki
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h
                1h