Magento : Recieving errors when config nginx varnish on docker

Magento : Recieving errors when config nginx varnish on docker

October 8, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento : Recieving errors when config nginx varnish on docker

Solving Dependency Loop Errors in Magento Nginx Varnish Setup on Docker

Hey there! If you’re facing dependency loop errors when setting up your Magento store using Nginx and Varnish on Docker, you’ve come to the right place. In this post, we’ll dive into these errors, understand their root cause, and provide a step-by-step solution to get your setup running smoothly.

Understanding the Errors

The errors you’re encountering stem from a common issue in Docker environments - the chicken-and-egg problem of dependent services that need each other before they can start. Let’s break down what’s happening:

  1. Nginx Error: The error message [emerg] host not found in upstream "varnish" in /etc/nginx/conf.d/default.conf:53 suggests that Nginx is unable to find the Varnish service while trying to set up its configuration.

  2. Varnish Error: The backend host resolution failure indicates that Varnish cannot connect to the backend Magento application running on port 8080 because it can’t resolve the hostname “web”.

The issue lies in the fact that both Nginx and Varnish are trying to reference services that haven’t fully started yet.

The Root Cause: Dependency Loop

In your docker-compose.yml file, you’ve configured:

  • nginx linking varnish
  • varnish linking web

However, the web service is also linked to both nginx and fpm. This creates a circular dependency where each service depends on services that depend on it.

The Solution: Removing Circular Dependencies

To resolve this issue, we need to break the circular dependencies by using Docker’s built-in networking capabilities instead of the older links feature. Here’s how:

  1. Update your docker-compose.yml file

First, remove the links section from both nginx and varnish:

# Remove these lines
  links:
    - varnish

And update the networks section to ensure all services are on the same network:

networks:
  internal_network:
    driver: bridge
    ipam:
      config:
        - subnet: 10.20.0.0/24

services:
  # ... other services ...

  nginx:
    networks:
      - internal_network
    ports:
      - "80:80"
      - "443:443"

  varnish:
    networks:
      - internal_network
    depends_on:
      - web
  1. Update the Nginx configuration

Since we’ve removed the links, we need to update the varnish address in your default.conf file:

upstream fastcgi_backend {
  # use tcp connection
  server  web:9000;
}

# ... rest of the config ...

server {
  listen 443 ssl http2 default_server;
  # ... existing configuration ...
  location / {
    proxy_pass http://varnish:6081;
    # ... other config lines ...
  }
}

By updating these files, we’ve eliminated the circular dependencies and allowed Docker to start each service in a well-defined order.

Conclusion

In this post, we’ve explored how dependency loops can cause issues when setting up Magento with Nginx and Varnish on Docker. We identified the root cause of the errors - circular dependencies created by links - and provided a solution using Docker’s built-in networking capabilities to break these loops.

Remember, always keep your development environment stable by avoiding circular dependencies and ensuring services start in the correct order.

For more advanced tips on optimizing your Magento setup, check out our article on Leveraging Varnish for Magento Performance.

Cache Admin Configuration Errors

Our network