Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Saravanakumar Selvaraj
    @saravanakumar1987
    Ah, i just figured some options available - knative-service.enabled
    Let me try it out!
    Claus Ibsen
    @davsclaus
    yeah you can turn off knative
    when knative is detected in the cluster its used by default
    the traits control almost everything
    and you can turn on|off a lot of stuff via those
    Omar Al-Safi
    @omarsmak

    Hey folks, I am trying to run camel-k on my AKS cluster. I installed it with dockerhub enabled during the install. Now when I try to run the example kamel run hello.groovy —dev, I see in my buildah logs the following :

    kubectl logs camel-k-kit-brqc6o92k48oaktde460-builder buildah                                                                                                                                                                    oalsafi@LT-C02YV0PGLVDR
    time="2020-06-25T15:32:44Z" level=warning msg="The cgroups manager is set to systemd but there is no systemd user session available"
    time="2020-06-25T15:32:45Z" level=warning msg="For using systemd, you may need to login using an user session"
    time="2020-06-25T15:32:45Z" level=warning msg="Alternatively, you can enable lingering with: `loginctl enable-linger 0` (possibly as root)"
    time="2020-06-25T15:32:45Z" level=warning msg="Falling back to --cgroup-manager=cgroupfs"
    STEP 1: FROM adoptopenjdk/openjdk11:slim
    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 https://localhost/v2/: dial tcp 127.0.0.1:443: connect: connection refused
    * "docker.io/adoptopenjdk/openjdk11:slim": Error initializing source docker://adoptopenjdk/openjdk11:slim: error pinging docker registry registry-1.docker.io: Get https://registry-1.docker.io/v2/: dial tcp 18.232.227.119:443: connect: connection refused
    * "registry.fedoraproject.org/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.fedoraproject.org/adoptopenjdk/openjdk11:slim: error pinging docker registry registry.fedoraproject.org: Get https://registry.fedoraproject.org/v2/: dial tcp 38.145.60.20:443: connect: connection refused
    * "registry.access.redhat.com/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.access.redhat.com/adoptopenjdk/openjdk11:slim: error pinging docker registry registry.access.redhat.com: Get https://registry.access.redhat.com/v2/: dial tcp 104.108.71.24:443: connect: connection refused
    * "registry.centos.org/adoptopenjdk/openjdk11:slim": Error initializing source docker://registry.centos.org/adoptopenjdk/openjdk11:slim: error pinging docker registry registry.centos.org: Get https://registry.centos.org/v2/: dial tcp 8.43.84.200:443: connect: connection refused
    * "quay.io/adoptopenjdk/openjdk11:slim": Error initializing source docker://quay.io/adoptopenjdk/openjdk11:slim: error pinging docker registry quay.io: Get https://quay.io/v2/: dial tcp 18.205.55.240:443: connect: connection refused
    level=error msg="exit status 1"

    I see connection refused Get https://registry-1.docker.io/v2/: dial tcp 18.232.227.119:443: connect: connection refused and I am not really sure why the container is not reaching to docker registry, any ideas? thank you

    2 replies
    Omar Al-Safi
    @omarsmak

    I tried to use different namespace, it seems to be connecting to dockerhub, however there is a new error:

    ~ » kubectl logs -f camel-k-kit-brqd3r6uajcveh7mvvu0-builder buildah                                                                                                                                                                 oalsafi@LT-C02YV0PGLVDR
    time="2020-06-25T16:34:33Z" level=warning msg="The cgroups manager is set to systemd but there is no systemd user session available"
    time="2020-06-25T16:34:33Z" level=warning msg="For using systemd, you may need to login using an user session"
    time="2020-06-25T16:34:33Z" level=warning msg="Alternatively, you can enable lingering with: `loginctl enable-linger 0` (possibly as root)"
    time="2020-06-25T16:34:33Z" level=warning msg="Falling back to --cgroup-manager=cgroupfs"
    STEP 1: FROM adoptopenjdk/openjdk11:slim
    Getting image source signatures
    Copying blob sha256:d7c3167c320d7a820935f54cf4290890ea19567da496ecf774e8773b35d5f065
    Copying blob sha256:6ac240b130982ad1c3ba3188abbf18ba4e54bdd9e504ce2d5c2eff6d3e86b8dd
    Copying blob sha256:53e8c97b6d35547fecc53be73da28ce825493cf8f74bc90145fd750c5b65e0ad
    Copying blob sha256:50eb3dbde98c9e30f784c7b0474201f343e4df7eac61c1d1f5d29768adb6dae4
    Copying blob sha256:131f805ec7fd68d45a887e2ef82de61de0247b4eb934ab03b7c933650e854baa
    Copying blob sha256:322ed380e680a77f30528ba013e3a802a7b44948a0609c7d1d732dd46a9a310d
    Copying blob sha256:64ac2b05b0e619c8018a97549c364f3b4f890ab309f634b6282736f90b233fb0
    Copying config sha256:95d6674907be43939abb7a09d8f7e1fc23c26e5a22f5545d48d0b918b4bbaa38
    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 https://localhost/v2/: dial tcp 127.0.0.1:443: connect: connection refused
    * "docker.io/adoptopenjdk/openjdk11:slim": Error committing the finished image: error adding layer with blob "sha256:d7c3167c320d7a820935f54cf4290890ea19567da496ecf774e8773b35d5f065": 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"

    Is this permission denied coming from the docker deamon?

    Nicola Ferraro
    @nicolaferraro
    No, it's the buildah binary
    Just out of curiosity, can you try with the other image builders @omarsmak ? "Kaniko" or "Spectrum" (kamel install --build-publish-strategy=Kaniko ...)
    4 replies
    Omar Al-Safi
    @omarsmak
    let me try
    Omar Al-Safi
    @omarsmak

    @nicolaferraro here is my finding:
    “Kaniko” produces an authentication issue to docker. Error :

    ~ » kubectl logs -f camel-k-kit-brqdau6uajci6uhb5uu0-builder kaniko                                                                                                                                                                  oalsafi@LT-C02YV0PGLVDR
    INFO[0001] Resolved base name adoptopenjdk/openjdk11:slim to adoptopenjdk/openjdk11:slim
    INFO[0001] Resolved base name adoptopenjdk/openjdk11:slim to adoptopenjdk/openjdk11:slim
    INFO[0001] Retrieving image manifest adoptopenjdk/openjdk11:slim
    INFO[0002] Retrieving image manifest adoptopenjdk/openjdk11:slim
    INFO[0004] Built cross stage deps: map[]
    INFO[0004] Retrieving image manifest adoptopenjdk/openjdk11:slim
    INFO[0004] Retrieving image manifest adoptopenjdk/openjdk11:slim
    INFO[0005] Unpacking rootfs as cmd ADD . /deployments requires it.
    INFO[0012] Taking snapshot of full filesystem...
    INFO[0021] Using files from context: [/builder/kit-brqdau6uajci6uhb5uu0/context]
    INFO[0021] ADD . /deployments
    INFO[0021] Taking snapshot of files...
    INFO[0022] USER 1000
    INFO[0022] cmd: USER
    error pushing image: failed to push to destination docker.io/omarsmak/camel-k-kit-brqdau6uajci6uhb5uu0:788576: UNAUTHORIZED: authentication required; [map[Action:pull Class: Name:omarsmak/camel-k-kit-brqdau6uajci6uhb5uu0 Type:repository] map[Action:push Class: Name:omarsmak/camel-k-kit-brqdau6uajci6uhb5uu0 Type:repository] map[Action:pull Class: Name:adoptopenjdk/openjdk11 Type:repository]]

    I tried “Spectrum” and it seems to work on my end

    3.3.0.jar:dependencies/org.apache.camel.camel-support-3.3.0.jar:dependencies/org.apache.camel.camel-timer-3.3.0.jar:dependencies/org.apache.camel.camel-util-3.3.0.jar:dependencies/org.apache.camel.k.camel-k-loader-groovy-1.3.0.jar:dependencies/org.apache.camel.k.camel-k-runtime-core-1.3.0.jar:dependencies/org.apache.camel.k.camel-k-runtime-main-1.3.0.jar:dependencies/org.apache.logging.log4j.log4j-api-2.13.3.jar:dependencies/org.apache.logging.log4j.log4j-core-2.13.3.jar:dependencies/org.apache.logging.log4j.log4j-slf4j-impl-2.13.3.jar:dependencies/org.codehaus.groovy.groovy-3.0.4.jar:dependencies/org.slf4j.slf4j-api-1.7.30.jar org.apache.camel.k.main.Application
    Condition "Ready" is "True" for Integration hello
    [1] 2020-06-25 16:55:53.434 INFO  [main] ApplicationRuntime - Add listener: org.apache.camel.k.listener.ContextConfigurer@7b94089b
    [1] 2020-06-25 16:55:53.439 INFO  [main] ApplicationRuntime - Add listener: org.apache.camel.k.listener.RoutesConfigurer@403f0a22
    [1] 2020-06-25 16:55:53.439 INFO  [main] ApplicationRuntime - Add listener: org.apache.camel.k.listener.PropertiesConfigurer@3568f9d2
    [1] 2020-06-25 16:55:53.451 INFO  [main] ApplicationRuntime - Listener org.apache.camel.k.listener.PropertiesConfigurer@3568f9d2 executed in phase ConfigureProperties
    [1] 2020-06-25 16:55:53.458 INFO  [main] RuntimeSupport - Looking up loader for language: groovy
    [1] 2020-06-25 16:55:53.773 INFO
    Nicola Ferraro
    @nicolaferraro
    Great, Spectrum should also be the fastest among them
    Can you open an issue about the others? With equal config, all three should work in theory
    Omar Al-Safi
    @omarsmak
    Sure I will. Thanks
    Saravanakumar Selvaraj
    @saravanakumar1987
    Hi, Are there any place where I can find the list of supported components in camel k?
    Claus Ibsen
    @davsclaus
    @saravanakumar1987 all components are essentially supported. However it depends what the base runtime is - camel-main or camel-quarkus
    we are moving to be camel-quarkus in the future, then its the components listed on it that are supported
    Saravanakumar Selvaraj
    @saravanakumar1987
    Hi Claus,
    Thank you. I understood from the camel K GA release notes and it says Camel 3.3.0 is used. Thanks for the clarification.
    Claus Ibsen
    @davsclaus
    yeah camel k 1.1 will update to camel 3.4
    currently 1.0.1 is on the way
    Claus Ibsen
    @davsclaus
    its actually listed in the camel-catalogs resource
    so you can do
    kubectrl get camel-catalogs
    or
    get cc
    cc = short name
    then you can look inside those, one for main and another for quarkus
    they list the camel components they know/support
    k describe cc camel-catalog-1.3.0-main
    Saravanakumar Selvaraj
    @saravanakumar1987
    Thanks a lot for the details.
    Claus Ibsen
    @davsclaus
    Camel K 1.0.1 is on VOTE (you can download and try/test it):
    https://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-K-1-0-1-td5872924.html
    Saravanakumar Selvaraj
    @saravanakumar1987
    I am preparing a comparion sheet with and Quarkus. But currently its in JVM mode. I am waiting for the Quarkus native mode support.
    Claus Ibsen
    @davsclaus
    ok sounds great
    just mind native mode compilation is "heavy"
    but camel k tend to be small integration so fits perfect there
    and yeah then quarkus is required and all its extensions supports native mode
    currently we have some camel quarkus extensions that are jvm only, you can see it on the website
    Saravanakumar Selvaraj
    @saravanakumar1987

    just mind native mode compilation is "heavy"

    yeah. During development, JVM mode can be used with code changes multiple time. We could do one time compilation in native mode before the final deployment.

    Claus Ibsen
    @davsclaus
    yeah we have talked about having a builder doing the native build and then do a rolling upgrade when its ready so you can run in jvm mode in the mean time
    but also a ci pipeline where a native build is done and deployed on some test namespace before rolling into prod etc
    so there are many ways
    but good point of jvm for development and native only later
    Ari Salonen
    @arsalone_twitter
    What should be Camel-K pod memory consumption after native build? I just noted that it is like 100M even there is nothing else than logging
    Claus Ibsen
    @davsclaus
    you need to set resource limits on the pods
    so for native you can lower that to 20-30 etc
    its a bit more heavy in java 11 and latest graalvm than it was with java 8
    there is a trait you can use to set those limits via kamel
    imasood90
    @imasood90
    hi i have question
    with default builder we can are not able to configure apache Camel k with the local repository