Replies: 19 comments
-
You definitely need to be using the java21 image but note the error
Are you using Portainer? It's usually the one that breaks the PATH variable like that. A |
Beta Was this translation helpful? Give feedback.
-
Hmm, no, I'm just using regular I'll make sure I'm not using super old versions, it could be that. |
Beta Was this translation helpful? Give feedback.
-
I have same issue on my server and also on the local machine.
I am traiing to start server on my qnap ts431 server and there I need to run from image java17, because of arm32. On my local windows machine it does not work as well with same error. Looks like that old version of java is inside of the container. When I modified the version and set 1.20.4 that it is looks like that it works. |
Beta Was this translation helpful? Give feedback.
-
Same issue - regular
|
Beta Was this translation helpful? Give feedback.
-
@darkweasel77 , run the following and provide the output of those
|
Beta Was this translation helpful? Give feedback.
-
If I specify something other than latest (say java11 or java17):
I get:
|
Beta Was this translation helpful? Give feedback.
-
@itzg I just installed jdk21 to see if that made a difference.
and
|
Beta Was this translation helpful? Give feedback.
-
@darkweasel77 I really wanted to see what image you had pulled previously, which is why I requested the output of the specific command I provided. In any case, It'll probably work now. |
Beta Was this translation helpful? Give feedback.
-
@itzg I'll set it back; w/ jdk21 I'm back to getting what I posted above. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
If i use:
I get:
|
Beta Was this translation helpful? Give feedback.
-
@itzg maybe more context
vs
|
Beta Was this translation helpful? Give feedback.
-
Thanks @darkweasel77 , that context seems interesting but I have no idea what it means 😀 The Java 21 is also from Eclipse Temurin so there's not a distro difference from Java 17. I'd say try googling for the Java VM error it's giving. |
Beta Was this translation helpful? Give feedback.
-
@itzg FYI - I upgraded my version of docker on my server to the latest and the problem went away. |
Beta Was this translation helpful? Give feedback.
-
could you give us docker versions for comparison? @darkweasel77 |
Beta Was this translation helpful? Give feedback.
-
@VictorDrijkoningen I didn't copy the output of now:
|
Beta Was this translation helpful? Give feedback.
-
Speaking of which, the separate |
Beta Was this translation helpful? Give feedback.
-
I don't disagree - I had configured this server awhile ago with ubuntu 20.04, upgraded to 22.04 but never changed docker since it 'worked'. I followed this guide from docker to upgrade my docker sub-system. |
Beta Was this translation helpful? Give feedback.
-
Sorry @darkweasel77 , that comment was really directed at anyone else reading this issue 😄 |
Beta Was this translation helpful? Give feedback.
-
Describe the problem
I'm having an issue creating new containers for version 1.20.5 and 1.20.6 on Ubuntu 22.04.
I've pulled the latest versions of both of the java17 and java21 tagged images. I may be doing something silly!
Container definition
With java21:
With java17:
Container logs
With java21:
With java17:
Beta Was this translation helpful? Give feedback.
All reactions