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
I have a folder in which I want to setup a ddb environment for a project I clone under it.
That cloned project have a docker-compoe.yml file, which the docker compose run uses by default, when I run $(ddb run npm).
Either we should provide a way to override this behavior manually, or we need to detect that conflicting docker-devbox.yml file, and force the -f option in that case. Another option would be just putting -f every time on the commands, to avoid such conflict.
What do you think ?
The text was updated successfully, but these errors were encountered:
export DDB_RUN_OPTS="-f ${DDB_PROJECT_HOME}/docker-compose.yml" should work as a workaround for now, but I'll appreciate a pull request adding the -f flag on every ddb run command.
I have a folder in which I want to setup a ddb environment for a project I clone under it.
That cloned project have a docker-compoe.yml file, which the
docker compose run
uses by default, when I run$(ddb run npm)
.This is due to this part of the code :
docker-devbox-ddb/ddb/feature/docker/binaries.py
Line 64 in ffb8f19
Either we should provide a way to override this behavior manually, or we need to detect that conflicting docker-devbox.yml file, and force the
-f
option in that case. Another option would be just putting-f
every time on the commands, to avoid such conflict.What do you think ?
The text was updated successfully, but these errors were encountered: