I have two development environments that regularly run projects that use docker-compose. I always gracefully stop the docker-compose process before shutting down the system. One laptop has suddenly begun automatically starting a particular container under a particular docker-compose configuration at boot-up. The other system starts like ten containers (a couple of containers in like five different docker-compose configurations), and has been doing this for a year.

All docker-compose services are configured with either no or unless-stopped.

Can anyone explain this behavior?