I have the following Dockerfile. FROM debian:10.7 ARG DEBIAN_FRONTEND=noninteractive RUN echo "Acquire::http::Proxy "${HTTP_PROXY}";" >> /etc/apt/apt.conf.d/50proxy && echo "Acquire::https::Proxy "${HTTPS_PROXY}";" >> /etc/apt/apt.conf.d/50proxy # Install coreutils, dialog, apt-utils since busybox seems to lack them RUN apt-get update && apt-get install -y coreutils…
I'm building a Docker image with Kaniko. I would like to use two separate private artifactories for my GitLab CI/CD pipeline: One from which the Dockerfile takes its source image (Artifactory1/Repo1) One to which the pipeline will push the ready…
Given a monorepo of ~35 services using a Gitlab-CI with k8s runners. The images are built using Kaniko, utilizing <job>.extends of a prototype template, and life is great. However, lately, we wanted to save a key on consul and change…
I was able to publish a Docker image using the jenkins pipeline, but not pull the docker image from the nexus.I used kaniko to build the image. deployment.yml apiVersion: apps/v1 kind: Deployment metadata: labels: app: test-app name: test-app namespace: jenkins…
The use case is such that I need both JDK and Mongo images in a single container, the java process starts up the Mongo daemon process.
I'm facing a pretty strange Problem. First of all my setup: I got a private Gitlab server which uses Gitlab CI Runners on Kubernetes to build Docker Images. For that purpose I use the Kaniko Image. The Runners are provisioned…