question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dockerfile failing to build again

See original GitHub issue

Builds worked on Sunday after the updates, but failed yesterday and today.

Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [29.4 kB]
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [61.3 kB]
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [82.3 kB]
Fetched 20.6 MB in 2s (10.5 MB/s)
Reading package lists...
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
The command '/bin/sh -c apt-get update && apt-get -y install   curl   gnupg   nodejs   npm &&   apt-get install -f &&   apt-get autoremove --purge &&   apt-get autoremove &&   apt-get clean &&   npm config set strict-ssl false &&   npm install -g @angular/cli' returned a non-zero code: 100
exit status 100

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:13 (1 by maintainers)

github_iconTop GitHub Comments

2reactions
samcro1967commented, May 4, 2022

No rush on my part. I am using a previous image that is working fine and stopped my CI/CD pipeline and nightly updates for this image so I am stable as you work toward 4.3. Figured you would want some feedback from folks trying the updates out in the wild.

1reaction
samcro1967commented, May 6, 2022

It looks like there are a couple of ways to do multistage with Drone. Agreed though it should be supported more natively and out of the box without jumping through extra steps.

I ran the build this morning (forgot to disable daily rebuilds) and it completed successfully, but I did not try to run it to validate the image created works successfully. So the changes to Dockerfile over the last couple of days seem to have at least the build working again in my environment.

How to effectively use cached layers for docker build steps?

Option 1 - caching layer The ultimate DroneCI caching guide

Options 2 - Host Docker daemon Interact directly with the host machine docker daemon

Read more comments on GitHub >

github_iconTop Results From Across the Web

How can I inspect the file system of a failed `docker build`?
The best solution I have found is to make sure that each step that does real work succeeds, and adding a check after...
Read more >
How to debug build failures - DockerEngine
I've written a guide on how to debug docker builds like that. In short, look at the container ID of the failed step,...
Read more >
How to debug Docker build failures - /admcpr
When a docker build is failing for me I find that a great way to understand what's causing the failure is to jump...
Read more >
debugging a failed docker build (intermediate) anthony ...
today we talk about two techniques for debugging a failed docker build !- how does docker work? https://youtu.be/tWvQAxkMaWsplaylist: ...
Read more >
Where's that log file? Debugging failed Docker builds
Your Docker build just failed, and the reason is buried a log file—which is somewhere inside the build process. How do you read...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found