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.

Sign up for GitHub

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

Jump to bottom

podman-remote: missing error messages #4096

Closed
edsantiago opened this issue Sep 24, 2019 · 4 comments
Closed

podman-remote: missing error messages #4096

edsantiago opened this issue Sep 24, 2019 · 4 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@edsantiago
Copy link
Member 

# podman-remote run alpine /no/such/command

(i.e. no output). Error message goes only to the varlink window:

# podman varlink --timeout=0
ERRO[1399] container_linux.go:346: starting container process caused "exec: \"/no/such/command\": stat /no/such/command: no such file or directory": OCI runtime command not found error

podman-1.6.0-2.fc30.x86_64 as well as current master @ 83b2348; but this is a longstanding bug
This was referenced Sep 24, 2019
Merged
Closed
edsantiago added a commit to edsantiago/libpod that referenced this issue Sep 24, 2019
@edsantiago
system tests: run test: reenable and fix
c146f8d 
Test had incorrectly been disabled for all podman; it
should've been disabled only for podman-remote. Fixed
that, and fixed the problem that was causing failures:
podman-remote is gobbling up stdin (containers#4095), so no
tests were actually being run at all, or only one.
Fixed by redirecting input on the run_podman invocation.
Added, as backup, a confirmation mechanism to ensure
that all expected tests are being run.

Note that test is reenabled, but the output check is
disabled for podman-remote due to containers#4096; this at least
lets us check exit status.

Signed-off-by: Ed Santiago <[email protected]>
@github-actions
Copy link

This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days.

@edsantiago
Copy link
Member Author

Problem still present in master @ 381fa4d

@github-actions github-actions bot closed this as completed Nov 8, 2019
@rhatdan rhatdan reopened this Nov 8, 2019
@mheon mheon removed the stale-issue label Nov 16, 2019
@mheon mheon reopened this Nov 16, 2019
@mheon
Copy link
Member

mheon commented Nov 16, 2019

You need to not only reopen, but clear the stale-issue label, to prevent it from autoclosing again. Sort of annoying.

@github-actions
Copy link

This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days.

@edsantiago edsantiago mentioned this issue Nov 9, 2020
Closed
@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 Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@edsantiago @rhatdan @mheon