Docker build fails
See original GitHub issueSo, I am failing to build the docker image from the master branch. Following is the the simple steps to reproduce the problem along with the resulting error message.
Steps to reproduce
git clone https://github.com/zalando/spilo.git
cd spilo/postgres-appliance
./build.sh --build-arg COMPRESS=true --tag my_tag .
Error message
+ apt-get source pgbouncer
Reading package lists...
NOTICE: 'pgbouncer' packaging is maintained in the 'Git' version control system at:
https://salsa.debian.org/postgresql/pgbouncer.git
Please use:
git clone https://salsa.debian.org/postgresql/pgbouncer.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 579 kB of source archives.
Get:1 http://apt.postgresql.org/pub/repos/apt bionic-pgdg/main pgbouncer 1.12.0-1.pgdg18.04+1 (dsc) [1400 B]
Get:2 http://apt.postgresql.org/pub/repos/apt bionic-pgdg/main pgbouncer 1.12.0-1.pgdg18.04+1 (tar) [567 kB]
Get:3 http://apt.postgresql.org/pub/repos/apt bionic-pgdg/main pgbouncer 1.12.0-1.pgdg18.04+1 (diff) [10.1 kB]
dpkg-source: info: extracting pgbouncer in pgbouncer-1.12.0
dpkg-source: info: unpacking pgbouncer_1.12.0.orig.tar.gz
dpkg-source: info: unpacking pgbouncer_1.12.0-1.pgdg18.04+1.debian.tar.xz
dpkg-source: info: applying debian-config
dpkg-source: info: applying python3
dpkg-source: info: applying no-sudo
W: Download is performed unsandboxed as root as file 'pgbouncer_1.12.0-1.pgdg18.04+1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
Fetched 579 kB in 1s (433 kB/s)
+ ls -d pgbouncer-1.12.0
+ cd pgbouncer-1.12.0
+ + sed -n /^diff --git a\/src\/client.c b\/src\/client.c/,$ p
patch -p1
+ curl -sL https://github.com/pgbouncer/pgbouncer/pull/326.diff
patching file src/client.c
Hunk #1 FAILED at 246.
Hunk #2 succeeded at 288 (offset 2 lines).
Hunk #3 succeeded at 303 with fuzz 2 (offset 2 lines).
1 out of 3 hunks FAILED -- saving rejects to file src/client.c.rej
patching file src/hba.c
The command '/bin/sh -c export DEBIAN_FRONTEND=noninteractive
... removed for briefness! ...
&& find /var/log -type f -exec truncate --size 0 {} \;' returned a non-zero code: 1
Am I missing something?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to debug build failures - Docker Community Forums
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 >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 >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 >Docker build failures - GoReleaser
This usually happens when trying to build the binary again from source code in the Docker image build process. The way GoReleaser works,...
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
Building from a different commit won’t work either. I’ll fix it tomorrow.
If you like please try https://github.com/zalando/spilo/tree/feature/pg12, there it’s already fixed.