Docker build failed with exit code 100
See original GitHub issueBug Description I am using version 3.0.0 & it’s been working just fine. But today, I started getting error on every run. Its not working anymore. I also tried changing to version 3.1.1, the same thing is happening. Any idea how it can be solved?
My Action Log
E: The repository 'http://security.debian.org/debian-security stable/updates Release' does not have a Release file.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Docker build returns exit code 100
My operating system is Windows 10 Pro. In my case, I created a Dockerfile in Visual Studio and used that command. I changed...
Read more >apt-get update' returned a non-zero code: 100
I tried restarting docker, cleaning up all docker images, installing apt-transport-https , but nothing worked. I dont know whats wrong here.
Read more >Error: Docker build failed with exit code 100 · Issue #19
When using the ssh action I'm getting this error: E: The repository 'http://security.debian.org/debian-security stable/updates Release' does ...
Read more >"apt-get install" returns exit code 100 - Build Environment
Running a CircleCI build that has worked for many months but now decides to fail (with no changes made to it). The step...
Read more >apt update on ubuntu:22.04 results in error 100 on some ...
The problem host machine seems to have had a nonstandard build, ... the host machine's /etc/apt/sources.list.d/docker.list had a single line ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue should now be resolved. I’ve updated versions
3.0.0
,3.1.0
, and3.1.1
with a fix. Note, if the action has not run for several commits you will be behind your latest code. This means you will need to increase thefetch-depth
option so the action sees all the missed commits.If you see a “Uploading all files since no commit was found” message, that’s due to your commits being behind. This issue will also resolve itself, but requires a full deploy which can take a while.
Please update to the version
4.1.0
if you can. Thanks.Looks like
debian
published a new version “Debian 11 - bullseye” over the weekend. That’s the likely cause.Looking into this.