如何高效管理Docker多项目？企业Docker运维难题咨询

Alright, let's work through your Docker project setup pain points—those random VirtualBox IPs and tedious environment swaps are definitely fixable. Here are actionable solutions tailored to your scenario:

1. Ditch docker-machine entirely: Use Docker Compose + Custom Networks #

This is the most streamlined fix for your use case, since docker-machine is designed for multi-host clusters, not single-machine project isolation.

• How it works: Each project gets its own docker-compose.yml file, with a dedicated custom bridge network. Services (MySQL, Nginx, PHP) within the same project can communicate using service names (e.g., mysql instead of IPs), and you avoid port conflicts by mapping unique host ports per project.
• Example Compose snippet for one project:

  version: '3.8'
  services:
    nginx:
      image: nginx:alpine
      ports:
        - "8081:80"  # Unique host port for this project's Nginx
      volumes:
        - ./nginx.conf:/etc/nginx/conf.d/default.conf
      networks:
        - project1-net
    php-fpm:
      image: php:8.2-fpm-alpine
      volumes:
        - ./src:/var/www/html
      networks:
        - project1-net
    mysql:
      image: mysql:8.0
      environment:
        MYSQL_ROOT_PASSWORD: your_secure_password
      volumes:
        - project1-db:/var/lib/mysql
      networks:
        - project1-net  # No need to map host port if only internal access is needed
  
  networks:
    project1-net:
      driver: bridge  # Isolates this project's services from others
  volumes:
    project1-db:  # Persists MySQL data for the project
  

• Benefits: No heavy VirtualBox VMs, stable service-to-service communication, and switching projects just means navigating to the project directory and running docker-compose up -d/docker-compose down—no Shell environment tweaks required.

2. Keep docker-machine but assign static IPs to VirtualBox VMs #

If you need to retain your existing docker-machine setup, fix the random IP issue with static assignments:

1. Stop the target machine first:

   docker-machine stop project1
   

2. Configure a host-only network in VirtualBox for static IPs:

   # Create a host-only adapter if it doesn't exist
   VBoxManage hostonlyif create
   VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.56.1 --netmask 255.255.255.0
   

3. Attach the adapter to your VM and set a static IP inside the machine:

   VBoxManage modifyvm project1 --nic2 hostonly --hostonlyadapter2 vboxnet0
   docker-machine start project1
   docker-machine ssh project1
   sudo su
   # Add static IP config to the network interfaces file
   echo -e "auto eth1\niface eth1 inet static\naddress 192.168.56.101\nnetmask 255.255.255.0" >> /etc/network/interfaces
   ifup eth1
   

4. Add the static IP to your local hosts file for easy access:

   192.168.56.101 project1.local
   

3. Simplify environment switching with tools or aliases #

Cut down on manual docker-machine env commands and reduce errors:

• Use direnv: This tool automatically loads/unloads environment variables when you enter/leave a directory.
  1. Install direnv and hook it into your shell (follow the official setup for Bash/Zsh/Fish).
  2. In each project's root directory, create a .envrc file with:

     eval $(docker-machine env project1)
     

  3. Run direnv allow in the project directory—now every time you cd into it, the docker-machine environment is loaded automatically.
• Create Shell aliases: Add these to your ~/.bashrc or ~/.zshrc:

  alias project1='eval $(docker-machine env project1)'
  alias project2='eval $(docker-machine env project2)'
  

  Switching environments is as simple as typing project1 or project2 in your terminal.

4. Add a reverse proxy (Traefik) for unified access #

If you want to avoid remembering ports/IPs entirely, use Traefik to route traffic to your projects via custom subdomains:

• Traefik automatically discovers Docker services and routes requests based on rules you define. For example, you can map project1.local to your first project's Nginx service, and project2.local to the second—no need to specify ports in your browser.
• This works with both Docker Compose and docker-machine setups, and eliminates the need to track individual project IPs/ports.

内容的提问来源于stack exchange，提问作者Ilya Manyahin