Open zanieb opened 3 months ago
I've tried things like...
❯ gd main -- base.Dockerfile
diff --git a/cpython-unix/base.Dockerfile b/cpython-unix/base.Dockerfile
index 76811a5..0401a9a 100644
--- a/cpython-unix/base.Dockerfile
+++ b/cpython-unix/base.Dockerfile
@@ -22,7 +22,8 @@ WORKDIR '/build'
RUN for s in debian_jessie debian_jessie-updates debian-security_jessie/updates; do \
echo "deb [trusted=yes] http://snapshot.debian.org/archive/${s%_*}/20230322T152120Z/ ${s#*_} main"; \
done > /etc/apt/sources.list && \
- ( echo 'quiet "true";'; \
+ ( echo 'Debug::Acquire::http "true";'; \
+ echo 'Debug::pkgAcquire::Worker "true";'; \
echo 'APT::Get::Assume-Yes "true";'; \
echo 'APT::Install-Recommends "false";'; \
echo 'Acquire::Check-Valid-Until "false";'; \
@@ -33,4 +34,4 @@ RUN ( echo 'amd64'; \
echo 'i386'; \
) > /var/lib/dpkg/arch
-RUN apt-get update
+RUN apt-get update 2>&1 | tee /tmp/output.txt
to get my hands on output from apt
, works great with docker build
but not with the build spawned by ensure_docker_image
.
I'm seeing extremely slow container builds on Linux that hang at 100% CPU during
apt-get update
. I see very little network IO, disk IO, and memory consumption. I've let it run for >30 minutes to no avail.Specifically, it looks like this is occurring for the
image-gcc
,image-xcb
, andimage-build
targets.I can't figure out how to get verbose output from
apt
here, any recommendations would be helpful I've been spinning my wheels on it for a while.Is it possible I'm misinterpreting the output?
e.g.
I can
docker build
a derived Dockerfile likewith no issues.