Immich can't start
Log information
}
Node.js v20.14.0
Detected CPU Cores: 4
node:fs:448
return binding.readFileUtf8(path, stringToFlags(options.flag));
^
Error: ENOENT: no such file or directory, open '/usr/src/app/dist/main'
at Object.readFileSync (node:fs:448:20)
at Module._extensions..js (node:internal/modules/cjs/loader:1378:18)
at Module.load (node:internal/modules/cjs/loader:1208:32)
at Module._load (node:internal/modules/cjs/loader:1024:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12)
at node:internal/main/run_main_module:28:49 {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/usr/src/app/dist/main'
}
8 Replies
:wave: Hey @SuitonJutsu,
Thanks for reaching out to us. Please follow the recommended actions below; 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 compose ps docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: I have read applicable release notes.
3. :blue_square: I have reviewed the FAQs for known issues.
4. :blue_square: I have reviewed Github for known issues.
5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
7. :blue_square: I have 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)
If this ticket can be closed you can use the /close command, and re-open it later if needed.@SuitonJutsu uploaded
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. @SuitonJutsu was the error in an Asustor environment? So far, the only posters I've seen with this problem have been using Asustor.
yes im using asustor
I've opened Asustor support ticket 81638, but I'm having trouble reproducing in a simple way
I have the same problem in my Asustor AS3302T, I understand that so far there is no solution to this error neither by Immich nor by Asustor, right?
Does Asustor have some kind of custom OS?
Guys may I ask you, are anyone who response from ASUSTOR support for this issue ? I have the same but /usr/src/app/dist folder exist, main - no. /usr/src/app/dist/main - so file path is not right due ob absense main folder.