You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I started using your excellent setup with some web apps and nodejs services. At some point, one service needs to make an HTTPS request to another service. It was failing since both DNS and root CA cert were not available for that service.
This was the first solution I came up with. It works. There may be better ones, but I'm not so deep into DevOps.
Additional context
I'm not sure what exactly would need to be changed here. Mostly raising it if someone else has a similar requirement. Possibly:
Traefic and dnsmasq could have static IPs by default and .env would use the Traefic IP
docs could include information on how to enable connected projects to use provided DNS, as well as how to add root CA cert. Either on the OS level or node js (or another runtime) level.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I started using your excellent setup with some web apps and nodejs services. At some point, one service needs to make an HTTPS request to another service. It was failing since both DNS and root CA cert were not available for that service.
Describe the solution you'd like
I used a combination of https://www.codingexplorations.com/blog/enhancing-docker-networking-with-dnsmasq-a-comprehensive-guide for the DNS. I needed to set static IP for both Traefic and dnsmasq, as well as update the
.env
to use Traefic static IP instead of localhost.For root CA cert it was pretty easy for node https://github.com/FiloSottile/mkcert?tab=readme-ov-file#using-the-root-with-nodejs
Other types of services may have different requirements.
Describe alternatives you've considered
This was the first solution I came up with. It works. There may be better ones, but I'm not so deep into DevOps.
Additional context
I'm not sure what exactly would need to be changed here. Mostly raising it if someone else has a similar requirement. Possibly:
.env
would use the Traefic IPThe text was updated successfully, but these errors were encountered: