assure apache_container to keep same local IP after updates

[punkyard]

hi
when containers are restarted, they won't necessarily be assigned to the same local IP address which can cause link breaking with external apps (ie Nginx with local IP bindings)

in AiO yaml file template, could it be possible to add network specs to assure the nextcloud-aio-apache container to be linked to the same local IP after each update and restart?

[szaimen]

Hi, honestly if you are using the private ip-address of the mastercontainer in your nginx config, you are doing something wrong...

Can you post your nginx config here and how did you install nginx?

If it should be running as a separate container, can you also post its docker run command or docker compose file here?

[punkyard]

thanks Simon @szaimen for your reply and analysis

I made a mistake mentioning the nextcloud-aio-mastercontainer. I meant nextcloud-aio-apache

here is my yaml - in Portainer which allocates apache to 172.22.0.13 this time and mastercontainer to 172.22.0.3

version: "3.8"
volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer #
services:
  nextcloud:
    image: nextcloud/all-in-one:latest
    restart: always
    container_name: nextcloud-aio-mastercontainer #
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config #
      - /var/run/docker.sock:/var/run/docker.sock:ro #
    ports:
      - 8895:8080
    environment:
     - APACHE_PORT=11000
     - APACHE_IP_BINDING=0.0.0.0
     - APACHE_DISABLE_REWRITE_IP=1
     - NEXTCLOUD_TRUSTED_DOMAINS=mydomain.net #123.345.456.789
     - TRUSTED_PROXIES= 172.22.0.0/16
     - NEXTCLOUD_MOUNT=/mnt/docker/nextcloud-aio/
     - NEXTCLOUD_UPLOAD_LIMIT=1G
     - NEXTCLOUD_MEMORY_LIMIT=4096M
     - NEXTCLOUD_ADDITIONAL_APKS=imagemagick libpq-dev
     - NEXTCLOUD_ADDITIONAL_PHP_EXTENSIONS=imagick pgsql
     - TALK_PORT=3478
     - OVERWRITEPROTOCOL=https

Next to it, i'm using Nginx Proxy Manager

[szaimen]

I see. Can you add NPM to the nextcloud-aio network and then use nextcloud-aio-apache instead of 172.22.0.13 in your NPM config?

[punkyard]

well.. Nginx network_mode is set to "host" as documentation requests (or requested 2 years ago ^^)

removing this broke all my proxies

networks:
  default:
    external: true
    name: nextcloud-aio

are you asking to add this network to only Nginx Prowy Manager?
Quid of all my other containers and docker compose yaml stacks?

doing this change, i can still access my NPM UI with public IP but it won't take my login and password.. 🥺
cool, i'm gonna spend the evening on this i guess

[punkyard]

⚠️ I can't access AiO interface since

[punkyard]

restarted the yaml and the console displayed after a very long time (20 sec)

Brave console returned:
a deprecated feature caused by unload event listeners that affected content.js :9
also, page layout is disturbed by Quirks Mode | https://public.ip:8895/containers

[punkyard]

and I see now there is an AiO update 10.3.0 - maybe that explains

[szaimen]

well, I guess I must thank you greatly once again Simon - for you time and teaching

No problem!

wishing you the best year (by the way I saw you during the last talk about NC new feats - cheers ;)

Wish you a good year as well! And funny that you saw me there, have you been at the conference? :D

[szaimen]

⚠️ I can't access AiO interface since

Can you access it again?