using the --remove-orphans flag

[AlexSHuk]

Describe the bug

the documentation states the following

however, given the directory structure when cloning the repository

the user will encounter a problem, namely:

• when L3 containers starts, all L2 containers will be destroyed.
  Example:

1. Running L2 containers

2. Running L3 containers You can see that all L2 containers were killed by the flag --remove-orphans

Steps to reproduce

Solution
use 2 different directories for L2 and L3 , for examples :

in this case, when L3 starts with --remove-orphans flag , the L2 containers remain untouched

Additional context

The --remove-orphans flag applies to all containers running within the Docker Compose project, regardless of the configuration file used to start them. Therefore, if there are other docker-compose.yml or docker-compose.*.yml files in the same directory, all containers not associated with any of these configuration files will be considered orphaned and will be removed when the --remove-orphans flag is used.

[AlexSHuk]

@d1onys1us d1onys1us check please my issue .

[d1onys1us]

@gitpoap-bot please give @AlexSHuk a gitpoap

[gitpoap-bot]

Congrats, @AlexSHuk ! You've earned a GitPOAP for your contribution!

GitPOAP: 2023 Taiko Contributor:

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.