Docker Image fails to start

[Bag72]

Just come across this app and it looks like it would save a lot of multiple containers.

However, I couldn't get it to start on my QNAP NAS. I copied the docker-compose from your version, modified the password in both places and performed a docker-compose up -d It looked like it had worked but I couldn't connected and when I looked in the logs I found some error messages. I've attached the messages. I tried a few things but no joy.
Error.txt

[thequailman]

Hey there, it looks like Homechart can't connect to the database. We see this a lot with NAS platforms and unfortunately it's always something specific with that platform. For unRAID, folks have set a static IP on the PostgreSQL container and used that for the address in Homechart. You could try something like that and see if it works.

FWIW, the docker compose setup works fine on vanilla Linux/Docker, not that it helps you right now.

[thequailman]

If you do get it to work, throw some notes in here and I'll add them to the docs

[Bag72]

OK. Interesting that I had not had the issue before but you were correct I needed to define the IP. I have a QNAP NAS with QTS Hero on it.
I added the following to the docker-compose.yaml file;
networks:
default:
ipv4_address: 172.66.66.56
Where networks lined up with the image command for homechart
and
networks:
default:
ipv4_address: 172.66.66.57
Where networks lined up with the image command for postgres It needed both for this app
and finally at the bottom of the file
networks:
default:
name: dockerlan
external: true

dockerlan is a bridge network I set up on my NAS so I could put my docker containers on the same IP subnet as the NAS.
So NAS is 172.66.66.10. Docker containers on dockerlan can be defined as above.

The bridge needs set up first though and can be set up by
docker network create -d macvlan --subnet=172.66.66.0/24 --gateway=172.29.66.1 -o parent=br0 dockerlan
This only needs entered once at the terminal prompt on the NAS and will survive a reboot.

So after that it worked fine with the internal IP but wouldn't connect externally with a 502 error. That is clearly a NGinx issue and I'll fix it.

I'll close this now. Thank you for your help. Off to play with my new App. Looks good so far.