Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

confusing debug message about lipod.conf #6378

Closed
FlorianLudwig opened this issue May 25, 2020 · 6 comments
Closed

confusing debug message about lipod.conf #6378

FlorianLudwig opened this issue May 25, 2020 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@FlorianLudwig
Copy link

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

/kind bug

Description

# podman  --log-level=debug 
DEBU[0000] Ignoring lipod.conf EventsLogger setting "journald". Use containers.conf if you want to change this setting and remove libpod.conf files. 

I cannot find any lipod.conf nor libpod.conf on my system. It is not obvious which configs podman is making use of.

Describe the results you received:

Describe the results you expected:

Show full path of all loaded configs when running with --log-level=debug

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

Output of podman version:

podman version
Version:            1.9.2
RemoteAPI Version:  1
Go Version:         go1.13.10
OS/Arch:            linux/amd64
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label May 25, 2020
@mheon
Copy link
Member

mheon commented May 25, 2020

We'd be looking at:

  • /etc/containers/libpod.conf
  • /usr/share/containers/libpod.conf

Can you confirm neither of these exists? If so, this definitely sounds like a bug...

@FlorianLudwig
Copy link
Author

@mheon /usr/share/containers/libpod.conf does exist. Sorry, I just checked in ~ and /etc.

While lipod.conf still does have a typo it would be great to not fix the typo bug instead having the absolute path in the log would be quite helpful.

@mheon
Copy link
Member

mheon commented May 25, 2020

I didn't even notice the typo when you originally posted - oops. I agree that printing full paths would be nice here, definitely.

@boaz0
Copy link
Collaborator

boaz0 commented May 26, 2020

@mheon can you assign it to me please 🙏
thanks

@rhatdan
Copy link
Member

rhatdan commented May 26, 2020

@boaz0 I already opened it in containers/common.

containers/common#164

@mheon
Copy link
Member

mheon commented Jun 2, 2020

Closing as c/common PR landed

@mheon mheon closed this as completed Jun 2, 2020
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

5 participants