mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #5885] Service network name is not exposed via job context. #1274
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#1274
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 @eakoli on GitHub (Jul 25, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/5885
Bug report info
Command used with act
Describe issue
job context does not seem to be fully implemented.
at a minimum it would be nice if ${{ job.container.network }} was populated with the network used for the containers. Without it its not possible to use any docker containers in the steps that need to run on the same network as the services
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@alexleach commented on GitHub (Dec 14, 2025):
Yes I've also got stung by this...
Your logs show
${{ job.services.postgres.ports }}is empty, and that's what I would like to working to get around port clashes on my host machine.A lot from GitHub's job context appear not to be available in
act.Another one that I have found fails with
actis getting the output from an earlier step, e.g.${{ steps.yarn-cache-dir-path.outputs.dir }}