[GH-ISSUE #291] [Bug] Doesn't resolve a relative path to a docker file in the Action #204

New issue

Closed

opened 2026-03-01 21:41:12 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 21:41:12 +03:00

Owner

Originally created by @JustinGrote on GitHub (Jun 24, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/291

#Issue Summary
If I have an action specified like this:

name: 'Super Duper Linter'
description: 'Lints and validates code files in your repository, very helpful for Pull Requests!'
runs:
  using: 'docker'
  image: '../../Dockerfile'

And a workflow specified like this:

name: Sandbox
on:
  push:
    branches:
      - sandbox
jobs:
  localTest:
    runs-on: ubuntu-latest
    steps:
      - name: Super Duper Linter Test
        uses: ./Tests/act
        continue-on-error: true

When running act -j localTest, the docker build step doesn't resolve the relative path to the docker file in the image: section

Actual vs Expected

docker build -t act-tests-act:latest C:\Users\jgrote\Projects\Super-Duper-Linter\Tests\act
should be
docker build -t act-tests-act:latest -f C:\Users\jgrote\Projects\Super-Duper-Linter\Dockerfile

Workaround

If you run docker build -t act-tests-act:latest -f C:\Users\jgrote\Projects\Super-Duper-Linter\Dockerfile manually right before the action, the docker build -t act-tests-act:latest C:\Users\jgrote\Projects\Super-Duper-Linter\Tests\act still silently fails but when the actual docker run image=act-tests-act:latest entrypoint=[] cmd=[] occurs then it is using the latest image.

Originally created by @JustinGrote on GitHub (Jun 24, 2020). Original GitHub issue: https://github.com/nektos/act/issues/291 #Issue Summary If I have an action specified like this: ```yaml name: 'Super Duper Linter' description: 'Lints and validates code files in your repository, very helpful for Pull Requests!' runs: using: 'docker' image: '../../Dockerfile' ``` And a workflow specified like this: ```yaml name: Sandbox on: push: branches: - sandbox jobs: localTest: runs-on: ubuntu-latest steps: - name: Super Duper Linter Test uses: ./Tests/act continue-on-error: true ``` When running `act -j localTest`, the docker build step doesn't resolve the relative path to the docker file in the `image:` section ![image](https://user-images.githubusercontent.com/15258962/85583394-14457c80-b5f3-11ea-8114-3794112d1d3b.png) # Actual vs Expected `docker build -t act-tests-act:latest C:\Users\jgrote\Projects\Super-Duper-Linter\Tests\act` should be `docker build -t act-tests-act:latest -f C:\Users\jgrote\Projects\Super-Duper-Linter\Dockerfile` # Workaround If you run `docker build -t act-tests-act:latest -f C:\Users\jgrote\Projects\Super-Duper-Linter\Dockerfile` manually right before the action, the `docker build -t act-tests-act:latest C:\Users\jgrote\Projects\Super-Duper-Linter\Tests\act` still silently fails but when the actual `docker run image=act-tests-act:latest entrypoint=[] cmd=[]` occurs then it is using the latest image.

kerem

2026-03-01 21:41:12 +03:00

closed this issue
added the
stale
label

kerem commented

2026-03-01 21:41:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 24, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Aug 24, 2020): Issue is stale and will be closed in 7 days unless there is new activity

No milestone

No project

No assignees

1 participant

Notifications

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#204

No description provided.

Rows
Columns