[Feature] Unraid Community / All-Inclusive Image #32

New Issue

OVERLORD · 2026-02-04T16:41:05+03:00

OVERLORD commented

2026-02-04 16:41:05 +03:00

Originally created by @alextran1502 on GitHub (Mar 29, 2022).

Feature Details:

Create a single docker image for all components
Create necessary XML files for publishing the new image to the unraid community applications section.
We will create the necessary thread on the unraid forum after any PRs are merged.

Follow the guide here for steps to create the required XML files for unraid.

Originally created by @alextran1502 on GitHub (Mar 29, 2022). ### Feature Details: - [ ] Create a single docker image for all components - [ ] Create necessary XML files for publishing the new image to the unraid community applications section. - [ ] We will create the necessary thread on the unraid forum after any PRs are merged. Follow the guide [here](https://forums.unraid.net/topic/57181-docker-faq/#comment-566084) for steps to create the required XML files for unraid.

OVERLORD closed this issue

2026-02-04 16:41:10 +03:00

OVERLORD commented

2026-02-04 16:41:18 +03:00

@JamesTeague commented on GitHub (Mar 30, 2022):

Is there an existing Docker image on Docker Hub already or would one need to get it into a registry?

@JamesTeague commented on GitHub (Mar 30, 2022): Is there an existing Docker image on Docker Hub already or would one need to get it into a registry?

OVERLORD commented

2026-02-04 16:41:25 +03:00

@JamesTeague commented on GitHub (Mar 30, 2022):

Also there seems to be a dependency on Postgres running in port 5432. Did I read that right? If so, that port should probably be configurable defaulting to 5432.

@JamesTeague commented on GitHub (Mar 30, 2022): Also there seems to be a dependency on Postgres running in port 5432. Did I read that right? If so, that port should probably be configurable defaulting to 5432.

OVERLORD commented

2026-02-04 16:41:31 +03:00

@alextran1502 commented on GitHub (Mar 30, 2022):

@JamesTeague There is no image that contains the whole application yet. I am working on the branch deployment/containerize-app-into-single-dockerfile to accomplish that goal.

It is correct that the Postgres port is 5432. You can access it on your local machine as well as throughout your local network with the VM IPV4

@alextran1502 commented on GitHub (Mar 30, 2022): @JamesTeague There is no image that contains the whole application yet. I am working on the branch `deployment/containerize-app-into-single-dockerfile` to accomplish that goal. It is correct that the Postgres port is 5432. You can access it on your local machine as well as throughout your local network with the VM IPV4

OVERLORD commented

2026-02-04 16:41:37 +03:00

@JamesTeague commented on GitHub (Mar 30, 2022):

@alextran1502 Regarding the port that is true, but there will be people running Postgres in a container not using port 5432. It's generally not a good assumption that the database will be exposed on that port. So in the case of Unraid it would help users to know that this template requires their own postées instance but it shouldn't also dictate the port they have to expose on the container. Or if for some reason they are running multiple instances of the database, 1 has to be running on a different port.

Once the container is in the registry though I wouldn't mind helping get the template set up and tested. Or trying to contribute on other things as well.

@JamesTeague commented on GitHub (Mar 30, 2022): @alextran1502 Regarding the port that is true, but there will be people running Postgres in a container not using port 5432. It's generally not a good assumption that the database will be exposed on that port. So in the case of Unraid it would help users to know that this template requires their own postées instance but it shouldn't also dictate the port they have to expose on the container. Or if for some reason they are running multiple instances of the database, 1 has to be running on a different port. Once the container is in the registry though I wouldn't mind helping get the template set up and tested. Or trying to contribute on other things as well.

OVERLORD commented

2026-02-04 16:41:45 +03:00

@Kjeldgaard commented on GitHub (May 21, 2022):

@JamesTeague There is no image that contains the whole application yet. I am working on the branch deployment/containerize-app-into-single-dockerfile to accomplish that goal.

Isn't the immich image sufficient if using an existing database?

@Kjeldgaard commented on GitHub (May 21, 2022): > @JamesTeague There is no image that contains the whole application yet. I am working on the branch `deployment/containerize-app-into-single-dockerfile` to accomplish that goal. Isn't the immich image sufficient if using an existing database?

OVERLORD commented

2026-02-04 16:41:49 +03:00

@alextran1502 commented on GitHub (May 21, 2022):

@JamesTeague There is no image that contains the whole application yet. I am working on the branch deployment/containerize-app-into-single-dockerfile to accomplish that goal.

Isn't the immich image sufficient if using an existing database?

There is a message queue that utilizes Redis for passing the message across the background processes, so you would need Redis as well.

Now that I am adding a web interface that is using SvelteKit, which has its own built-in Nodejs server, this adds an additional complexity to the process of putting everything into a single Docker image.

@alextran1502 commented on GitHub (May 21, 2022): > > @JamesTeague There is no image that contains the whole application yet. I am working on the branch `deployment/containerize-app-into-single-dockerfile` to accomplish that goal. > > Isn't the immich image sufficient if using an existing database? There is a message queue that utilizes Redis for passing the message across the background processes, so you would need Redis as well. Now that I am adding a web interface that is using SvelteKit, which has its own built-in Nodejs server, this adds an additional complexity to the process of putting everything into a single Docker image.

OVERLORD commented

2026-02-04 16:41:57 +03:00

@Kjeldgaard commented on GitHub (May 21, 2022):

I actually already have Redis up and running, but how should that be configured? According to 'Step 1' from https://github.com/alextran1502/immich, there is only the database configuration.

@Kjeldgaard commented on GitHub (May 21, 2022): I actually already have Redis up and running, but how should that be configured? According to 'Step 1' from https://github.com/alextran1502/immich, there is only the database configuration.

OVERLORD commented

2026-02-04 16:42:05 +03:00

@JamesTeague commented on GitHub (May 22, 2022):

@JamesTeague There is no image that contains the whole application yet. I am working on the branch deployment/containerize-app-into-single-dockerfile to accomplish that goal.

Isn't the immich image sufficient if using an existing database?

I think so, most people probably want to decouple that and Redis anyway.

@JamesTeague commented on GitHub (May 22, 2022): > > @JamesTeague There is no image that contains the whole application yet. I am working on the branch `deployment/containerize-app-into-single-dockerfile` to accomplish that goal. > > > > Isn't the immich image sufficient if using an existing database? I think so, most people probably want to decouple that and Redis anyway.

OVERLORD commented

2026-02-04 16:42:15 +03:00

@martabal commented on GitHub (Jul 22, 2022):

@JamesTeague There is no image that contains the whole application yet. I am working on the branch deployment/containerize-app-into-single-dockerfile to accomplish that goal.

The branch doesn't exist anymore. It would be very nice to have a single container to deploy. I already have postgres and redis dockers running and don't want to deploy other instances.

@martabal commented on GitHub (Jul 22, 2022): > @JamesTeague There is no image that contains the whole application yet. I am working on the branch `deployment/containerize-app-into-single-dockerfile` to accomplish that goal. The branch doesn't exist anymore. It would be very nice to have a single container to deploy. I already have postgres and redis dockers running and don't want to deploy other instances.

OVERLORD commented

2026-02-04 16:42:18 +03:00

@zackpollard commented on GitHub (Jul 22, 2022):

You can use environment variables to point your Immich services at your existing redis and postgres containers, check the .env file

@zackpollard commented on GitHub (Jul 22, 2022): You can use environment variables to point your Immich services at your existing redis and postgres containers, check the .env file

OVERLORD commented

2026-02-04 16:42:22 +03:00

@martabal commented on GitHub (Jul 31, 2022):

Is it possible to get rid of the .env file and to use only the environment variables ? It would allow to run the services with docker run

@martabal commented on GitHub (Jul 31, 2022): Is it possible to get rid of the .env file and to use only the environment variables ? It would allow to run the services with docker run

OVERLORD commented

2026-02-04 16:42:25 +03:00

@bo0tzz commented on GitHub (Aug 1, 2022):

Sure, you can skip the .env file and pass the variables in any other way you like.

@bo0tzz commented on GitHub (Aug 1, 2022): Sure, you can skip the .env file and pass the variables in any other way you like.

OVERLORD commented

2026-02-04 16:42:29 +03:00

@martabal commented on GitHub (Aug 8, 2022):

For now Immich works with Unraid with the docker-compose plugin but in my understanding to run with the docker run command, it would be easier to integrate the entrypoint in the Dockerfile. Is there any particular reason to put it outside the file?

@martabal commented on GitHub (Aug 8, 2022): For now Immich works with Unraid with the docker-compose plugin but in my understanding to run with the `docker run` command, it would be easier to integrate the entrypoint in the Dockerfile. Is there any particular reason to put it outside the file?

OVERLORD commented

2026-02-04 16:42:32 +03:00

@Nonobis commented on GitHub (Aug 8, 2022):

yes the custom entrypoint is the main problem .. in my case, even in advanced docker mode in unraid i don't see where to put the custom entrypoint for each image.

@Nonobis commented on GitHub (Aug 8, 2022): yes the custom entrypoint is the main problem .. in my case, even in advanced docker mode in unraid i don't see where to put the custom entrypoint for each image.

OVERLORD commented

2026-02-04 16:42:43 +03:00

@martabal commented on GitHub (Aug 8, 2022):

There is the --entrypoint argument but it is for overwriting the default entrypoint of the image. But there is no entrypoint by default in the images. So it is currently impossible to run Immich images with docker run

@martabal commented on GitHub (Aug 8, 2022): There is the `--entrypoint` argument but it is for overwriting the default entrypoint of the image. But there is no entrypoint by default in the images. So it is currently impossible to run Immich images with `docker run`

OVERLORD commented

2026-02-04 16:42:47 +03:00

@bo0tzz commented on GitHub (Aug 8, 2022):

The images are built on top of the node base image, so there is a default entrypoint defined that you can override. A command like docker run --entrypoint /bin/sh altran1502/immich-server:release ./start-server.sh works just fine (it doesn't have the necessary config, but it will start the right executable). That said, I agree that having entrypoints defined in the images is nicer, and I've suggested it to the team.

@bo0tzz commented on GitHub (Aug 8, 2022): The images are built on top of the node base image, so there is a default entrypoint defined that you can override. A command like `docker run --entrypoint /bin/sh altran1502/immich-server:release ./start-server.sh` works just fine (it doesn't have the necessary config, but it will start the right executable). That said, I agree that having entrypoints defined in the images is nicer, and I've suggested it to the team.

OVERLORD commented

2026-02-04 16:42:51 +03:00

@martabal commented on GitHub (Aug 8, 2022):

For a release on Unraid, it would be a lot better to avoid arguments other than path, device, port or environment variable. Other arguments has to be passed with the extra-parameters field which is not very user-friendly.
And of course to have only one image.

@martabal commented on GitHub (Aug 8, 2022): For a release on Unraid, it would be a lot better to avoid arguments other than path, device, port or environment variable. Other arguments has to be passed with the extra-parameters field which is not very user-friendly. And of course to have only one image.

OVERLORD commented

2026-02-04 16:42:56 +03:00

@guim31 commented on GitHub (Aug 9, 2022):

Sorry for my useless message but I have to say I would really love ab easy unraid install !!!

@guim31 commented on GitHub (Aug 9, 2022): Sorry for my useless message but I have to say I would really love ab easy unraid install !!!

OVERLORD commented

2026-02-04 16:43:03 +03:00

@martabal commented on GitHub (Aug 14, 2022):

I managed to install altran1502/immich-server:release on Unraid without docker-compose. But for now there is too many images to publish it for Unraid community. Another thing I noticed with my install is that I created a specific user on Postgres to Immich but it didn't work, I had to pass the default postgres user to work.

@martabal commented on GitHub (Aug 14, 2022): I managed to install `altran1502/immich-server:release` on Unraid without docker-compose. But for now there is too many images to publish it for Unraid community. Another thing I noticed with my install is that I created a specific user on Postgres to Immich but it didn't work, I had to pass the default postgres user to work.

OVERLORD commented

2026-02-04 16:43:09 +03:00

@guim31 commented on GitHub (Aug 16, 2022):

Thanks @martabal for your feedback.
I hope someone with some Docker skills could merge all those images in one !

@guim31 commented on GitHub (Aug 16, 2022): Thanks @martabal for your feedback. I hope someone with some Docker skills could merge all those images in one !

OVERLORD commented

2026-02-04 16:43:17 +03:00

@martabal commented on GitHub (Aug 17, 2022):

No problem, I will try to merge the images next week

@martabal commented on GitHub (Aug 17, 2022): No problem, I will try to merge the images next week

OVERLORD commented

2026-02-04 16:43:25 +03:00

@blaine07 commented on GitHub (Aug 21, 2022):

No problem, I will try to merge the images next week

You’d be a hero here. Looking forward to this! :-)

@blaine07 commented on GitHub (Aug 21, 2022): > No problem, I will try to merge the images next week You’d be a hero here. Looking forward to this! :-)

OVERLORD commented

2026-02-04 16:43:26 +03:00

@dsfsdbvxc commented on GitHub (Aug 24, 2022):

No problem, I will try to merge the images next week

Yea thanks, keen to give this a go :)

@dsfsdbvxc commented on GitHub (Aug 24, 2022): > No problem, I will try to merge the images next week Yea thanks, keen to give this a go :)

OVERLORD commented

2026-02-04 16:43:29 +03:00

@dhruvinsh commented on GitHub (Sep 2, 2022):

I managed to install altran1502/immich-server:release on Unraid without docker-compose

@martabal how did manage to override the entrypoint? unraid webpage Extra Parameters doesn't seems to help
Edit:
Nevermind I got it working, I needed to use "Post Argument" commnad

@dhruvinsh commented on GitHub (Sep 2, 2022): > I managed to install altran1502/immich-server:release on Unraid without docker-compose @martabal how did manage to override the entrypoint? unraid webpage Extra Parameters doesn't seems to help Edit: Nevermind I got it working, I needed to use "Post Argument" commnad

OVERLORD commented

2026-02-04 16:43:31 +03:00

@ark- commented on GitHub (Sep 3, 2022):

Would we need to install a bunch of individual "apps" (containers) one by one to get this working on unraid without docker-compose? It looks like there's 7 containers, is that right?

I'm hesitant to use compose on unraid as it doesn't play well with their Web UI and that is my primary interface to the server.

@ark- commented on GitHub (Sep 3, 2022): Would we need to install a bunch of individual "apps" (containers) one by one to get this working on unraid without docker-compose? It looks like there's 7 containers, is that right? I'm hesitant to use compose on unraid as it doesn't play well with their Web UI and that is my primary interface to the server.

OVERLORD commented

2026-02-04 16:43:35 +03:00

@bo0tzz commented on GitHub (Sep 3, 2022):

Currently, yes, you would need to set up the individual containers manually. For Redis and Postgres you could use templates, and the machine-learning container is not required (but you would miss out on object detection/tagging).

@bo0tzz commented on GitHub (Sep 3, 2022): Currently, yes, you would need to set up the individual containers manually. For Redis and Postgres you could use templates, and the machine-learning container is not required (but you would miss out on object detection/tagging).

OVERLORD commented

2026-02-04 16:43:42 +03:00

@ark- commented on GitHub (Sep 8, 2022):

I got this working by installing the unraid plugin for docker-compose. This is an OK workaround for now, but it makes a bunch of unmanaged containers in the main docker window.

Install docker compose manager from the app store
Add a new "stack" (find the button at the bottom of the docker tab) and call it "immich"
Edit the docker compose of the immich stack pasting in the contents docker/docker-compose.yml and save changes
Edit the environment of the immich stack pasting in the contents docker/.env, editing to suit your environment and save changes
Click the "Docker Up" button for the stack

Enjoy

@ark- commented on GitHub (Sep 8, 2022): I got this working by installing the unraid plugin for docker-compose. This is an OK workaround for now, but it makes a bunch of unmanaged containers in the main docker window. 1. Install docker compose manager from the app store 2. Add a new "stack" (find the button at the bottom of the docker tab) and call it "immich" 3. Edit the docker compose of the immich stack pasting in the contents `docker/docker-compose.yml` and save changes 4. Edit the environment of the immich stack pasting in the contents `docker/.env`, editing to suit your environment and save changes 5. Click the "Docker Up" button for the stack Enjoy

OVERLORD commented

2026-02-04 16:43:44 +03:00

@martabal commented on GitHub (Sep 8, 2022):

I got this working by installing the unraid plugin for docker-compose

Yeah, It works but is not ideal for many unraid users.

@martabal commented on GitHub (Sep 8, 2022): > I got this working by installing the unraid plugin for docker-compose Yeah, It works but is not ideal for many unraid users.

OVERLORD commented

2026-02-04 16:43:51 +03:00

@guim31 commented on GitHub (Sep 8, 2022):

Maybe we should also post here : https://discourse.linuxserver.io/t/request-immich/4482/2

Linuxserver's team would be a BIG step for Immich integration on Unraid and it would offer a really big visibility IMO.

@guim31 commented on GitHub (Sep 8, 2022): Maybe we should also post here : https://discourse.linuxserver.io/t/request-immich/4482/2 Linuxserver's team would be a BIG step for Immich integration on Unraid and it would offer a really big visibility IMO.

OVERLORD commented

2026-02-04 16:43:54 +03:00

@martabal commented on GitHub (Sep 8, 2022):

Yeah Linuxserver's work is amazing, I hope they will create an Immich image. Btw, this issue doesn't appear in the Kanban. Hope this isn't a bad thing.

@martabal commented on GitHub (Sep 8, 2022): Yeah Linuxserver's work is amazing, I hope they will create an Immich image. Btw, this issue doesn't appear in the [Kanban](https://github.com/orgs/immich-app/projects/1/views/1). Hope this isn't a bad thing.

OVERLORD commented

2026-02-04 16:44:03 +03:00

@InsanePirate commented on GitHub (Sep 17, 2022):

I got this working by installing the unraid plugin for docker-compose. This is an OK workaround for now, but it makes a bunch of unmanaged containers in the main docker window.

1. Install docker compose manager from the app store

2. Add a new "stack" (find the button at the bottom of the docker tab) and call it "immich"

3. Edit the docker compose of the immich stack pasting in the contents `docker/docker-compose.yml` and save changes

4. Edit the environment of the immich stack pasting in the contents `docker/.env`, editing to suit your environment and save changes

5. Click the "Docker Up" button for the stack

Enjoy

I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid.

@InsanePirate commented on GitHub (Sep 17, 2022): > I got this working by installing the unraid plugin for docker-compose. This is an OK workaround for now, but it makes a bunch of unmanaged containers in the main docker window. > > 1. Install docker compose manager from the app store > > 2. Add a new "stack" (find the button at the bottom of the docker tab) and call it "immich" > > 3. Edit the docker compose of the immich stack pasting in the contents `docker/docker-compose.yml` and save changes > > 4. Edit the environment of the immich stack pasting in the contents `docker/.env`, editing to suit your environment and save changes > > 5. Click the "Docker Up" button for the stack > > > Enjoy I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid.

OVERLORD commented

2026-02-04 16:44:11 +03:00

@MattFaz commented on GitHub (Sep 22, 2022):

I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid.

I got it working the other day so quickly put a rough guide online to help others: https://mfaz.dev/posts/immich-unraid/

@MattFaz commented on GitHub (Sep 22, 2022): > I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid. I got it working the other day so quickly put a rough guide online to help others: https://mfaz.dev/posts/immich-unraid/

OVERLORD commented

2026-02-04 16:44:17 +03:00

@alextran1502 commented on GitHub (Sep 22, 2022):

@Mattyfaz Thank you so much for posting the guide!! Do you want to post it on Reddit or I can include the link in the next monthly update?

@alextran1502 commented on GitHub (Sep 22, 2022): @Mattyfaz Thank you so much for posting the guide!! Do you want to post it on Reddit or I can include the link in the next monthly update?

OVERLORD commented

2026-02-04 16:44:26 +03:00

@MattFaz commented on GitHub (Sep 22, 2022):

@Mattyfaz Thank you so much for posting the guide!! Do you want to post it on Reddit or I can include the link in the next monthly update?

@alextran1502 Feel free to post wherever/include in your update 😊

@MattFaz commented on GitHub (Sep 22, 2022): > @Mattyfaz Thank you so much for posting the guide!! Do you want to post it on Reddit or I can include the link in the next monthly update? @alextran1502 Feel free to post wherever/include in your update 😊

OVERLORD commented

2026-02-04 16:44:32 +03:00

@guim31 commented on GitHub (Sep 22, 2022):

Thanks a lot @Mattyfaz for your guide 👍

I have to admit that this screenshot :

Is the reason why people hope someone would achieve to merge all the images together ! ;)

Personnaly I'll wait for this moment as I always have the feeling that it would make my unraid server a mess

EDIT : typo

@guim31 commented on GitHub (Sep 22, 2022): Thanks a lot @Mattyfaz for your guide :+1: I have to admit that this screenshot : ![image](https://user-images.githubusercontent.com/33096540/191769569-2b44af44-82e1-4885-a904-a7a47ef43af6.png) Is the reason why people hope someone would achieve to merge all the images together ! ;) Personnaly I'll wait for this moment as I always have the feeling that it would make my unraid server a mess EDIT : typo

OVERLORD commented

2026-02-04 16:44:40 +03:00

@dsfsdbvxc commented on GitHub (Sep 23, 2022):

Agreed, it would be nice to have all in one container to simplify things. However, docker folders is pretty useful to put all the current containers together, can always collapse the folder to make it look more tidy.

@dsfsdbvxc commented on GitHub (Sep 23, 2022): Agreed, it would be nice to have all in one container to simplify things. However, docker folders is pretty useful to put all the current containers together, can always collapse the folder to make it look more tidy.

OVERLORD commented

2026-02-04 16:44:55 +03:00

@sohail579 commented on GitHub (Oct 10, 2022):

awesome write up but I also think i will wait for a unified image. is there a view on how long this will take?

@sohail579 commented on GitHub (Oct 10, 2022): awesome write up but I also think i will wait for a unified image. is there a view on how long this will take?

OVERLORD commented

2026-02-04 16:45:00 +03:00

@alextran1502 commented on GitHub (Oct 10, 2022):

@sohail579 We don't have any concrete plan when to put resource into this yet. Right now it is heavily depend on the community to provide support for a single Docker image.

@alextran1502 commented on GitHub (Oct 10, 2022): @sohail579 We don't have any concrete plan when to put resource into this yet. Right now it is heavily depend on the community to provide support for a single Docker image.

OVERLORD commented

2026-02-04 16:45:03 +03:00

@guim31 commented on GitHub (Oct 17, 2022):

Here is the answer from a LSIO moderator :
https://discourse.linuxserver.io/t/request-immich/4482/5?u=guilhem

I hope the immich contributors will make it possible :)

@guim31 commented on GitHub (Oct 17, 2022): Here is the answer from a LSIO moderator : https://discourse.linuxserver.io/t/request-immich/4482/5?u=guilhem I hope the immich contributors will make it possible :)

OVERLORD commented

2026-02-04 16:45:12 +03:00

@martabal commented on GitHub (Oct 17, 2022):

I have successfully created an image bundling, web, machine-learning, nginx and server images. It works but I have some bugs with machine-learning. I tested it on Unraid and it works. However, this is just a draft, I don't plan to update this image frequently. You can try the container by pulling martabal/immich:latest, and you can give a look to the Dockerfile here

It uses almost 1 gb of RAM 😧 (but all official images combined use 1 gb of RAM)

@martabal commented on GitHub (Oct 17, 2022): I have successfully created an image bundling, web, machine-learning, nginx and server images. It works but I have some bugs with machine-learning. I tested it on Unraid and it works. However, this is just a draft, I don't plan to update this image frequently. You can try the container by pulling martabal/immich:latest, and you can give a look to the Dockerfile [here](https://github.com/martabal/immich/blob/main/Dockerfile) It uses almost 1 gb of RAM 😧 (but all official images combined use 1 gb of RAM)

OVERLORD commented

2026-02-04 16:45:15 +03:00

@bo0tzz commented on GitHub (Oct 17, 2022):

Nice work! It's good to have an initial approach (even if just a draft) to drive discussion further - for example, it just made me realise that doing this fully will be dependent on #647, since all the services will only be reachable on localhost.

@bo0tzz commented on GitHub (Oct 17, 2022): Nice work! It's good to have an initial approach (even if just a draft) to drive discussion further - for example, it just made me realise that doing this fully will be dependent on #647, since all the services will only be reachable on localhost.

OVERLORD commented

2026-02-04 16:45:18 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid.

I got it working the other day so quickly put a rough guide online to help others: https://mfaz.dev/posts/immich-unraid/

@Mattyfaz Thankyou for this awesome write up I had it up and running in minuets. I have a question though. I endered my location for the media upload folder but normally on unraid i would expect to see a folder in the appdata with all of the appdata.. where is this all now? where are all the thumbnails saved? am i just filling up my docker image now?

@sohail579 commented on GitHub (Oct 21, 2022): > > I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid. > > I got it working the other day so quickly put a rough guide online to help others: https://mfaz.dev/posts/immich-unraid/ @Mattyfaz Thankyou for this awesome write up I had it up and running in minuets. I have a question though. I endered my location for the media upload folder but normally on unraid i would expect to see a folder in the appdata with all of the appdata.. where is this all now? where are all the thumbnails saved? am i just filling up my docker image now?

OVERLORD commented

2026-02-04 16:45:20 +03:00

@bo0tzz commented on GitHub (Oct 21, 2022):

Thumbnails and such are saved in your library folder. The database data is (by default) stored in a docker volume, which probably is ending up in your docker img right now. That shouldn't be that much data though.

@bo0tzz commented on GitHub (Oct 21, 2022): Thumbnails and such are saved in your library folder. The database data is (by default) stored in a docker volume, which probably is ending up in your docker img right now. That shouldn't be that much data though.

OVERLORD commented

2026-02-04 16:45:22 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

Thumbnails and such are saved in your library folder. The database data is (by default) stored in a docker volume, which probably is ending up in your docker img right now. That shouldn't be that much data though.

@bo0tzz your are everywhere :) and your advise and help is appreciated and awesome.. should my database in that case not be in my app data so that i am never going to loose it? or wlll the database rebuild itself from the media folder if needed ever?

@sohail579 commented on GitHub (Oct 21, 2022): > Thumbnails and such are saved in your library folder. The database data is (by default) stored in a docker volume, which probably is ending up in your docker img right now. That shouldn't be that much data though. @bo0tzz your are everywhere :) and your advise and help is appreciated and awesome.. should my database in that case not be in my app data so that i am never going to loose it? or wlll the database rebuild itself from the media folder if needed ever?

OVERLORD commented

2026-02-04 16:45:26 +03:00

@martabal commented on GitHub (Oct 21, 2022):

Quick update, the container runs very well, finally no bug observed. It uses between 800 and 900 mb of RAM. I pushed a version for arm64 for everyone using a raspberry pi. I will do my best to keep them up to date.

@bo0tzz In the long term do you plan to merge images or keep them sperated?

@martabal commented on GitHub (Oct 21, 2022): Quick update, the container runs very well, finally no bug observed. It uses between 800 and 900 mb of RAM. I pushed a version for arm64 for everyone using a raspberry pi. I will do my best to keep them up to date. ![image](https://user-images.githubusercontent.com/74269598/197064647-b3dc9eb3-7f2a-4f3f-9ea7-4dba1dc2132b.png) @bo0tzz In the long term do you plan to merge images or keep them sperated?

OVERLORD commented

2026-02-04 16:45:31 +03:00

@MattFaz commented on GitHub (Oct 21, 2022):

@sohail579

where is this all now? where are all the thumbnails saved? am i just filling up my docker image now?

In your upload location - If you followed my guide you can see I set the upload location as mnt/user/images/immich.

Within that directory you can see a folder with a uuid, and inside that is 3 folders: encoded-video, original, and thumb. :)

@MattFaz commented on GitHub (Oct 21, 2022): @sohail579 > where is this all now? where are all the thumbnails saved? am i just filling up my docker image now? In your upload location - If you followed my guide you can see I set the upload location as `mnt/user/images/immich`. Within that directory you can see a folder with a uuid, and inside that is 3 folders: `encoded-video`, `original`, and `thumb`. :) ![image](https://user-images.githubusercontent.com/10377148/197066470-57216574-399a-4ae7-a698-b1b0aa5c1589.png)

OVERLORD commented

2026-02-04 16:45:38 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

@sohail579

where is this all now? where are all the thumbnails saved? am i just filling up my docker image now?

In your upload location - If you followed my guide you can see I set the upload location as mnt/user/images/immich.

Within that directory you can see a folder with a uuid, and inside that is 3 folders: encoded-video, original, and thumb. :)

thanks @Mattyfaz - on the other note I ubderstand that the database is stored in the docker image. shouldn't this be in the app data?

@sohail579 commented on GitHub (Oct 21, 2022): > @sohail579 > > > where is this all now? where are all the thumbnails saved? am i just filling up my docker image now? > > In your upload location - If you followed my guide you can see I set the upload location as `mnt/user/images/immich`. > > Within that directory you can see a folder with a uuid, and inside that is 3 folders: `encoded-video`, `original`, and `thumb`. :) > > ![image](https://user-images.githubusercontent.com/10377148/197066470-57216574-399a-4ae7-a698-b1b0aa5c1589.png) thanks @Mattyfaz - on the other note I ubderstand that the database is stored in the docker image. shouldn't this be in the app data?

OVERLORD commented

2026-02-04 16:45:45 +03:00

@MattFaz commented on GitHub (Oct 21, 2022):

@sohail579

I ubderstand that the database is stored in the docker image. shouldn't this be in the app data?

Ideally - I've just tried and managed to get it working with an existing Postgres container separate from Immich so all data will be in my appdata now. Here is what I did.

.Env File
Update the database values to match your postgres container.

# DB_HOSTNAME=immich_postgres
DB_HOSTNAME=192.168.0.25
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_DATABASE_NAME=immich

# Optional Database settings:
DB_PORT=5432

Compose file:
You'll need to comment out all reference of database in this file.
Comment out the whole database service:

#  database:
#    container_name: immich_postgres
#    image: postgres:14
#    env_file:
#      - .env
#    environment:
#      POSTGRES_PASSWORD: ${DB_PASSWORD}
#      POSTGRES_USER: ${DB_USERNAME}
#      POSTGRES_DB: ${DB_DATABASE_NAME}
#      PG_DATA: /var/lib/postgresql/data
#    volumes:
#      - pgdata:/var/lib/postgresql/data
#    restart: always

Then for each other service remove the dependency on databse:

depends_on:
  - redis
# - database

Finally remove the volume at the bottom:

# volumes:
#	pgdata:

Doing this I've successfully got it running.

@MattFaz commented on GitHub (Oct 21, 2022): @sohail579 > I ubderstand that the database is stored in the docker image. shouldn't this be in the app data? Ideally - I've just tried and managed to get it working with an existing Postgres container separate from Immich so all data will be in my appdata now. Here is what I did. **.Env File** Update the database values to match your postgres container. ``` # DB_HOSTNAME=immich_postgres DB_HOSTNAME=192.168.0.25 DB_USERNAME=postgres DB_PASSWORD=postgres DB_DATABASE_NAME=immich # Optional Database settings: DB_PORT=5432 ``` **Compose file:** You'll need to comment out all reference of database in this file. Comment out the whole database service: ``` # database: # container_name: immich_postgres # image: postgres:14 # env_file: # - .env # environment: # POSTGRES_PASSWORD: ${DB_PASSWORD} # POSTGRES_USER: ${DB_USERNAME} # POSTGRES_DB: ${DB_DATABASE_NAME} # PG_DATA: /var/lib/postgresql/data # volumes: # - pgdata:/var/lib/postgresql/data # restart: always ``` Then for each other service remove the dependency on databse: ``` depends_on: - redis # - database ``` Finally remove the volume at the bottom: ``` # volumes: # pgdata: ``` Doing this I've successfully got it running. ![image](https://user-images.githubusercontent.com/10377148/197071615-ae09e64e-4e25-4e4d-8267-eb7d9122c4ca.png)

OVERLORD commented

2026-02-04 16:45:54 +03:00

@bo0tzz commented on GitHub (Oct 21, 2022):

@bo0tzz In the long term do you plan to merge images or keep them sperated?

We had some discussions with the contributor team and did a few experiments ourselves with merging images. For now, we have decided not to build an all-in-one image.

Running multiple services inside one docker image is an unusual way of doing things, and would come with some issues (especially if including the Redis and Postgres dependencies). Merging the current images into one would also take time and energy away from developing other Immich features, as would providing support for the resulting mega-image.

In addition, the current images work just fine, also on Unraid (especially with @Mattyfaz's great guide). At the moment, the only reason for creating an all-in-one image would be to have it work with Unraid's Docker templates, but docker-compose fills a similar role to those already.

@bo0tzz commented on GitHub (Oct 21, 2022): > @bo0tzz In the long term do you plan to merge images or keep them sperated? We had some discussions with the contributor team and did a few experiments ourselves with merging images. For now, we have decided not to build an all-in-one image. Running multiple services inside one docker image is an unusual way of doing things, and would come with some issues (especially if including the Redis and Postgres dependencies). Merging the current images into one would also take time and energy away from developing other Immich features, as would providing support for the resulting mega-image. In addition, the current images work just fine, also on Unraid (especially with @Mattyfaz's [great guide](https://mfaz.dev/posts/immich-unraid/)). At the moment, the only reason for creating an all-in-one image would be to have it work with Unraid's Docker templates, but docker-compose fills a similar role to those already.

OVERLORD commented

2026-02-04 16:45:58 +03:00

@blaine07 commented on GitHub (Oct 21, 2022):

So I have been using a different app on my phone to upload photos to Unraid forever. What is going to happen if I follow Immich guide and point it at a directory already full of existing photos and media?

@blaine07 commented on GitHub (Oct 21, 2022): So I have been using a different app on my phone to upload photos to Unraid forever. What is going to happen if I follow Immich guide and point it at a directory already full of existing photos and media?

OVERLORD commented

2026-02-04 16:46:02 +03:00

@bo0tzz commented on GitHub (Oct 21, 2022):

What is going to happen if I follow Immich guide and point it at a directory already full of existing photos and media?

Nothing, you need to give Immich an empty directory to work with and upload files via the API. There is an open issue for what you're looking for: #34. If you need to do a bulk import you can use the CLI https://github.com/immich-app/cli

@bo0tzz commented on GitHub (Oct 21, 2022): > What is going to happen if I follow Immich guide and point it at a directory already full of existing photos and media? Nothing, you need to give Immich an empty directory to work with and upload files via the API. There is an open issue for what you're looking for: #34. If you need to do a bulk import you can use the CLI https://github.com/immich-app/cli

OVERLORD commented

2026-02-04 16:46:11 +03:00

@MattFaz commented on GitHub (Oct 21, 2022):

@blaine07

So I have been using a different app on my phone to upload photos to Unraid forever. What is going to happen if I follow Immich guide and point it at a directory already full of existing photos and media?

It won't pick them up (someone please correct me if I am wrong), if you'd rather not re-upload via your mobile an alternative is to copy the images from Unraid to your PC and upload via the WebUI as shown in the image below.

@MattFaz commented on GitHub (Oct 21, 2022): @blaine07 > So I have been using a different app on my phone to upload photos to Unraid forever. What is going to happen if I follow Immich guide and point it at a directory already full of existing photos and media? It won't pick them up _(someone please correct me if I am wrong)_, if you'd rather not re-upload via your mobile an alternative is to copy the images from Unraid to your PC and upload via the WebUI as shown in the image below. ![image](https://user-images.githubusercontent.com/10377148/197083816-9971d4e6-1e1d-4600-ab05-663376f9c403.png)

OVERLORD commented

2026-02-04 16:46:18 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

not sure I got this.. you still havent said anywhere to use a file location in appdata, isnt is as simple as replacing pgdata with a location in the appdata folder?

@sohail579 commented on GitHub (Oct 21, 2022): > not sure I got this.. you still havent said anywhere to use a file location in appdata, isnt is as simple as replacing pgdata with a location in the appdata folder?

OVERLORD commented

2026-02-04 16:46:49 +03:00

@bo0tzz commented on GitHub (Oct 21, 2022):

That should also work, yes.

@bo0tzz commented on GitHub (Oct 21, 2022): That should also work, yes.

OVERLORD commented

2026-02-04 16:47:01 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

That should also work, yes.

would that need to be everywhere where it says pgdata or do you just create it as a variable in the env file?

@sohail579 commented on GitHub (Oct 21, 2022): > That should also work, yes. would that need to be everywhere where it says pgdata or do you just create it as a variable in the env file?

OVERLORD commented

2026-02-04 16:47:12 +03:00

@bo0tzz commented on GitHub (Oct 21, 2022):

Just this line, you would replace it with something like - /mnt/user/appdata/immich:/var/lib/postgresql/data.

@bo0tzz commented on GitHub (Oct 21, 2022): Just [this line](https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml#L68), you would replace it with something like `- /mnt/user/appdata/immich:/var/lib/postgresql/data`.

OVERLORD commented

2026-02-04 16:47:24 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

what about the last 2 lins? it also makes a reference to pgdata there wouldnt that also need to be the same?

@sohail579 commented on GitHub (Oct 21, 2022): what about the last 2 lins? it also makes a reference to pgdata there wouldnt that also need to be the same?

OVERLORD commented

2026-02-04 16:47:28 +03:00

@bo0tzz commented on GitHub (Oct 21, 2022):

The

volumes:
  pgdata:

instructs Docker to create the pgdata volume. If you're not using it, you can remove that part, but leaving it won't do any harm.

@bo0tzz commented on GitHub (Oct 21, 2022): The ``` volumes: pgdata: ``` instructs Docker to create the pgdata volume. If you're not using it, you can remove that part, but leaving it won't do any harm.

OVERLORD commented

2026-02-04 16:47:44 +03:00

@sohail579 commented on GitHub (Oct 21, 2022):

The
volumes:
  pgdata:
instructs Docker to create the pgdata volume. If you're not using it, you can remove that part, but leaving it won't do any harm.

got you thanks I thought it was trying to mount the volume :)

@sohail579 commented on GitHub (Oct 21, 2022): > The > > ``` > volumes: > pgdata: > ``` > > instructs Docker to create the pgdata volume. If you're not using it, you can remove that part, but leaving it won't do any harm. got you thanks I thought it was trying to mount the volume :)

OVERLORD commented

2026-02-04 16:47:52 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid.

I got it working the other day so quickly put a rough guide online to help others: https://mfaz.dev/posts/immich-unraid/

Pardon my idiocracy, but how do I update everything once it's setup? I do have it working but... curious?

Thanks

@blaine07 commented on GitHub (Oct 23, 2022): > > I'm sorry could you share your .env and .yaml files? For the life of me, I can't get it working on unraid. > > I got it working the other day so quickly put a rough guide online to help others: https://mfaz.dev/posts/immich-unraid/ Pardon my idiocracy, but how do I update everything once it's setup? I do have it working but... curious? Thanks

OVERLORD commented

2026-02-04 16:47:55 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

Also, with docker compose plugin installed on Unraid is it normal for it to say this at bottom of the docker tab:

Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/compose.manager/php/compose_manager_main.php on line 32

@blaine07 commented on GitHub (Oct 23, 2022): Also, with docker compose plugin installed on Unraid is it normal for it to say this at bottom of the docker tab: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/compose.manager/php/compose_manager_main.php on line 32

OVERLORD commented

2026-02-04 16:47:59 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

Are those of you who have followed the Unraid Guide seeing this, below, spamming your syslogs since Immich was installed?

@blaine07 commented on GitHub (Oct 23, 2022): Are those of you who have followed the Unraid Guide seeing this, below, spamming your syslogs since Immich was installed? ![Screen Shot 2022-10-23 at 9 14 59 AM](https://user-images.githubusercontent.com/63940698/197397541-05d115d1-eb36-4f07-842a-791783836d60.png)

OVERLORD commented

2026-02-04 16:48:07 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

Is it possibly because this Machine-Learning 1 is continuing to restart/bootloop?

@blaine07 commented on GitHub (Oct 23, 2022): ![Screen Shot 2022-10-23 at 9 31 50 AM](https://user-images.githubusercontent.com/63940698/197397889-ecd6c227-7cc8-4adb-9618-39e5f5168a91.png) Is it possibly because this Machine-Learning 1 is continuing to restart/bootloop?

OVERLORD commented

2026-02-04 16:48:12 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

I disable JUST that container and Syslog spam stops in Unraid; I just have no idea how important it is that piece runs nor how to fix just that piece? Is there anything I can do or?

@blaine07 commented on GitHub (Oct 23, 2022): I disable JUST that container and Syslog spam stops in Unraid; I just have no idea how important it is that piece runs nor how to fix just that piece? Is there anything I can do or?

OVERLORD commented

2026-02-04 16:48:18 +03:00

@alextran1502 commented on GitHub (Oct 23, 2022):

Is it possibly because this Machine-Learning 1 is continuing to restart/bootloop?

Yes looks like your machine cannot run the Machine Learning container

@alextran1502 commented on GitHub (Oct 23, 2022): > ![Screen Shot 2022-10-23 at 9 31 50 AM](https://user-images.githubusercontent.com/63940698/197397889-ecd6c227-7cc8-4adb-9618-39e5f5168a91.png) > > Is it possibly because this Machine-Learning 1 is continuing to restart/bootloop? Yes looks like your machine cannot run the Machine Learning container

OVERLORD commented

2026-02-04 16:48:27 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

Is it possibly because this Machine-Learning 1 is continuing to restart/bootloop?

Yes looks like your machine cannot run the Machine Learning container

So what can I do and how can I fix it? It's a old-ish Dell T610 server, FWIW

@blaine07 commented on GitHub (Oct 23, 2022): > > ![Screen Shot 2022-10-23 at 9 31 50 AM](https://user-images.githubusercontent.com/63940698/197397889-ecd6c227-7cc8-4adb-9618-39e5f5168a91.png) > > Is it possibly because this Machine-Learning 1 is continuing to restart/bootloop? > > Yes looks like your machine cannot run the Machine Learning container So what can I do and how can I fix it? It's a old-ish Dell T610 server, FWIW

OVERLORD commented

2026-02-04 16:48:35 +03:00

@blaine07 commented on GitHub (Oct 23, 2022):

Google says my Dell T610 doesn't have AVX support; so thats probably the reason my machine learning portion won't stay running: https://github.com/immich-app/immich/discussions/300

Still not sure of the side effects of it not running or if that will cause me other issues. Also still unsure if docker compose plugin installed on Unraid if it is normal for it to say this at bottom of the docker tab:

Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/compose.manager/php/compose_manager_main.php on line 32

@blaine07 commented on GitHub (Oct 23, 2022): Google says my Dell T610 doesn't have AVX support; so thats probably the reason my machine learning portion won't stay running: https://github.com/immich-app/immich/discussions/300 Still not sure of the side effects of it not running or if that will cause me other issues. Also still unsure if docker compose plugin installed on Unraid if it is normal for it to say this at bottom of the docker tab: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/compose.manager/php/compose_manager_main.php on line 32

OVERLORD commented

2026-02-04 16:48:44 +03:00

@martabal commented on GitHub (Oct 23, 2022):

Wouldn't it be better to use environment variables rather than using hardcoded urls ? This would allow for a single image and users to rename their containers as they wish. #647

2c189d5c78/server/apps/microservices/src/processors/machine-learning.processor.ts (L23)

2c189d5c78/server/apps/microservices/src/processors/machine-learning.processor.ts (L43)

2c189d5c78/web/src/api/api.ts (L48)

2c189d5c78/nginx/nginx.conf (L65)

2c189d5c78/nginx/nginx.conf (L90)

@martabal commented on GitHub (Oct 23, 2022): Wouldn't it be better to use environment variables rather than using hardcoded urls ? This would allow for a single image and users to rename their containers as they wish. #647 https://github.com/immich-app/immich/blob/2c189d5c78fa35e9f235b134f47765ac1b71b8b3/server/apps/microservices/src/processors/machine-learning.processor.ts#L23 https://github.com/immich-app/immich/blob/2c189d5c78fa35e9f235b134f47765ac1b71b8b3/server/apps/microservices/src/processors/machine-learning.processor.ts#L43 https://github.com/immich-app/immich/blob/2c189d5c78fa35e9f235b134f47765ac1b71b8b3/web/src/api/api.ts#L48 https://github.com/immich-app/immich/blob/2c189d5c78fa35e9f235b134f47765ac1b71b8b3/nginx/nginx.conf#L65 https://github.com/immich-app/immich/blob/2c189d5c78fa35e9f235b134f47765ac1b71b8b3/nginx/nginx.conf#L90

OVERLORD commented

2026-02-04 16:48:50 +03:00

@blaine07 commented on GitHub (Oct 27, 2022):

Every single time in Unraid I "docker compose down" then "Update Stack" MORE of my Docker Image is full. How can I "clean up" after this configuration? @Mattyfaz ? Anyone?

@blaine07 commented on GitHub (Oct 27, 2022): Every single time in Unraid I "docker compose down" then "Update Stack" MORE of my Docker Image is full. How can I "clean up" after this configuration? @Mattyfaz ? Anyone?

OVERLORD commented

2026-02-04 16:48:56 +03:00

@bo0tzz commented on GitHub (Oct 27, 2022):

https://docs.docker.com/engine/reference/commandline/system_prune/ should do the trick.

@bo0tzz commented on GitHub (Oct 27, 2022): https://docs.docker.com/engine/reference/commandline/system_prune/ should do the trick.

OVERLORD commented

2026-02-04 16:49:05 +03:00

@blaine07 commented on GitHub (Oct 27, 2022):

https://docs.docker.com/engine/reference/commandline/system_prune/ should do the trick.

That will work in Unraid?

@blaine07 commented on GitHub (Oct 27, 2022): > https://docs.docker.com/engine/reference/commandline/system_prune/ should do the trick. That will work in Unraid?

OVERLORD commented

2026-02-04 16:49:18 +03:00

@blaine07 commented on GitHub (Oct 27, 2022):

https://docs.docker.com/engine/reference/commandline/system_prune/ should do the trick.

I ran it; eventually the unraid command window wen't away. Didn't see that it did anything; docker image still larger than expected?

Did it from ssh and it deleted 284mb :scratches head:

Yep, that was a bad idea; deleted containers I had that weren't running...a few I can't seem to get recreated right. DOH LOL

@blaine07 commented on GitHub (Oct 27, 2022): > https://docs.docker.com/engine/reference/commandline/system_prune/ should do the trick. I ran it; eventually the unraid command window wen't away. Didn't see that it did anything; docker image still larger than expected? Did it from ssh and it deleted 284mb :scratches head: Yep, that was a bad idea; deleted containers I had that weren't running...a few I can't seem to get recreated right. DOH LOL

OVERLORD commented

2026-02-04 16:49:30 +03:00

@MattFaz commented on GitHub (Oct 27, 2022):

Every single time in Unraid I "docker compose down" then "Update Stack" MORE of my Docker Image is full. How can I "clean up" after this configuration? @Mattyfaz ? Anyone?

Not sure sorry, I don’t think I have the same issue. I don’t click “docker compose down”, I just click “update stack” and it does it all for you.

@MattFaz commented on GitHub (Oct 27, 2022): > Every single time in Unraid I "docker compose down" then "Update Stack" MORE of my Docker Image is full. How can I "clean up" after this configuration? @Mattyfaz ? Anyone? Not sure sorry, I don’t think I have the same issue. I don’t click “docker compose down”, I just click “update stack” and it does it all for you.

OVERLORD commented

2026-02-04 16:49:38 +03:00

@sohail579 commented on GitHub (Oct 27, 2022):

Every single time in Unraid I "docker compose down" then "Update Stack" MORE of my Docker Image is full. How can I "clean up" after this configuration? @Mattyfaz ? Anyone?

Install user scripts and create this as a script it will remove any dangling images

#!/bin/bash

remove_orphaned_images="yes" # select "yes" or "no" to remove any orphaned images
remove_unconnected_volumes="yes" # select "yes" or "no" to remove any unconnected volumes

#Do not make changes below this line#

echo "##################################################################################"
echo "Cleanup before starting (if requested in script)"
echo "##################################################################################"
echo
if [ "$remove_orphaned_images" == "yes" ] ; then
echo "Removing orphaned images..."
echo
docker image prune -af
else
echo "Not removing orphaned images (this can be set in script if you want to)"
fi
echo
echo "---------------------------------------------------------------------------------"
echo
if [ "$remove_unconnected_volumes" == "yes" ] ; then
echo "Removing unconnected docker volumes"
echo
docker volume prune -f
else
echo "Not removing unconnected docker volumes (this can be set in script if you want to)"
fi
echo
echo "##################################################################################"
echo "List of Image, Container and docker volume size."
echo "##################################################################################"
echo
#docker system df
docker system df --format 'There are \t {{.TotalCount}} \t {{.Type}} \t taking up ......{{.Size}}'
echo
echo "##################################################################################"
echo "List of containers showing size and virtual size"
echo "##################################################################################"
echo
echo "First size is the writable layers of the container (Virtual size is writable and read only layers)"
echo
docker container ls -a --format '{{.Size}} \t Is being taken up by ......... {{.Image}}'
echo
echo "##################################################################################"
echo "List of containers in size order"
echo "##################################################################################"
echo
docker image ls --format "{{.Repository}} {{.Size}}" |
awk '{if ($2~/GB/) print substr($2, 1, length($2)-2) *1000 "MB - " $1 ; else print $2 " - " $1 }' |
sed '/^0/d' |
sort -nr
echo
echo "##################################################################################"
echo "List of docker volumes, the container which they are connected to their size"
echo "##################################################################################"
echo
volumes=$(docker volume ls --format '{{.Name}}')
for volume in $volumes
do
name=(docker ps -a --filter volume="$volume" --format '{{.Names}}' | sed 's/^/ /')
size=(du -sh $(docker volume inspect --format '{{ .Mountpoint }}' $volume) | cut -f -1)
echo "ID" "$volume"
echo "This volume connected to" $name "has a size of" $size
echo ""
done
echo
echo "##################################################################################"
echo
echo "Done. Scroll up to view results"
exit

@sohail579 commented on GitHub (Oct 27, 2022): > Every single time in Unraid I "docker compose down" then "Update Stack" MORE of my Docker Image is full. How can I "clean up" after this configuration? @Mattyfaz ? Anyone? Install user scripts and create this as a script it will remove any dangling images #!/bin/bash remove_orphaned_images="yes" # select "yes" or "no" to remove any orphaned images remove_unconnected_volumes="yes" # select "yes" or "no" to remove any unconnected volumes #Do not make changes below this line# echo "##################################################################################" echo "Cleanup before starting (if requested in script)" echo "##################################################################################" echo if [ "$remove_orphaned_images" == "yes" ] ; then echo "Removing orphaned images..." echo docker image prune -af else echo "Not removing orphaned images (this can be set in script if you want to)" fi echo echo "---------------------------------------------------------------------------------" echo if [ "$remove_unconnected_volumes" == "yes" ] ; then echo "Removing unconnected docker volumes" echo docker volume prune -f else echo "Not removing unconnected docker volumes (this can be set in script if you want to)" fi echo echo "##################################################################################" echo "List of Image, Container and docker volume size." echo "##################################################################################" echo #docker system df docker system df --format 'There are \t {{.TotalCount}} \t {{.Type}} \t taking up ......{{.Size}}' echo echo "##################################################################################" echo "List of containers showing size and virtual size" echo "##################################################################################" echo echo "First size is the writable layers of the container (Virtual size is writable and read only layers)" echo docker container ls -a --format '{{.Size}} \t Is being taken up by ......... {{.Image}}' echo echo "##################################################################################" echo "List of containers in size order" echo "##################################################################################" echo docker image ls --format "{{.Repository}} {{.Size}}" | \ awk '{if ($2~/GB/) print substr($2, 1, length($2)-2) *1000 "MB - " $1 ; else print $2 " - " $1 }' | \ sed '/^0/d' | \ sort -nr echo echo "##################################################################################" echo "List of docker volumes, the container which they are connected to their size" echo "##################################################################################" echo volumes=$(docker volume ls --format '{{.Name}}') for volume in $volumes do name=`(docker ps -a --filter volume="$volume" --format '{{.Names}}' | sed 's/^/ /')` size=`(du -sh $(docker volume inspect --format '{{ .Mountpoint }}' $volume) | cut -f -1)` echo "ID" "$volume" echo "This volume connected to" $name "has a size of" $size echo "" done echo echo "##################################################################################" echo echo "Done. Scroll up to view results" exit

OVERLORD commented

2026-02-04 16:49:42 +03:00

@Enlinks commented on GitHub (Nov 19, 2022):

Not sure if this has been discussed but there are other templates (at least 1 I know of) like TubeArchivist that require multiple dockers to work correctly that currently work with the Unraid Community Applications Plugin. Would this approach be more appropriate?

@Enlinks commented on GitHub (Nov 19, 2022): Not sure if this has been discussed but there are other templates (at least 1 I know of) like [TubeArchivist](https://github.com/tubearchivist/tubearchivist/blob/master/docs/Installation.md#unraid) that require multiple dockers to work correctly that currently work with the Unraid Community Applications Plugin. Would this approach be more appropriate?

OVERLORD commented

2026-02-04 16:49:53 +03:00

@bo0tzz commented on GitHub (Nov 25, 2022):

It looks like TubeArchivist doesn't do anything special, they just have a template for each of their containers. At that point, docker-compose is still the better option :)

@bo0tzz commented on GitHub (Nov 25, 2022): It looks like TubeArchivist doesn't do anything special, they just have a template for each of their containers. At that point, docker-compose is still the better option :)

OVERLORD commented

2026-02-04 16:49:56 +03:00

@alexbelgium commented on GitHub (Jan 11, 2023):

I second the request, a single container for all elements would be great! I am managing Home Assistant addons, which is not compatible with stacks of several containers.

@alexbelgium commented on GitHub (Jan 11, 2023): I second the request, a single container for all elements would be great! I am managing Home Assistant addons, which is not compatible with stacks of several containers.

OVERLORD commented

2026-02-04 16:50:02 +03:00

@bo0tzz commented on GitHub (Jan 11, 2023):

There is now a single AIO image at https://github.com/martabal/docker-immich. It isn't supported by the Immich team though.

@bo0tzz commented on GitHub (Jan 11, 2023): There is now a single AIO image at https://github.com/martabal/docker-immich. It isn't supported by the Immich team though.

OVERLORD commented

2026-02-04 16:50:06 +03:00

@SmoochSmackers commented on GitHub (Jan 11, 2023):

Sorry if this is a silly question, but since you closed this issue, does this mean that there will never be an official AIO Immich image? Only the third party one you linked to?

My number one issue right now, as an extremely novice self-hoster, is the way that I have to use docker compose on my Unraid machine to use it. The three issues I have with this is that:
1.) It spins up 5 separate containers.
2.) I cannot mass update it along with the rest of my docker containers and have to keep an eye on the github page for any new releases.
3.) I think that not having a single image available in Unraid's Community App store creates an artificial hurtle that limits Immich's reach. It took quite a lot of time, and build up of frustration with other photo hosting apps, to finally push me to learn how to use docker compose. I feel there are many like me out there, but with less time on their hands, who are not ready to take the plunge. It's a matter of getting more users/supporters by lowering the bar to entry.

To be clear, I'm not writing this in anger or frustration. To the contrary! I absolutely love this software and understand the ungodly amount of work you all must have in front of you, tackling such a project! I just wanted to give my perspective as a newbie trying their darndest to rip as many of Google's tendrils from my life as possible and taking back control of my data.

Thank you all for your amazing work, I've been looking for a solid google photos replacement for years now. From my experience trying to self-host Photoview, Photoprism, etc., Immich is far and away the best one I've come across, the only one that truly has a google photos-like experience with the mobile app, and the only one that has runs rock solid with almost no issues with its core functionalites. In fact, I love this project so much that I created a github account to better follow your progress and so that I could donate.

@SmoochSmackers commented on GitHub (Jan 11, 2023): Sorry if this is a silly question, but since you closed this issue, does this mean that there will never be an _official_ AIO Immich image? Only the third party one you linked to? My number one issue right now, as an extremely novice self-hoster, is the way that I have to use docker compose on my Unraid machine to use it. The three issues I have with this is that: 1.) It spins up 5 separate containers. 2.) I cannot mass update it along with the rest of my docker containers and have to keep an eye on the github page for any new releases. 3.) I think that not having a single image available in Unraid's Community App store creates an artificial hurtle that limits Immich's reach. It took quite a lot of time, and build up of frustration with other photo hosting apps, to finally push me to learn how to use docker compose. I feel there are many like me out there, but with less time on their hands, who are not ready to take the plunge. It's a matter of getting more users/supporters by lowering the bar to entry. To be clear, I'm not writing this in anger or frustration. To the contrary! I absolutely _love_ this software and understand the ungodly amount of work you all must have in front of you, tackling such a project! I just wanted to give my perspective as a newbie trying their darndest to rip as many of Google's tendrils from my life as possible and taking back control of my data. Thank you all for your amazing work, I've been looking for a solid google photos replacement for years now. From my experience trying to self-host Photoview, Photoprism, etc., Immich is far and away the best one I've come across, the only one that truly has a google photos-like experience with the mobile app, and the only one that has runs _rock solid_ with almost no issues with its core functionalites. In fact, I love this project so much that I created a github account to better follow your progress and so that I could donate.

OVERLORD commented

2026-02-04 16:50:15 +03:00

@alextran1502 commented on GitHub (Jan 11, 2023):

@SmoochSmackers Thank you for your very detailed thoughts and ideas. On behalf of the team, I will answer your questions.

When I first started building Immich, I structure the app to be microservices and make them scalable. In order to scale with Docker, you either need Docker Swarm or a simpler and straightforward approach is to use Docker Compose. The number of containers is the number of underlying technology you need for the solution to work. If you are a Windows user, and you install software that required a database, it will install the database as well, but the services are often hidden from your eyes so you don't notice them. With self-hosting, you install every yourself and you know exactly what technologies are required to run, so it might take some time to get used to. Lastly, the point of us not building the all-in-one solution is the level of maintenance and complexity involved that we don't have the resources to spare. We rather use it to develop and maintain the core functionality of the application.
Immich is still under active development, so I encourage you not to rely on an auto-updating tool but to update the Docker's containers manually after reading the Release notes in cases there are breaking changes that need user involvement to perform a successful update
As you can see that the motion of self-hosting solutions is moving toward Docker and containers more and more. And it is a learning experience for us all, you start off with the convenience of running your services from a click of a button, then eventually your needs grow and you want to be able to control, configure, and understand how the underlying technology that you run the services you are most depended on work. So there is no harm in trying to learn and to know more about those information/technologies. I would encourage all self-hosters to do that for the sake of securing their data/resources. We provide information to run and set up Immich on Unraid so it takes some learning but I think it will be worthwhile for all parties involved.

Cheer!

@alextran1502 commented on GitHub (Jan 11, 2023): @SmoochSmackers Thank you for your very detailed thoughts and ideas. On behalf of the team, I will answer your questions. 1. When I first started building Immich, I structure the app to be microservices and make them scalable. In order to scale with Docker, you either need Docker Swarm or a simpler and straightforward approach is to use Docker Compose. The number of containers is the number of underlying technology you need for the solution to work. If you are a Windows user, and you install software that required a database, it will install the database as well, but the services are often hidden from your eyes so you don't notice them. With self-hosting, you install every yourself and you know exactly what technologies are required to run, so it might take some time to get used to. Lastly, the point of us not building the all-in-one solution is the level of maintenance and complexity involved that we don't have the resources to spare. We rather use it to develop and maintain the core functionality of the application. 2. Immich is still under active development, so I encourage you not to rely on an auto-updating tool but to update the Docker's containers manually after reading the Release notes in cases there are breaking changes that need user involvement to perform a successful update 3. As you can see that the motion of self-hosting solutions is moving toward Docker and containers more and more. And it is a learning experience for us all, you start off with the convenience of running your services from a click of a button, then eventually your needs grow and you want to be able to control, configure, and understand how the underlying technology that you run the services you are most depended on work. So there is no harm in trying to learn and to know more about those information/technologies. I would encourage all self-hosters to do that for the sake of securing their data/resources. We provide information to run and set up Immich on Unraid so it takes some learning but I think it will be worthwhile for all parties involved. Cheer!

OVERLORD commented

2026-02-04 16:50:18 +03:00

@jrasm91 commented on GitHub (Jan 11, 2023):

Updated the immich docs to link to the community all-in-one github repository (#1301).

https://immich.app/docs/install/all-in-one

@jrasm91 commented on GitHub (Jan 11, 2023): Updated the immich docs to link to the community all-in-one github repository (#1301). https://immich.app/docs/install/all-in-one

OVERLORD commented

2026-02-04 16:50:20 +03:00

@SmoochSmackers commented on GitHub (Jan 11, 2023):

@alextran1502 Thank you very much for your detailed reply! In regards to the Windows comparison, I'd honestly never thought of it in terms of everything an exe is doing in the background, so it makes a lot of sense that multiple containers would be a necessity. Regardless of how you need to do it, I'm just glad you're doing it!

Just spit-balling, but maybe, way down the line when you're not in active pre-production development, you could maybe revisit this, or even somehow put all the different containers on the unraid app store, such that one is a "core" for basic photo backup, another serves as an addon for utilizing the mobile app, another serves as an addon for machine learning, etc. No idea how possible any of that is, but I just wanted to throw it out there for consideration much later down the line.

Keep up the incredible work!! Thanks again!

@SmoochSmackers commented on GitHub (Jan 11, 2023): @alextran1502 Thank you very much for your detailed reply! In regards to the Windows comparison, I'd honestly never thought of it in terms of everything an exe is doing in the background, so it makes a lot of sense that multiple containers would be a necessity. Regardless of how you need to do it, I'm just glad you're doing it! Just spit-balling, but maybe, way down the line when you're not in active pre-production development, you could maybe revisit this, or even somehow put all the different containers on the unraid app store, such that one is a "core" for basic photo backup, another serves as an addon for utilizing the mobile app, another serves as an addon for machine learning, etc. No idea how possible any of that is, but I just wanted to throw it out there for consideration much later down the line. Keep up the incredible work!! Thanks again!

OVERLORD commented

2026-02-04 16:50:24 +03:00

@martabal commented on GitHub (Jan 12, 2023):

Hello !
Do you want that I maintain the all-in-one Dockerfile on a separate repo or do you want me to create a pull request ?

@martabal commented on GitHub (Jan 12, 2023): Hello ! Do you want that I maintain the all-in-one Dockerfile on a separate repo or do you want me to create a pull request ?

OVERLORD commented

2026-02-04 16:50:29 +03:00

@jrasm91 commented on GitHub (Jan 12, 2023):

I think we're good with you keeping it in a separate repo for now. We just get the occasional question about it, so now everyone will know to go ask you instead. 😁

@jrasm91 commented on GitHub (Jan 12, 2023): I think we're good with you keeping it in a separate repo for now. We just get the occasional question about it, so now everyone will know to go ask you instead. 😁

OVERLORD commented

2026-02-04 16:50:40 +03:00

@guim31 commented on GitHub (Jan 12, 2023):

@martabal do you think you could provide an unraid template ? I don't really know how your image could land on Unraid's community software... maybe it should be requested idk.
I know that everything could be working right know as it is, but like many other Unraid user, I use this system because of the simplicity to install Docker containers with just few clicks.

Thanks a lot for your work, and THANKS a lot @alextran1502

@guim31 commented on GitHub (Jan 12, 2023): @martabal do you think you could provide an unraid template ? I don't really know how your image could land on Unraid's community software... maybe it should be requested idk. I know that everything could be working right know as it is, but like many other Unraid user, I use this system because of the simplicity to install Docker containers with just few clicks. Thanks a lot for your work, and THANKS a lot @alextran1502

OVERLORD commented

2026-02-04 16:50:43 +03:00

@jagjordi commented on GitHub (Jan 12, 2023):

Would it be possible to migrate from the normal docker-compose setup to the all-in-one docker preserving the database and uploaded pictures?

@jagjordi commented on GitHub (Jan 12, 2023): Would it be possible to migrate from the normal docker-compose setup to the all-in-one docker preserving the database and uploaded pictures?

OVERLORD commented

2026-02-04 16:50:45 +03:00

@jrasm91 commented on GitHub (Jan 12, 2023):

Would it be possible to migrate from the normal docker-compose setup to the all-in-one docker preserving the database and uploaded pictures?

Immich persists data to the upload folder and postgres data volumes. As long as you start up the AIO with those same two volumes it should be possible.

@jrasm91 commented on GitHub (Jan 12, 2023): > Would it be possible to migrate from the normal docker-compose setup to the all-in-one docker preserving the database and uploaded pictures? Immich persists data to the upload folder and postgres data volumes. As long as you start up the AIO with those same two volumes it should be possible.

OVERLORD commented

2026-02-04 16:50:52 +03:00

@martabal commented on GitHub (Jan 12, 2023):

@guim31 Yep, I plan to do it this week. But you can already install it on unraid manually.

@martabal commented on GitHub (Jan 12, 2023): @guim31 Yep, I plan to do it this week. But you can already install it on unraid manually.

OVERLORD commented

2026-02-04 16:51:02 +03:00

@martabal commented on GitHub (Jan 12, 2023):

@jrasm91 Is it ok that my image is published on unraid community apps ?

@martabal commented on GitHub (Jan 12, 2023): @jrasm91 Is it ok that my image is published on unraid community apps ?

OVERLORD commented

2026-02-04 16:51:05 +03:00

@jrasm91 commented on GitHub (Jan 12, 2023):

I don't have a problem with it, just as long as it's clear it's not officially supported by Immich dev team and they should ask you question if they run into issues 😁

@jrasm91 commented on GitHub (Jan 12, 2023): I don't have a problem with it, just as long as it's clear it's not officially supported by Immich dev team and they should ask you question if they run into issues 😁

OVERLORD referenced this issue

2026-02-05 04:52:47 +03:00

Android app doesn't show images on Server #2053

Sign in to join this conversation.

Branches Tags

main

feat/asset-file-apis

chore/translations

fix/web-switch-label-clickable

fix/web-people-hidden-state

renovate/typescript-projects

release/next

fix/timezones

fix/time-zone-upserts

midzelis/wip

push-zpwsovysllvn

push-nwxlpmyzkyrl

push-nvnkszuqwppm

renovate/github-actions

push-smstsuupsowp

refactor/adaptive_image

push-olwpzvrxnomt

push-lmxsupnmxspl

renovate/machine-learning

feat/web-chromecast-video-looping

feat/use-native-clients

renovate/flutter

fix/create-face-edited

fix/mobile-ios-mtls

docs/contributing

docs/mise-mobile

renovate/grafana-monorepo

feature/bottom-buttons-order

feat/immich-mobile-ui-showcase

refactor/consolidate-image-requests

renovate/connectivity_plus-7.x

renovate/major-vitest-monorepo

renovate/pypi-python-multipart-vulnerability

fix/mobile-people-query

sqlite_thumbs

feat/html-text

chore/no-macro-validation

refactor/purchase-store

uhthomas/mobile-fix-app-bar-fade

uhthomas/mobile-fix-asset-jump

feat/pano-ocr

feat/shared-link-login

fix/database-backup-db-names

fix-keep-correct-ios-shared-album-asset

fix-memory-generation-and-display

feat/verify-permissions

refactor/album-service-small-tests

fix/ml-rocm-build

fix/flipped-dimensions-mobile

push-vpxwmwwxwnvw

fix-migration-width-height

refactor/more-queries

revert/prettier-translations

refactor/asset-service-queries

fix/locale-settings-desc

chore/add-debug-log

feat/edit-filters

shared-deep-link-handler

feat/mobile-editing

feat/thumbnail-native-clients

feat/platform-clients

feat/integrity-checks-izzy

fix/foreground-cloud-sync

feat/dynamic-layout

filter-by-person

feat/csp

refactor/sidebar

fix/disable-editing

fix/view-timeline-deeplink

image-zoom-on-slow-connection

fix-consider-dar-for-video-dimension

fix/merged-edited-assets

perf/optimize-album-sort

open-api-fix

feat/create-job-with-dto

use-toast-primary

feat/vitest-4

feat/ios-fastlane-match

match-signing

fix-update-time-update-timeline

chore/translation-keys

feat/modal-routes

feat/panorama-tiles

feature/mobile-view-asset-owner

feat/system-settings

feature/show-activity-count

better-info-in-asset-viewer

fix/all-people-count

feat/location-favorites

feature/rearrange-buttons-2

fix/download-storage-template

feat/kb-shortcuts-mobile

fix/people-count

push-qolzzzzxrvvn

chore/originals-in-asset-files

feat/asset-size-columns

ben/tree-a11y

new-search-filter-ui

refactor/expectSelectedReadonly

refactor/mobile-grdb

push-qvuktpxmkknu

feat/mobile-native-local-sync

refactor/timeline_ops

fix/scrubber_end

feat/version.txt

feat/context-menus

feat/server-chunked-uploads

refactor/virtualsegment

refactor/rename_daymonth_groups

fix/restrict-android-bg-worker

feat/android-periodic-worker

fix-remote-sync-clean-up

refactor/timeline_move_ops

renovate/mapbox-mapbox-gl-rtl-text-0.x

fix/timeline_split_selectable

feat/keyboard_actions_help_modal

feat/static_frontend

feat/notification-warnign-android

feat/plugins2

feat/plugins

test/create-workflow-token-action

fix/docs-force

debug/search-result-similarity

debug/cf-chunked-uploads

feat/eslint_rule

feat/search-filter-album/web

refactor/timeline_photostream

refactor/timelineasset_asset

feat/session-permissions

feat/timeline_photostream_assetnav

feat/timeline_minor_optimize

feat/timeline_perf_nocomp

feat/timeline_search_results_actions

feat/timeline_search_results_page

fix/timeline_padding

fix/timeline_search_reactivity_warnings

feat/timeline_scrollbar

feat/timeline_stream_withviewer

fix/timeline_back_forth_nav

refactor/timeline_photostream_component

fix/generated-files-checks

fix/locate-button-local

chore/base-image-mimalloc

refactor/timeline_assetlayout

refactor/timeline_selectable

refactor/timeline_aware_actions

refactor/timeline_monthsegment

feat/remove-old-pages

chore/deps-gradle

tmp_photostream

tmp/lcms

feat/mobile-dynamic-thumbnails

fix/mobile-finer-thumbnail-concurrency

refactor/timeline1

refactor/extract_photostream

refactor/rename_load_api

refactor/timeline2

refactor/timeline3

feat/multi-select-asset-viewer

feat-no-thumbhash-cache

refactor/asset_grid

feat/faster-access-checks

fix/18991

fix/19543

chore/temp-remove

fix/21419

feat/mobile-hdr-images

chore/update-mise-lockfile

feat/mise-server-checks

feat/mise-ci

feat/windows-2025

feat/dev_cli

refactor/mobile-migrate-clients

fix/map-theme

fix/require-checkbox

chore/use_swc

feat/efficient-thumbnail-decoding

refactor/mobile-thumbhash

refactor/mobile-thumbhash-new

fix/mobile-uncached-zoom

feat/beta-background-upload

fix/beta-timeline-memories-setting

fix/failed-uploads-not-removed

feat/mobile-shared-album

feat/groups

drift-map-page

drift-auth-user-sync

fix/disable-memory

feat/add-to-album-action

edit-date-time-action

drift-people-page

sqlite-remove-isIn

feat/inline-storage-columns

chore/required-reviewers

refact/asset-manager

fix/folder-sort

pnpm

feat/widget-multiple-server-urls

chore/medium-tests-dbname

fix/web-no-iterator-find

fix/map-pan-interruption

track-livephotos

timeline_events

chore/oxlint-migration

feat/maintenance-worker

feat/dav

chore/demo-snapshot

refactor/server-side-dedupe

feat/integrity-checks

dev/recognition-eval

lighter_buckets_test

perf/postgres-queue

postgres-queue

focus_rings

refactor/web-stores-1

refactor/add-to-taken

feat/sort-places

feat/sidecar-asset-file

vet

tmp/demo-snapshot-preview

fix/server-migration-file-extension

refactor/mobile-v2

fix/asset-update-race-condition

rknn-toolkit-lite2

refactor/mobile-split-up-search-page

feature/Add-rocm-support-for-machine-learning

feat/rocm

chore/async-hash-file

feat/shared-link-view-count

feat/rotation

feat/graphql

feat/job-ids

feat/ignore-library-permission-error

feat/docker-compose-builder

feat/kysely-typeorm

mobile/onboarding

no-video-player

fix/server-qsv-output-format

chore/server-geodata-tweaks

mobile/native-video-player-no-hero

feat/xxhash

fix/docs-concurrency

feat/preload-ml-textual-model

feat/local-tileserver

refactor/exif-orientation

original-path-infix

refactor/mobile/login-form-1

feat/server-editor-endpoints

fix/server-qsv-vbr

fix-mobile-db-problems

feat/ml-armnn-conversion

feat/mobile/backup-with-album-info

feat/fast-initial-sync-1

chore/handle-output_dims

feat/server-more-robust-generation

feat/unassign-faces

feat/shortcuts-on-asset-grid

feat/background-upload

feat/capacitor-mobile-app-poc

feat/server-nvenc-hw-decoding

release/v1.105

fix/mobile-fetch-non-archive

feat/fine-grained-access-controls

web/automation-ui

feat/mobile-server-endpoint-save-dropdown

feat/blurhash-thumbnail

object-storage

feat/memories-animations

dev/metrics

ml/tflite

feat/ml-export-cli

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: immich-app/immich#32