Closed kev626 closed 1 year ago
are you on unraid?
pls Post output of
hostnamectl status
are you on unraid?
pls Post output of
hostnamectl status
This is not an unraid system and this error occurs on any system that attempts to execute the latest build of the Java 17 egg (and likely all of the others as well).
root@DFW-04-5950x:~# hostnamectl status
Static hostname: DFW-04-5950x
Icon name: computer-desktop
Chassis: desktop
Machine ID: <snip>
Boot ID: <snip>
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 5.10.0-20-amd64
Architecture: x86-64
See:
root@pterotest:~# curl https://get.docker.com | bash
<snip>
root@pterotest:~# docker run -it --rm ghcr.io/parkervcp/yolks:java_17
Unable to find image 'ghcr.io/parkervcp/yolks:java_17' locally
java_17: Pulling from parkervcp/yolks
7007490126ef: Pull complete
56c7ccc62e5c: Pull complete
56fed29f45ad: Pull complete
33cb37dbba70: Pull complete
0ef4548c8825: Pull complete
a3c17b0d923c: Pull complete
4f4fb700ef54: Pull complete
ce0df5629fec: Pull complete
Digest: sha256:ac2a806d0890bab817c259fbddd81e0e1cb8e555db14fbbb8780e2a04e6590a9
Status: Downloaded newer image for ghcr.io/parkervcp/yolks:java_17
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/entrypoint.sh": permission denied: unknown.
ERRO[0020] error waiting for container:
Replicated on a completely fresh Debian 11 system.
Seems to be affecting me as well
Considering the entrypoint hasn't had to change in over a year and all the java docker files are 6 months old this is a strange turn of events.
Considering the entrypoint hasn't had to change in over a year and all the java docker files are 6 months old this is a strange turn of events.
I'm not disagreeing with you. But like I said, run it yourself. On a freshly installed system this happens.
This isn't a permissions issue but a bug with the build
it is.its more or lesser a Problem with danny fix. Had the same problems and Quinten dont add the permissions fix, i told him.
chown +x is not enough. enteypoint.sh must be owned by Container.
in my eyes, dannys fix is not needed, when someone can build Wings with Parkers pr's for stopcmdcmd Bug and owner
The issue I still have is that this worked before today's build. There is no reason it shouldn't work.
btw. i cant confirm the issue:
latest yolk Ubuntu 22.04 Kernel: 6.4.8
btw. i cant confirm the issue:
latest yolk
You're using the wrong image. This affects the Java 17 image. Your screenshot/test is irrelevant. It can be replicated using the commands I showed above. This IS an issue.
Seems to be affecting me as well
can you show me also the Output of:
hostnamectl status?
You're using the wrong image. This affects the Java 17 image. Your screenshot/test is irrelevant. It can be replicated using the commands I showed above. This IS an issue.
you are right. i clicked the wrong Egg. sry, only online on my mobile.
i can confirm this Error. have the Same. IT worked a week ago, when i updated lavalink
When starting Java containers (Java 17 tested) on the latest build (released <1 hour ago) the following error occurs indicating a permissions issue of some kind with the entrypoint file: