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
Currently, I've got a custom DNS running at home for giving out custom domain names for my services run at home - even though my host has as only DNS server my custom one, portainer somehow does not resolve these custom domains correctly if they are also defined externally (split-dns), to fix this I added the --add-host parameter to the portainer container, sadly this is not copied over to the compose-unpacker or even configurable, so it's having the same issues my current work around for this is running a while loop using a format script to get the RUN command for compose-unpacker container and adapt it with the --add-host parameters needed and run it manually but this is getting really cumbersome.
So, it would be great if the compose-unpacker copies the --network and --add-host parameters from the portainer container to fix this up.
Currently, I've got a custom DNS running at home for giving out custom domain names for my services run at home - even though my host has as only DNS server my custom one, portainer somehow does not resolve these custom domains correctly if they are also defined externally (split-dns), to fix this I added the
--add-host
parameter to the portainer container, sadly this is not copied over to thecompose-unpacker
or even configurable, so it's having the same issues my current work around for this is running a while loop using a format script to get the RUN command forcompose-unpacker
container and adapt it with the--add-host
parameters needed and run it manually but this is getting really cumbersome.So, it would be great if the
compose-unpacker
copies the--network
and--add-host
parameters from theportainer
container to fix this up.Command I RUN:
The text was updated successfully, but these errors were encountered: