UPDATE DOCKER AND KUBERNETES ON PI INSTALL
UPDATE DOCKER AND KUBERNETES ON PI SOFTWARE
UPDATE DOCKER AND KUBERNETES ON PI PC

Making the configuration changes after I flashed the SD card wouldn’t stick: Each time I rebooted, the default hostname would reappear. But that’s not a straightforward task, as the image of the operating system used to flash an SD card is not easy to edit. The instructions for changing the hostname on the Hypriot website suggest editing a configuration file on the SD card before flashing the operating system and booting it. My first challenge though was to find enough Compute Module 3s to build a cluster. Then all I had to do was give each one a unique hostname so it could be identified on my local network. The Hypriot website details the rather fiddly process of flashing its OS to an SD card via the command line, but I just used the Raspberry Pi Imager graphical utility on my Mac. For the others I needed to use SD cards-the Turing Pi provides a reader for each module. I was only able to get one compute module with built-in storage. When you’re done, you can check that the upload went okay because any module in the first slot has access to an HDMI port in addition to USB, meaning you can plug in a screen and keyboard to interact with it. The Turing Pi makes it easy to put Hypriot on a module with an onboard flash chip: You can put the module into the first slot, move a jumper to put it in flash mode, and upload Hypriot from a desktop computer via a micro-USB port. The CM3 comes in two flavors: those with an onboard flash chip and those without, which need an external SD card for storage.

UPDATE DOCKER AND KUBERNETES ON PI INSTALL

How you install Hypriot depends on the flavor of your compute modules. The Turing Pi docs recommend using HypriotOS, which is a stripped-down version of the Debian Linux operating system with the Docker container system preinstalled.

The next step was to prepare the compute modules for cluster life by configuring each one’s operating system.

UPDATE DOCKER AND KUBERNETES ON PI PC

Next, I realized the Turing Pi really can’t just sit unprotected on the surface of a desk, so I 3D-printed the base of an ITX PC case to support it. Eventually I tracked five down at a local Micro Center. The current semiconductor supply squeeze meant I couldn’t find any in stock online. The Turing Pi provides centralized power and a built-in Ethernet switch to connect the modules. The point of the Turing Pi is to replace the mess of network cables, boxes, and multiple power supplies that are the invariable by-products of trying to build a cluster from standard Raspberry Pi’s. Up to seven Raspberry Pi compute modules can be fitted, but not all slots have to be filled at once.

The Turing Pi has the same form factor as a mini ITX PC motherboard and can be fitted into a standard mini PC case, although I just printed the bottom portion of one. (A version that supports the latest, Compute Module 4 has been announced but there is no word yet on pricing or a release date). The current version supports the Raspberry Pi Compute Module 1 and Compute Module 3: these are essentially just Raspberry Pi’s minus any input/output ports. But what looks like a row of slots for memory chips are slots for compute modules. The US $199 Turing Pi has the same dimensions as a mini ITX PC motherboard and has USB, HDMI, and Ethernet ports. I wanted to get my feet wet with container technology without the risk of accidentally running up hefty cloud charges, so I decided to try out the Turing Pi, which lets you use up to seven Raspberry Pi compute modules as a cluster. The idea is straightforward, but the array of implementations is bewildering, especially if, like me, you’re not a seasoned system administrator. And as a bonus, containers make it easier to deploy applications efficiently in a cloud or across a local computing cluster.

UPDATE DOCKER AND KUBERNETES ON PI SOFTWARE

One increasingly popular solution today is to add a container layer to the software stack, giving each application its own temporary, sandboxed environment without needing the resources required for a complete stand-alone virtual machine. But as computers became more complex, so did installation procedures, which led to problems like “ dependency hell,” as different applications dueled over conflicting system configurations.

Once upon a time, if you wanted to install a piece of software, you just stuck an executable file on your hard drive somewhere and went on your merry way.

Update docker and kubernetes on pi