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

deploy: Log filtered content warning to journal, not stderr #301

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

cgwalters
Copy link
Collaborator

This one is really a "soft warning"...it's not a serious problem to have stuff in /run, it's just ignored.

At the same time, we want to persist it so that someone debugging things later can find the information.

This one is really a "soft warning"...it's not a serious
problem to have stuff in `/run`, it's just ignored.

At the same time, we want to persist it so that someone debugging
things later can find the information.

Signed-off-by: Colin Walters <[email protected]>
Copy link
Contributor

@jeckersb jeckersb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jeckersb jeckersb enabled auto-merge February 5, 2024 22:31
@jeckersb jeckersb merged commit 8969314 into containers:main Feb 5, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants