Support for older Docker versions?
I just tried to install the latest version on my Synology NAS, but it appears that the
healthcheck feature requires Docker engine v25+... but the Container Manager on Synology appears to be stuck on v20 (), and I can't seem to find ways to update the underlying docker on this device.
Am I SOL? Does anyone have instructions for having all images stored on a NAS from a separate docker machine?
Thanks!
docker --version // Docker version 20.10.23, build 876964a
9 Replies
:wave: Hey @HashtagOctothorp,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Hmm, I see https://immich.app/docs/FAQ/#how-can-i-mount-a-cifssamba-volume-within-docker for "if you can't do it on the docker host itself", but nothing much else for that... which might make sense as "your docker host could be anything"...
But nothing else on github about minimum docker versions.
Compose file
Worth noting: I had v1.121.0 running on this device, but it was created in a portainer instance that ended up dying, so the source stack is missing (though I think I have the un-modifed compose file from that install), hence the goal of re-creating with the latest info.
Hmm... I just checked the differences between the old and new (unmodified) templates, and all I saw were
* Renamed .env values
* new hash for redis
* formatting change to postgres test and command (from string array to that
>- notation)You can remove the healthcheck lines
any impact / loss of notable functionality?
removing just the offending interval items from the postgres one (which seems to work fine?), I'm still seeing the server report it's old version (used the same postgress and files during upgrade...) is that normal?
No healthchecks 😛
I'm not sure what you mean?
yeah, but what does that actually do?
Not all that much tbh, on plain docker healthchecks aren't particularly useful
It'll just give you a more detailed container status in
docker ps