docker-install VS Home Manager using Nix

Now we can install Uptime Kuma using the Docker install instructions here. We're using docker instead of bare metal to keep things contained, and Docker images are less likely to be blocked, while NodeJS NPM packages are.

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.

It's probably overkill for what you are trying to do. But I have been using home-manager [0] as a way to quickly restore my working environment.

[0] https://nix-community.github.io/home-manager/

$ home-manager --version 23.05 $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-23.11.tar.gz home-manager $ nix-channel --update $ nix-shell '' -A install [...] All done! The home-manager tool should now be installed and you can edit /home/MY-USERNAME/.config/home-manager/home.nix to configure Home Manager. Run 'man home-configuration.nix' to see all available options. $ home-manager --version 23.05

Unfortunately until we find more volunteers in this area, it is hard to see status quo changing. See also https://github.com/nix-community/home-manager/issues/607 and this ongoing project https://github.com/pjones/plasma-manager

> Channels are, AFAIU, a reference to some point-in-time/commit/version of nixpkgs

It's not specifically nixpkgs, but any Nix code generally.

Per the Nix manual[0]:

> Channels are a mechanism for referencing remote Nix expressions and conveniently retrieving their latest version.

e.g. home-manager's suggested channel is just the github tarball for the relevant branch[1]:

  nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager

It sounds like you'd benefit a lot from Nix/NixOS [1], if not just home-manager[2].

1. https://nixos.org/

2. https://github.com/nix-community/home-manager

nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager nix-channel --update nix-shell '' -A install

I'm using flakes and home manager and not really sure how to go about managing my neovim configuration. I've read through some other posts, github issues, and various articles trying to suss out a good way to do this. Reading through other people's configs and posts was somewhat helpful but there is a lot going on I don't understand and everyone's examples I've seen vary wildly.

Said store path contains the home-manager repo. After the home-manager run, the store path is recreated.

I can't answer all your questions, but home-manager does have a dconf module that would probably be better to use than that external tool. Everything inside the options block are the things you can pass to the dconf module.