docker-install VS nixos-config

curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh # Install docker compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Apply executable permissions to the binary sudo chmod +x /usr/local/bin/docker-compose # Run Project docker-compose up -d

root@ubuntu-16gb-hel1-1:~# curl -fsSL https://get.docker.com | sh - # Executing docker install script, commit: e5543d473431b782227f8908005543bb4389b8de + sh -c apt-get update -qq >/dev/null + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null + sh -c install -m 0755 -d /etc/apt/keyrings + sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | gpg --dearmor --yes -o /etc/apt/keyrings/docker.gpg + sh -c chmod a+r /etc/apt/keyrings/docker.gpg + sh -c echo "deb [arch=arm64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable" > /etc/apt/sources.list.d/docker.list + sh -c apt-get update -qq >/dev/null + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce docker-ce-cli containerd.io docker-compose-plugin docker-ce-rootless-extras docker-buildx-plugin >/dev/null + sh -c docker version Client: Docker Engine - Community Version: 26.0.0 API version: 1.45 Go version: go1.21.8 Git commit: 2ae903e Built: Wed Mar 20 15:18:14 2024 OS/Arch: linux/arm64 Context: default Server: Docker Engine - Community Engine: Version: 26.0.0 API version: 1.45 (minimum version 1.24) Go version: go1.21.8 Git commit: 8b79278 Built: Wed Mar 20 15:18:14 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.28 GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0 ================================================================================ To run Docker as a non-privileged user, consider setting up the Docker daemon in rootless mode for your user: dockerd-rootless-setuptool.sh install Visit https://docs.docker.com/go/rootless/ to learn about rootless mode. To run the Docker daemon as a fully privileged service, but granting non-root users access, refer to https://docs.docker.com/go/daemon-access/ WARNING: Access to the remote API on a privileged Docker daemon is equivalent to root access on the host. Refer to the 'Docker daemon attack surface' documentation for details: https://docs.docker.com/go/attack-surface/ ================================================================================ root@ubuntu-16gb-hel1-1:~# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

curl | sh is a bad practice, but lack of "curl https://get.docker.com | sh" scenario is certainly bad for Podman adoption.

sudo apt-get purge docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras sudo rm -rf /var/lib/docker sudo rm -rf /var/lib/containerd Install Docker curl -fsSL https://get.docker.com -o get-docker.sh sudo sh ./get-docker.sh

For Linux (using curl): curl -fsSL https://get.docker.com -o get-docker.sh && sh get-docker.sh

Install Docker (curl -sSL https://get.docker.com/ | sudo sh)

On WSL2, you just install Docker the same way as you would do on Linux. `sudo apt install docker.io` (from Debian/Ubuntu repo) or `curl https://get.docker.com | sh` (from Docker Inc). If you are using different WSL distribution, the standard way to install docker should work just fine. (e.g. `sudo pacman -S docker` works as expected on ArchWSL)

curl https://get.docker.com | bash -E

After all the resources are provisioned, I need to install Docker and pull a specific image. I will install Docker like this: curl -sSL https://get.docker.com | sh.

# 1. download the script # # $ curl -fsSL https://get.docker.com -o install-docker.sh # # 2. verify the script's content # # $ cat install-docker.sh # # 3. run the script with --dry-run to verify the steps it executes # # $ sh install-docker.sh --dry-run # # 4. run the script either as root, or using sudo to perform the installation. # # $ sudo sh install-docker.sh #

I use Nix/NixOS. My system state is a direct result of my config that is declared in a bunch of text files. For example, leaf packages that are installed system-wide are declared here: https://github.com/Atemu/nixos-config/blob/e646c4ec1aac80cfdf7b8c79debcfaee70237018/packages.nix

If it matters, my distro is NixOS and here's the machine's system config: https://github.com/Atemu/nixos-config/blob/95f9bb201ab4c2ab95fb3089909f5951a0646699/configs/HEPHAISTOS/default.nix

If something really goes south, I can have my entire system rebuilt automatically almost to the bit within 5-20min (mostly dependant on Internet speed) because my system is reproducible from just a bunch of text files.

Here's my desktop configuration to give you an idea: https://github.com/Atemu/nixos-config/blob/0e97d9af632852e7440563a9b5976663e61071b7/desktop.nix

If you want to know more: https://nixos.org/ Here's how such a system declaration can look like: My current desktop configuration, packages "installed" system-wide.

If you're looking for a way to restore your system configuration should your drive go kaput, perhaps look into declarative means of configuration instead. With those, your system is defined by a few text files and restoring or duplicating it is trivial. If you want to stay with Arch (great distro), imperative tools like Ansible, Puppet or Chef should work. If you want to try greener pastures, look into NixOS which is what I use. All I need to restore my machine is a few text files like this one (I just clone the git repo).

It only takes https://github.com/Atemu/nixos-config/blob/master/configs/HEPHAISTOS/default.nix#L14 and all these settings are applied: https://github.com/Atemu/nixos-config/blob/af0960a7f7b0d6b9d775015c63a107ede6f63c82/desktop.nix

Here's the list of packages available in all my systems or my desktop configuration to give you an idea.

Set it up once precisely the way you like it, run forever. You only need slight tweaks every now and then to keep up with progress. On how many machines you want with as much shared configuration you want, any time you want. If your NixOS boot drive died, you could have a working NixOS system that's exactly[3] like the old one in a matter of minutes depending on your internet and hardware speed. (Without user data of course.) All you need is one (or a few if you prefer) lean text files that can and should be tracked in a git repo like this on: https://github.com/Atemu/nixos-config