You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For working with containers from within a container, I bind-mount /run/podman/podman.sock from the host and use podman-remote. Bolt only calls the local podman command to interact with containers.
Describe the Solution You Would Like
Add a podman transport option that accepts any valid Podman URL from podman-remote(1), including examples like:
That will cause bolt to work with /run/podman/podman.sock for all containers. One could set the environment variable CONNECTION_HOST to some other value. This would also apply to all containers. A transport option would allow this to be specified on a per target basis and let Bolt orchestrate tasks among many container hosts.
The text was updated successfully, but these errors were encountered:
Use Case
For working with containers from within a container, I bind-mount
/run/podman/podman.sock
from the host and usepodman-remote
. Bolt only calls the localpodman
command to interact with containers.Describe the Solution You Would Like
Add a podman transport option that accepts any valid Podman URL from podman-remote(1), including examples like:
When this new option is set, Bolt should call
podman-remote --url=VALUE
to interact with containers.Describe Alternatives You've Considered
As a workaround, I prepare my management container with:
That will cause bolt to work with
/run/podman/podman.sock
for all containers. One could set the environment variableCONNECTION_HOST
to some other value. This would also apply to all containers. A transport option would allow this to be specified on a per target basis and let Bolt orchestrate tasks among many container hosts.The text was updated successfully, but these errors were encountered: