Issues in setting up standalone Jenkins build - Kaniko issue

[nsrivastava2]

Dear Sir We are facing issues while building the application. Following is the issue we are facing when we tried to build the application for OTP service

• echo 'Attempting to build image, docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-4'
  Attempting to build image, docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-4
• sleep 600
• pwd
• pwd
• /kaniko/executor -f /home/jenkins/agent/workspace/builds/upyog/core-services/user-otp/build/maven/Dockerfile -c /home/jenkins/agent/workspace/builds/upyog/core-services/user-otp/./ --build-arg 'WORK_DIR=./core-services/user-otp' --build-arg 'token=********' '--cache=true' '--cache-dir=/cache' '--single-snapshot=true' '--snapshotMode=time' '--destination=docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-4' '--no-push=false' '--cache-repo=velsof/cache/cache' --force
  �[33mWARN�[0m[0000] kaniko is being run outside of a container. This can have dangerous effects on your system
  �[33mWARN�[0m[0000] Error detecting container runtime. Using default keychain: container runtime could not be found
  error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "index.docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-4": UNAUTHORIZED: authentication required; [map[Action:pull Class: Name:velsof/user-otp Type:repository] map[Action:push Class: Name:velsof/user-otp Type:repository]]

[vinothrallapalli-eGov]

@nsrivastava2 Please try removing the sleep

[kumarnarendra701]

@vinothrallapalli-eGov - This was only for debugging purposes and getting same error.

+ echo 'Attempting to build image,  docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-6'
Attempting to build image,  docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-6
+ pwd
+ pwd
+ /kaniko/executor -f /home/jenkins/agent/workspace/builds/upyog/core-services/user-otp/build/maven/Dockerfile -c /home/jenkins/agent/workspace/builds/upyog/core-services/user-otp/./ --build-arg 'WORK_DIR=./core-services/user-otp' --build-arg 'token=********' '--cache=true' '--cache-dir=/cache' '--single-snapshot=true' '--snapshotMode=time' '--destination=docker.io/velsof/user-otp:2.0-velsof-fsm-baae6ba6a3-6' '--no-push=false' '--cache-repo=velsof/cache/cache'
kaniko should only be run inside of a container, run with the --force flag if you are sure you want to continue
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
ERROR: script returned exit code 1

[Gowtham-egov]

Hi @kumarnarendra701
First of all, I want to clarify that we haven't previously worked with K3d. The build failure you're encountering might be due to the fact that K3d clusters often use a user that lacks the necessary permissions to write to your local disk.
If you have prior experience with K3d, I recommend cross-checking the configuration and permissions of your current cluster.
If you're new to K3d, it might be more straightforward to use Amazon EKS for your Jenkins setup, as it typically provides a smoother integration and better support for CI/CD pipelines.

[kumarnarendra701]

@Gowtham-egov - Thank you for the reply. Will it matter because we run everything inside a K8 pod? It doesn't matter if it's a K3D or EKS pod. We shared the k8 config file with you. If you look into this, it will might fix the issue.