-
Notifications
You must be signed in to change notification settings - Fork 8
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
olat_1 | /bin/bash: /entrypoint.sh: Permission denied #1
Comments
Hello, there could be several reasons why your openolat container is not starting up. First I would say that the user permissions on your volume is not correct. Another reason could be a misconfiguration of the openolat.config. |
Set the folder to 777. What are you thinking the issue would be with the openolat.config? |
maybe there are some misconfigurations in the file but do you have any logfiles from the container? |
I'm gonna hang on to this one. First of all, thanks for the container! I'm currently also failing to start the container successfully. I have taken the
After I manually set it to the available version
|
Thank you for your the tip and I changed the default value. I see that Apache removed the Tomcat version from there Website. Could you try to delete the volume entry in the compose file. Maybe there are some problems with the different file systems but I will try it within the next days. |
Short update from my side. I tested it on my Synology DS918+ and it worked. I will test it on my other homeserver but I need a new fan. So the final test and repair will start at the weekend. I hope that's ok. |
I came up to the following result: I cannot run openolat with docker-compose at all. I receive always the same errors like you but when I pull the repository and build it then I didn't get any errors and I can run it. So please currently don't use docker-compos but I will continue to search the problem. If there are any other mistakes please report it to me and I will look forward to fix them. :D |
I'm guessing that the script isn't set to executable in the repo? just tried pulling it from docker hub and running it with this docker-compose file to try it out:
If I'm doing it wrong would love to know how! Thanks!^^
The text was updated successfully, but these errors were encountered: