[GH-ISSUE #1633] Using -P platform with local image #811

New issue

Open

opened 2026-03-01 21:46:35 +03:00 by kerem · 9 comments

kerem commented 2026-03-01 21:46:35 +03:00

Owner

Copy link

Originally created by @dannystaple on GitHub (Feb 18, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1633

Act version

0.2.42

Feature description

I would like to be able to use a local image for the -P flag.
For example:

act --eventpath myevent.json \
  -P ubuntu-latest=my-local-latest

The intent would be to take the medium image and add other parts I might need, for example the python components if the intent is to test pipelines around the python ecosystem.

Currently running this, it will force pull from a remote on dockerhub, however, this may simply be a local image that I do not intend to put onto dockerhub.

Originally created by @dannystaple on GitHub (Feb 18, 2023). Original GitHub issue: https://github.com/nektos/act/issues/1633 ### Act version 0.2.42 ### Feature description I would like to be able to use a local image for the `-P` flag. For example: ``` act --eventpath myevent.json \ -P ubuntu-latest=my-local-latest ``` The intent would be to take the medium image and add other parts I might need, for example the python components if the intent is to test pipelines around the python ecosystem. Currently running this, it will force pull from a remote on dockerhub, however, this may simply be a local image that I do not intend to put onto dockerhub.

kerem added the

kind/feature-request

label 2026-03-01 21:46:35 +03:00

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@ChristopherHX commented on GitHub (Feb 18, 2023):

Use --pull=false. The reason that this flag now defaults to true is a breaking change in act with older default docker images.

You have to manually keep uptodate, if you use this flag.

<!-- gh-comment-id:1435718418 --> @ChristopherHX commented on GitHub (Feb 18, 2023): Use `--pull=false`. The reason that this flag now defaults to true is a breaking change in act with older default docker images. You have to manually keep uptodate, if you use this flag.

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@dannystaple commented on GitHub (Feb 18, 2023):

Worked a treat - just updating the docs to reflect that.

<!-- gh-comment-id:1435726672 --> @dannystaple commented on GitHub (Feb 18, 2023): Worked a treat - just updating the docs to reflect that.

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@joanrodriguez commented on GitHub (Feb 21, 2023):

Hey, the flag doesn't work for me if I never uploaded the image to Docker Hub....

Steps to reproduce:

• Create Docker image locally and give repository name (foobar/docker-github-actions-runner)
• Run this:

  act --container-architecture linux/arm64/v8
  --pull=false
  -P ubuntu-latest=foobar/docker-github-actions-runner
  -P self-hosted=foobar/docker-github-actions-runner
  

Returns: Error: Error response from daemon: pull access denied for foobar/docker-github-actions-runner, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Do I make a mistake with the flags or the feature doesn't exist?

<!-- gh-comment-id:1438881620 --> @joanrodriguez commented on GitHub (Feb 21, 2023): Hey, the flag doesn't work for me if I never uploaded the image to Docker Hub.... Steps to reproduce: - Create Docker image locally and give repository name (foobar/docker-github-actions-runner) - Run this: ``` act --container-architecture linux/arm64/v8 --pull=false -P ubuntu-latest=foobar/docker-github-actions-runner -P self-hosted=foobar/docker-github-actions-runner ``` Returns: `Error: Error response from daemon: pull access denied for foobar/docker-github-actions-runner, repository does not exist or may require 'docker login': denied: requested access to the resource is denied` Do I make a mistake with the flags or the feature doesn't exist?

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@ChristopherHX commented on GitHub (Feb 21, 2023):

I cannot reproduce your error.
You should see forcePull=false in the log and if act finds you image it will use it.

forcePull=true will always pull the image (--pull)
forcePull=false will pull the image if missing (--pull=false)

<!-- gh-comment-id:1438911447 --> @ChristopherHX commented on GitHub (Feb 21, 2023): I cannot reproduce your error. You should see forcePull=false in the log and if act finds you image it will use it. forcePull=true will always pull the image (--pull) forcePull=false will pull the image if missing (--pull=false)

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@dannystaple commented on GitHub (Feb 21, 2023):

@joanrodriguez I take it the line continuation characters are not posted just for aesthetics or that this was all on one line?
Can you show the docker image in docker list. It isn't looking for a local arm64 image when you have a x86 image is it?

<!-- gh-comment-id:1438921013 --> @dannystaple commented on GitHub (Feb 21, 2023): @joanrodriguez I take it the line continuation characters are not posted just for aesthetics or that this was all on one line? Can you show the docker image in docker list. It isn't looking for a local arm64 image when you have a x86 image is it?

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@joanrodriguez commented on GitHub (Feb 22, 2023):

Hey guys, I had some conflicting stuff in my .~/.actrc. After emptying it and removing the architecture arg, I'm able to use a local docker image :)

$ docker images
REPOSITORY                                    TAG                        IMAGE ID       CREATED         SIZE
spingwun/docker-github-actions-runner         latest                     a8ed893ffe96   16 hours ago    1.83GB
$ act --pull=false -P ubuntu-latest=spingwun/docker-github-actions-runner -P self-hosted=spingwun/docker-github-actions-runner
WARN  ⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠  
[main/checks] 🚀  Start image=spingwun/docker-github-actions-runner
[main/db    ] 🚀  Start image=spingwun/docker-github-actions-runner
[main/build ] 🚀  Start image=spingwun/docker-github-actions-runner
[main/build ]   🐳  docker pull image=spingwun/docker-github-actions-runner platform= username= forcePull=false
[main/db    ]   🐳  docker pull image=spingwun/docker-github-actions-runner platform= username= forcePull=false
[main/checks]   🐳  docker pull image=spingwun/docker-github-actions-runner platform= username= forcePull=false
[main/db    ]   🐳  docker create image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[main/db    ]   🐳  docker run image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[main/checks]   🐳  docker create image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[main/build ]   🐳  docker create image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[main/checks]   🐳  docker run image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]
[main/build ]   🐳  docker run image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[]

You can't really tell that it didn't pull it from the logs but it was instantaneous and I had deleted the Docker image from the hub so it definitely worked :)

Thanks again

<!-- gh-comment-id:1439755849 --> @joanrodriguez commented on GitHub (Feb 22, 2023): Hey guys, I had some conflicting stuff in my `.~/.actrc`. After emptying it and removing the architecture arg, I'm able to use a local docker image :) ```sh $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE spingwun/docker-github-actions-runner latest a8ed893ffe96 16 hours ago 1.83GB $ act --pull=false -P ubuntu-latest=spingwun/docker-github-actions-runner -P self-hosted=spingwun/docker-github-actions-runner WARN ⚠ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. ⚠ [main/checks] 🚀 Start image=spingwun/docker-github-actions-runner [main/db ] 🚀 Start image=spingwun/docker-github-actions-runner [main/build ] 🚀 Start image=spingwun/docker-github-actions-runner [main/build ] 🐳 docker pull image=spingwun/docker-github-actions-runner platform= username= forcePull=false [main/db ] 🐳 docker pull image=spingwun/docker-github-actions-runner platform= username= forcePull=false [main/checks] 🐳 docker pull image=spingwun/docker-github-actions-runner platform= username= forcePull=false [main/db ] 🐳 docker create image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [main/db ] 🐳 docker run image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [main/checks] 🐳 docker create image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [main/build ] 🐳 docker create image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [main/checks] 🐳 docker run image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [main/build ] 🐳 docker run image=spingwun/docker-github-actions-runner platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] ``` You can't really tell that it didn't pull it from the logs but it was instantaneous and I had deleted the Docker image from the hub so it definitely worked :) Thanks again

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@thomashutcheson-msm commented on GitHub (Feb 27, 2023):

Hey, the flag doesn't work for me if I never uploaded the image to Docker Hub....

Steps to reproduce:

• Create Docker image locally and give repository name (foobar/docker-github-actions-runner)
• Run this:

  act --container-architecture linux/arm64/v8
  --pull=false
  -P ubuntu-latest=foobar/docker-github-actions-runner
  -P self-hosted=foobar/docker-github-actions-runner
  

Returns: Error: Error response from daemon: pull access denied for foobar/docker-github-actions-runner, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Do I make a mistake with the flags or the feature doesn't exist?

I was getting this error too, then realised I needed to add the tag as well as repository name.
my-self-hosted-image:v1
now I can run
act -j my_github_workflow -P self-hosted=my-self-hosted-image:v1 --pull=false

<!-- gh-comment-id:1446202190 --> @thomashutcheson-msm commented on GitHub (Feb 27, 2023): > Hey, the flag doesn't work for me if I never uploaded the image to Docker Hub.... > > Steps to reproduce: > > * Create Docker image locally and give repository name (foobar/docker-github-actions-runner) > * Run this: > ``` > act --container-architecture linux/arm64/v8 > --pull=false > -P ubuntu-latest=foobar/docker-github-actions-runner > -P self-hosted=foobar/docker-github-actions-runner > ``` > > Returns: `Error: Error response from daemon: pull access denied for foobar/docker-github-actions-runner, repository does not exist or may require 'docker login': denied: requested access to the resource is denied` > > Do I make a mistake with the flags or the feature doesn't exist? I was getting this error too, then realised I needed to add the tag as well as repository name. `my-self-hosted-image:v1` now I can run `act -j my_github_workflow -P self-hosted=my-self-hosted-image:v1 --pull=false`

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@dgrebb commented on GitHub (Jun 19, 2023):

The only question that wasn't answered here, which ended up being the issue for me:

act --container-architecture linux/amd64 --pull=false -P ubuntu-latest=custom-image-name:latest ...

This will look for that image in the specific architecture.

If your custom image wasn't build with that architecture, act will then attempt to pull an image from the registry, even with the --pull=false flag set.

@dannystaple this issue and your subsequent comment saved me days of banging my head against a wall. Thank you!

@joanrodriguez I take it the line continuation characters are not posted just for aesthetics or that this was all on one line? Can you show the docker image in docker list. It isn't looking for a local arm64 image when you have a x86 image is it?

I needed to docker buildx build --platform linux/amd64 my custom image.

<!-- gh-comment-id:1596405635 --> @dgrebb commented on GitHub (Jun 19, 2023): The only question that wasn't answered here, which ended up being the issue for me: `act --container-architecture linux/amd64 --pull=false -P ubuntu-latest=custom-image-name:latest ...` This will look for that image in the specific architecture. If your custom image wasn't build with that architecture, `act` will then attempt to pull an image from the registry, even with the `--pull=false` flag set. @dannystaple this issue and your subsequent comment saved me days of banging my head against a wall. Thank you! > @joanrodriguez I take it the line continuation characters are not posted just for aesthetics or that this was all on one line? Can you show the docker image in docker list. It isn't looking for a local arm64 image when you have a x86 image is it? I needed to `docker buildx build --platform linux/amd64` my custom image.

kerem commented 2026-03-01 21:46:36 +03:00

Author

Owner

Copy link

@surgiie commented on GitHub (Aug 7, 2024):

--pull=false doesnt work with me.

[deployment/Deployment/build-and-deploy]   🐳  docker pull image=self-hosted-workers-prod:latest platform= username= forcePull=false
[deployment/Deployment/build-and-deploy] [DEBUG]   🐳  docker pull self-hosted-workers-prod:latest
[deployment/Deployment/build-and-deploy] [DEBUG] Image exists? false
[deployment/Deployment/build-and-deploy] [DEBUG] pulling image 'docker.io/library/self-hosted-workers-prod:latest' ()
Error: Error response from daemon: pull access denied for self-hosted-workers-prod, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Im building image with --platform linux/amd64 as suggested above but its still trying to pull.

Im also able to run a container with said image:

docker run -it self-hosted-workers-prod:latest /bin/bash

Feels like my flag is being ignored. Using act version : 0.2.65

Any one have the same issue?

<!-- gh-comment-id:2274416678 --> @surgiie commented on GitHub (Aug 7, 2024): `--pull=false` doesnt work with me. ``` [deployment/Deployment/build-and-deploy] 🐳 docker pull image=self-hosted-workers-prod:latest platform= username= forcePull=false [deployment/Deployment/build-and-deploy] [DEBUG] 🐳 docker pull self-hosted-workers-prod:latest [deployment/Deployment/build-and-deploy] [DEBUG] Image exists? false [deployment/Deployment/build-and-deploy] [DEBUG] pulling image 'docker.io/library/self-hosted-workers-prod:latest' () Error: Error response from daemon: pull access denied for self-hosted-workers-prod, repository does not exist or may require 'docker login': denied: requested access to the resource is denied ``` Im building image with `--platform linux/amd64` as suggested above but its still trying to pull. Im also able to run a container with said image: `docker run -it self-hosted-workers-prod:latest /bin/bash` Feels like my flag is being ignored. Using act version : `0.2.65` Any one have the same issue?

kerem referenced this issue 2026-03-01 21:52:03 +03:00

[PR #845] [CLOSED] Update homebrew-based installation #1641

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dependabot/go_modules/github.com/go-git/go-git/v5-5.18.0

dependabot/go_modules/dependencies-08815e2262

mergify/configuration-deprecated-update

dependabot/github_actions/dependencies-a3a104477f

chore/simplify-ci-and-makefile

dependabot/go_modules/golang.org/x/crypto-0.45.0

dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.4.0

panekj/ci/improve-jobs

fix-skip-non-yaml-files-in-dir

normalize-pull-rebuild-flags

fix-no-recurse-by-default

2517-poor-error-for-incomplete-action-step

2472-make-use-new-action-cache-the-new-default-for-downloading-actions

act-tart

act-lxc

act-oidc

act-dind

avoid-slash-in-actor

dependabot/go_modules/github.com/docker/docker-26.1.4incompatible

meta-keep-filetime

local-repository-action-cache

pr-merger

update-docker-deps

follow_local_action_symlink

boltdb-lock-in-handler

use-socket-path

no-pull-no-rebuild

path-issues

fix/env

feat/podman

refactor/testdata

v0.2.87

v0.2.86

v0.2.85

v0.2.84

v0.2.83

v0.2.82

v0.2.81

v0.2.80

v0.2.79

v0.2.78

v0.2.77

v0.2.76

v0.2.75

v0.2.74

v0.2.73

v0.2.72

v0.2.71

v0.2.70

v0.2.69

v0.2.68

v0.2.67

v0.2.66

v0.2.65

v0.2.64

v0.2.63

v0.2.62

v0.2.61

v0.2.60

v0.2.59

v0.2.58

v0.2.57

v0.2.56

v0.2.55

v0.2.54

v0.2.53

v0.2.52

v0.2.51

v0.2.50

v0.2.49

v0.2.48

v0.2.47

v0.2.46

v0.2.45

v0.2.44

v0.2.43

v0.2.42

v0.2.41

v0.2.40

v0.2.39

v0.2.38

v0.2.37

v0.2.36

v0.2.35

v0.2.34

v0.2.33

v0.2.32

v0.2.31

v0.2.30

v0.2.29

v0.2.28

v0.2.27

v0.2.26

v0.2.25

v0.2.24

v0.2.23

v0.2.22

v0.2.21

v0.2.20

v0.2.19

v0.2.18

v0.2.17

v0.2.16

v0.2.15

v0.2.14

v0.2.13

v0.2.12

v0.2.11

v0.2.10

v0.2.9

v0.2.8

v0.2.7

v0.2.6

v0.2.5

v0.2.4

v0.2.3

v0.2.2

v0.2.1

v0.2.0

v0.1.3

v0.1.2

v0.1.1

v0.1.0

v0.0.5

v0.0.4

v0.0.3

v0.0.2

v0.0.1

Labels

Clear labels   

area/action

  

area/cli

  

area/docs

  

area/image

  

area/runner

  

area/workflow

  

backlog

  

confirmed/not-planned

  

kind/bug

  

kind/discussion

  

kind/external

  

kind/feature-request

  

kind/question

  

meta/duplicate

  

meta/invalid

  

meta/need-more-info

  

meta/resolved

  

meta/wontfix

  

meta/workaround

  

needs-work

  

pull-request

Mirrored from GitHub Pull Request

  

review/not-planned

  

size/M

  

size/XL

  

size/XXL

  

stale

  

stale-exempt

No labels

area/action

area/cli

area/docs

area/image

area/runner

area/workflow

backlog

confirmed/not-planned

kind/bug

kind/discussion

kind/external

kind/feature-request

kind/question

meta/duplicate

meta/invalid

meta/need-more-info

meta/resolved

meta/wontfix

meta/workaround

needs-work

pull-request

review/not-planned

size/M

size/XL

size/XXL

stale

stale-exempt

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#811

No description provided.