Describe the bug
When using the *arr stack (prowlarr, radarr, sonarr, lidarr, qbittorrent, sabnzbd), global DNS is not explicitly passed into the containers, breaking the containers. ds -c also removes the dns settings from .config/compose/docker-compose.yml. When using docker compose up -d on the manually altered file, containers work. When using ds -c, manually applied DNS settings are removed, breaking containers.
To Reproduce
Steps to reproduce the behavior:
run ds -c
Expected behavior
when ds -c is run, the GLOBAL_DNS settings should be passed into each container in the docker compose file.
Screenshots
no screenshots, but output files are attached.
docker-compose-bad is what is output on my system.
docker-compose-bad.yml
Docker-compose-backup is what I have manually changed the values to and what is expected from ds -c.
docker-compose-backup.yml
System
(please complete the following information):
Additional context
Add any other context about the problem here.
Describe the bug
When using the *arr stack (prowlarr, radarr, sonarr, lidarr, qbittorrent, sabnzbd), global DNS is not explicitly passed into the containers, breaking the containers.
ds -calso removes the dns settings from .config/compose/docker-compose.yml. When using docker compose up -d on the manually altered file, containers work. When using ds -c, manually applied DNS settings are removed, breaking containers.To Reproduce
Steps to reproduce the behavior:
run ds -c
Expected behavior
when ds -c is run, the GLOBAL_DNS settings should be passed into each container in the docker compose file.
Screenshots
no screenshots, but output files are attached.
docker-compose-bad is what is output on my system.
docker-compose-bad.yml
Docker-compose-backup is what I have manually changed the values to and what is expected from ds -c.
docker-compose-backup.yml
System
(please complete the following information):
Additional context
Add any other context about the problem here.