-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Issue: Got error when use act at locally with remote docker contexts #583
Comments
This comment has been minimized.
This comment has been minimized.
@catthehacker I can help test or contribution, please do some feedback |
I think act doesn't read docker context configurations, no idea how to do that. I would try to set the environment variable DOCKER_HOST=ssh://aisuko@192.168.1.104 act In the log it tried to connect to localhost, because |
Thanks, I will take it a try. |
Docker contexts are not supported and it's quite easy to overcome that (example above). Anyone can feel free to make PR with such feature but it won't be actively pursued. |
Here are one liners to set
export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}')
$env:DOCKER_HOST = (docker context inspect --format '{{.Endpoints.docker.Host}}') |
I believe we can add these to the |
In fact, I'd like to add these to the |
This comment has been minimized.
This comment has been minimized.
We can close this issue due to #749 |
Is this meant to be a workaround forever? |
Using podman machine start // this will show the optional helper installation command
podman machine stop
sudo /opt/homebrew/Cellar/podman/5.1.2/bin/podman-mac-helper install Now you can use it like it's |
Act version
Expected behaviour
act
can work well with remote docker context, and I can pull the target image by manually.Actual behaviour
act
can not pull the imageWorkflow and/or repository
workflow
Steps to reproduce
act
outputLog
The text was updated successfully, but these errors were encountered: