Trying to run the latest docker image on my docker but can't start it. docker logs isn't showing much more than that. I have IPv6 exposed to the docker containers. Is it to try to listen to IPv6:80 and then fails to listen via IPv4:80?
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Result: success
My docker-compose:
version: "2.4"
services:
freshrss:
image: freshrss/freshrss
container_name: freshrss
environment:
- PUID=1031
- PGID=100
- TZ=Europe/Zurich
volumes:
- /volume1/docker/freshrss/data:/var/www/FreshRSS/data
ports:
- 8180:80
network_mode: host
restart: unless-stopped
Idea is to launch this, then go in and modify the config to point to a running mysql instance on my Synology instead of a db in a container. Stuck as it won't launch and keeps restarting.
Hello,
As you are trying network_mode: host, make sure you do not have anything else on your server that runs on port 80 while testing:
sudo netstat -ltpn
When experimenting a setup for the first time, please use our latest stable release, e.g. freshrss/freshrss:1.17.0 to simplify the tests.
In Docker, published ports are discarded when using host network mode.
To run FreshRSS in network_mode: host together with another service running natively on the host also on port 80, I think the cleanest would be for us to provide an environment variable to change the Apache port:
Suggestion implemented in https://github.com/FreshRSS/FreshRSS/pull/3343
@McMac You should be able to try the following:
docker-compose pull
version: "2.4"
services:
freshrss:
image: freshrss/freshrss:latest
container_name: freshrss
logging:
options:
max-size: 10m
network_mode: host
volumes:
- /volume1/docker/freshrss/data:/var/www/FreshRSS/data
environment:
- CRON_MIN=5,35
- TZ=Europe/Zurich
- LISTEN=0.0.0.0:8180
@McMac Please let us know whether that works for you
Thank you @Alkarex for you quick response. It worked! Thank you for the quick response time!!! 馃挴
You were correct, I wasn't aware that the network_mode: host was causing the the port setting to be ignored (working on a Mac, this is not needed there) - learned something new! 馃憤
One comment, as this is a local server not exposed on the web, during a setup I had chosen a default user and selected authentication "none" however config.php then contained `'auth_type' => 'form',. Found in another issue to change that to "none", change password and revert to "form".
So, glitch here, if during setup, one selects "none", by default you can't login as the webform won't let you keep the password empty.
Good :-)
Please open a new issue for the auth_type bug.
Do we need to document that?
@aledeg Yes, but the whole readme for Docker needs to be updated. I am in late for that!
@Alkarex No pressure. It's to keep track what needs to be done. I think we need an issue to keep track of that.
What do you think?
Good idea, for 1.18.0