-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
adjust --follow arg positioning to be compatible with docker and podman #12200
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
Conversation
All contributors have signed the CLA ✍️ ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to LocalStack! Thanks for raising your first Pull Request and landing in your contributions. Our team will reach out with any reviews or feedbacks that we have shortly. We recommend joining our Slack Community and share your PR on the #community channel to share your contributions with us. Please make sure you are following our contributing guidelines and our Code of Conduct.
I have read the CLA Document and I hereby sign the CLA |
Corresponding issue created here: |
Per the contributing doc, it appears I need to add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very reasonable change, thank you for your contribution!
This change will be part of the released CLI with the next minor release, which is scheduled for tomorrow!
Motivation
As described in this issue:
#12201
localstack fails to log under podman. Before this PR, starting logstack when using podman will reach the following error:
and logging will stop.
technically localstack will start, but no further console logs are produced after the above error.
In short, podman appears to be sensitive to the position of the
-f
or--follow
argument. Moving the argument before the container id is compatible with both docker and podmanChanges
localstack will now start without generating a logging error under podman, allowing console logs to be followed.