Error: /usr/src/dist/main.js not found after updating to v.2.2.0
Got this error after updating from v.1.3.4 to v.2.2.0
Tried
docker image prune -a followed by a new compose pull, that did nothing.
21 Replies
:wave: Hey @Vindicator ππ»,
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.
β
sudo docker ps -a | grep Immich
oh yeah
https://github.com/immich-app/immich/discussions?discussions_q=label%3Achangelog%3Abreaking-change+sort%3Adate_created
you need to go through every breaking changes
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
https://docs.immich.app/install/upgrading#migrating-to-vectorchord and migrate to vectorchord
image: tensorchord/pgvecto-rs:pg14-v0.2.0You mean this one?
yeah, look at the link I sent it is explained there, immich has moved from pgvecto to its successor vectorchord
little confused though. if this is the issue, then why did it run fine on 1.3.4
cus this db stuff is from 1.3.3
they had backwarts compatability for 1.134 i guess to give people more time to upgrade
I'm still not sure on how this applies to the issue I reported. main.js has nothing to do with the database (afaik). and the database is running and healthy
You've got a lot of breaking changes to go through
Please read the release notes
Even if another thing is causing the main.js issue, the wrong database will cause you the next one if you donβt look into it (and into every other breaking change)
I don't really mind and I can tackle those individually, I don't know what to do with the main.js issue and was looking for guidance on that.
Donβt try to directly upgrade to the latest release, go through every breaking changes and update to their pinned release using a pinned tag like :v1.137.0 for example and hope that is works, if it doesnβt tell us
It surely is one of the breaking changes causing your issue
Also consider to move to the new compose.yml in combination with the .env file. Your setup looks really old
Yeah I'm just going to cut my losses and reinstall it completely.
Not like I don't have copies of the data elsewhere.
Why?
Just stepping through breaking changes should get you where you need to be
this compose file was one converted from a different file type, it was set up through a marketplace for the app I use to manage my servers. Something of a TrueNAS alternative. I knew I was going to run into issues sooner or later but the initial choice was made to convert it to avoid losing data. I've since made backups of it so I think it's time I just re-do it from scratch and do it the recommended way this time.
It's been held together by duct tape for months now.
To avoid reinstalling completely download the official compose file for your current version from the release notes of it, move to it and start going through breaking changes from there
It's fine guys. Working now π
Thanks for all the help
Glad you got it working π
You can close the ticket with
/closeThis thread has been closed. To re-open, use the button below.