-
Notifications
You must be signed in to change notification settings - Fork 6
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 support for podman --remote
#27
Labels
enhancement
New feature or request
Comments
ewchong
pushed a commit
to ewchong/arcaflow-engine-deployer-podman
that referenced
this issue
Apr 23, 2024
ewchong
pushed a commit
to ewchong/arcaflow-engine-deployer-podman
that referenced
this issue
Apr 23, 2024
ewchong
pushed a commit
to ewchong/arcaflow-engine-deployer-podman
that referenced
this issue
Apr 24, 2024
ewchong
pushed a commit
to ewchong/arcaflow-engine-deployer-podman
that referenced
this issue
Apr 25, 2024
ewchong
pushed a commit
to ewchong/arcaflow-engine-deployer-podman
that referenced
this issue
Apr 25, 2024
ewchong
pushed a commit
to ewchong/arcaflow-engine-deployer-podman
that referenced
this issue
Apr 25, 2024
webbnh
added a commit
that referenced
this issue
May 4, 2024
* Add podman remote support Close #27 --------- Co-authored-by: Edwin Chong <8726446-ewchong@users.noreply.gitlab.com> Co-authored-by: Webb Scales <wscales@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe what you would like to see in this project
Podman has the ability to run containers on a remote system via a socket connected to over ssh. We would like the ability to utilize this feature with both the default deployer and within a plugin step.
Please describe your use case
Running workflow plugins on target remote systems provides flexibility to include non-k8s remote targets, which would be helpful for CI execution as well as for parallelization of workflows across multiple targets.
Additional context
The server-side prerequisite for this is for the remote target host to enable the socket:
You can validate this is working on the server side with:
On the client side (from where the workflow is run), an ssh identity for connection authentication with the remote host is required.
From the client, the remote connection is setup with:
This connection can be validated on the client side with:
Once the remote connection is established and validated, a
podman
command can be run as usual, adding only--connection <connection_name>
to the parameters (before therun
command), for example:The text was updated successfully, but these errors were encountered: