-
Notifications
You must be signed in to change notification settings - Fork 3k
Add remote exec #3624
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
Add remote exec #3624
Conversation
a269fe0 to
06acabc
Compare
|
☔ The latest upstream changes (presumably #3630) made this pull request unmergeable. Please resolve the merge conflicts. |
Signed-off-by: Peter Hunt <[email protected]>
including changing -l to the container id and separating a case of setting the env that remote can't handle Signed-off-by: Peter Hunt <[email protected]>
There's no way to get the error if we successfully get an exit code (as it's just printed to stderr instead). instead of relying on the error to be passed to podman, and edit based on the error code, process it on the varlink side instead Also move error codes to define package Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
06acabc to
d59f083
Compare
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
48ae4df to
01a8483
Compare
|
LGTM and happy green tests |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
Make appropriate changes to varlink exec api and containers_remote to implement remote exec.
Update the exec e2e tests to run with remote exec.
Note, there currently exists one flaw with this implementation, where running a shell in -ti and calling exit causes the runtime to exit with 130 and print an ugly message. not sure why this happens in remote and not local. Stay tuned, but I figured I'd get this out there for review in the meantimeEdit: the above is no longer a problem, and this is ready for review