podman: Bug: Errors when using rootless containers

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

/kind bug

Description

Hi,

when running rootless containers, I am getting some errors:

podman run -dt -p 8080:80 docker.io/library/httpd:2.4
ERRO[0000] unable to write pod event: "open : no such file or directory" 
ERRO[0000] unable to write pod event: "open : no such file or directory" 
ERRO[0000] unable to write pod event: "open : no such file or directory"

These kind of errors occur for several subcommands like: run, stop, start, restart Other subcommands like “ps” seem not to be affected. Disabling SELinux does not help to prevent the errors.

information

OS: Fedora 32 Silverblue Podman: 1.9.1

If you need any additional information, please feel free to reach out to me.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 16 (10 by maintainers)

Most upvoted comments

I think we need this fixed for v2.0, to make sure that upgrades from older Podmans do not blow up.

mheon on Jun 2, 2020

If you did not modify libpod.conf, it is probably best to remove the file.

rhatdan on May 6, 2020

And podman will create an empty “.lock” file in $PWD.

junjieyuan on May 9, 2020

I know we’re now ignoring events_logger which is probably why we’re forcing file…

@daniel-wtd Can you remove the events_logfile_path = "" line and see if the errors go away? I suspect we’re going to have to ignore that setting as well if it’s explicitly set to ""

mheon on May 5, 2020