kaniko icon indicating copy to clipboard operation
kaniko copied to clipboard

Build Container Images In Kubernetes

Results 466 kaniko issues
Sort by recently updated
recently updated
newest added

**Actual behavior** Error while retrieving image from cache: golang:1.17-alpine strict validation requires the registry to be explicitly defined **Expected behavior** No error like with the 1.6 release. **To Reproduce** Steps...

area/caching
priority/p1
priority/p2
area/registry
regression
fixed-needs-verfication
regression/v1.6.0

Hello, as of now I could see kaniko supports GitHub PAT for authentication but this is discouraged in many organisations rather they advise to use GitHub App. Is it supported...

kind/question
kind/feature-request
priority/p3
area/registry
area/authentication

For more details see https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/syntax.md That would help avoiding contortions in the Dockerfile due to COPY's silly "partial flattening" of file hierarchies... Also for performance some of the other types...

kind/enhancement
kind/feature-request
area/dockerfile-command
priority/p1
priority/p0
works-with-docker
differs-from-docker
issue/mount
feat/docker-syntax
categorized

The OCI spec [recently](https://github.com/opencontainers/image-spec/pull/822/) added specification for two new standard annotations, to facilitate pointing to a base image: > * **org.opencontainers.image.base.digest** [Digest](descriptor.md#digests) of the image this image is based on...

kind/feature-request
priority/p3
area/usability
needs-discussion
feat/oci

I have a use case where I want to build from a git repo with Kaniko. However, I have some git repos that have several projects in subdirectories with a...

kind/enhancement
priority/p2
area/context

Kaniko can work without needing to fetch the remote context itself. This would open the workflow to non-GCS remote contexts. 1. Init container with with whatever auth helpers needed (gcloud,...

help wanted
kind/feature-request
area/documentation
area/usability

I am trying to use Kaniko to build a multi-stage image within a Gitlab-CI pipeline. The pipeline crashes with the following, rather unhelpful message: `ERROR: Job failed: pod "runner-" status...

kind/bug
area/multi-stage builds
area/performance
priority/p1
area/behavior
priority/p0
gitlab
area/layers
differs-from-docker
kind/friction
issue/oom
issue/build-fails
issue/big-image
area/snapshotting
categorized

Fixes #2423 #2713 #2883 **Description** given base image `ubuntu:22.04` with oci format: $ crane manifest ubuntu@sha256:0eb0f877e1c869a300c442c41120e778db7161419244ee5cbc6fa5f134e74736 | jq ```json { "schemaVersion": 2, "mediaType": "application/vnd.oci.image.manifest.v1+json", "config": { "mediaType": "application/vnd.oci.image.config.v1+json", "size": 2297,...

2 months ago with below set up, kaniko was able to grab the credentials from CICD runner to run bundle install that contains private repos. It used CI gitlab self...

work-around-available
priority/p1
area/filesystems
area/registry
regression
area/env-variable
gitlab
area/authentication
area/credentials

**Actual behavior** In gitlab, kaniko obtains the manifest of an image, but fails to obtain the image from GCR. **Expected behavior** In gitlab, kaniko obtains the image from GCR. **To...