Container image v2024.2 failes to start apache2 and squid

[tfunq]

Upgrading from v2023.3 to v2024.2 failes. It seems like apache2 and squid wont start. I get

Setting hostname ...
hostname: sethostname: Operation not permitted                                                                                                                                                                                
ERROR: hostname failed to start

Any ideas what to do?

[juanluisrp]

We have found the same problem running the image in kubernetes. Apache and Squid can't start. There was some discussion in this other support issue about this #1081 (comment) but it was closed because it wasn't related to the original ticket subject.

[stempler]

For me as workaround it worked to add changes to the Dockerfile as mentioned here and modify the Pod configuration in Kubernetes as mentioned here.

Before that had tried to disable the use of squid as proxy for HTTP, but this resulted in errors when running tests, as the validator was not able to load some resources that use redirects.