Closed mglaman closed 1 year ago
This is mitigated by ensuring you run pygmy down
versus pygmy stop
.
Copying in some notes. This is a nice feature if you're only on this kind of stack.
Maybe the default run cmd could be --restart no
and add a --persist
or --autostart
flag to pygmy start
for those who <3 this
Just noticed the same. After a system restart I still had something bind to port 443. And it was indeed the HAProxy service from pygmy.
The dnsmasq service doesn't use the restart argument (probably due to the sudo requirements) so pygmy isn't fully started.
Would also like to see the ability have this configurable.
https://github.com/pygmystack/pygmy supports this
https://docs.docker.com/engine/reference/run/#restart-policies---restart
Several of the services are set to always restart whenever the Docker engine restarts.
When using various local development stacks (or any local development) this causes conflicts.
Related issue from DDEV from a year ago (they had explicit
restart: always
previously)Proposal: remove
restart
policy from the definitions.ssh_agent.rb
haproxy.rb
mailhog.rb