docker-entrypoint.sh

[tarky363]

Commands in docker-entrypoint.sh are not suitable for alpine version of linux

[DanielMartinPerezdeLeon]

Dear @tarky363,

Thank you for pointing out this issue.

Indeed, there are some instructions docker-entrypoint.sh that are not suited to Alpine Linux. While these commands do not affect the functionality or validation of the Docker container, we acknowledge that their presence in the file is not appropriate, so the docker-entrypoint.sh file will be updated in the next release accordingly.

Thank you for your contribution to improve the project.

Regards,

[stempler]

What I can observe in the current alpine based image is that

• squid won't start (ERROR: cannot start squid as hostname would not start)
• related to that, as squid is configured by default as proxy for HTTP, requests to http:// resources fail

Does anyone else experience the same problem?

I tried to work around that by using none for the HTTP proxy, which works, at least in most cases. But open issues still remain in some tests, for instance here:

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 <hr> tag and it is tried to be loaded as XML).

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!