Kaniko: Multistage COPY fails `gcr.io/kaniko-project/executor:debug`

Created on 23 May 2020 · 5Comments · Source: GoogleContainerTools/kaniko

I just tested with gcr.io/kaniko-project/executor:debug

#: Dockerfile
FROM python:3.7.7-slim-buster as part-one
RUN set -x \
    && python -m venv /venv
RUN ls -l /venv

FROM python:3.7.7-slim-buster
COPY --from=part-one /venv /venv
RUN ls -l /venv

It's failing.

INFO[0016] args: [-c ls -l /venv]
ls: cannot access '/venv': No such file or directory
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 2

_Originally posted by @dmilan77 in https://github.com/GoogleContainerTools/kaniko/issues/1110#issuecomment-632946871_

Source

dmilan77

Most helpful comment

Do you by chance have a .dockerignore file?

There seems to be a recent regression where the .dockerignore is read during multi-stage builds so the files are ignored when the copy takes place.

I use a .dockerignore in whiltelist mode and this caught me out as as well.

MAHDTech on 23 May 2020

👍3

All 5 comments

Do you by chance have a .dockerignore file?

There seems to be a recent regression where the .dockerignore is read during multi-stage builds so the files are ignored when the copy takes place.

I use a .dockerignore in whiltelist mode and this caught me out as as well.

MAHDTech on 23 May 2020

👍3

Do you by chance have a .dockerignore file?

There seems to be a recent regression where the .dockerignore is read during multi-stage builds so the files are ignored when the copy takes place.

I use a .dockerignore in whiltelist mode and this caught me out as as well.

It did the trick. Seems still a bug.

dmilan77 on 23 May 2020

Same case here, using .dockerignore in whitelist mode, either removing the .dockerignore or setting it to * right before the building may be a workaround while this is solved