Environment variables reset if calling docker via sudo about dockerswarm.rocks

[dmrty]

I'll try to work on a PR. Let me open another issue specificially for this ${VARIABLE:?} question (instead of poluting this issue) and i'll work at a PR for it. 👌

[dmrty]

FYI, I've started to use ${VARIABLE:?Variable not found} when there is no obvious default so that the deploy crash if the variable is not set:
See docker reference on variable substitution for more info.
Maybe that would make sense to change the ${VARIABLE} or ${VARIABLE:-} by ${VARIABLE:?} for a more solid deploy process?

[tiangolo]

Good idea @dmrty ! I'll change it later (unless a PR doing it comes first 😁 ).

[tiangolo]

Thanks @dmrty ! Let's move to the new issue for that.

@dmontagu as your PR fixing the sudo part it is merged already, I'll close this issue now.

[anatoly-khomenko]

When running:
sudo docker stack deploy -c traefik.yml traefik-consul
I was getting:
invalid interpolation format for services.consul-leader.deploy.labels.[]: "required variable DOMAIN is missing a value: Variable DOMAIN not set". You may need to escape any $ with another $.

unless I specified -E flag as @dmontagu proposed:
sudo -E docker stack deploy -c traefik.yml traefik-consul

It would be good to reflect this in the instruction, as the error text made me try to fix yml syntax instead of looking elsewhere.