Open edib opened 1 week ago
https://github.com/GoogleContainerTools/kaniko#known-issues
Running kaniko in any Docker image other than the official kaniko image is not supported due to implementation details.
Specifically it is not sufficient to copy the kaniko binary. kaniko depends on the entire filetree being in its expected state. This is not so much a "known issue" but a fundamental design constraint when building an image inside your own container.
Actual behavior A clear and concise description of what the bug is. I have a custom kaniko image that combines Kaniko and git and in gitlab-ci pipeline after kaniko being executed brokes its building container library dependencies. $ git config --global user.email "gitlab-ci@mydomain.com" && git config --global user.name "Gitlab-ci" git: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by git)
Expected behavior A clear and concise description of what you expected to happen. above command should run
To Reproduce Steps to reproduce the behavior:
Additional Information
FROM dotnet-sdk:6.0.1-nuget
RUN apt-get update && \ apt-get install -y git \ apt-get clean && \ rm -rf /var/lib/apt/lists/*
COPY --from=kaniko /kaniko/executor /kaniko/executor COPY --from=kaniko /etc/nsswitch.conf /etc/nsswitch.conf COPY --from=kaniko /kaniko/.docker /kaniko/.docker
RUN dotnet tool install --global dotnet-sonarscanner