Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfpulux <>
Subject: [ISSUE] failed to build podman image
Date: Mon, 14 Mar 2022 11:43:13 +0100	[thread overview]
Message-ID: <> (raw)

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

New issue by pfpulux on void-packages repository

<!-- Don't request update of package. We have a script for that. . However, a quality pull request may help. -->
### System

* xuname:  
  * Void 5.15.28_1 x86_64 AuthenticAMD
* package:  
  *affected package(s) including the version*: ``podman-4.0.2_2``

### Expected behavior
build a new image with name t1:latest

### Actual behavior
$ podman build -t t1 -f C1
STEP 1/2: FROM 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-14T11:37:11+01:00" level=warning msg="unable to get oom kill count" error="no directory specified for memory.oom_control"
time="2022-03-14T11:37:11+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

### Steps to reproduce the behavior
$ cat C1
from voidlinux-musl
RUN xbps-install -Suy ncurses-base bash

             reply	other threads:[~2022-03-14 10:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 10:43 pfpulux [this message]
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
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 \ \ \ \

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