Docker compose won't find $PWD environment variable

Question

Here\'s my docker-compose:

version: \'2\'
services:
  couchpotato:
    build:
        context: ./couchpotato
        dockerfile: Dockerfile
    ports:
     -         


        

Answer 1

You don't need ${PWD} for this, you can just make the path relative and compose will expand it (one major difference between compose paths and those processed by docker run).

version: '2'
services:
  couchpotato:
    build:
        context: ./couchpotato
        dockerfile: Dockerfile
    ports:
     - 5050:5050
    volumes:
     - "./couchpotato/data:/home/CouchPotato/data/"
     - "./couchpotato/config:/home/CouchPotato/config/"

As for why compose doesn't see this variable, that depends on your shell. Compose looks for an exported environment variable, contents of the .env file, and command line flags to the docker-compose command. If each of those comes up empty for the variable, you'll get that warning.

Answer 2

My advice: change all $PWD to .

Answer 3

I was with the same issues, on Windows.

For solve "mariadb keeping restarting", I was using this:

mariadb:
  image: mariadb
  volumes:
    - ${PWD}/data:/var/lib/mysql

It solved, but always showed me the message:

WARNING: The PWD variable is not set. Defaulting to a blank string.

Then I just used on this way, whithout "." at beginning:

mariadb:
  image: mariadb
  volumes:
    - /data:/var/lib/mysql

Answer 4

I had the same issue with one of my env vars. On looking at my bashrc file more closely, I found out that I hadn't exported that variable.
Before:
VAR=<value>
After:
export VAR=<value>

Answer 5

$PWD will not work if you are running using sudo. Try the recommended settings from Docker for Linux https://docs.docker.com/engine/install/linux-postinstall/.

Sudo will run as a different user, with a different env.

$ sudo env | grep -i pwd
$ env | grep -i pwd
PWD=/home/user
OLDPWD=/