Closed cgwalters closed 5 years ago
@TomSweeneyRedHat PTAL
I've a strong suspicion that this is the same issue as: https://github.com/containers/buildah/issues/1578
@TomSweeneyRedHat if you replicate this, just connect to the pid with dlv and you will know right away whats going on ... if you need help with this one, let me know.
@baude given the other irons in the fire that I have atm and my suspicion that @nalind has a fix in flight, I'll most likely wait until early next week to check in with him when he returns.
This is definitely a regression, works fine with podman-1.3.1-1.git7210727.fc30.x86_64
.
@TomSweeneyRedHat We're not expecting a fix for this in the Buildah revendor tomorrow, right?
@mheon, unless the Buildah Fix Fairy swings by, I'm not suspecting this will be fixed for 1.8.4
Alright, Podman 1.5.0 it is, then.
The first of the two dots in the Copy command seem to be the issue. If I change that first dot to a file or even an '*' (asterisk), it seems to work. Smaller reproducer:
# cat ~/Dockerfile.copyhang
FROM alpine
WORKDIR /tmp
COPY . .
# buildah bud --layers -t tom -f Dockerfile.copyhang .
@cgwalters if you have a chance, can you try running your build command with --log-level debug
added? podman --log-level debug build ...
? Adding that seems to make things work for me and I'm not quite understanding why ATM.
@cgwalters @TomSweeneyRedHat any updates fellas?
Lets say this is fixed in podman 1.5, and reopen if I am mistaken.
Did a test with rootless and
$ rpm -q podman
podman-1.5.1-3.fc30.x86_64
and yeah, seems to work now.
/kind bug
Steps to reproduce the issue:
git clone https://github.com/openshift/machine-config-operator/
podman build -t localhost/machine-config-server:latest -f Dockerfile.machine-config-server --no-cache
Describe the results you received:
Indefinite hang at
STEP 3: COPY . .
Describe the results you expected:
Successful build.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
physical