alkdst
IImmich
•Created by SuitonJutsu on 7/6/2024 in #help-desk-support
Immich can't start
I've opened Asustor support ticket 81638, but I'm having trouble reproducing in a simple way
10 replies
IImmich
•Created by SuitonJutsu on 7/6/2024 in #help-desk-support
Immich can't start
@SuitonJutsu was the error in an Asustor environment? So far, the only posters I've seen with this problem have been using Asustor.
10 replies
IImmich
•Created by SuitonJutsu on 7/6/2024 in #help-desk-support
Immich can't start
I have the same issue. I think that there are ownership and permission issues when installing immich in Portainer, at least in the Asustor environment. To understand why the ENOENT is raised, I tried the following in Portainer, after starting the Stack:
1. On the immich_server container page, click Duplicate/Edit. In the Advanced Container Settings Panel, in the Commands & Logging tab, I set the Command to Default (leave command blank) and the EntryPoint to 'tini' '--' '/bin/bash' and the Console to Interactive & TTY (-i -t)
2. I clicked on Deploy the Container, which replaced the existing immich_server container.
3. I attached a Console to the immich_server container by clicking the paper clip icon in Portainer's container list
4. In the Console, I ran ls -ld /usr/src/app/dist. I expected the owner to be root, but it wasn't. The ownership and permissions look corrupted:
ls -ld /usr/src/app/dist ?--------- 7499841 538976288 538976288 9 Dec 31 1969 /usr/src/app/distAll files seem to have the same owner and permissions. Hopefully the troubleshooting above was correct and didn't introduce any weirdness; this is my first time using Portainer. I'm not sure why the ownership and permissions are corrupted, but if I find time I'll look at building the server image with a Dockerfile that has some verbose logging.
10 replies