From Docker to Kubernetes - Multi-Arch with Go and Nodejs¶
This guide has 5 main parts:
- Getting Official with Multi-arch Images
- Learning How to Build Best-practice Node.js Docker Images
- Guide to Building Best-practice Go Docker Images
- Building Multi-arch Docker Images
- Kubernetes Time
Proxy Users here is your extra part to start with:
Who is a proxy user?
A proxy user is an individual connecting to the internet via a proxy server. This setup is done for network security in enterprise environments and requires setting proxy variables such as http_proxy, etc. If you are behind a proxy server, you would most likely know about it due to the need to change settings to get various applications to work. Therefore, if you don't think you are using a proxy, you most likely are not. However, if you are really unsure about this, this article can help you find out for certain.
Prerequisites¶
-
Have an up and running Kubernetes cluster
-
Setup access to that cluster using kubectl
-
Register for a DockerHub account following the process outlined on DockerHub here
-
Download Docker on your workstation from DockerHub using your newly created free account here
What will this Guide do for you?¶
This guide will start by looking at what Official Repositories are and how to build from them. Then, it will shine light on how to tell if an app will run on your platform (architecture). Next, we will look at how best to build images for go and nodejs in Docker with examples and then actually build these images with Multi-Architecture manifests. Finally, we will use these images or my pre-built images to deploy to a Kubernetes cluster.
What in the Tarnation is a Container?¶
Application containers make use of linux kernel features to provide lightweight isolation by limiting what a process (running program) can see (namespaces), what system resources a process can use (cgroups), and what system calls a process can make (seccomp) combined with other features such as enhanced access control (SELinux). We use container images (all the dependencies and files our application needs to run put together in layers), which we can bundle and store in image repositories to use to start containers (run a process using the files from the aforementioned container image (image) tar file in an environment with the isolation described above).
If you just finished reading the above and want to get a little deeper into some of the parts of containers I just name-dropped please have a look see at What even is a container: namespaces and cgroups.
If you want a technical deep-dive into containers and container runtimes getting into the nitty-gritty, the fabulous 4 part series Container Runtimes is the happy path for you.
Get the Code¶
The code for this guide is on the accompanying GitHub. You can also access this page by clicking on the GitHub icon on the top right of every page.
If you have git installed, it can be brought onto your computer with:
git clone https://github.com/siler23/MultiArchDockerKubernetes.git
If you don't have git or don't want to clone this repo, you can use the download link in the top right corner of the GitHub page.
Search to your Heart's Content¶
Search the docs for the content you want by using the search bar at the top of each page like so for hello world.
Tip
You can also immediately jump to the search bar by typing f or s.
Let's Begin¶
Non-Proxy Users (Regular Users) Start Here: Official Docker Repos and Multi-Arch Primer
Proxy Users Start Here: Proxy PSA for Proxy Users