-
Notifications
You must be signed in to change notification settings - Fork 22
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
docker-entrypoint.sh #1081
Comments
Dear @tarky363, Thank you for pointing out this issue. Indeed, there are some instructions docker-entrypoint.sh that are not suited to Alpine Linux. Thank you for your contribution to improve the project. Regards, |
What I can observe in the current alpine based image is that
Does anyone else experience the same problem? I tried to work around that by using The resource trying to be accessed in this example exists, but it redirects to HTTPS. The error message hints at that whatever tries to access it can't handle the redirect (hint is that the redirect response is HTML including an Based on that it seems right now using squid is required to work around the issue that redirects are not supported at least in some cases. Any hints on how to resolve that? Thank you! |
Hi,
So we then created the /etc/network/interfaces file (as shown below)
In the Dockerfile we added the following:
Now squid and apache2 start correctly in the container. Also be aware that the Inspire Registry is not currently available so any tests that try to download a codelist will fail as the codelist cannot be accessed. Hope this helps |
Thanks @petbod-lm for the hint! For me it at first still failed with the hostname service:
I only got it to run in my case in Kubernetes by adding a With
both
Not ideal, but works for now. Not sure why that was not necessary with the previous debian based base image. |
Both problems ( |
Commands in docker-entrypoint.sh are not suitable for alpine version of linux
The text was updated successfully, but these errors were encountered: