Skip to content
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

firmware-action fails when running offline #448

Closed
AtomicFS opened this issue Nov 28, 2024 · 0 comments · Fixed by #453
Closed

firmware-action fails when running offline #448

AtomicFS opened this issue Nov 28, 2024 · 0 comments · Fixed by #453
Labels
bug Something isn't working docker docker related go Pull requests that update Go code good_first_issue Good for newcomers low_priority Not very important quality_of_life Improve usage

Comments

@AtomicFS
Copy link
Collaborator

When firmware-action is executed without internet connection, it fails to fetch the contianer (even though it is already present locally) and fails the whole build.

- error: input: container.from resolve: failed to resolve image ghcr.io/9elements/firmware-action/udk2017:v0.8.0: failed to resolve source metadata for ghcr.io/9elements/firmware-action/udk2017:v0.8.0: failed to do request: Head "https://ghcr.io/v2/9elements/firmware-action/udk2017/manifests/v0.8.0": dial tcp: lookup ghcr.io: i/o timeout

This error should not cause firmware-action to fail all together, at most it should give a warning and carry on if there is a container already present.

@AtomicFS AtomicFS added bug Something isn't working good_first_issue Good for newcomers docker docker related go Pull requests that update Go code low_priority Not very important quality_of_life Improve usage labels Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working docker docker related go Pull requests that update Go code good_first_issue Good for newcomers low_priority Not very important quality_of_life Improve usage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant