Latest rootless podman always gives: error creating libpod runtime: exit status 125

[refi64]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Latest rootless podman does not work. At all. 😐

Steps to reproduce the issue:

1. Run podman --log-level debug run --rm alpine echo 123.

2. ...

3. Profit?

Describe the results you received:

INFO[0000] running as rootless                          
DEBU[0000] Initializing boltdb state at /var/home/ryan/.local/share/containers/storage/libpod/bolt_state.db 
DEBU[0000] Using graph driver overlay                   
DEBU[0000] Using graph root /var/home/ryan/.local/share/containers/storage 
DEBU[0000] Using run root /run/user/1000                
DEBU[0000] Using static dir /var/home/ryan/.local/share/containers/storage/libpod 
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp      
DEBU[0000] Set libpod namespace to ""                   
DEBU[0000] Not configuring container store              
ERRO[0000] error creating libpod runtime: exit status 125 

Describe the results you expected:

(log messages...)
123
(more log messages...)

Additional information you deem important (e.g. issue happens only occasionally):

Happens with the absolute latest podman from COPR.

Output of podman version:

Version:       1.0.1-dev
Go Version:    go1.11.4
Git Commit:    "877a299f938c906c82bbd10747f65e5ec2dbe9ce"
Built:         Mon Jan 21 08:06:01 2019
OS/Arch:       linux/amd64

Output of podman info:

could not get runtime: failed to mount overlay for metacopy check: operation not permitted

Yes, has failed so badly not even podman info works.

Additional environment details (AWS, VirtualBox, physical, etc.):

On Fedora Silverblue 29. I'm trying to download the Git version to see if I can figure out where this error is coming from.

Here's my storage.conf since podman info is borked:

[storage]
  driver = "overlay"
  runroot = "/run/user/1000"
  graphroot = "/var/home/ryan/.local/share/containers/storage"
  [storage.options]
    mount_program = "/usr/bin/fuse-overlayfs"

[refi64]

So this is actually because podman run calls into podman info, which is where the actual failure comes from.

[refi64]

And looks like this was already fixed, whoops.

[refi64]

Actually, can there be a new vendor directory update to fix this?