[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/lfdominguez/kaniko_with_git/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","lfdominguez","reponame","kaniko_with_git","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2021-04-19T15:15:21.228117Z","description","","is_private","last_updated","2021-04-19T16:35:47.919086Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",903,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# kaniko - Build Images In Kubernetes\n\n`NOTE: kaniko is not an officially supported Google product`\n\n[![Build Status](https://travis-ci.com/GoogleContainerTools/kaniko.svg?branch=master)](https://travis-ci.com/GoogleContainerTools/kaniko) [![Go Report Card](https://goreportcard.com/badge/github.com/GoogleContainerTools/kaniko)](https://goreportcard.com/report/github.com/GoogleContainerTools/kaniko)\n\n![kaniko logo](logo/Kaniko-Logo.png)\n\nkaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster.\n\nkaniko doesn't depend on a Docker daemon and executes each command within a Dockerfile completely in userspace.\nThis enables building container images in environments that can't easily or securely run a Docker daemon, such as a standard Kubernetes cluster.\n\nkaniko is meant to be run as an image: `gcr.io/kaniko-project/executor`. We do **not** recommend running the kaniko executor binary in another image, as it might not work.\n\nWe'd love to hear from you! Join us on [#kaniko Kubernetes Slack](https://kubernetes.slack.com/messages/CQDCHGX7Y/)\n\n:mega: **Please fill out our [quick 5-question survey](https://forms.gle/HhZGEM33x4FUz9Qa6)** so that we can learn how satisfied you are with kaniko, and what improvements we should make. Thank you! :dancers:\n\n\n_If you are interested in contributing to kaniko, see [DEVELOPMENT.md](DEVELOPMENT.md) and [CONTRIBUTING.md](CONTRIBUTING.md)._\n\n\n\n\n**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)*\n\n- [Community](#community)\n- [How does kaniko work?](#how-does-kaniko-work)\n- [Known Issues](#known-issues)\n- [Demo](#demo)\n- [Tutorial](#tutorial)\n- [Using kaniko](#using-kaniko)\n - [kaniko Build Contexts](#kaniko-build-contexts)\n - [Using Azure Blob Storage](#using-azure-blob-storage)\n - [Using Private Git Repository](#using-private-git-repository)\n - [Using Standard Input](#using-standard-input)\n - [Running kaniko](#running-kaniko)\n - [Running kaniko in a Kubernetes cluster](#running-kaniko-in-a-kubernetes-cluster)\n - [Kubernetes secret](#kubernetes-secret)\n - [Running kaniko in gVisor](#running-kaniko-in-gvisor)\n - [Running kaniko in Google Cloud Build](#running-kaniko-in-google-cloud-build)\n - [Running kaniko in Docker](#running-kaniko-in-docker)\n - [Caching](#caching)\n - [Caching Layers](#caching-layers)\n - [Caching Base Images](#caching-base-images)\n - [Pushing to Different Registries](#pushing-to-different-registries)\n - [Pushing to Docker Hub](#pushing-to-docker-hub)\n - [Pushing to Google GCR](#pushing-to-google-gcr)\n - [Pushing to Google GCR - Workload Identity](#pushing-to-google-gcr-using-workload-identity)\n - [Pushing to Amazon ECR](#pushing-to-amazon-ecr)\n - [Additional Flags](#additional-flags)\n - [--build-arg](#--build-arg)\n - [--cache](#--cache)\n - [--cache-dir](#--cache-dir)\n - [--cache-repo](#--cache-repo)\n - [--cache-ttl duration](#--cache-ttl-duration)\n - [--cleanup](#--cleanup)\n - [--context-sub-path](#--context-sub-path)\n - [--customPlatform](#--customPlatform)\n - [--digest-file](#--digest-file)\n - [--dockerfile](#--dockerfile)\n - [--force](#--force)\n - [--git](#--git)\n - [--image-name-with-digest-file](#--image-name-with-digest-file)\n - [--image-name-tag-with-digest-file](#--image-name-tag-with-digest-file)\n - [--insecure](#--insecure)\n - [--insecure-pull](#--insecure-pull)\n - [--insecure-registry](#--insecure-registry)\n - [--label](#--label)\n - [--log-format](#--log-format)\n - [--log-timestamp](#--log-timestamp)\n - [--no-push](#--no-push)\n - [--oci-layout-path](#--oci-layout-path)\n - [--push-retry](#--push-retry)\n - [--registry-certificate](#--registry-certificate)\n - [--registry-mirror](#--registry-mirror)\n - [--reproducible](#--reproducible)\n - [--single-snapshot](#--single-snapshot)\n - [--skip-tls-verify](#--skip-tls-verify)\n - [--skip-tls-verify-pull](#--skip-tls-verify-pull)\n - [--skip-tls-verify-registry](#--skip-tls-verify-registry)\n - [--skip-unused-stages](#--skip-unused-stages)\n - [--snapshotMode](#--snapshotmode)\n - [--tarPath](#--tarpath)\n - [--target](#--target)\n - [--use-new-run](#--use-new-run)\n - [--verbosity](#--verbosity)\n - [--whitelist-var-run](#--whitelist-var-run)\n - [--ignore-path](#--ignore-path)\n - [Debug Image](#debug-image)\n- [Security](#security)\n - [Verifying Signed Kaniko Images](#verifying-signed-kaniko-images)\n- [Comparison with Other Tools](#comparison-with-other-tools)\n- [Community](#community-1)\n- [Limitations](#limitations)\n - [mtime and snapshotting](#mtime-and-snapshotting)\n\n\n\n## Community\nWe'd love to hear from you! Join [#kaniko on Kubernetes Slack](https://kubernetes.slack.com/messages/CQDCHGX7Y/)\n\n## How does kaniko work?\n\nThe kaniko executor image is responsible for building an image from a Dockerfile and pushing it to a registry.\nWithin the executor image, we extract the filesystem of the base image (the FROM image in the Dockerfile).\nWe then execute the commands in the Dockerfile, snapshotting the filesystem in userspace after each one.\nAfter each command, we append a layer of changed files to the base image (if there are any) and update image metadata.\n\n## Known Issues\n\n* kaniko does not support building Windows containers.\n* Running kaniko in any Docker image other than the official kaniko image is not supported (ie YMMV).\n * This includes copying the kaniko executables from the official image into another image.\n* kaniko does not support the v1 Registry API ([Registry v1 API Deprecation](https://engineering.docker.com/2019/03/registry-v1-api-deprecation/))\n\n## Demo\n\n![Demo](/docs/demo.gif)\n\n## Tutorial\n\nFor a detailed example of kaniko with local storage, please refer to a [getting started tutorial](./docs/tutorial.md).\n\nPlease see [References](#References) for more docs & video tutorials\n\n## Using kaniko\n\nTo use kaniko to build and push an image for you, you will need:\n\n1. A [build context](#kaniko-build-contexts), aka something to build\n2. A [running instance of kaniko](#running-kaniko)\n\n### kaniko Build Contexts\n\nkaniko's build context is very similar to the build context you would send your Docker daemon for an image build; it represents a directory containing a Dockerfile which kaniko will use to build your image.\nFor example, a `COPY` command in your Dockerfile should refer to a file in the build context.\n\nYou will need to store your build context in a place that kaniko can access.\nRight now, kaniko supports these storage solutions:\n- GCS Bucket\n- S3 Bucket\n- Azure Blob Storage\n- Local Directory\n- Local Tar\n- Standard Input\n- Git Repository\n\n_Note about Local Directory: this option refers to a directory within the kaniko container.\nIf you wish to use this option, you will need to mount in your build context into the container as a directory._\n\n_Note about Local Tar: this option refers to a tar gz file within the kaniko container.\nIf you wish to use this option, you will need to mount in your build context into the container as a file._\n\n_Note about Standard Input: the only Standard Input allowed by kaniko is in `.tar.gz` format._\n\nIf using a GCS or S3 bucket, you will first need to create a compressed tar of your build context and upload it to your bucket.\nOnce running, kaniko will then download and unpack the compressed tar of the build context before starting the image build.\n\nTo create a compressed tar, you can run:\n\n```shell\ntar -C -zcvf context.tar.gz .\n```\nThen, copy over the compressed tar into your bucket.\nFor example, we can copy over the compressed tar to a GCS bucket with gsutil:\n\n```shell\ngsutil cp context.tar.gz gs://\n```\n\nWhen running kaniko, use the `--context` flag with the appropriate prefix to specify the location of your build context:\n\n| Source | Prefix | Example |\n| ------------------ | --------------------------------------------------------------------- | ----------------------------------------------------------------------------- |\n| Local Directory | dir://[path to a directory in the kaniko container] | `dir:///workspace` |\n| Local Tar Gz | tar://[path to a .tar.gz in the kaniko container] | `tar://path/to/context.tar.gz` |\n| Standard Input | tar://[stdin] | `tar://stdin` |\n| GCS Bucket | gs://[bucket name]/[path to .tar.gz] | `gs://kaniko-bucket/path/to/context.tar.gz` |\n| S3 Bucket | s3://[bucket name]/[path to .tar.gz] | `s3://kaniko-bucket/path/to/context.tar.gz` |\n| Azure Blob Storage | https://[account].[azureblobhostsuffix]/[container]/[path to .tar.gz] | `https://myaccount.blob.core.windows.net/container/path/to/context.tar.gz` |\n| Git Repository | git://[repository url][#reference][#commit-id] | `git://github.com/acme/myproject.git#refs/heads/mybranch#` |\n\nIf you don't specify a prefix, kaniko will assume a local directory.\nFor example, to use a GCS bucket called `kaniko-bucket`, you would pass in `--context=gs://kaniko-bucket/path/to/context.tar.gz`.\n\n### Using Azure Blob Storage\nIf you are using Azure Blob Storage for context file, you will need to pass [Azure Storage Account Access Key](https://docs.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) as an environment variable named `AZURE_STORAGE_ACCESS_KEY` through Kubernetes Secrets\n\n### Using Private Git Repository\nYou can use `Personal Access Tokens` for Build Contexts from Private Repositories from [GitHub](https://blog.github.com/2012-09-21-easier-builds-and-deployments-using-git-over-https-and-oauth/).\n\nYou can either pass this in as part of the git URL (e.g., `git://TOKEN@github.com/acme/myproject.git#refs/heads/mybranch`)\nor using the environment variable `GIT_TOKEN`.\n\nYou can also pass `GIT_USERNAME` and `GIT_PASSWORD` (password being the token) if you want to be explicit about the username.\n\n### Using Standard Input\nIf running kaniko and using Standard Input build context, you will need to add the docker or kubernetes `-i, --interactive` flag.\nOnce running, kaniko will then get the data from `STDIN` and create the build context as a compressed tar.\nIt will then unpack the compressed tar of the build context before starting the image build.\nIf no data is piped during the interactive run, you will need to send the EOF signal by yourself by pressing `Ctrl+D`.\n\nComplete example of how to interactively run kaniko with `.tar.gz` Standard Input data, using docker:\n```shell\necho -e 'FROM alpine \\nRUN echo \"created from standard input\"' > Dockerfile | tar -cf - Dockerfile | gzip -9 | docker run \\\n --interactive -v $(pwd):/workspace gcr.io/kaniko-project/executor:latest \\\n --context tar://stdin \\\n --destination=\n```\n\nComplete example of how to interactively run kaniko with `.tar.gz` Standard Input data, using Kubernetes command line with a temporary container and completely dockerless:\n```shell\necho -e 'FROM alpine \\nRUN echo \"created from standard input\"' > Dockerfile | tar -cf - Dockerfile | gzip -9 | kubectl run kaniko \\\n--rm --stdin=true \\\n--image=gcr.io/kaniko-project/executor:latest --restart=Never \\\n--overrides='{\n \"apiVersion\": \"v1\",\n \"spec\": {\n \"containers\": [\n {\n \"name\": \"kaniko\",\n \"image\": \"gcr.io/kaniko-project/executor:latest\",\n \"stdin\": true,\n \"stdinOnce\": true,\n \"args\": [\n \"--dockerfile=Dockerfile\",\n \"--context=tar://stdin\",\n \"--destination=gcr.io/my-repo/my-image\"\n ],\n \"volumeMounts\": [\n {\n \"name\": \"cabundle\",\n \"mountPath\": \"/kaniko/ssl/certs/\"\n },\n {\n \"name\": \"docker-config\",\n \"mountPath\": \"/kaniko/.docker/\"\n }\n ]\n }\n ],\n \"volumes\": [\n {\n \"name\": \"cabundle\",\n \"configMap\": {\n \"name\": \"cabundle\"\n }\n },\n {\n \"name\": \"docker-config\",\n \"configMap\": {\n \"name\": \"docker-config\"\n }\n }\n ]\n }\n}'\n```\n\n### Running kaniko\n\nThere are several different ways to deploy and run kaniko:\n\n- [In a Kubernetes cluster](#running-kaniko-in-a-kubernetes-cluster)\n- [In gVisor](#running-kaniko-in-gvisor)\n- [In Google Cloud Build](#running-kaniko-in-google-cloud-build)\n- [In Docker](#running-kaniko-in-docker)\n\n#### Running kaniko in a Kubernetes cluster\n\nRequirements:\n\n- Standard Kubernetes cluster (e.g. using [GKE](https://cloud.google.com/kubernetes-engine/))\n- [Kubernetes Secret](#kubernetes-secret)\n- A [build context](#kaniko-build-contexts)\n\n##### Kubernetes secret\n\nTo run kaniko in a Kubernetes cluster, you will need a standard running Kubernetes cluster and a Kubernetes secret, which contains the auth required to push the final image.\n\nTo create a secret to authenticate to Google Cloud Registry, follow these steps:\n1. Create a service account in the Google Cloud Console project you want to push the final image to with `Storage Admin` permissions.\n2. Download a JSON key for this service account\n3. Rename the key to `kaniko-secret.json`\n4. To create the secret, run:\n\n```shell\nkubectl create secret generic kaniko-secret --from-file=\n```\n\n_Note: If using a GCS bucket in the same GCP project as a build context, this service account should now also have permissions to read from that bucket._\n\nThe Kubernetes Pod spec should look similar to this, with the args parameters filled in:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n name: kaniko\nspec:\n containers:\n - name: kaniko\n image: gcr.io/kaniko-project/executor:latest\n args:\n - \"--dockerfile=\"\n - \"--context=gs:///\"\n - \"--destination=\"\n volumeMounts:\n - name: kaniko-secret\n mountPath: /secret\n env:\n - name: GOOGLE_APPLICATION_CREDENTIALS\n value: /secret/kaniko-secret.json\n restartPolicy: Never\n volumes:\n - name: kaniko-secret\n secret:\n secretName: kaniko-secret\n```\n\nThis example pulls the build context from a GCS bucket.\nTo use a local directory build context, you could consider using configMaps to mount in small build contexts.\n\n#### Running kaniko in gVisor\n\nRunning kaniko in [gVisor](https://github.com/google/gvisor) provides an additional security boundary.\nYou will need to add the `--force` flag to run kaniko in gVisor, since currently there isn't a way to determine whether or not a container is running in gVisor.\n\n```shell\ndocker run --runtime=runsc -v $(pwd):/workspace -v ~/.config:/root/.config \\\ngcr.io/kaniko-project/executor:latest \\\n--dockerfile= --context=/workspace \\\n--destination=gcr.io/my-repo/my-image --force\n```\n\nWe pass in `--runtime=runsc` to use gVisor.\nThis example mounts the current directory to `/workspace` for the build context and the `~/.config` directory for GCR credentials.\n\n#### Running kaniko in Google Cloud Build\n\nRequirements:\n- A [build context](#kaniko-build-contexts)\n\nTo run kaniko in GCB, add it to your build config as a build step:\n\n```yaml\nsteps:\n- name: gcr.io/kaniko-project/executor:latest\n args: [\"--dockerfile=\",\n \"--context=dir://\",\n \"--destination=\"]\n```\n\nkaniko will build and push the final image in this build step.\n\n#### Running kaniko in Docker\n\nRequirements:\n\n- [Docker](https://docs.docker.com/install/)\n\nWe can run the kaniko executor image locally in a Docker daemon to build and push an image from a Dockerfile.\n\nFor example, when using gcloud and GCR you could run kaniko as follows:\n```shell\ndocker run \\\n -v \"$HOME\"/.config/gcloud:/root/.config/gcloud \\\n -v /path/to/context:/workspace \\\n gcr.io/kaniko-project/executor:latest \\\n --dockerfile /workspace/Dockerfile \\\n --destination \"gcr.io/$PROJECT_ID/$IMAGE_NAME:$TAG\" \\\n --context dir:///workspace/\n```\n\nThere is also a utility script [`run_in_docker.sh`](./run_in_docker.sh) that can be used as follows:\n```shell\n./run_in_docker.sh \n```\n\n_NOTE: `run_in_docker.sh` expects a path to a\nDockerfile relative to the absolute path of the build context._\n\nAn example run, specifying the Dockerfile in the container directory `/workspace`, the build\ncontext in the local directory `/home/user/kaniko-project`, and a Google Container Registry\nas a remote image destination:\n\n```shell\n./run_in_docker.sh /workspace/Dockerfile /home/user/kaniko-project gcr.io/$PROJECT_ID/$TAG\n```\n\n### Caching\n\n#### Caching Layers\nkaniko can cache layers created by `RUN` and `Copy` (configured by flag `--cache-copy-layers`) commands in a remote repository.\nBefore executing a command, kaniko checks the cache for the layer.\nIf it exists, kaniko will pull and extract the cached layer instead of executing the command.\nIf not, kaniko will execute the command and then push the newly created layer to the cache.\n\nNote that kaniko cannot read layers from the cache after a cache miss: once a layer has not been found in the cache, all subsequent layers are built locally without consulting the cache.\n\nUsers can opt into caching by setting the `--cache=true` flag.\nA remote repository for storing cached layers can be provided via the `--cache-repo` flag.\nIf this flag isn't provided, a cached repo will be inferred from the `--destination` provided.\n\n#### Caching Base Images\n\nkaniko can cache images in a local directory that can be volume mounted into the kaniko pod.\nTo do so, the cache must first be populated, as it is read-only. We provide a kaniko cache warming\nimage at `gcr.io/kaniko-project/warmer`:\n\n```shell\ndocker run -v $(pwd):/workspace gcr.io/kaniko-project/warmer:latest --cache-dir=/workspace/cache --image= --image=\n```\n\n`--image` can be specified for any number of desired images.\nThis command will cache those images by digest in a local directory named `cache`.\nOnce the cache is populated, caching is opted into with the same `--cache=true` flag as above.\nThe location of the local cache is provided via the `--cache-dir` flag, defaulting to `/cache` as with the cache warmer.\nSee the `examples` directory for how to use with kubernetes clusters and persistent cache volumes.\n\n### Pushing to Different Registries\n\nkaniko uses Docker credential helpers to push images to a registry.\n\nkaniko comes with support for GCR, Docker `config.json` and Amazon ECR, but configuring another credential helper should allow pushing to a different registry.\n\n#### Pushing to Docker Hub\n\nGet your docker registry user and password encoded in base64\n\n echo -n USER:PASSWORD | base64\n\nCreate a `config.json` file with your Docker registry url and the previous generated base64 string\n\n**Note:** Please use v1 endpoint. See #1209 for more details\n\n```\n{\n\t\"auths\": {\n\t\t\"https://index.docker.io/v1/\": {\n\t\t\t\"auth\": \"xxxxxxxxxxxxxxx\"\n\t\t}\n\t}\n}\n```\n\nRun kaniko with the `config.json` inside `/kaniko/.docker/config.json`\n\n docker run -ti --rm -v `pwd`:/workspace -v `pwd`/config.json:/kaniko/.docker/config.json:ro gcr.io/kaniko-project/executor:latest --dockerfile=Dockerfile --destination=yourimagename\n\n#### Pushing to Google GCR\n\nTo create a credentials to authenticate to Google Cloud Registry, follow these steps:\n1. Create a [service account](https://console.cloud.google.com/iam-admin/serviceaccounts) or in the Google Cloud Console project you want to push the final image to with `Storage Admin` permissions.\n2. Download a JSON key for this service account\n3. (optional) Rename the key to `kaniko-secret.json`, if you don't rename, you have to change the name used the command(in the volume part)\n4. Run the container adding the path in GOOGLE_APPLICATION_CREDENTIALS env var\n\n```shell\ndocker run -ti --rm -e GOOGLE_APPLICATION_CREDENTIALS=/kaniko/config.json \\\n-v `pwd`:/workspace -v `pwd`/kaniko-secret.json:/kaniko/config.json:ro gcr.io/kaniko-project/executor:latest \\\n--dockerfile=Dockerfile --destination=yourimagename\n```\n\n#### Pushing to GCR using Workload Identity\nIf you have enabled Workload Indentity on your GKE cluster then you can use the workload identity to push built images to GCR without adding a `GOOGLE_APPLICATION_CREDENTIALS` in your kaniko pod specification.\n\nLearn more on how to [enable](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#enable_on_cluster) and [migrate existing apps](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#migrate_applications_to) to workload identity.\n\nTo authenticate using workload identity you need to run the kaniko pod using the Kubernetes Service Account (KSA) bound to Google Service Account (GSA) which as `Storage.Admin` permissions to push images to Google Container registry.\n\nPlease follow the detailed steps [here](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#authenticating_to) to create a Kubernetes Service Account, Google Service Account and create an IAM policy binding between the two to allow the Kubernetes Service account to act as the Google service account.\n\n\nTo grant the Google Service account the right permission to push to GCR, run the following GCR command\n```\ngcloud projects add-iam-policy-binding $PROJECT \\\n --member=serviceAccount:[gsa-name]@${PROJECT}.iam.gserviceaccount.com \\\n --role=roles/storage.objectAdmin\n```\n\nPlease ensure, kaniko pod is running in the namespace and with Kubernetest Service Account.\n\n\n#### Pushing to Amazon ECR\n\nThe Amazon ECR [credential helper](https://github.com/awslabs/amazon-ecr-credential-helper) is built into the kaniko executor image.\nTo configure credentials, you will need to do the following:\n\n1. Update the `credsStore` section of [config.json](https://github.com/awslabs/amazon-ecr-credential-helper#configuration):\n\n ```json\n { \"credsStore\": \"ecr-login\" }\n ```\n\n You can mount in the new config as a configMap:\n\n ```shell\n kubectl create configmap docker-config --from-file=\n ```\n\n2. Configure credentials\n\n 1. You can use instance roles when pushing to ECR from a EC2 instance or from EKS, by [configuring the instance role permissions](https://docs.aws.amazon.com/AmazonECR/latest/userguide/ECR_on_EKS.html).\n\n 2. Or you can create a Kubernetes secret for your `~/.aws/credentials` file so that credentials can be accessed within the cluster.\n To create the secret, run:\n ```shell\n kubectl create secret generic aws-secret --from-file=\n ```\n\nThe Kubernetes Pod spec should look similar to this, with the args parameters filled in.\nNote that `aws-secret` volume mount and volume are only needed when using AWS credentials from a secret, not when using instance roles.\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n name: kaniko\nspec:\n containers:\n - name: kaniko\n image: gcr.io/kaniko-project/executor:latest\n args:\n - \"--dockerfile=\"\n - \"--context=s3:///\"\n - \"--destination=\"\n volumeMounts:\n - name: docker-config\n mountPath: /kaniko/.docker/\n # when not using instance role\n - name: aws-secret\n mountPath: /root/.aws/\n restartPolicy: Never\n volumes:\n - name: docker-config\n configMap:\n name: docker-config\n # when not using instance role\n - name: aws-secret\n secret:\n secretName: aws-secret\n```\n\n### Additional Flags\n\n#### --build-arg\n\nThis flag allows you to pass in ARG values at build time, similarly to Docker.\nYou can set it multiple times for multiple arguments.\n\n#### --cache\n\nSet this flag as `--cache=true` to opt into caching with kaniko.\n\n#### --cache-dir\n\nSet this flag to specify a local directory cache for base images. Defaults to `/cache`.\n\n_This flag must be used in conjunction with the `--cache=true` flag._\n\n#### --cache-repo\n\nSet this flag to specify a remote repository that will be used to store cached layers.\n\nIf this flag is not provided, a cache","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",25891598,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",5087106,"full_size",25882650,"id",146171700,"images",[97],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},"architecture","amd64","digest","sha256:bb566f50cc215b8adbaebef92bd2d44f7118dbbb883a9ae021fea5d7b2502978","features","last_pulled","2026-09-23T13:24:52.148410176Z","last_pushed","2021-04-19T16:35:48Z","os","linux","os_features","os_version","size","variant","2021-04-19T16:35:47.602675Z","last_updater","last_updater_username","media_type","latest","repository",12481619,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":11,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

lfdominguez/kaniko_with_git

Tags for lfdominguez/kaniko_with_git