I have one of the 8gb pi4 units that i am using to teach myself docker as the 8gb of ram and the 64bit os is great for running docker on it, currently have
a microsoft SQL server 2019 docker container setup on it which seems to be really stable. i have a 2gb pi 4 that i run as an amiga as i have the offical licence from cloanto and a 4gb pi 4 that i connect to my ipad pro 2020 via
the USB-C connector on the pi and ipad so it is powered just from the ipad
and the ipad sees it as a ethernet device which is really cool.

--- Mystic BBS v1.12 A44 2020/02/04 (Raspberry Pi/32)
* Origin: Dales BBS (21:4/168)

I see that they have renamed Raspbian to Raspberry Pi OS as part of making a 64bit version. Hopefully Raspbian Buster continues to receive updates because I only just finished upgrading the various Pi devices I have in the house (cameras, bbs, k3s cluster etc) from Stretch.

Can't recommend Docker and containers in general enough though. Makes it a lot
easier doing OS upgrades if all you need to do is spin up your containers instead of going back to install scripts and remembering which config files you
modified, which libraries had to be installed from source and such like.

--- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.16.1)
* Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)

On 10 Jun 2020, pokeswithastick said the following...

Can't recommend Docker and containers in general enough though. Makes
it a lot easier doing OS upgrades

I really need to play with docker & wrap my head around it better. I get the concept of a VM, that's easy, but for some reason my head has a hard time
with containers.

Jay

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (21:3/110)

Re: Re: Raspberry Pi OS (64 bit)
By: Warpslide to pokeswithastick on Wed Jun 10 2020 08:50 am

Can't recommend Docker and containers in general enough though.
Makes it a lot easier doing OS upgrades

I'm a huge fan of docker, and this point is one of the reasons why. Easy backup
and recovery is another. (Data backup + container image = PC shutdown/restart)

I pretty much run everything in containers now, and its not uncommon that if I need to a host, that I "move" my containers to another host, do the update/upgrade and then move them back when I do that other host.

Hub 3 is a container, that I can bounce between 2 of my Pis, if I need to do something to one of them.

I really need to play with docker & wrap my head around it better. I get the concept of a VM, that's easy, but for some reason my head has a hard time with containers.

There are a few things to get your head around, but once you have, they are
pretty easy to work with. The first one to understand is "data" (and to an extent application "configuration") needs to be stored specifically somewhere, because the container itself can be deleted and recreated. When it is, just pair it back up with the data (and configuration), and its like a PC was just rebooted.

My cloud servers and home lab, I run ESXi with 3 linux "docker hosts", configured as a docker swarm. I can then shutdown 1 host (if I need to do something to it), and the containers automatically move to one of the other 2. No change to networking, configuration or anything required - whatever those apps were (normally a LAMP server of some sort), just keep working. When that 1
server is back online, any new containers normally get deployed there first.

...ëîåï

... Never let your feet run faster than your shoes.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)