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

Podman fails to run with --log-driver=journald on Centos 7 #5467

Closed
alitvak69 opened this issue Mar 12, 2020 · 14 comments
Closed

Podman fails to run with --log-driver=journald on Centos 7 #5467

alitvak69 opened this issue Mar 12, 2020 · 14 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. Packaging Bug is in a Podman package stale-issue

Comments

@alitvak69
Copy link

alitvak69 commented Mar 12, 2020

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:

  1. podman run --name test --log-driver=journald httpd

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:

Version:            1.8.1
RemoteAPI Version:  1
Go Version:         go1.13.6
OS/Arch:            linux/amd64

Output of podman info --debug:

debug:
  compiler: gc
  git commit: ""
  go version: go1.13.6
  podman version: 1.8.1
host:
  BuildahVersion: 1.14.2
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.11-1.1.el7.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.11, commit: cf3619d7130285b31fb70d0573414e1fae5ebe4e'
  Distribution:
    distribution: '"centos"'
    version: "7"
  MemFree: 6653034496
  MemTotal: 8368828416
  OCIRuntime:
    name: runc
    package: runc-1.0.0-15.1.el7.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc10
      commit: 67b92f062188d9cb6472b428855432c9f35efcf5
      spec: 1.0.1-dev
  SwapFree: 4294963200
  SwapTotal: 4294963200
  arch: amd64
  cpus: 8
  eventlogger: journald
  hostname: host.example.com
  kernel: 4.13.10-1.el7.elrepo.x86_64
  os: linux
  rootless: false
  uptime: 6535h 56m 26.77s (Approximately 272.29 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 3
  GraphDriverName: overlay
  GraphOptions: {}
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 33
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):

conmon-2.0.11-1.1.el7.x86_64
podman-1.8.1-2.1.el7.x86_64

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

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 12, 2020
@alitvak69
Copy link
Author

Rebuilding conmon source RPM with packages below installed fixed the issue.

systemd-libs
systemd-devel

I believe it was the same issue with packaging as the one I have seen for ubuntu while ago.

@mheon
Copy link
Member

mheon commented Mar 12, 2020

@alitvak69 Where are these packages sourced from? I'm pretty sure the official repos aren't shipping those versions yet

@alitvak69
Copy link
Author

@alitvak69
Copy link
Author

The repo for centos listed there and managed by @lsm5

@lsm5 lsm5 self-assigned this Mar 12, 2020
@lsm5 lsm5 added the Packaging Bug is in a Podman package label Mar 12, 2020
@lsm5
Copy link
Member

lsm5 commented Mar 12, 2020

Rebuilding conmon source RPM with packages below installed fixed the issue.

systemd-libs
systemd-devel

I believe it was the same issue with packaging as the one I have seen for ubuntu while ago.

@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?

@mheon
Copy link
Member

mheon commented Mar 12, 2020

Yep, if not already done, we should depend on those in Fedora as well

@alitvak69
Copy link
Author

@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.

@alitvak69
Copy link
Author

Any news about this. I have not seen any updates on kubik.

@TomSweeneyRedHat
Copy link
Member

@mheon @haircommander PTAL

@lsm5
Copy link
Member

lsm5 commented Mar 16, 2020

i did make the changes on fedora, I think i need to change the centos branch too, let me check..

@lsm5
Copy link
Member

lsm5 commented Mar 16, 2020

@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

@lsm5
Copy link
Member

lsm5 commented Mar 16, 2020

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Apr 16, 2020

I take it the build has dropped so closing.

@rhatdan rhatdan closed this as completed Apr 16, 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. Packaging Bug is in a Podman package stale-issue
Projects
None yet
Development

No branches or pull requests

6 participants