You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I acknowledged that Kaniko already mentioned "Running kaniko in any Docker image other than the official kaniko image is not supported due to implementation details".
I'm trying to achieve this for GitLab Runner to build container images with Kaniko.
There is no issues for the container image which built on my laptop.
However, when my GitLab runner execute the same command on the same container image (GitLab Runner + Kaniko) on AWS ECS (Fargate Task). I noticed that there is no installation logs of the step.
INFO[2025-02-11T03:42:15Z] Taking snapshot of full filesystem...
INFO[2025-02-11T03:42:15Z] RUN apk upgrade --no-cache && apk add --no-cache openssh git git-lfs ca-certificates envsubst && ssh-keygen -A && sed -i -e 's/^#HostKey/HostKey/g' /etc/ssh/sshd_config && sed -i -e 's/^#Port 22/Port 22/g' /etc/ssh/sshd_config && sed -i -e 's/^#PubkeyAuthentication yes/PubkeyAuthentication yes/g' /etc/ssh/sshd_config && sed -i -e 's/^#PasswordAuthentication yes/PasswordAuthentication no/g' /etc/ssh/sshd_config && sed -i -e 's/^AuthorizedKeysFile\t.ssh/authorized_keys/AuthorizedKeysFile\t%h/.ssh/authorized_keys/g' /etc/ssh/sshd_config
INFO[2025-02-11T03:42:15Z] Cmd: /bin/sh
INFO[2025-02-11T03:42:15Z] Args: [-c apk upgrade --no-cache && apk add --no-cache openssh git git-lfs ca-certificates envsubst && ssh-keygen -A && sed -i -e 's/^#HostKey/HostKey/g' /etc/ssh/sshd_config && sed -i -e 's/^#Port 22/Port 22/g' /etc/ssh/sshd_config && sed -i -e 's/^#PubkeyAuthentication yes/PubkeyAuthentication yes/g' /etc/ssh/sshd_config && sed -i -e 's/^#PasswordAuthentication yes/PasswordAuthentication no/g' /etc/ssh/sshd_config && sed -i -e 's/^AuthorizedKeysFile\t.ssh/authorized_keys/AuthorizedKeysFile\t%h/.ssh/authorized_keys/g' /etc/ssh/sshd_config]
INFO[2025-02-11T03:42:15Z] Running: [/bin/sh -c apk upgrade --no-cache && apk add --no-cache tini openssh git git-lfs ca-certificates envsubst && ssh-keygen -A && sed -i -e 's/^#HostKey/HostKey/g' /etc/ssh/sshd_config && sed -i -e 's/^#Port 22/Port 22/g' /etc/ssh/sshd_config && sed -i -e 's/^#PubkeyAuthentication yes/PubkeyAuthentication yes/g' /etc/ssh/sshd_config && sed -i -e 's/^#PasswordAuthentication yes/PasswordAuthentication no/g' /etc/ssh/sshd_config && sed -i -e 's/^AuthorizedKeysFile\t.ssh/authorized_keys/AuthorizedKeysFile\t%h/.ssh/authorized_keys/g' /etc/ssh/sshd_config]
INFO[2025-02-11T03:42:17Z] Taking snapshot of full filesystem...
Other libraries look good except tini. Normally, it will installed in /sbin
Yeah, I have noticed a similar thing. Multiple invocations with different AWS credentials lead to broken images. The first build correctly installs the required Ubuntu packages but subsequent builds seem to exclude them
Hello, I acknowledged that Kaniko already mentioned "Running kaniko in any Docker image other than the official kaniko image is not supported due to implementation details".
I'm trying to achieve this for GitLab Runner to build container images with Kaniko.
Here is the example Dockerfile, https://github.com/aws-samples/cdk-fargate-gitlab-runner/blob/main/docker_images/kaniko/Dockerfile.
I extracted a part from my Dockerfile
Here is the build logs on my laptop.
There is no issues for the container image which built on my laptop.
However, when my GitLab runner execute the same command on the same container image (GitLab Runner + Kaniko) on AWS ECS (Fargate Task). I noticed that there is no installation logs of the step.
Other libraries look good except tini. Normally, it will installed in
/sbin
apk is showing tini is installed but no executable file in /sbin path.
Could you please guide me what could be the cause of this issue?
My base image in Dockerfile is alpine:3.21, and the architecture is arm64.
The text was updated successfully, but these errors were encountered: