I thought I'd share my experience doing this, as it was quite a pain, and maybe this will help someone else. It contains the process I took to set it all up, and the workarounds, and solutions that I found along the way. 1. Hardware that I used: [Raspberry Pi 1 Model B rev 2.0](https://web.archive.org/web/20230923000322/https://www.pololu.com/product/2750), [SanDisk Ultra SD Card (32GB)](https://web.archive.org/web/20231026234811/https://www.westerndigital.com/en-ca/products/memory-cards/sandisk-ultra-uhs-i-sd?sku=SDSDUN4-032G-GN6IN). 2. I had issues using the [Raspberry Pi Imager](https://github.com/raspberrypi/rpi-imager) (v1.8.5, Flatpak): It initially flashed pretty quickly, but the verification process was taking an unreasonably long time — I waited ~30mins before giving up, and cancelling it; so, I ended up manually fashing the image to the SD card: 1. I connected the SD card to a computer (running Arch Linux). 2. I located what device corresponded to it by running `lsblk` (`/dev/sdd`, in my case). 3. I downloaded the image from [here](https://www.raspberrypi.com/software/operating-systems/). I specifically chose the "Raspberry Pi OS Lite" option, as it was 32-bit, it had Debian Bookworm, which was the version needed for `podman-compose` (as seen [here](https://packages.debian.org/search?suite=all&searchon=names&keywords=podman-compose)), and it lacked a desktop environment, which I wanted, as I was running it headless. 4. I then flashed the image to the SD card with `dd if= of= BS=50M status=progress` - `` is the path to the file downloaded from step 3. - `` is the device that corresponds to the SD card, as found in step 2.2. - `BS=50M` I found that 50M is an adequately sized buffer size. I tested some from 1M to 100M. - `status=progress` is a neat option that shows you the live status of the command's execution (write speed, how much has been written, etc.). 3. I enabled SSH for headless access. This was rather poorly documented (which was a theme for this install). 1. To enable SSH, as noted [here](https://web.archive.org/web/20240101104715/https://www.raspberrypi.com/documentation/computers/configuration.html#remote-access), one must put an empty file named `ssh` at the "root of the SD card". This is, unfortunately, rather misleading. What one must actually do is put that file in the root of the *boot partition*. That is not to say the directory `/boot` contained in the root partition, `rootfs`, but, instead, it must be placed within the boot partition, `bootfs` (`bootfs`, and `rootfs` are the two partitions written to the SD card whe you flash the downloaded image). So the proper path would be `/ssh`. I simply mounted `bootfs` within my file manager, but, without that, I would have had to manually locate which partition corresponded to that, and mount it manually to be able to create the file. The ownership of the file didn't seem to matter — it was owned by my user, rather than root (as was every other file in that directory, it seemed). 2. One must then enable password authentication in the SSH daemon, otherwise one won't be able to connect via SSH using a password (I don't understand why this is not the default): 1. Edit `/etc/ssh/sshd_config` 2. Set `PasswordAuthentication yes` (I just found the line that contained `PasswordAuthentication`, uncommented the line, and set it to `yes`). 4. I changed the hostname by editing `/etc/hostname` and replacing it with one that I wanted. 5. I created a user (the user is given sudo priveleges automatically) 1. Create a file at `/userconf.txt` — that is, create a file named `userconf.txt` in the `bootfs` partition (again, poorly documented [here](https://web.archive.org/web/20240101104715/https://www.raspberrypi.com/documentation/computers/configuration.html#configuring-a-user)). 2. As mentioned in that documentation, add a single line in that file of the format `:, where - `` is the chosen username for the user. - `` is the salted hash of your chosen password, which is generated by running `openssl passwd -6` and following its prompts. 6. Plug the SD card into the Pi, plug in power, and wait for it to boot. This is an old Pi, so it takes a good minute to boot fully and become available. You can ping it with `ping .local` to see when it comes online (where `` is yor chosen hostname). 7. SSH into the Pi with `ssh @.local` (You'll of course need mDNS, like Avahi, setup on your device running SSH). 8. Make sure that everything is updated on the Pi with `sudo apt update && sudo apt upgrade` 9. Install Podman with `sudo apt install podman` (the socket gets automatically started by `apt`). 10. Install Podman Compose with `sudo apt install podman-compose`. 11. Create the compose file `compose.yaml`. Written using [the official](https://github.com/pi-hole/docker-pi-hole) as reference, it contains the following: ```yaml version: "3" services: pihole: container_name: pihole image: docker.io/pihole/pihole:latest ports: - ":53:53/tcp" - ":53:53/udp" - "80:80/tcp" environment: TZ: '' volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' ``` - `` is the ip of the device running the container. The reason for why this is needed can be found in the solution of [this post](https://web.archive.org/web/20240315031012/https://sh.itjust.works/post/16201887). - `` is your timezone as listed [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). - For the line that contains `image: docker.io/pihole/pihole:latest`, `docker.io` [is necessary](https://stackoverflow.com/questions/69162077/podman-pull-official-images-from-docker-hub), as Podman does not default to using [hub.docker.com](https://hub.docker.com/). - Note that there isn't a `restart: unless-stopped` policy. Apparently, [podman-compose currently doesn't support restart policies](https://github.com/containers/podman-compose/issues/91). One would have to create a Systemd service (which I personally think is quite ugly to expect of a user) to be able to restart the service at boot. 12. (NOTE: if you wan't to skip step 13, run this command as sudo) Pull the image with `podman-compose --podman-pull-args="--arch=arm/v6" pull` - `--podman-pull-args="--arch=arm/v6"` is necessary as `podman-compose` [doesn't currently support specifying the `platform` in the compose file](https://github.com/containers/podman-compose/issues/551). - Specifying the architecture itself is required as, from what I've found, Podman appears to have a bug where it doesn't properly recognize the platform of this Pi, so you have to manually specify which architecture that it is i.e. `armv6` (you can see this architecture mentioned [here](https://hub.docker.com/r/pihole/pihole/tags) under "latest"). - This took a little while on my Pi. The download rate was well below my normal download rate, so I assume the single threaded CPU is just being too bogged down to handle a high download rate. - Don't be concerned if it stays at the "Copying blob..." phase for a while. This CPU is seriously slow. 13. Allow podman to use ports below 1024, so that it can run rootless: - Edit `/etc/sysctl.conf`, and add the line `net.ipv4.ip_unprivileged_port_start=53`. This allows all non-priveleged users to access ports >=53. Not great, but [it's what's currently needed](https://github.com/containers/podman/blob/main/rootless.md). You can avoid this step by running step 12, and 14 as sudo. - Apply this with `sysctl -p` 14. (NOTE: if you wan't to skip step 13, run this command as sudo) Start the container with `podman-compose up -d`. - It will take a while to start. Again, this Pi is slow. - Don't worry if `podman-compose ps` shows that the container is "unhealthy". This should go away after about a minute, or so. I think it's just in that state while it starts up. 15. Access the Pihole's admin panel in a browser at `http:///admin`. - The password is found in the logs. You can find it with `podman-compose logs | grep random`. The password is randomly generated everytime the container starts. If you want to set your own password, then you have to specify it in the compose file as mentioned [here](https://github.com/pi-hole/docker-pi-hole).