I forgot to mention that on my test installation on macOS that the container did resolve. I’m only running a single node, but I’m also running in
network mode: bridge to properly interact with my nginx-proxy container. I’m not sure if that would be the cause for my issue.
In any case, for a single-node installation, I really prefer the mysqld.sock method.
@zayn, here’s an example of my configuration:
# Pydio-cells config for use alongside the nginx-proxy & letsencrypt containers.
# For deployment on a Portainer single-node instance.
# Required version 2 for Portainer single-node stack (restricted by latest available API)
# Args for cells
# Publish on all interfaces inside docker network (doesn't expose on host)
# Match the FQDN that the end user will see
# Turn off SSL *management* by Cells container (using Caddy)
# SSL will still be served by nginx-proxy
# Args for nginx-proxy
# Access the database using the mysqld sock.
# Using `expose:` here gives the nginx-proxy a clue about how to proxy Cells.
# The container must be on the `bridge` network in order for nginx-proxy to reach it.
MYSQL_ROOT_PASSWORD: weakpass # Change this password after installation!
# Give access to the mysqld sock via a named container.
# Since Cells is on the bridge, this one is as well...
# but with the current named volume config, it may not need to be.
command: [mysqld, --character-set-server=utf8mb4, --collation-server=utf8mb4_unicode_ci]
# `driver: local` is required for Portainer management. It's also a good practice to specify.