Community Unraid Container like nextcloud-aio
Hey everyone,
I discovered Ente through the folks at Kagi and it looks really promising. I tried to self-host it on my Unraid server, like many others, and ran into two problems:
1. Official install script
It doesn’t bind containers to storage correctly, so the .yaml files aren’t editable. 2. Docker Compose manager plugin
I created a custom docker-compose.yaml for the ente + ente-cli stack. The server starts and login works, but image uploads fail. Others in the community have reported the same issue. I understand Ente is a Docker stack, so a native Unraid template isn’t straightforward. Could this be handled like Nextcloud-AIO, where you install a master container template that then creates the rest of the stack? Is anyone interested in trying this with me or has ideas on how to make it work? Thanks!
It doesn’t bind containers to storage correctly, so the .yaml files aren’t editable. 2. Docker Compose manager plugin
I created a custom docker-compose.yaml for the ente + ente-cli stack. The server starts and login works, but image uploads fail. Others in the community have reported the same issue. I understand Ente is a Docker stack, so a native Unraid template isn’t straightforward. Could this be handled like Nextcloud-AIO, where you install a master container template that then creates the rest of the stack? Is anyone interested in trying this with me or has ideas on how to make it work? Thanks!
10 Replies
I'm sorry, I couldn't find the answer in the documentation.
-# If your issue is resolved, feel free to use the /solved command to close this thread. If you'd like to ask me another question use /docsearch
🔍 Similar Solved Posts
Found some similar posts that might help:
📋 Check these out:
I have Ente running on unraid. The following install method should get you going.
First, ensure that you have properly removed any previous docker images and volumes related to Ente.
Create a share named docker_compose. Open Unraid terminal and cd /mnt/user/docker_compose Paste the quickstart script and press enter. When prompted Do you want to start Ente select no. Navigate to the my-ente folder that was created. Create a folder named data.
Open the compose.yaml file with an editor. Under museum volumes, Postgres volumes and Minio volumes edit the volumes to match your local unraid locations: - /mnt/user/docker_compose/my-ente/museum.yaml:/museum.yaml:ro - /mnt/user/docker_compose/my-ente/data:/data:ro - /mnt/user/docker_compose/my-ente/data/postgres-data:/var/lib/postgresql/data - /mnt/user/docker_compose/my-ente/data/minio-data:/data Save those changes to the compose.yaml file. On the Unraid dashboard, navigate to the docker tab and with the docker compose plugin manager choose add new stack. On the dialog box click on Advanced and paste your Ente docker compose location under Stack Directory. /mnt/user/docker_compose/my-ente Next click update stack and it should spin up and be reachable. This stack tends to run best on a cache only share but you can create an additional array only share and store the minio-data location on that share if you need a ton of storage space.
Create a share named docker_compose. Open Unraid terminal and cd /mnt/user/docker_compose Paste the quickstart script and press enter. When prompted Do you want to start Ente select no. Navigate to the my-ente folder that was created. Create a folder named data.
Open the compose.yaml file with an editor. Under museum volumes, Postgres volumes and Minio volumes edit the volumes to match your local unraid locations: - /mnt/user/docker_compose/my-ente/museum.yaml:/museum.yaml:ro - /mnt/user/docker_compose/my-ente/data:/data:ro - /mnt/user/docker_compose/my-ente/data/postgres-data:/var/lib/postgresql/data - /mnt/user/docker_compose/my-ente/data/minio-data:/data Save those changes to the compose.yaml file. On the Unraid dashboard, navigate to the docker tab and with the docker compose plugin manager choose add new stack. On the dialog box click on Advanced and paste your Ente docker compose location under Stack Directory. /mnt/user/docker_compose/my-ente Next click update stack and it should spin up and be reachable. This stack tends to run best on a cache only share but you can create an additional array only share and store the minio-data location on that share if you need a ton of storage space.
Thats Awesome! Thank you very much, I will try it out. Do you also have ente-cli running?
On the server, no. I run Ente-cli from my desktop computer to connect to the server.
What did you write into the docker-compose.yml that the plugin manager creates? Should that be the same as the compose.yaml?
Okay, its working now 🙂 copying fixed it
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Thread marked as solved. It will be closed in <t:1757600306:R>.
Sorry, I forgot to mention that you need to rename the Ente compose file to compose.yml in order for unraid docker compose manager plugin to automatically use it.
Thank you I figured it out, I also needed to change the ip in the museum.yaml to the local one from my server. Now the upload works, thank you very much!
This thread is now closed.