-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can´t read machine-id from normal Java container for Java 17 #4043
Comments
This would be an issue for any docker container. It's even an issue on the machineid git repo. |
Hm, but why is it specific the Java 17 yolk then. Yolks 8,11,16 and 8J9,11J9,16J9 and 17J9 all work fine. |
Every server has a uuid attached to it and is part of the env vars. If you passed in a machine id file they would all get the same id every time. |
Could i not just use that env var to put into the file thats missing in the eggs install script? |
No. The only files that are saved are the ones in |
Closing this out, doesn't appear to be software specific. |
Current Behavior
One of my Eggs requires a way to get a unique id, for this it reads a file thats pressent on most OSs and diffrent locations.
However it cant find the file in the normal Java Yolk for java 17:
open /etc/machine-id: no such file or directory
it works as expected with the J9 version.Java 8,11 and 16 Yolks have this file aswell, only Java 17 is not working.
Expected Behavior
Should be able to read /etc/machine-id from Java 17 Yolk like on most distros and the J9 yolks and older normal Java Yolks.
Steps to Reproduce
Try to read /etc/machine-id file with the Java Yolk
Or use the egg thats not working.
Panel Version
1.7.0
Wings Version
1.6.1
Games and/or Eggs Affected
https://github.com/gekware/minecraft-server-hibernation-pterodactyl-egg/blob/main/egg-paper-on-demand.json
Docker Image
ghcr.io/pterodactyl/yolks:java_17
Error Logs
2022/04/09 18:42:14 [error * ] main: LoadConfig: loadDefault: machineid: machineid: open /etc/machine-id: no such file or directory
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: