Skip to content

Conversation

@ibazulic
Copy link
Member

When Quay container starts via the systemd unit, it gets automatically removed as a post-stop action. This causes problems when trying to diagnose startup issues, such as any validation errors. Logs are written in journal and can be pulled out by journalctl but sometimes it's just easier to call container logs instead. With this change, we set the removal of Quay container, if it exists, as an ExecStartPre action. This allows the container to persist after exiting for additional debugging.

When Quay container starts via the systemd unit, it gets automatically removed as a post-stop action. This causes problems when trying to diagnose startup issues, such as any validation errors. Logs are written in journal and can be pulled out by `journalctl` but sometimes it's just easier to call container logs instead.
With this change, we set the removal of Quay container, if it exists, as an `ExecStartPre` action. This allows the container to persist after exiting for additional debugging.
Copy link
Contributor

@harishsurf harishsurf left a comment

Choose a reason for hiding this comment

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

lgtm

@harishsurf harishsurf added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Nov 26, 2024
@ibazulic ibazulic enabled auto-merge (squash) December 2, 2024 17:09
@ibazulic ibazulic requested a review from harishsurf December 10, 2024 16:20
@ibazulic ibazulic disabled auto-merge December 10, 2024 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Development

Successfully merging this pull request may close these issues.

2 participants