I've been seeing this error quite often lately. Re-running the tests sometimes fixes the issue but other times it takes multiple re-runs to get it to pass. Any ideas????
[ERROR] DOCKER> Unable to build image [gdcc/configbaker:unstable] : "The command '/bin/bash -eu -c true && mkdir -p ${SCRIPT_DIR} ${SECRETS_DIR} ${SOLR_TEMPLATE} && apt-get update -q && apt-get install -qqy --no-install-recommends ${PKGS} && apt -qqy --no-install-recommends install python3 python3-venv pipx && pipx install pipx && apt purge -qqy --autoremove pipx && ~/.local/bin/pipx install --global pipx && rm -rf \"~/.local\" && rm -rf \"/var/lib/apt/lists/\" \"/var/cache/apt/archives/\"' returned a non-zero code: 100" ["The command '/bin/bash -eu -c true && mkdir -p ${SCRIPT_DIR} ${SECRETS_DIR} ${SOLR_TEMPLATE} && apt-get update -q && apt-get install -qqy --no-install-recommends ${PKGS} && apt -qqy --no-install-recommends install python3 python3-venv pipx && pipx install pipx && apt purge -qqy --autoremove pipx && ~/.local/bin/pipx install --global pipx && rm -rf \"~/.local\" && rm -rf \"/var/lib/apt/lists/\" \"/var/cache/apt/archives/\"' returned a non-zero code: 100" ]
100 generally means that the issue is happening within the apt commands.
But for better monitoring, it might be a good idea to decouple that single command into multiple steps and enable logging/monitoring
Phil mentioned it here: #containers > Unable to build image [gdcc/configbaker:unstable]
Thanks, I was going to mention that other topic. Actually. I'll just merge them into one. It's the same topic, really.
5 messages were moved here from #containers > Unable to build image [gdcc/configbaker:unstable] by Philip Durbin ๐.
Ok. Combined.
@Steven Winship like @Ash Manda is saying, last time it was an ephemeral problem.
@Oliver Bertuch any thoughts on this?
I just added it to our next container meeting agenda, at least.
Last updated: Aug 18 2026 at 08:27 UTC