You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are trying with running maven container inside openshift and getting this error since AUG 1 . we are using the image [3.3.6](maven:3.3.6 -openjdk-17) , then we also tried using image maven:3.8.4-openjdk-17 , it still throws the same error , issue is pod terminates instantly and we don't have much control to change the permissions in home , other thing we noticed that jenkins build was working fine before when it's taking the home path as /home/jenkins , it only started failing after taking path as / and also started throwing the warning after Aug 1 build failures :-
[WARNING] HOME is set to / in the jnlp container. You may encounter troubles when using tools or ssh client. This usually happens if the uid doesnt have any entry in /etc/passwd. Please add a user to your Dockerfile or set the HOME environment variable to a valid directory in the pod template definition.
We are blocked , help would be appreciated , thanks
Bharat
+13147368511 ( Us)
The text was updated successfully, but these errors were encountered:
we are trying with running maven container inside openshift and getting this error since AUG 1 . we are using the image [3.3.6](maven:3.3.6 -openjdk-17) , then we also tried using image maven:3.8.4-openjdk-17 , it still throws the same error , issue is pod terminates instantly and we don't have much control to change the permissions in home , other thing we noticed that jenkins build was working fine before when it's taking the home path as /home/jenkins , it only started failing after taking path as / and also started throwing the warning after Aug 1 build failures :-
[WARNING] HOME is set to / in the jnlp container. You may encounter troubles when using tools or ssh client. This usually happens if the uid doesnt have any entry in /etc/passwd. Please add a user to your Dockerfile or set the HOME environment variable to a valid directory in the pod template definition.
We are blocked , help would be appreciated , thanks
Bharat
+13147368511 ( Us)
The text was updated successfully, but these errors were encountered: