Closed WGOS closed 4 years ago
This could affect more than just the single server you ran. This is no from me.
Other servers could fail horribly with this.
I'm with @parkervcp here, but wouldn't be opposed to it being a new image that we host.
This could affect more than just the single server you ran. This is no from me.
Other servers could fail horribly with this.
Well, it had been worked fine for me for years on different builds
I'm with @parkervcp here, but wouldn't be opposed to it being a new image that we host.
Yes, it's probably should be a new image
Actually I uploaded it to Docker hub already wgos/pteroq-images:java-zulu
so it could be tested
We have a Java open j9 image. So I don't see why we wouldn't add another jvm image.
I stop would rather have this be Debian based for compatibility reasons.
It could be just an alternative option, I suppose.
Are there compatibility issues with Alpine? Just interesting
Alpine uses muslc and not glibc. This has caused issues with modded servers in the past. Before moving to debian we were running alpine-java-glibc but it used oracle java and got dcma'd.
Well that was gross and I am sorry I made all that noise there adding and changing the branch.
Uh, that wasn't gross at all. Just a regular discussion
I was talking about all the changes and the merge conflict I added by changing the base branch.
I also unmentioned that Forge does not work on OpenJ9 properly. In my case it freezes with Sponge and server doesn't launch
There is a reason openj9 isn't default...
I finally resolved all problems with git so it may be ready to merge, I suppose
Base image changed to Debian. Also added "might-be-usefull" packages like in java branch
As I see on Zulu in Alpine docker uses glibc (it's event stated on their site that glibc required). So maybe redo this container on Alpine due to lightweight?