We have currently a feature difference between the Docker driver and the Podman driver even tho the Docker driver does not fully support it in the right way it would be nice if we can use the --add-host=host:ip command is used when we use the config.ext
Use-cases
As a maintainer, I want to route specific URLS (often .cloud URLs) to my VPN/NAT routing because of the security of my network.
fullygenerated.url.aws.service.cloud should go to IP 172.168.1.1
Attempted Solutions
We seem to be able to do this in the Docker setup but not in the Podman setup:
Hi @Thadir I'm moving this issue to the nomad-driver-podman repo because the configuration for task drivers is entirely owned by the task driver itself and not the Nomad agent. I'll mark it for triage there.
Proposal
We have currently a feature difference between the Docker driver and the Podman driver even tho the Docker driver does not fully support it in the right way it would be nice if we can use the
--add-host=host:ip
command is used when we use the config.extUse-cases
As a maintainer, I want to route specific URLS (often .cloud URLs) to my VPN/NAT routing because of the security of my network. fullygenerated.url.aws.service.cloud should go to IP 172.168.1.1
Attempted Solutions
We seem to be able to do this in the Docker setup but not in the Podman setup:
Docker documentation This is fully supported for the Podman https://docs.podman.io/en/latest/markdown/options/add-host.html and is simular variables see https://docs.podman.io/en/latest/markdown/options/add-host.html