sudo docker-compose logs -f wouldn't work

[gmorningman]

I didn't copy paste exactly what the error was but it was something along the lines of [ERROR DEX_PATH /modules/blah/blah/blah]

I edit my docker-compose.yml to just use my full path and its working fine now. however didn't work "out of the box"
/home/username/ergo/ergo-dex-backend/modules/utxo-tracker/target/docker/stage
/home/username/ergo/ergo-dex-backend/modules/amm-executor/target/docker/stage
/home/username/ergo/ergo-dex-backend/modules/pool-resolver/target/docker/stage

Brand new installation of ubuntu server 20.04.3

[FidgetyRat]

Yes, the environment variable set in the script isn't working even if explicitly exported first (Same for me on Debian). Had to hard code the paths.

[riidatibula]

Try using the latest version of docker-compose. I had the same error when using the earlier versions (1.29.x)

[jmagan]

Go to the folder /home/username/ergo/ergo-dex-backend/ and execute export DEX_SOURCES_PATH=${PWD}. When you set the environment variable to use in the docker-compose.yml, then execute sudo -E docker-compose logs -f . The "-E" option is used to pass all the environment variable of the current session to the sudo command.