mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1205] apt-get hangs when installing directly or indirectly keyboard-configuration #667
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#667
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 @Elanis on GitHub (Jun 7, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1205
Bug report info
Command used with act
Describe issue
When running a ubuntu-latest CI which does a apt install, act hangs out when trying to install
keyboard-configurationpackage.Based on https://github.com/docker/build-push-action/issues/504, I had to set environement variable
DEBIAN_FRONTEND=noninteractiveto be able to run my apt install completly.Link to GitHub repository
https://github.com/Elanis/web-to-desktop-framework-comparison/
Non-working workflow content
Working workflow content
Relevant log output
(https://pastebin.com/ugWdjBZC)
Additional information
No response
@github-actions[bot] commented on GitHub (Jul 8, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@alek-kam commented on GitHub (Jul 8, 2022):
Had the same issue.
@github-actions[bot] commented on GitHub (Aug 8, 2022):
Issue is stale and will be closed in 14 days unless there is new activity
@Elanis commented on GitHub (Aug 8, 2022):
Still a bug
@KnisterPeter commented on GitHub (Aug 8, 2022):
It's not a bug as it does work like on GitHub actions.
The solution could be found in the referenced issue: https://github.com/docker/build-push-action/issues/504
Also the working workflow in this issue description shows the solution as well.
Do not expect act to run in an interactive terminal.
@Elanis commented on GitHub (Aug 8, 2022):
Well, I expected
actto work in the same way as Github Actions. Adding a environement variable to fix a local tool issue isn't a solution imo@KnisterPeter commented on GitHub (Aug 8, 2022):
I think the main problem might be that in GitHub actions the ubuntu is preconfigured to run non-interactive, while the image used by default in act is missing this. @catthehacker Is that right?
@Elanis You can configure act to use a custom image and map it to
ubuntu-latest. Then you can change this without adding ENV-Vars nor act need to be changed. It's just a matter of configuration.@ChristopherHX commented on GitHub (Aug 8, 2022):
No, actions/runner doesn't allocate a tty.
You can make act do the same just assign false to isTerminal
github.com/nektos/act@92ddcdae09/pkg/container/docker_run.go (L543)Doing this disables color output of a lot of tools and is an issue in the actions/runner repo for years.
I had fix for that preserved the tty, but tells apt to stop while waiting for input. I abandoned the fix.
envs.txt/event.jsonto fixed location #1548