git-josip opened a new issue, #823: URL: https://github.com/apache/camel-karavan/issues/823
I am experiencing an issue when setting up camel-karavan locally with Minikube and docker. I am using Ammple silicon but I do not believe the issue is happening because of that. Karavan starts normally and I successfully set up gitea, repository is working and I have created a repository which then is added to `karavan-cloud/minikube/karavan-secret.yaml` file with credentials. I create project and push changes to gitea, and I can see in gitea UI dashboard changes are there in the repository, new camel integration and properties. Issue occurrs when I try to deploy it to k8s minikube cluster. Spring boot build job is started and I get follwoing error: ``` fatal: could not read Username for 'http://192.168.65.254:3000': No such device or address /tekton/scripts/script-0-9j2b7: line 15: cd: /scripts/testscheduler: No such file or directory jbang -Dcamel.jbang.version=3.20.3 camel@apache/camel export --local-kamelet-dir=/scripts/kamelets [jbang] Resolving dependencies... [jbang] org.apache.camel:camel-bom:3.20.3@pom [jbang] org.apache.camel:camel-jbang-core:3.20.3 ``` git clone obviously fails with that strange error and later also fails `cd` command because there is no my project `testscheduler` . I tried using many different ids and gitea deployments but no luck. I had deployed gitea using docker-compose and lates was with k8s helm chart, but the error is always happening on that same step. I had found similar old issue: https://github.com/tektoncd/pipeline/issues/1375 This is karavan tekon build task script: ``` script: | #!/usr/bin/env bash CHECKOUT_DIR="/scripts" KAMELETS_DIR="/scripts/kamelets" if [[ $GIT_REPOSITORY == https* ]] ; then replacer=https://$GIT_PASSWORD@ prefix=https:// url="${GIT_REPOSITORY/$prefix/$replacer}" git clone --depth 1 --branch ${GIT_BRANCH} $url ${CHECKOUT_DIR} else git clone --depth 1 --branch ${GIT_BRANCH} ${GIT_REPOSITORY} ${CHECKOUT_DIR} fi ..... ...... ``` And error is happening on `git clone --depth 1 --branch ${GIT_BRANCH} ${GIT_REPOSITORY} ${CHECKOUT_DIR}` I do not know what else to do. Thank you, Josip -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
