Bug#947007: buildah bud causes errors with Dockerfile
Dear Dmitry, Thank you for your response. I also noticed the lack of /etc/container/storage.conf. Its absense did not cause any error, but storage.conf is mentioned at the bottom of the buildah man page as https://github.com/containers/buildah/blob/master/docs/buildah.md#files So inclusion of storage.conf at /usr/share/doc/buildah/examples or /etc/containers might be suitable. storage.conf(5) is mentioned in https://github.com/containers/buildah/blob/master/docs/buildah.md but I didn't find storage.conf(5) in the Debian package. Best regards, Ryutaroh From: Dmitry Smirnov Subject: Re: Bug#947007: buildah bud causes errors with Dockerfile Date: Thu, 19 Dec 2019 23:58:46 +1100 > Yes, thanks. Most of those issues are already fixed in the repository > and pending upload. > > > On Thursday, 19 December 2019 11:06:05 PM AEDT Ryutaroh Matsumoto wrote: >> The reason of buildah bud giving errors are three-fold: >> >> (1) Lack of /etc/containers/registries.conf >> I copied /usr/share/doc/buildah/examples/registries.conf in the >> buildah Debian package. > > That's how it is expected to be used. > > Not everybody need Docker registries and having them by default > may not be a good idea... > > Also this configuration file is shared with Podman which adds > to complexity... > > >> (2) Lack of /etc/containers/policy.json >> I copied policy.json from the golang-github-containers-image-dev >> Debian package. > > https://salsa.debian.org/go-team/packages/golang-github-containers-buildah/commit/911ac680 > > >> (3) Lack of runc or crun >> I manually installed crun and executed buildah --runtime /usr/bin/cron >> The runc or crun package should be suggested/recommended by the >> buildah Debian package. > > https://salsa.debian.org/go-team/packages/golang-github-containers-buildah/commit/9b802644 > > Certainly fixes for 2 and 3 will be uploaded soon. > Not sure about 1 as I'm still thinking about how to resolve it elegantly > and what would be reasonable default. > > -- > Cheers, > Dmitry Smirnov. > > --- > > Freedom is the freedom to say that two plus two make four. If that is > granted, all else follows. > -- George Orwell
Bug#947007: buildah bud causes errors with Dockerfile
Yes, thanks. Most of those issues are already fixed in the repository and pending upload. On Thursday, 19 December 2019 11:06:05 PM AEDT Ryutaroh Matsumoto wrote: > The reason of buildah bud giving errors are three-fold: > > (1) Lack of /etc/containers/registries.conf > I copied /usr/share/doc/buildah/examples/registries.conf in the > buildah Debian package. That's how it is expected to be used. Not everybody need Docker registries and having them by default may not be a good idea... Also this configuration file is shared with Podman which adds to complexity... > (2) Lack of /etc/containers/policy.json > I copied policy.json from the golang-github-containers-image-dev > Debian package. https://salsa.debian.org/go-team/packages/golang-github-containers-buildah/commit/911ac680 > (3) Lack of runc or crun > I manually installed crun and executed buildah --runtime /usr/bin/cron > The runc or crun package should be suggested/recommended by the > buildah Debian package. https://salsa.debian.org/go-team/packages/golang-github-containers-buildah/commit/9b802644 Certainly fixes for 2 and 3 will be uploaded soon. Not sure about 1 as I'm still thinking about how to resolve it elegantly and what would be reasonable default. -- Cheers, Dmitry Smirnov. --- Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- George Orwell signature.asc Description: This is a digitally signed message part.
Bug#947007: buildah bud causes errors with Dockerfile
Package: buildah Version: 1.10.1-5 Severity: normal Dear Maintainer, buildah bud does not work on a Dockerfile starting with FROM alpine:3.10 I tried to create an image by https://github.com/y-yu/new-year-letter/blob/master/docker/Dockerfile The reason of buildah bud giving errors are three-fold: (1) Lack of /etc/containers/registries.conf I copied /usr/share/doc/buildah/examples/registries.conf in the buildah Debian package. (2) Lack of /etc/containers/policy.json I copied policy.json from the golang-github-containers-image-dev Debian package. (3) Lack of runc or crun I manually installed crun and executed buildah --runtime /usr/bin/cron The runc or crun package should be suggested/recommended by the buildah Debian package. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages buildah depends on: ii libc6 2.29-3 ii libdevmapper1.02.1 2:1.02.155-3 ii libglib2.0-02.62.3-2 ii libgpgme11 1.13.1-1 ii libostree-1-1 2019.6-1 ii libseccomp2 2.4.2-2 ii libselinux1 3.0-1 ii uidmap 1:4.7-2 Versions of packages buildah recommends: ii fuse-overlayfs 0.7.2-1 buildah suggests no packages. -- no debconf information
