Mason Huemmer
Mason Huemmer
Appending `docker login` helped me resolve my issue. ``` printf "%s" "${DOCKER_PASSWORD}" | docker login -u ${DOCKER_USERNAME} --password-stdin ${DOCKER_REGISTRY} ```
Here is the script I run to generate my config.json. ```yaml - CREDENTIALS=$(echo -n ${DOCKER_USERNAME}:${DOCKER_PASSWORD} | base64) - echo "{\"auths\":{\"https://index.docker.io/v1/\":{\"auth\":\"${CREDENTIALS}\"}}}" > /kaniko/.docker/config.json ```
After I removed the multi-stage build in the Dockerfile, I was able to push to the repository. Does Kaniko not support multi-stage builds or does it have issues with multi-stage...
Even setting "tag" to a static value (e.g. 1.0.0), the "branch" name is still getting applied as a tag.
Any progress made on this issue?
Any update to this ticket?
Any update?
Any update?
Experiencing the same issue. It looks to be an issue with the Community Catalog. It creates a job to unpack the bundle, however the pod cannot be scheduled as the...
Any update on this?