chore(container): Correct webpack binding in container

[bastilian]

This corrects the binding behaviour of webpack dev server when it is running within a container.

Secure Coding Practices Checklist GitHub Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

[akofink]

As discussed in Slack: this prevents the proxy from being able to access a local API (i.e. localhost:3000 for compliance-backend); however, the dns issue seems to be resolved.

[skateman]

I investigated further the issue with the DNS servers and if the host OS uses systemd-resolved, podman copies /run/systemd/resolve/resolv.conf for host networked containers, which in my case somehow only contains the DNS servers provided by my ISP. As this file is auto-generated, I tried to mess with the DNS priorities in my NetworkManager but that didn't really help me.

containers/podman#3277 (comment)
containers/podman#7616

If we're not using host networking for the proxy, the API is basically inaccessible as it is running in a separate pod and podman doesn't support host.docker.internal or anything similar like host.podman.internal and according to what I found, they are suggesting people to just use --net=host 😕

[akofink]

I think we can close this one. As @skateman says, we were hitting issues with new Fedora 33 'features' 😆

[skateman]

I'm still struggling with the frontend not listening on 0.0.0.0 so I have to keep stashing stuff when git-pulling.

[akofink]

Ok, sure. @bastilian could we repurpose this PR to fix just the bind?

[bastilian]

@skateman The binding should now work out of the box.

[skateman]

[bastilian]

For some reason the Docker compose documentation is not right. A environment variable defined in the .env file doesn't seem to overwrite the one in the compose file[1].

[1] https://docs.docker.com/compose/environment-variables/