bthj opened a new issue #1376: Local insecure registry declared but not used - integration installations fail URL: https://github.com/apache/camel-k/issues/1376 Installing Camel K to a local MicroK8s cluster with ``` kamel install --registry-insecure true --registry localhost:32000 --kaniko-build-cache=false --force --wait --example ``` successfully installs the camel-k-operator but the example integration installed with the `--example` flag fails to build, with those messages: ``` $ kubectl logs -f camel-k-kit-bpu91bq2032o5jv6daig-builder STEP 1: FROM adoptopenjdk/openjdk8:slim Getting image source signatures Copying blob sha256:24e9ea251047e2f8f6e81eee2c7468307906b95d988f92039c6e13a6d764ae3e Copying blob sha256:f11b29a9c7306674a9479158c1b4259938af11b97359d9ac02030cc1095e9ed1 Copying blob sha256:5bed26d33875e6da1d9ff9a1054c5fef3bbeb22ee979e14b72acf72528de007b Copying blob sha256:930bda195c84cf132344bf38edcad255317382f910503fef234a9ce3bff0f4dd Copying blob sha256:022f48766a856d5901451ec6d39fd887807f9c3fa64dd45dabaa935ba70561e7 Copying blob sha256:78bf9a5ad49e4ae42a83f4995ade4efc096f78fd38299cf05bc041e8cdda2a36 Copying blob sha256:0a5ab47c17c313991b8420037ab81f08ca958498b4331e2a352e530019f42b05 Copying config sha256:2d20634b71d274c9aa0c13463b0c92f177cc8a5b1ee5e5947f8b14e2045ba014 Writing manifest to image destination Storing signatures level=error msg="Error while applying layer: ApplyLayer exit status 1 stdout: stderr: permission denied" error creating build container: The following failures happened while trying to pull image specified by "adoptopenjdk/openjdk8:slim" based on search registries in /etc/containers/registries.conf: * "localhost/adoptopenjdk/openjdk8:slim": Error initializing source docker://localhost/adoptopenjdk/openjdk8:slim: error pinging docker registry localhost: Get http://localhost/v2/: dial tcp [::1]:80: connect: connection refused * "docker.io/adoptopenjdk/openjdk8:slim": Error committing the finished image: error adding layer with blob "sha256:5bed26d33875e6da1d9ff9a1054c5fef3bbeb22ee979e14b72acf72528de007b": ApplyLayer exit status 1 stdout: stderr: permission denied * "registry.fedoraproject.org/adoptopenjdk/openjdk8:slim": Error initializing source docker://registry.fedoraproject.org/adoptopenjdk/openjdk8:slim: Error reading manifest slim in registry.fedoraproject.org/adoptopenjdk/openjdk8: manifest unknown: manifest unknown * "registry.access.redhat.com/adoptopenjdk/openjdk8:slim": Error initializing source docker://registry.access.redhat.com/adoptopenjdk/openjdk8:slim: Error reading manifest slim in registry.access.redhat.com/adoptopenjdk/openjdk8: name unknown: Repo not found * "registry.centos.org/adoptopenjdk/openjdk8:slim": Error initializing source docker://registry.centos.org/adoptopenjdk/openjdk8:slim: Error reading manifest slim in registry.centos.org/adoptopenjdk/openjdk8: manifest unknown: manifest unknown * "quay.io/adoptopenjdk/openjdk8:slim": Error initializing source docker://quay.io/adoptopenjdk/openjdk8:slim: Error reading manifest slim in quay.io/adoptopenjdk/openjdk8: unauthorized: access to the requested resource is not authorized level=error msg="exit status 1" ``` MicroK8s' built-in registry is referenced in the `kamel install` command with the flags `--registry-insecure true --registry localhost:32000` and that registry has proven to be up and running properly for other deployments. According to the log output, the registry declared with the installation flags isn't being called, but rather `http://localhost/v2/`(so not localhost on port 32000 as desired). Is there something I need to add to the Camel K installation command?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
