containers / buildah

A tool that facilitates building OCI images.
https://buildah.io
Apache License 2.0
7.28k stars 769 forks source link

cannot run `apt-get update` while running `buildah bud` inside a container #3790

Closed Masber closed 2 years ago

Masber commented 2 years ago

Description we are trying to build a container image inside a container using buildah. The build process starts but then fails when we try to run apt-get update

error:

error running container: error from crun creating container for [/bin/sh -c apt-get update   && env DEBIAN_FRONTEND=noninteractive TZ=Europe/Zurich   apt-get -yqq install --no-install-recommends     build-essential     ca-certificates     curl     file     g++     gcc     gfortran     git     gnupg2     iproute2     lmod     locales     lua-posix     make     patch     python3     python3-pip     python3-setuptools     tcl     unzip     vim     less   && locale-gen en_US.UTF-8   && rm -Rf /var/lib/apt/lists/*]: creating cgroup directory `/sys/fs/cgroup/memory/buildah-buildah1277165473`: No such file or directory

Steps to reproduce the issue:

  1. Install buildah in container image

    • apk add buildah
    • mkdir -p $HOME/.config/containers
    • echo "unqualified-search-registries = ['docker.io']" > $HOME/.config/containers/registries.conf
    • mount
    • id
    • env
    • buildah bud -f Dockerfile --format docker -t $IMAGE_NAME
    • buildah login -u $CSCS_REGISTRY_USER -p $CSCS_REGISTRY_PASSWORD $CSCS_REGISTRY
    • buildah push $IMAGE_NAME
  2. Docker file FROM ubuntu:20.04

ARG SPACK_VER=0.17.0 ENV SPACK_ROOT=/opt/spack

This list corresponds mostly to the list from the spack dockerfile (share/spack/docker/ubuntu-1804.dockerfile)

RUN apt-get update \ && env DEBIAN_FRONTEND=noninteractive TZ=Europe/Zurich \ apt-get -yqq install --no-install-recommends \ build-essential \ ca-certificates \ curl \ file \ g++ \ gcc \ gfortran \ git \ gnupg2 \ iproute2 \ lmod \ locales \ lua-posix \ make \ patch \ python3 \ python3-pip \ python3-setuptools \ tcl \ unzip \ vim \ less \ && locale-gen en_US.UTF-8 \ && rm -Rf /var/lib/apt/lists/*

RUN mkdir -p $SPACK_ROOT \ && git clone -b v${SPACK_VER} https://github.com/spack/spack $SPACK_ROOT \ && ln -s $SPACK_ROOT/share/spack/docker/entrypoint.bash /usr/local/bin/docker-shell \ && ln -s $SPACK_ROOT/share/spack/docker/entrypoint.bash /usr/local/bin/interactive-shell \ && ln -s $SPACK_ROOT/share/spack/docker/entrypoint.bash /usr/local/bin/spack-env

ENV LANGUAGE en_US.UTF-8 ENV LANG en_US.UTF-8 ENV LC_ALL en_US.UTF-8

RUN mkdir -p /root/.spack \ && cp $SPACK_ROOT/share/spack/docker/modules.yaml /root/.spack/modules.yaml \ && rm -rf /root/. /run/nologin $SPACK_ROOT/.git

WORKDIR /root SHELL ["docker-shell"]

RUN spack spec hdf5+mpi ENTRYPOINT ["/bin/bash", "/opt/spack/share/spack/docker/entrypoint.bash"] CMD ["interactive-shell"]

Describe the results you received:

$ buildah bud --storage-driver=vfs -f Dockerfile --format docker -t $IMAGE_NAME
STEP 1/15: FROM ubuntu:20.04
Resolving "ubuntu" using unqualified-search registries (/root/.config/containers/registries.conf)
Trying to pull docker.io/library/ubuntu:20.04...
Getting image source signatures
Copying blob sha256:08c01a0ec47e82ebe2bec112f373d160983a6d1e9e66627f66a3322bc403221b
Copying blob sha256:08c01a0ec47e82ebe2bec112f373d160983a6d1e9e66627f66a3322bc403221b
Copying config sha256:54c9d81cbb440897908abdcaa98674db83444636c300170cfd211e40a66f704f
Writing manifest to image destination
Storing signatures
STEP 2/15: MAINTAINER Andreas Fink <andreas.fink@cscs.ch>
STEP 3/15: ARG SPACK_VER=0.17.0
STEP 4/15: ENV SPACK_ROOT=/opt/spack
STEP 5/15: RUN apt-get update   && env DEBIAN_FRONTEND=noninteractive TZ=Europe/Zurich   apt-get -yqq install --no-install-recommends     build-essential     ca-certificates     curl     file     g++     gcc     gfortran     git     gnupg2     iproute2     lmod     locales     lua-posix     make     patch     python3     python3-pip     python3-setuptools     tcl     unzip     vim     less   && locale-gen en_US.UTF-8   && rm -Rf /var/lib/apt/lists/*
error running container: error from crun creating container for [/bin/sh -c apt-get update   && env DEBIAN_FRONTEND=noninteractive TZ=Europe/Zurich   apt-get -yqq install --no-install-recommends     build-essential     ca-certificates     curl     file     g++     gcc     gfortran     git     gnupg2     iproute2     lmod     locales     lua-posix     make     patch     python3     python3-pip     python3-setuptools     tcl     unzip     vim     less   && locale-gen en_US.UTF-8   && rm -Rf /var/lib/apt/lists/*]: creating cgroup directory `/sys/fs/cgroup/memory/buildah-buildah1277165473`: No such file or directory

Describe the results you expected:

I would expect buildah bud to create the container image successfully

Output of rpm -q buildah or apt list buildah:

$ apk list buildah
buildah-1.23.2-r0 x86_64 {buildah} (Apache-2.0) [installed]

Output of buildah version:

$ buildah version
Version:         1.23.2
Go Version:      go1.17.4
Image Spec:      1.0.1-dev
Runtime Spec:    1.0.2-dev
CNI Spec:        0.4.0
libcni Version:  v0.8.1
image Version:   5.16.0
Git Commit:      1.23.2
Built:           Tue Jan 25 22:12:24 2022
OS/Arch:         linux/amd64
BuildPlatform:   linux/amd64

Output of podman version if reporting a podman build issue:

(paste your output here)

*Output of `cat /etc/release`:**

$ cat /etc/*release
3.15.0
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.15.0
PRETTY_NAME="Alpine Linux v3.15"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

Output of uname -a:

$ uname -a
Linux runner-9q2boogi-project-1213-concurrent-0grfv9 5.3.18-24.75_10.0.189-cray_shasta_c #1 SMP Sun Sep 26 14:27:04 UTC 2021 (0388af5) x86_64 Linux

Output of cat /etc/containers/storage.conf:

$ cat /etc/containers/storage.conf
# This file is is the configuration file for all tools
# that use the containers/storage library.
# See man 5 containers-storage.conf for more information
# The "container storage" table contains all of the server options.
[storage]
# Default Storage Driver, Must be set for proper operation.
driver = "overlay"
# Temporary storage location
runroot = "/run/containers/storage"
# Primary Read/Write location of container storage
graphroot = "/var/lib/containers/storage"
# Storage path for rootless users
#
# rootless_storage_path = "$HOME/.local/share/containers/storage"
[storage.options]
# Storage options to be passed to underlying storage drivers
# AdditionalImageStores is used to pass paths to additional Read/Only image stores
# Must be comma separated list.
additionalimagestores = [
]
# Remap-UIDs/GIDs is the mapping from UIDs/GIDs as they should appear inside of
# a container, to the UIDs/GIDs as they should appear outside of the container,
# and the length of the range of UIDs/GIDs.  Additional mapped sets can be
# listed and will be heeded by libraries, but there are limits to the number of
# mappings which the kernel will allow when you later attempt to run a
# container.
#
# remap-uids = 0:1668442479:65536
# remap-gids = 0:1668442479:65536
# Remap-User/Group is a user name which can be used to look up one or more UID/GID
# ranges in the /etc/subuid or /etc/subgid file.  Mappings are set up starting
# with an in-container ID of 0 and then a host-level ID taken from the lowest
# range that matches the specified name, and using the length of that range.
# Additional ranges are then assigned, using the ranges which specify the
# lowest host-level IDs first, to the lowest not-yet-mapped in-container ID,
# until all of the entries have been used for maps.
#
# remap-user = "containers"
# remap-group = "containers"
# Root-auto-userns-user is a user name which can be used to look up one or more UID/GID
# ranges in the /etc/subuid and /etc/subgid file.  These ranges will be partitioned
# to containers configured to create automatically a user namespace.  Containers
# configured to automatically create a user namespace can still overlap with containers
# having an explicit mapping set.
# This setting is ignored when running as rootless.
# root-auto-userns-user = "storage"
#
# Auto-userns-min-size is the minimum size for a user namespace created automatically.
# auto-userns-min-size=1024
#
# Auto-userns-max-size is the minimum size for a user namespace created automatically.
# auto-userns-max-size=65536
[storage.options.overlay]
# ignore_chown_errors can be set to allow a non privileged user running with
# a single UID within a user namespace to run containers. The user can pull
# and use any image even those with multiple uids.  Note multiple UIDs will be
# squashed down to the default uid in the container.  These images will have no
# separation between the users in the container. Only supported for the overlay
# and vfs drivers.
#ignore_chown_errors = "false"
# Inodes is used to set a maximum inodes of the container image.
# inodes = ""
# Path to an helper program to use for mounting the file system instead of mounting it
# directly.
#mount_program = "/usr/bin/fuse-overlayfs"
# mountopt specifies comma separated list of extra mount options
mountopt = "nodev"
# Set to skip a PRIVATE bind mount on the storage home directory.
# skip_mount_home = "false"
# Size is used to set a maximum size of the container image.
# size = ""
# ForceMask specifies the permissions mask that is used for new files and
# directories.
#
# The values "shared" and "private" are accepted.
# Octal permission masks are also accepted.
#
#  "": No value specified.
#     All files/directories, get set with the permissions identified within the
#     image.
#  "private": it is equivalent to 0700.
#     All files/directories get set with 0700 permissions.  The owner has rwx
#     access to the files. No other users on the system can access the files.
#     This setting could be used with networked based homedirs.
#  "shared": it is equivalent to 0755.
#     The owner has rwx access to the files and everyone else can read, access
#     and execute them. This setting is useful for sharing containers storage
#     with other users.  For instance have a storage owned by root but shared
#     to rootless users as an additional store.
#     NOTE:  All files within the image are made readable and executable by any
#     user on the system. Even /etc/shadow within your image is now readable by
#     any user.
#
#   OCTAL: Users can experiment with other OCTAL Permissions.
#
#  Note: The force_mask Flag is an experimental feature, it could change in the
#  future.  When "force_mask" is set the original permission mask is stored in
#  the "user.containers.override_stat" xattr and the "mount_program" option must
#  be specified. Mount programs like "/usr/bin/fuse-overlayfs" present the
#  extended attribute permissions to processes within containers rather then the
#  "force_mask"  permissions.
#
# force_mask = ""
[storage.options.thinpool]
# Storage Options for thinpool
# autoextend_percent determines the amount by which pool needs to be
# grown. This is specified in terms of % of pool size. So a value of 20 means
# that when threshold is hit, pool will be grown by 20% of existing
# pool size.
# autoextend_percent = "20"
# autoextend_threshold determines the pool extension threshold in terms
# of percentage of pool size. For example, if threshold is 60, that means when
# pool is 60% full, threshold has been hit.
# autoextend_threshold = "80"
# basesize specifies the size to use when creating the base device, which
# limits the size of images and containers.
# basesize = "10G"
# blocksize specifies a custom blocksize to use for the thin pool.
# blocksize="64k"
# directlvm_device specifies a custom block storage device to use for the
# thin pool. Required if you setup devicemapper.
# directlvm_device = ""
# directlvm_device_force wipes device even if device already has a filesystem.
# directlvm_device_force = "True"
# fs specifies the filesystem type to use for the base device.
# fs="xfs"
# log_level sets the log level of devicemapper.
# 0: LogLevelSuppress 0 (Default)
# 2: LogLevelFatal
# 3: LogLevelErr
# 4: LogLevelWarn
# 5: LogLevelNotice
# 6: LogLevelInfo
# 7: LogLevelDebug
# log_level = "7"
# min_free_space specifies the min free space percent in a thin pool require for
# new device creation to succeed. Valid values are from 0% - 99%.
# Value 0% disables
# min_free_space = "10%"
# mkfsarg specifies extra mkfs arguments to be used when creating the base
# device.
# mkfsarg = ""
# metadata_size is used to set the `pvcreate --metadatasize` options when
# creating thin devices. Default is 128k
# metadata_size = ""
# Size is used to set a maximum size of the container image.
# size = ""
# use_deferred_removal marks devicemapper block device for deferred removal.
# If the thinpool is in use when the driver attempts to remove it, the driver
# tells the kernel to remove it as soon as possible. Note this does not free
# up the disk space, use deferred deletion to fully remove the thinpool.
# use_deferred_removal = "True"
# use_deferred_deletion marks thinpool device for deferred deletion.
# If the device is busy when the driver attempts to delete it, the driver
# will attempt to delete device every 30 seconds until successful.
# If the program using the driver exits, the driver will continue attempting
# to cleanup the next time the driver is used. Deferred deletion permanently
# deletes the device and all data stored in device will be lost.
# use_deferred_deletion = "True"
# xfs_nospace_max_retries specifies the maximum number of retries XFS should
# attempt to complete IO when ENOSPC (no space) error is returned by
# underlying storage device.
# xfs_nospace_max_retries = "0"
TomSweeneyRedHat commented 2 years ago

@Masber this smells like a crun issue in Ubuntu. I think 20.04 has crun included, but I'm not sure if it's the default. I don't have a way to check quickly, can you?

Masber commented 2 years ago

sorry, need to clarify this. So by crun, do you mean this https://github.com/containers/crun?

nalind commented 2 years ago

What sort of host is it? If it's using cgroups v1, and the container isn't privileged, it's not going to be able to create its own control groups. Try setting BUILDAH_ISOLATION=chroot or running it with --isolation chroot to have buildah use something that's more like chroot for handling RUN instructions, instead of attempting to run a proper container inside the container.

github-actions[bot] commented 2 years ago

A friendly reminder that this issue had no activity for 30 days.

rhatdan commented 2 years ago

Since we received no further feedback, I am going to close, reopen if you have more feedback.