Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691397 - Buildah creates storage.conf with old format podman can't read
Summary: Buildah creates storage.conf with old format podman can't read
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: buildah
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Frantisek Kluknavsky
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-21 14:20 UTC by Matt Micene
Modified: 2019-03-21 14:20 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Matt Micene 2019-03-21 14:20:15 UTC
Description of problem:

In RC1, running as a non-root user, buildah creates ~/.config/container/storage.conf using the older CamelCase 
format causing podman to fail with "ERRO[0000] 'overlay' is not supported over xfs" if buildah is run first on a clean install.

Version-Release number of selected component (if applicable):

buildah-1.5-3.gite94b4f9.module+el8+2769+577ad176.x86_64
podman-1.0.0-2.git921f98f.module+el8+2785+ff8a053f.x86_64


How reproducible:

Every time

Steps to Reproduce:
1. Install podman and buildah
2. Pull a container using buildah as a non-root user (must be run before any podman commands are run)
3. Run 'podman ps' - get overlay not supported error

Actual results:
[cloud-user@8beta3 ~]$ sudo yum install podman buildah
Complete!

[cloud-user@8beta3 ~]$ cat .config/containers/storage
cat: .config/containers/storage: No such file or directory

[cloud-user@8beta3 ~]$ buildah pull registry.access.redhat.com/rhel7
Getting image source signatures
Copying blob sha256:da59b306fcf51d4fe2f11ef4660a9b72a48788d81a3685c57687ab8e22295229
 72.31 MiB / ? [-----------------------=-----------------------------------] 7s 
Copying blob sha256:e23b0afac3fa3bc3736efa2a2f7b05f810ecc499278d804c4d531b1ec52842b2
 1.23 KiB / ? [-----------------=------------------------------------------] 0s 
Copying config sha256:b8fffd14574a044315ebd7afb12cedde603bcf1e03f97b08e8a30d7a462f3144
 6.31 KiB / 6.31 KiB [======================================================] 0s
Writing manifest to image destination
Storing signatures
b8fffd14574a044315ebd7afb12cedde603bcf1e03f97b08e8a30d7a462f3144

[cloud-user@8beta3 ~]$ cat .config/containers/storage.conf 
RunRoot = "/run/user/1000"
GraphRoot = "/home/cloud-user/.local/share/containers/storage"
GraphDriverName = "overlay"
GraphDriverOptions = ["overlay.mount_program=/usr/bin/fuse-overlayfs"]

[cloud-user@8beta3 ~]$ podman ps
ERRO[0000] 'overlay' is not supported over xfs at "/home/cloud-user/.local/share/containers/storage/overlay" 
ERRO[0000] [graphdriver] prior storage driver overlay failed: kernel does not support overlay fs: 'overlay' is not supported over xfs at "/home/cloud-user/.local/share/containers/storage/overlay": backing file system is unsupported for this graph driver 
error creating libpod runtime: kernel does not support overlay fs: 'overlay' is not supported over xfs at "/home/cloud-user/.local/share/containers/storage/overlay": backing file system is unsupported for this graph driver


Expected results:
[cloud-user@8beta3 ~]$ cat .config/containers/storage.conf 
[storage]
  driver = "overlay"
  runroot = "/run/user/1000"
  graphroot = "/home/cloud-user/.local/share/containers/storage"
  [storage.options]
    mount_program = "/usr/bin/fuse-overlayfs"

[cloud-user@8beta3 ~]$ podman ps
CONTAINER ID  IMAGE  COMMAND  CREATED  STATUS  PORTS  NAMES

Additional info:

If podman creates the file by pulling a container first, the newer format is created and both tools will successfully use storage.  This can also be corrected by removing the local storage.conf, and running a podman command as a non-root user to create in the new format.  Not sure if this has side effects.

This appears to be somewhat related to https://github.com/containers/buildah/issues/1286 upstream, and is likely fixed in a later version of buildah.


Note You need to log in before you can comment on or make changes to this bug.