{"id":3288,"date":"2023-12-04T09:41:37","date_gmt":"2023-12-04T15:41:37","guid":{"rendered":"https:\/\/lab.rapternet.us\/?p=3288"},"modified":"2023-11-05T22:14:38","modified_gmt":"2023-11-06T04:14:38","slug":"docker-compose-on-unraid","status":"publish","type":"post","link":"https:\/\/lab.rapternet.us\/?p=3288","title":{"rendered":"Docker Compose on Unraid"},"content":{"rendered":"\n

Recently I restarted my journey towards a self hosted photos system again. This time I was planning on trying it immich. Immich provides a docker compose file to startup their entire stack of 6+ containers, which I wanted to run on unraid that lacks compose in the default configuration. Queue journey to get docker compose capabilities on unraid.<\/p>\n\n\n\n\n\n\n\n

We’re going to start out in the community apps section. We’ll be using the docker compose manager plugin. <\/p>\n\n\n\n

\"\"
Docker Compose Manager<\/figcaption><\/figure>\n\n\n\n

Once it’s installed, navigate to the docker page again and scroll to the very bottom. You’ll find new options available, besides the usual add container, you’ll now have the ability to add a new stack with docker compose.<\/p>\n\n\n\n

\"\"
At the bottom of the docker page in unraid<\/figcaption><\/figure>\n\n\n\n

When you add a new stack, you’ll need to give it a name, since I’m going to be installing Immich, that will be my stack name.<\/p>\n\n\n\n

\"\"
Stack Name<\/figcaption><\/figure>\n\n\n\n

Now you’ll have the new stack listed, if you click on the gear next to the name you’ll be provided a number of options for configuring it. The edit stack option will give you the main options needed for your docker compose inputs.<\/p>\n\n\n\n

\"\"
New Stack Shown<\/figcaption><\/figure>\n\n\n\n
\"\"
Stack Configuration Options<\/figcaption><\/figure>\n\n\n\n

This is where you’ll have the options to modify your compose file and environment file. There is also a UI label option that I haven’t used.<\/p>\n\n\n\n

\"\"
Edit Stack Options<\/figcaption><\/figure>\n\n\n\n

Now that we’re in our compose file, we can start editing the yaml, for me, I’ll be pasting in the provided compose file for immich and modifying data directory locations.<\/p>\n\n\n\n

\"\"
Docker compose file entry<\/figcaption><\/figure>\n\n\n\n

After saving the compose file, the stack ui labels dialog popped up, I left this as is and hit the save button at the bottom of it.<\/p>\n\n\n\n

\"\"
Stack Labels<\/figcaption><\/figure>\n\n\n\n

For my stack, I also edited the environment file, copying in the immich default file and editing the variables for my environment and added secure passwords. Once that was done, I could use the compose up on my stack to try and start it up. The start\/stop\/update commands are on the right hand side of your new stack, along with the auto start option<\/p>\n\n\n\n

\"\"
Start\/Stop\/Update\/Auto-Start<\/figcaption><\/figure>\n\n\n\n

Once I got everything configured, it worked well on my first try starting it, no need to reconfigure and retry with different settings. All the containers in my stack came up and immich was running quickly. I’ll certainly be using this functionality for more software in the future. This also works out well with docker logins, so you can get a higher number of image pulls before docker hub blocks your pulls.<\/p>\n\n\n\n

Resources<\/h2>\n\n\n\n