-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
network-scoped alias is supported only for containers in user defined networks #2074
Comments
I've run into this problem as well.
Workflow file: .github/workflows/code-style-dev.yml act -W '.github/workflows/code-style-dev.yml' Output:
|
This problem occurs in v0.2.53, but it no longer occurs after downgrading to v0.2.51. |
I can confirm this bug, I'm working on a fix... |
go\pkg\mod\github.com\docker\[email protected]+incompatible\api\types\container\hostconfig_unix.go
go\pkg\mod\github.com\docker\[email protected]+incompatible\api\types\container\hostconfig_windows.go
Why did docker this? Seems like I have to replace the convenience function with it's unix definition |
We've also run into this problem. Fixed temporary by downgrading act to v0.2.51. |
I'm experiencing the same issue. I can provide any information if you need |
The patch is finished from my side, but I'm not in the position to be allowed to merge.
I would only need 2 reviewer from maintainers (while I'm one of them, my PR's need a total amount of 3 maintainers, if you would open a PR with the same change I could approve it so only one maintainer review is missing), but that's a bottle neg. (One reason why my commit rate for this repository is declining and I'm less motivated to review other PR's) Please comment and test my linked PR #2075, this could increase the chance another maintainer have a look at the change. |
If you use gh, in the meantime: gh extension install https://github.com/nektos/gh-act --pin v0.2.51 |
I faced this problem today after the upgrade. Downgraded to 0.2.51 and it worked :) |
Due to the mass of PR's merged today, I prefer to do manual regression testing before creating a hotfix release. If there is no release till wednesday, please ping me. |
Please update to v0.2.54
|
@ChristopherHX, thank you! Chocolatey has not found an update yet. I'll check back later. |
I've updated to 0.2.54 and am still experiencing the problem. |
Whops
|
Running on
|
Still broken for me as above. Install scoop on Power Shell (Windows package manager) Run on cmd: |
I just installed act and I am getting above error. Installed act with winget:
Versions:
|
It's a real problem not having CI for windows compatibility. Can you cross test #2093?, the last time I got comments like works but it didn't work Any ideas how to properly test for windows linux container compatibility on GitHub Actions? I could think of using a tmate ssh tunnel from ubuntu-latest to windows-latest. So can also macOS start testing again using an ubuntu-latest to provide docker.. |
Can confirm this indeed still happens on Windows 11 with latest Winget version. Rolling back to 0.2.52 does the trick, still. |
0.2.54 did not work for me (Windows 11). But 0.2.52 worked great! |
Same error in windows. the docker is installed in ubuntu
|
Do you still get the error with: act-windows-x64-pr-2093.zip? (pr #2093) |
Yes, it work for me. |
I do not get the error with this patched version. Windows 11 22H2 with feature update. |
@ChristopherHX it is working for me |
Sorry my first attempt to fix this issue ended up beeing untested from my side, before realizing docker stubbed IsHost as false and therefore didn't care about it in IsUserDefined. No reviewer told me about this problem (see #2075 (comment)). It's hard for me to work on nektos/act, most maintainer left and the owner cplee does approve PR unregulary |
Works!
|
I still get this on 0.2.55.
|
Unfortunately I can confirm is still broken, even on latest docker:
|
I can no longer reproduce this issue starting with v0.2.56, waiting for review from maintainer timed out after 1 month. Available on
|
Issue is stale and will be closed in 14 days unless there is new activity |
Bug report info
Command used with act
Describe issue
docker image will not run with error:
Error: failed to start container: Error response from daemon: network-scoped alias is supported only for containers in user defined networks
It works fine when downgrading to 0.2.52
What I found: docker-archive/compose-cli#1619
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: