-
Notifications
You must be signed in to change notification settings - Fork 0
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
/usr/local/bin/docker-entrypoint.sh: line 122: start.sh: No such file or directory #8
Comments
Hi @efstajas , I'm not familiar with Nomad, but I just noticed that I did not use an absolute path in line 122 for the start script. The Docker I will push a patch release in the next minues. Hopefully this fixes the issue - otherwise we have to do more debugging. |
@flobernd Thank you very much for your fast response. Unfortunately still getting the same issue:
I also tried running the docker start command from your README on my Mac to rule out any config issue with my Nomad spec, and am getting the same issue there. If I understand the script correctly, it's first supposed to download the actual pack before attempting to modify start.sh, right? The error appears immediately after startup, and the mounted dir also stays entirely empty, so that it can't find the file makes sense. It seems like the problem is that it skips the download for some reason. Could it be a problem with the arm build of the image, maybe? I don't have an x86 host to try it on here at the moment. |
Hi @efstajas , thank you for testing the new version. Your observation seems correct. The container should download the modpack installer in the first step. If the directory stays empty, something must be wrong here (and my error handling seems to be insufficient 😅). I have an ARM device available. I'm going to test it there and see if that's the issue. |
Hi @efstajas, I published a new version. Please let me know, if that fixes your issue. |
@flobernd thanks a ton! 🙌 it installs and runs fine now on my Mac. On my Raspberry Pi 5 (via nomad) though, after the installation (which now works) I get this error: When I have a moment I'll try to debug this on my own, and assuming it's not a config problem on my end, open either a new issue or PR depending on whether I figure it out 👌 |
Happy to hear that it installs now 🙂 If you have the chance to test it with regular Docker, that could probably rule out Nomad configuration issues. It's definitely some kind of permission issue. From a brief research it seems like this can happen if you run Nomad itself in a container. |
@flobernd It turns out it was indeed a (very strange) problem with Nomad, but I found a temporary workaround which is to run the container as |
Hey @efstajas , thanks for the update! I think it might be worth trying the image with rootless Docker CE to see if the problem occurs here as well. On my side, I could imagine adding a UID/GID argument which could be used to run the container as a specific user right away and omit the calls to chown and the user switch. |
I think UID/GID arguments for this container would definitely be useful regardless of my issue, because another challenge is to get it to work with mounts. My mount into this image is an NFS share which is configured to just squash all users to a default user that can access the shared directory, which is good enough for me, but ideally it'd be customisable on the image level for sure. I don't think it'd make a difference for this permission issue I'm seeing regardless. I have some other containers that fail seemingly due to the same problem unless Regarding rootless Docker — I've been thinking about this too, but Nomad doesn't currently support it. The whole thing is quite odd, because the permission denied issues arise within the container, regardless of any mounts. As far as I know what user the container runs at or what privileges it has on the host should not have any effect on permission within the container's own filesystem? But I'm sure I'm just missing some obvious configuration problem on my end. Curious to see what comes out of that issue I opened on Nomad. |
Trying to deploy this on my Nomad cluster, but after starting it up I only get this error:
Nothing at all is being written to the mounted dir.
Am I doing something wrong?
My job spec, which includes the docker config:
Thanks for making this!
The text was updated successfully, but these errors were encountered: