-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Podman fails to run with --log-driver=journald on Centos 7 #5467
Comments
Rebuilding conmon source RPM with packages below installed fixed the issue.
I believe it was the same issue with packaging as the one I have seen for ubuntu while ago. |
@alitvak69 Where are these packages sourced from? I'm pretty sure the official repos aren't shipping those versions yet |
The repo for centos listed there and managed by @lsm5 |
@alitvak69 so you only added these two as build-deps and no other change in the build process, yes? I can fix that for centos. @mheon @haircommander fedora would need this too, yes? |
Yep, if not already done, we should depend on those in Fedora as well |
@lsm5 I didn't changed specs I just made sure those packages were there :-). But yes it totally makes sense to add those as dependencies. |
Any news about this. I have not seen any updates on kubik. |
@mheon @haircommander PTAL |
i did make the changes on fedora, I think i need to change the centos branch too, let me check.. |
@alitvak69 sorry the webhook integration for autobuilds was a little messed up, it's building now using this spec file: https://build.opensuse.org/package/view_file/devel:kubic:libcontainers:stable/conmon/_service:obs_scm:conmon.spec?expand=1 |
A friendly reminder that this issue had no activity for 30 days. |
I take it the build has dropped so closing. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When running podman it fails to start the container if log driver set to journald. Looks like the same issue described in containers/conmon#67 (comment)
Steps to reproduce the issue:
Describe the results you received:
[conmon:e] Include journald in compilation path to log to systemd journal
Error: write child: broken pipe
Describe the results you expected:
Container started without errors
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: