I'm trying to change the web UI port for Sourcebans, but there's a twist - I wish to run the container with network_mode set to "host", which means modifying the port in the docker compose file is out of the question.
Inside the Dockerfile, I found the following lines:
sed -i 's/Listen 80/Listen 8080/g' /etc/apache2/ports.conf && \
sed -i 's/80/8080/g' /etc/apache2/sites-enabled/000-default.conf
I tried to modify these two lines to replace the port to 8081 instead:
sed -i 's/Listen 80/Listen 8081/g' /etc/apache2/ports.conf && \
sed -i 's/80/8081/g' /etc/apache2/sites-enabled/000-default.conf
However, despite removing the volume, the container and the image, trying to docker compose build --no-cache && docker compose up after performing these changes keeps resulting in Apache trying to use port 8080 regardless:
web-1 | (98)Address already in use: AH00072: make_sock: could not bind to address [::]:8080
web-1 | (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:8080
Is this port change perhaps being done somewhere else (eg. inside the image), causing the Dockerfile's change to get overridden?
I'm trying to change the web UI port for Sourcebans, but there's a twist - I wish to run the container with network_mode set to "host", which means modifying the port in the docker compose file is out of the question.
Inside the Dockerfile, I found the following lines:
I tried to modify these two lines to replace the port to 8081 instead:
However, despite removing the volume, the container and the image, trying to
docker compose build --no-cache && docker compose upafter performing these changes keeps resulting in Apache trying to use port 8080 regardless:Is this port change perhaps being done somewhere else (eg. inside the image), causing the Dockerfile's change to get overridden?