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 restart container, no more stdout logs #12776

Closed
Taymindis opened this issue Jan 8, 2022 · 9 comments
Closed

podman restart container, no more stdout logs #12776

Taymindis opened this issue Jan 8, 2022 · 9 comments
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

@Taymindis
Copy link

Taymindis commented Jan 8, 2022

podman restart container no more stdout logs

/kind bug

Description

Steps to reproduce the issue:

podman run --name zookeeper-1 -d docker.io/zookeeper
podman logs -f --tail 10 -- working find and still tailing
podman restart zookeeper-1
podman logs -f --tail 10  --- keep exiting, no more tailing


podman --version
podman version 3.4.2

Why do i think it's a bug,

i have tried docker do the same steps, working fine and no issue

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 8, 2022
@rhatdan
Copy link
Member

rhatdan commented Jan 8, 2022

Could you try this against main branch or podman 3.4.4

I tried your example here and I see logs?

@Taymindis
Copy link
Author

my server version is

ubuntu 20.04

I can't find any latest version thatn 3.4.2.

And I could see there is a code merged on 3.4.3 to fixed this issue

But i can't find a way to upgrade it unless I build from scratch

ref:

https://podman.io/getting-started/installation

@Taymindis
Copy link
Author

Taymindis commented Jan 9, 2022

@rhatdan

Any way I can get the 3.4.4 binary or Will it be releasing soon on ubuntu? I saw that version still remain 3.4.2.

Managed to install from source and issue fixed, but I wiil wait for Ubuntu package released to be more safer than customized from source.

it's a great help.

Thanks @rhatdan ,

@vrothberg
Copy link
Member

@lsm5 PTAL

@vrothberg
Copy link
Member

The Ubuntu packages will be updated soon, thanks for pointing it out!

@mheon
Copy link
Member

mheon commented Jan 10, 2022

I'll dogpile on and say that I definitely recall backporting the fix for this at some point, so it should be resolved on 3.4.4 at latest.

@nils-ballmann
Copy link

@vrothberg still not updated by now 😸 but that's on a private server... so 🤷

$ apt-cache policy podman
podman:
  Installiert:           100:3.4.2-5
  Installationskandidat: 100:3.4.2-5
  Versionstabelle:
 *** 100:3.4.2-5 500
        500 https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/xUbuntu_20.04  Packages
        100 /var/lib/dpkg/status

@vrothberg
Copy link
Member

I think the 20.04 packages will be stuck on this version. Too old golang etc.

@nils-ballmann
Copy link

Ah okay, we'll it's time to update that server anyway. 😸

@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 Nov 3, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 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