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
When dev {project} down is run only the project container is shut down. Any other containers listed in the docker-compose files for the project are not brought down. This was intentional b/c dev doesn't really know the relationship between all the projects. Once issue #4 is resolved, flags can be added to the 'down' command to shut down all shared dependencies (probably should result in a warning that other dependent projects will also be shu down).
The text was updated successfully, but these errors were encountered:
svrana
changed the title
Unable to bring stop non project containers
Unable to down non project containers
Jun 2, 2019
want to point out that, if there's another running container B that depends on the dependencies of container A, dev down on A should not bring down the dependencies of A that are also dependencies of B
When dev {project} down is run only the project container is shut down. Any other containers listed in the docker-compose files for the project are not brought down. This was intentional b/c dev doesn't really know the relationship between all the projects. Once issue #4 is resolved, flags can be added to the 'down' command to shut down all shared dependencies (probably should result in a warning that other dependent projects will also be shu down).
The text was updated successfully, but these errors were encountered: