[GH-ISSUE #192] Interpolation not working for the Docker image name #130

Closed
opened 2026-03-01 21:40:29 +03:00 by kerem · 13 comments
Owner

Originally created by @321zeno on GitHub (Apr 14, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/192

Possibly related to https://github.com/nektos/act/issues/108:

Here's a sample of my workflow:

jobs:
  build:
    strategy:
      matrix:
        container: [foo, bar]
    runs-on: ubuntu-latest
    name: ${{ matrix.container }}
    container: ${{ matrix.container }}

Using 0.2.7 outputs:

[testing/foo-2] 🧪  Matrix: map[variant:foo]
[testing/bar-1] 🧪  Matrix: map[variant:bar]
[testing/bar-1] 🚀  Start image=${{ matrix.variant }}
[testing/foo-2] 🚀  Start image=${{ matrix.variant }}
Error: invalid reference format

Using -v:

 🐳  docker pull ${{ matrix.container }}
pulling image 'docker.io/library/${{ matrix.container }}'
invalid reference format

It looks like the interpolation works for the name parameter but not for container

Originally created by @321zeno on GitHub (Apr 14, 2020). Original GitHub issue: https://github.com/nektos/act/issues/192 Possibly related to https://github.com/nektos/act/issues/108: Here's a sample of my workflow: ```yaml jobs: build: strategy: matrix: container: [foo, bar] runs-on: ubuntu-latest name: ${{ matrix.container }} container: ${{ matrix.container }} ``` Using 0.2.7 outputs: ``` [testing/foo-2] 🧪 Matrix: map[variant:foo] [testing/bar-1] 🧪 Matrix: map[variant:bar] [testing/bar-1] 🚀 Start image=${{ matrix.variant }} [testing/foo-2] 🚀 Start image=${{ matrix.variant }} Error: invalid reference format ``` Using `-v`: ``` 🐳 docker pull ${{ matrix.container }} pulling image 'docker.io/library/${{ matrix.container }}' invalid reference format ``` It looks like the interpolation works for the `name` parameter but not for `container`
kerem 2026-03-01 21:40:29 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Jun 16, 2020):

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

<!-- gh-comment-id:644455152 --> @github-actions[bot] commented on GitHub (Jun 16, 2020): Issue is stale and will be closed in 7 days unless there is new activity
Author
Owner

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

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

<!-- gh-comment-id:674461220 --> @github-actions[bot] commented on GitHub (Aug 16, 2020): Issue is stale and will be closed in 7 days unless there is new activity
Author
Owner

@SuperSandro2000 commented on GitHub (Aug 16, 2020):

Bump

<!-- gh-comment-id:674463591 --> @SuperSandro2000 commented on GitHub (Aug 16, 2020): Bump
Author
Owner

@amyspark commented on GitHub (Sep 8, 2020):

I can confirm this is a bug in act 0.2.14.

<!-- gh-comment-id:689050844 --> @amyspark commented on GitHub (Sep 8, 2020): I can confirm this is a bug in act 0.2.14.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 8, 2020):

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

<!-- gh-comment-id:723513011 --> @github-actions[bot] commented on GitHub (Nov 8, 2020): Issue is stale and will be closed in 7 days unless there is new activity
Author
Owner

@SuperSandro2000 commented on GitHub (Nov 8, 2020):

bump

<!-- gh-comment-id:723514908 --> @SuperSandro2000 commented on GitHub (Nov 8, 2020): bump
Author
Owner

@lewkoo commented on GitHub (Dec 14, 2020):

I can confirm this is still a problem in 0.2.17.

<!-- gh-comment-id:744369384 --> @lewkoo commented on GitHub (Dec 14, 2020): I can confirm this is still a problem in 0.2.17.
Author
Owner

@zakame commented on GitHub (Dec 17, 2020):

This seems fixed in #413 which should show up in the next release 🤞

<!-- gh-comment-id:747191912 --> @zakame commented on GitHub (Dec 17, 2020): This seems fixed in #413 which should show up in the next release :crossed_fingers:
Author
Owner

@github-actions[bot] commented on GitHub (Jan 17, 2021):

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

<!-- gh-comment-id:761708063 --> @github-actions[bot] commented on GitHub (Jan 17, 2021): Issue is stale and will be closed in 14 days unless there is new activity
Author
Owner

@SuperSandro2000 commented on GitHub (Jan 17, 2021):

Bump

<!-- gh-comment-id:761822111 --> @SuperSandro2000 commented on GitHub (Jan 17, 2021): Bump
Author
Owner

@catthehacker commented on GitHub (Jan 17, 2021):

@SuperSandro2000 the issue has been already fixed since https://github.com/nektos/act/releases/tag/v0.2.18
image
image

<!-- gh-comment-id:761844446 --> @catthehacker commented on GitHub (Jan 17, 2021): @SuperSandro2000 the issue has been already fixed since https://github.com/nektos/act/releases/tag/v0.2.18 ![image](https://user-images.githubusercontent.com/31106839/104850219-14d69500-58ee-11eb-8cb8-bea9e698bffc.png) ![image](https://user-images.githubusercontent.com/31106839/104850243-39cb0800-58ee-11eb-879f-e24b11fec9af.png)
Author
Owner

@SuperSandro2000 commented on GitHub (Jan 19, 2021):

Then please close the issue. I am just fighting stale bot.

<!-- gh-comment-id:763069329 --> @SuperSandro2000 commented on GitHub (Jan 19, 2021): Then please close the issue. I am just fighting stale bot.
Author
Owner

@321zeno commented on GitHub (Jan 20, 2021):

Can confirm this issue is no longer present in 0.2.18.

Thanks!

<!-- gh-comment-id:763479264 --> @321zeno commented on GitHub (Jan 20, 2021): Can confirm this issue is no longer present in 0.2.18. Thanks!
Sign in to join this conversation.
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#130
No description provided.