For the purposes of this example, we’ll be using Raspberry Pi OS 64-bit as the base filesystem for our new Docker image. Since this operating system lacks an official one on Docker Hub, it feels like a good fit. However, the principles described here should work well enough for any OS.
Lima (short for Linux on Mac) is a virtual machine management tool for running Linux boxes (think Vagrant, but for development tooling). It focuses on offering a convenient way to run and interact with containerd, but its high customizability allows for a lot more. The examples folder in its repository gives a good idea of its capabilities.
To use the regular Docker CLI with Amazon Elastic Container Registry (Amazon ECR), you need to acquire specific login credentials first. Assuming you already have basic AWS credentials, run the following to pass them to Docker. Note that, below, AWS_ACCOUNT_ID refers to the repository owner, which may not be your own AWS account.
When dealing with container IPs, it’s important to note which network each container is connected to and which network mode it’s using. The default network mode for a Docker installation is bridge, so I’ll assume you’re using it too.
The following command starts a Jupyter instance and mounts the current folder.
We will use k3s, a lightweight Kubernetes distribution, to get the most out of our hardware. This tutorial uses a Raspberry Pi 4 and the latest Raspberry Pi OS 32-bit (formerly known as Raspbian). The 64-bit version is pretty much the same for these steps.
This tutorial was tested on a Raspberry Pi 4 with the RGB Cooling HAT model “YB-EBV02 VER1.1”, by Yahboom, on both 32-bit and 64-bit OS.
To create and manage Java projects, it’s common to use an IDE like IntelliJ IDEA or Eclipse.
We’ll use Docker to avoid installing the Android SDK on our computer for this task. This is possible thanks to this Ionic Docker image.
docker run -it -v ${PWD}:/etc/letsencrypt --entrypoint="sh" certbot/certbot
certbot certonly -d <domain_name> --manual --preferred-challenges dns# Create the database dump on your server
docker exec <my_mongodb_container> mongodump --archive=/backups/mongodb-`date +%Y%m%d`.gz --gzip --db <database_name>
# Copy it to your local machine, if needed
scp -r <server_user>@<server_ip>:<remote_backup_path> <local_backup_path>
# Restore it directly into a running Docker container
zcat <backup_path> | docker exec -i <my_mongodb_container> mongorestore --archive --dropdocker run -it --rm -e KUBECONFIG=/root/.kube/config -v ${PWD}:/apps -v <local_path_to_kube_folder>:/root/.kube alpine/helm:<desired_version> <helm_command>