Portainer Implementation on Synology NAS

[whizwith]

I am trying to implement Photon on my Synology NAS through Portainer

I was able to get Dawarich installed no problem but Photon is unhealthy

I'm new to Docker/Portainer

In my compose file:

services:
photon:
image: rtuszik/photon-docker:latest
environment:
- UPDATE_STRATEGY=PARALLEL
- UPDATE_INTERVAL=24h
# - COUNTRY_CODE=zw # Optional: country-specific index
volumes:
- photon_data:/volume1/docker/photon/data
restart: unless-stopped
ports:
- "2322:2322"
volumes:
photon_data:

and I have attached my log
_photon-photon-1_logs.txt

Was hoping someone could point me in the right direction.

TIA

Ray

[rtuszik]

Hi there,
the first thing that jumps out to me is the volume mounts you have set.

with the volumes key in a docker compose service, the left side is the host path, while the right side is the container internal path. The right side should therefore be left unchanged. You can use the left side to specify where you want the volume to end up on your host system.

With the top-level key volumes you are creating a named volume on the host machine, which will allow the data to persist across restarts of the container.

If you want to specify the actual location on the drive, its easiest for you to set that up in the services key, without specifying a named volume at the bottom of the file.

For example:

services:
  photon:
  ...
    volumes:
      - /volume1/docker/photon/data:/photon/data
  ...

You can check #11 for more info on synology bind mounts as well, though it uses an older version of the compose file which used /photon/photon_data instead of the current /photon/data.

Let me know if you have other questions.

[whizwith]

Thank you! While I get this sorted out, can you help me to point dawarich to your public server for reverse geocoding? (e.g. using the docker-compose.yml) I've made a couple of attempts but when I load a test file (Google Takeout semantic json) I still only get suggested points without any addresses/names. I have most of what I need on my device and have it backed up. It's just that I have a few accounts, and one of them has most of the places I've been and activities but not all, and I embarked on this to keep everything in one place. But it's a little harder than I expected. Thank you in advance! Ray

…

On Mon, Jan 5, 2026 at 3:20 PM Robin Tuszik ***@***.***> wrote: Hi there, the first thing that jumps out to me is the volume mounts you have set. with the volumes key in a docker compose service, the left side is the host path, while the right side is the container internal path. The right side should therefore be left unchanged. You can use the left side to specify where you want the volume to end up on your host system. With the top-level key volumes you are creating a named volume on the host machine, which will allow the data to persist across restarts of the container. If you want to specify the actual location on the drive, its easiest for you to set that up in the services key, without specifying a named volume at the bottom of the file. For example: services: photon: ... volumes: - /volume1/docker/photon/data:/photon/data ... You can check #11 <#11> for more info on synology bind mounts as well, though it uses an older version of the compose file which used /photon/photon_data instead of the current /photon/data. Let me know if you have other questions. — Reply to this email directly, view it on GitHub <#213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGLXJVUSN3WZ7ULPQJI7WML4FLBRFAVCNFSM6AAAAACQXIYRDSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBRHAZDEOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[whizwith]

Actually - it seems to be working now. I had to add the line "PHOTON_API_USE_HTTPS: true" after "PHOTON_API_HOST: photon.koalasec.org" Now I just need to figure out a way to accept all of the suggestions instead of confirming each one!

…

On Mon, Jan 5, 2026 at 7:46 PM Raymond Tsao ***@***.***> wrote: Thank you! While I get this sorted out, can you help me to point dawarich to your public server for reverse geocoding? (e.g. using the docker-compose.yml) I've made a couple of attempts but when I load a test file (Google Takeout semantic json) I still only get suggested points without any addresses/names. I have most of what I need on my device and have it backed up. It's just that I have a few accounts, and one of them has most of the places I've been and activities but not all, and I embarked on this to keep everything in one place. But it's a little harder than I expected. Thank you in advance! Ray On Mon, Jan 5, 2026 at 3:20 PM Robin Tuszik ***@***.***> wrote: > Hi there, > the first thing that jumps out to me is the volume mounts you have set. > > with the volumes key in a docker compose service, the left side is the > host path, while the right side is the container internal path. The right > side should therefore be left unchanged. You can use the left side to > specify where you want the volume to end up on your host system. > > With the top-level key volumes you are creating a named volume on the > host machine, which will allow the data to persist across restarts of the > container. > > If you want to specify the actual location on the drive, its easiest for > you to set that up in the services key, without specifying a named volume > at the bottom of the file. > > For example: > > services: > photon: > ... > volumes: > - /volume1/docker/photon/data:/photon/data > ... > > You can check #11 <#11> > for more info on synology bind mounts as well, though it uses an older > version of the compose file which used /photon/photon_data instead of > the current /photon/data. > > Let me know if you have other questions. > > — > Reply to this email directly, view it on GitHub > <#213 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGLXJVUSN3WZ7ULPQJI7WML4FLBRFAVCNFSM6AAAAACQXIYRDSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBRHAZDEOA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >