Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfpulux <>
Subject: Re: failed to build podman image
Date: Tue, 15 Mar 2022 11:15:41 +0100	[thread overview]
Message-ID: <20220315101541.YuuSzMzjQvee0KRO0ljLA8xeFbJYv7FYfMovzZ7Zfr8@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2748 bytes --]

New comment by pfpulux on void-packages repository

I also test on an other machine (glibc, no efi, Intel) with hits the issue.

$ podman build -t t1 -f C1
STEP 1/2: FROM voidlinux/voidlinux-musl
STEP 2/2: RUN xbps-install -Suy ncurses-base bash
error running container: error from /usr/bin/runc creating container for [/bin/sh -c xbps-install -Suy ncurses-base bash]: time="2022-03-15T11:12:38+01:00" level=warning msg="unable to get oom kill count" error="no directory specified for memory.oom_control"
time="2022-03-15T11:12:38+01:00" level=error msg="runc create failed: unable to start container process: error during container init: error mounting \"cgroup\" to rootfs at \"/sys/fs/cgroup\": mount /proc/self/fd/8:/sys/fs/cgroup/cpuset (via /proc/self/fd/9), flags: 0x20502f: operation not permitted"
: exit status 1
ERRO[0005] did not get container create message from subprocess: read |0: i/o timeout
Error: error building at STEP "RUN xbps-install -Suy ncurses-base bash": error while running runtime: exit status 1

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,size=16366884k,nr_inodes=4091721,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,inode64)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,mode=755,inode64)
/dev/nvme0n1p2 on / type ext4 (rw,noatime)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755,inode64)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,relatime,nsdelegate)
/dev/nvme0n1p1 on /boot type ext4 (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,inode64)

  parent reply	other threads:[~2022-03-15 10:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 10:43 [ISSUE] " pfpulux
2022-03-14 22:00 ` CameronNemo
2022-03-15  9:51 ` pfpulux
2022-03-15 10:08 ` pfpulux
2022-03-15 10:08 ` pfpulux
2022-03-15 10:15 ` pfpulux [this message]
2022-04-12 23:41 ` gbrlsnchs
2022-05-11 15:43 ` CameronNemo
2022-08-10  2:09 ` github-actions
2022-08-24  2:15 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220315101541.YuuSzMzjQvee0KRO0ljLA8xeFbJYv7FYfMovzZ7Zfr8@z \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).