mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2137] Inconsistency using custom Docker image #1018
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1018
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sockmaster27 on GitHub (Dec 20, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/2137
Bug report info
Command used with act
Describe issue
When using a custom Docker image, my tests pass locally, but not in the actual GitHub CI.
Specifically, the installation of Cargo on the image works fine when run with act, but fails in the real environment, because
rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.While I understand that the base runner environments aren't identical to the real ones, it was my understanding that using a custom image on top of that should create an entirely isolated environment. Am I misunderstanding something?
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
The contents of the Dockerfile is as follows:
@github-actions[bot] commented on GitHub (Jun 18, 2024):
Issue is stale and will be closed in 14 days unless there is new activity