Please update docker-compose.yml restart policy for `webpack` and `engine` containers. Right now, both have "restart: always" and, according docker docs (attached screenshot) this produces that, on every host machine restart (dockerd service restart really), those containers are started again too. Consuming resources and cpu silently without any need. Even if I need to start manually my local Fusion environment, `npm start` will stop those containers and start them again from scratch.
From my perspective, expected behavior is that, if I tear down manually my environment, it should remain down until I manually start that environment again.
This setting could be updated to "restart: on-failure" and you'll achieve the effect of restarting those containers automatically on failure without generating this invasive behavior on host machines.
For reproduce this mentioned behavior:
Run `npm start`
After env is ready, tear env down (ctrl-c)
restart your dockerd service
run `docker ps` to confirm which containers are up
Fernando Jascovich
Encountered this before and in my experience the best policy was "restart: unless-stopped". This works the same as "restart: always" in all the ways except when the container was stopped by the user.
This is fixed as of CLI 2.0.2
Thanks for the feedback, we switched from "on-failure" to "always" as it was not working as documented in our testing during previous releases. We can re-evaluate this in an upcoming release.