You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/08/17 08:40:40 UTC
[GitHub] [camel-k] jeremie-H edited a comment on issue #1661: Unable to install camel-k with Google Kubernetes Engine
jeremie-H edited a comment on issue #1661:
URL: https://github.com/apache/camel-k/issues/1661#issuecomment-674735769
Hi Emmanuel,
It's better indeed,
Before Mathieu and me, we've got only the `camel-k-operator` pod created and in error, now we've got :
```
k get pods [08/17/20|10:16:56]
NAME READY STATUS RESTARTS AGE
camel-k-cache 0/1 Completed 0 7m48s
camel-k-kit-bsr8rg8b08boubro1hdg-builder 0/1 Error 0 3m31s
camel-k-operator-5985c6f7fd-ltnvj 1/1 Running 0 7m53s
```
And now logs in camel-kit are the following:
```
time="2020-08-17T08:13:57Z" level=warning msg="The cgroups manager is set to systemd but there is no systemd user session available"
time="2020-08-17T08:13:57Z" level=warning msg="For using systemd, you may need to login using an user session"
time="2020-08-17T08:13:57Z" level=warning msg="Alternatively, you can enable lingering with: `loginctl enable-linger 0` (possibly as root)"
time="2020-08-17T08:13:57Z" level=warning msg="Falling back to --cgroup-manager=cgroupfs"
STEP 1: FROM adoptopenjdk/openjdk11:slim
Getting image source signatures
Copying blob sha256:b6c12202c5ef07dc9eb8f9d9e71407064684ed70f8c4040b62679b7d30200840
Copying blob sha256:5cea793e6ad6ce1ffe87380ea746a18f65b886f88e1e353047625a18d0a351f6
Copying blob sha256:70799171ddba93a611490ba3557d782714b3f4da8963d49ac8726786ba8274a5
Copying blob sha256:cff6cc990f182d61eee99ddfc92f7068de1e05bc3745feb2ad814145cc39891d
Copying blob sha256:d13af8ca898f36af68711cb67c345f65046a78ccd802453f4b129adf9205b1f8
Copying blob sha256:7595c8c21622ea8a8b9778972e26dbbe063f7a1c4b0a28a80a34ebb3d343b586
Copying blob sha256:9bb22edff5a9b6260be5fb0aeb5ea46ea8159260948c6415e3c29b8f8c5ef2de
Copying config sha256:523aef2db1219918ccd5976ade7a415286fedf06efb8429153fb482187553d61
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/openjdk11:slim" based on search registries in /etc/containers/registries.conf:
* "localhost/adoptopenjdk/openjdk11:slim": Error initializing source docker://localhost/adoptopenjdk/openjdk11:slim: error pinging docker registry localhost: Get http://localhost/v2/: dial tcp 127.0.0.1:80: connect: connection refused
* "docker.io/adoptopenjdk/openjdk11:slim": Error committing the finished image: error adding layer with blob "sha256:7595c8c21622ea8a8b9778972e26dbbe063f7a1c4b0a28a80a34ebb3d343b586": ApplyLayer exit status 1 stdout: stderr: permission denied
* "registry.fedoraproject.org/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.fedoraproject.org/adoptopenjdk/openjdk11:slim: Error reading manifest slim in registry.fedoraproject.org/adoptopenjdk/openjdk11: manifest unknown: manifest unknown
* "registry.access.redhat.com/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.access.redhat.com/adoptopenjdk/openjdk11:slim: Error reading manifest slim in registry.access.redhat.com/adoptopenjdk/openjdk11: name unknown: Repo not found
* "registry.centos.org/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.centos.org/adoptopenjdk/openjdk11:slim: Error reading manifest slim in registry.centos.org/adoptopenjdk/openjdk11: manifest unknown: manifest unknown
* "quay.io/adoptopenjdk/openjdk11:slim": Error initializing source docker://quay.io/adoptopenjdk/openjdk11:slim: Error reading manifest slim in quay.io/adoptopenjdk/openjdk11: unauthorized: access to the requested resource is not authorized
level=error msg="exit status 1"
```
I think it's a duplicate issue here :
#1571
----------------------------------------------------------------
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:
users@infra.apache.org