Editing Introduction to a Self Managed Life: a 13 hour & 28 minute presentation by FUTO software (section)

=== Step 1: Install docker properly. ===

<blockquote>'''NOTE:''' This step may not be necessary!
</blockquote>
**YOU DO NOT NEED TO PERFORM THIS STEP IF YOU INSTALLED DOCKER WHILE INSTALLING ONLYOFFICE. IF YOU INSTALLED DOCKER PRIOR TO INSTALLING ONLYOFFICE, SKIP THIS STEP! IF YOU DID NOT INSTALL ONLYOFFICE BECAUSE YOU DIDN’T WANT ONLYOFFICE, THAT MEANS YOU SKIPPED INSTALLING DOCKER AS WELL; IN WHICH CASE, YOU WILL NEED TO FOLLOW THESE INSTRUCTIONS.

<span id="never-use-ubuntus-snap-version-of-docker-1"></span>
==== Never use Ubuntu’s snap version of docker ====

Ubuntu installs docker by default using the cancerous snap. We do not want to use snap. Ubuntu installer will ask if you want to install Docker, and you should always say No. 

<span id="doesnt-onlyoffices-install-script-install-docker-for-me-1"></span>
==== Doesn’t onlyoffice’s install script install docker for me? ====

Onlyoffice’s installation script '''DOES''' install docker for you. I am still going to have you do it manually.

* If you choose to not install onlyoffice, and wish to install Immich, I want you to know how to install docker on this virtual machine ''yourself.''
* I don’t want to rely on onlyoffice’s script. It won’t install docker for us if it detects Docker already, so we’re not going to do a double install. What if onlyoffice’s installation script stops installing docker the same way in a new version, or stops installing docker at all within its script?

It’s little work to install Docker the right way for our purposes manually, and it’s good to have it documented so that you can use docker for immich even if you elect not to install Onlyoffice.

<span id="update-and-upgrade-your-system-3"></span>
==== 1.1 Update and upgrade your system ====

<pre>sudo apt update &amp;&amp; sudo apt upgrade -y
sudo apt install curl git wget -y</pre>
<span id="check-for-other-docker-installations-2"></span>
==== 1.2 Check for other Docker installations: ====

Run <code>docker --version</code> and see what is installed. Nothing should be installed yet since this is a fresh system. If something is installed, remove it.

<pre># Just in case you accidentally installed snap version of docker:

sudo snap remove docker

# For other versions of docker: 

sudo apt remove docker docker-engine docker.io containerd runc</pre>
<span id="install-docker-using-official-docker-script-3"></span>
==== 1.3 Install Docker using official Docker script: ====

<pre>curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh</pre>
<blockquote>'''Note:''' It’s very important to use the official Docker installation and not the Snap version. The Snap version can cause issues due to its sandboxed nature, making it a mess for mailcow’s requirements. Docker snap makes me sad, and it’ll make you sad too if you try to make things work with it.
</blockquote>
<span id="install-docker-compose-2"></span>
==== 1.4 Install Docker Compose: ====

Ubuntu’s <code>docker-compose-plugin</code> is safe to use, it is not snap cancer.

<pre>sudo apt install docker-compose-plugin -y
sudo systemctl enable --now docker</pre>
<span id="verify-the-install-2"></span>
==== 1.5 Verify the install ====

Run <code>docker compose version</code> and make sure the version is 2.0 or higher. Run <code>docker --version</code> and make sure version is 24.0.0 or higher

<span id="set-proper-permissions-3"></span>
==== 1.6 Set proper permissions: ====

Docker needs to be run as root for some operations, but you can add your user to the docker group to avoid using <code>sudo</code> all the time. To be clear, mailcow’s own [https://docs.mailcow.email/getstarted/install/#check-selinux-specifics documentation] and [https://community.mailcow.email/d/59-mailcow-containers-running-as-root community] suggest starting with root or <code>sudo</code>, and you should trust them more than me. To quote mailcow developers, ''“Controlling the Docker daemon as non-root user does not give you additional security. The unprivileged user will spawn the containers as root likewise. The behaviour of the stack is identical.”'' Run this command to add your user:

<pre>sudo usermod -aG docker $USER</pre>
Log out and log back in, or run:
<code>newgrp docker</code>

<div class="figure">

<gallery mode="packed-hover" heights=250 widths=400 perrow=2>
File:immichdiagrambad.png
</gallery>

</div>
<div class="figure">

<gallery mode="packed-hover" heights=250 widths=400 perrow=2>
File:immichok.png
</gallery>

</div>
<div class="figure">

<gallery mode="packed-hover" heights=250 widths=400 perrow=2>
File:immichdiagramgood.png
</gallery>

</div>
<span id="step-2-understand-how-this-will-be-set-up-differently-from-stock-setup."></span>