varnish-cache | Varnish Cache source code repository | Caching library

I discovered the key information in the logs:

You need to set Xdebug's xdebug.client_host to the IP address of your IDE, which you indicated is 192.168.1.150.

You also need to turn off xdebug.discover_client_host, as that would try to use the internal Docker network IP (172.100.0.2), which is not where your IDE is listening on.

Remember: Xdebug makes a connection to the IDE, not the other way around.

According to https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart= :

Unless Type= is oneshot, exactly one command must be given. When Type=oneshot is used, zero or more commands may be specified. Commands may be specified by providing multiple command lines in the same directive, or alternatively, this directive may be specified more than once with the same effect. If the empty string is assigned to this option, the list of commands to start is reset, prior assignments of this option will have no effect. If no ExecStart= is specified, then the service must have RemainAfterExit=yes and at least one ExecStop= line set. (Services lacking both ExecStart= and ExecStop= are not valid.)

Long story short:

• All occurences of ExecStart are executed, unless Type=oneshot
• By setting ExecStart=, we're making sure that previous values are removed
• By setting ExecStart again with an actual value, only this command will be executed

Everything is working as expected according to your log format:

log_format main '$http_x_forwarded_for - $remote_user [$time_local] ' '"$request" $status $body_bytes_sent "$http_referer" ' '"$http_user_agent"';

Note how you're logging the value of X-Forwarded-For header, as opposed to the IP.

If you want real IP, use $remote_addr together with the directives you already tried:

It looks like you're doing all the right things, but I would advise you to do some debugging.

If you run the following command, the Hash tag will appear in varnishlog:

Thanks to advice from David Maze, I struggled further with configuring the docker-compose setup to work with multiple projects.

Information based on docker-compose v1.25.0 (July 2020)

This discussion is especially important when you want to re-use (persist) your containers (start/stop instead of just up/down - deleting)

As initially pointed out in my question - if you try to create containers using docker-compose up -d there are some pitfalls which the tool simply does not support right at the moment.

PITFALLS OF CURRENT DOCKER-COMPOSE IMPLEMENTATION:

1. If you just use overridden docker-compose*.yml with different container_names (per 'project') with files in the same folder

docker-compose up will simply replace existing containers as explained in my question.

1. You can do the following: docker-compose -p CUSTOM_PROJECT_NAME -f file1.yml -f file2.yml up -d, but:

This on its own is useless - these containers will only work until you want stop them. As soon as you want to do docker-compose start (to restart existing container set) it will simply fail with Error: No containers to start

1. If you use two different folders with the same docker-compose project (ie cloned project): for instance ./dc-project1 ./dc-project2 but using container_name field inside docker-compose.*.yml file:

When you try to run docker-compose -f f1.yml -f f2.yml up -d inside ./dc-project1 and the same inside ./dc-project2 folder, you will get the following error: You have to remove (or rename) that container to be able to reuse that name.

1. Similar issues with your Docker network will occur with docker-compose when you use overridden files: Removed most of the custom settings to make the network setting clearer:

Network will be attached correctly from your overridden file on docker-compose up, but as soon as you want to docker-compose start it looks for your default network name: in the default docker-compose.yml or even the docker-compose.override.yml file if it exists. In other words - it ignores your custom docker-compose override files (see example below):

docker-compose.yml:

In core Docker, there are two separate concepts. An image is a built version of some piece of software packaged together with its dependencies; a container is a running instance of an image. There are separate docker build and docker run commands to build images and launch containers, and you can launch multiple containers from a single image.

Docker Compose wraps these concepts. In particular, the build: block corresponds to the image-build step, and that is what invokes the Dockerfile. None of the other Compose options are available or visible inside the Dockerfile. You cannot access the container_name: or environment: variables or volumes: because those don't exist at this point in the build lifecycle; you also cannot contact other Compose services from inside the Dockerfile.

It's pretty common to have multiple containers run off the same image if they have largely the same code base but need a different top-level command. One example is a Python Django application that needs Celery background workers; you'd have the same project structure but a different command for the Celery worker.

The issue you're experiencing is probably related to the fact that your Magento base URL is set to 192.168.1.250:8080.

Magento will enforce that value if it notices the Host header (or the protocol scheme) doesn't match its own.

So in your case, you're sending the following host header to Magento through Varnish:

If you want to check for authenticated users, I'd advise you to have a look at vmod_basicauth.

Its a Varnish module that reads an .htpasswd file and gives you a VCL API to interact with these logins.

Here's how to use this module in VCL: