fix: podman create requires dummy command for static plugin images#2551
Merged
gashcrumb merged 1 commit intoJun 3, 2026
Merged
Conversation
Plugin OCI images are static file bundles with no CMD or ENTRYPOINT. Running 'podman create' without a command argument fails with: Error: no command or entrypoint provided, and no CMD or ENTRYPOINT from image Fix: Pass /bin/true as a dummy command. The container is never run, just created so we can extract files with podman cp. Fixes instrumentation job failure on PR redhat-developer#2550. Ref: https://github.com/redhat-developer/rhdh-plugin-export-overlays/actions/runs/26902663501
|
gashcrumb
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
instrumentjob introduced in #2383 fails when creating containers from plugin OCI images:Plugin images are static file bundles (contain only JS/CSS assets, no executable). They have no
CMDorENTRYPOINTdefined. Runningpodman createwithout a command argument fails.Fix
Pass
/bin/trueas a dummy command:CID=$(podman create "$PROD_IMAGE" /bin/true)The container is never actually run - it's only created so we can extract files with
podman cp. The dummy command satisfies podman's requirement.Testing
Validated fix against the failed run:
After merge, will re-run
/publishon #2550 to validate end-to-end coverage collection.Impact
Without this fix, all coverage collection is broken - the
instrumentjob fails immediately for every workspace.