Am I missing something. What's the difference between these two docker calls..and why does one work but the other doesn't?

[GavinNL]

Hello,

I'm trying to set up lets encrypt on my server, but I'm running into a weird issue. I'm running the two docker containers, and they seem work correctly

I have the following shell script called www.sh, which basically just starts up a nginx container and mounts the $PWD/docker_data folder to the html path. This seems to work correctly, and i can go to https://jelly.mydomain.com and I dont get any issues

#!/bin/bash
docker run  \
    --name www-proxy \
    --env "VIRTUAL_HOST=jelly.mydomain.com" \
    --env "LETSENCRYPT_HOST=jelly.mydomain.com" \
    --env "[email protected]" \
    -v $PWD/docker_data:/usr/share/nginx/html:ro \
    nginx

But, I tried to set up the exact same call, but using a docker-compose file below. Now when i go to https://jelly.mydomain.com i keep getting a BAD GATEWAY ERROR.

docker-compose.yml

version: '3.3'
services:
    nginx:
        volumes:
            - "$PWD/docker_data:/usr/share/nginx/html:ro"
        environment:
            - VIRTUAL_HOST=jelly.mydomain.com
            - LETSENCRYPT_HOST=jelly.mydomain.com
            - [email protected]
        container_name: www-proxy
        image: nginx

If I then shutdown the docker-compose run and run the shell script again, everything seem to work. Am I missing something here? Why does calling the docker run... command seem to work but the docker-compose not? If I docker exec .... /bin/bash into the containers, and call a curl localhost, both are serving the correct page.

[buchdag]

@GavinNL the docker run command implicitly run your container with --network bridge while docker-compose set up a single new network for you app.

Your proxied containers have to be on the same network than nginx-proxy to work, this isn't the case for the one created by your compose file.

You can also check the Docker Compose doc for this repo.