Shadyman has quit [Remote host closed the connection]
starblue has quit [Ping timeout: 276 seconds]
starblue has joined #beagle
M-blaise has joined #beagle
otisolsen70 has quit [Quit: Leaving]
Guest52 has joined #beagle
M-blaise has quit [Read error: Connection reset by peer]
M-blaise has joined #beagle
otisolsen70 has joined #beagle
M-blaise has quit [Read error: Connection reset by peer]
brook has joined #beagle
M-blaise has joined #beagle
GenTooMan has quit [Ping timeout: 240 seconds]
GenTooMan has joined #beagle
akaWolf has quit [Ping timeout: 276 seconds]
vvn has quit [Quit: WeeChat 3.5]
vvn has joined #beagle
vvn has quit [Client Quit]
vvn has joined #beagle
SJFriedl has joined #beagle
akaWolf has joined #beagle
vvn has quit [Client Quit]
vvn has joined #beagle
vvn has quit [Client Quit]
Steve_ has joined #beagle
vvn has joined #beagle
Steve_ has quit [Quit: Leaving]
GenTooMan has quit [Ping timeout: 264 seconds]
GenTooMan has joined #beagle
M-blaise has quit [Ping timeout: 246 seconds]
M-blaise has joined #beagle
azarubkin has joined #beagle
<azarubkin>
Hi guys, do you use Docker or other containerisation technique on the Beaglebone Black?
<zmatt>
azarubkin: we use some containerized services
<azarubkin>
this is interesting, what are they?
<zmatt>
not whole-OS containers or anything, just the service and its dependencies packed into a squashfs image
<azarubkin>
I'm evaluating the use of Docker for my application
<azarubkin>
zmatt: so if possible, could you please tell me more about these services?
<zmatt>
just internal components of our application... we containerize just for easy of updating individual services without any worries about shared libraries and such
<zmatt>
*ease of
<zmatt>
and for security isolation
<azarubkin>
that's exactly the reasons I'm evaluating containers
<azarubkin>
so do you use Docker containers, or another tool, or a home-made thing?
<zmatt>
no tool, systemd natively supports containerizing services through appropriate properties in the service file
<zmatt>
tailored for the specific service obviously
<zmatt>
the mountpoint is for a squashfs image... I've previously tried using RootImage= to have systemd automatically mount the image instead but that didn't work back then, at least for squashfs images... maybe it works nowadays, haven't tested in a while
<zmatt>
it's very lightweight... no software used other than systemd, and the images are typically only a few MB each (except the ones that use nodejs, which are 26 MB :P )
<azarubkin>
mountpoint - do you mean "RootDirectory=/mnt/clerk" line?
<zmatt>
the mountpoint (/mnt/clerk in this case) is used as root directory for the service obviously
<zmatt>
the service image is mounted at that location using a systemd mount unit
djFloridaFresh has joined #beagle
<azarubkin>
I see. Is this solution the same as systemd-nspawn? Just for clarity :)
<zmatt>
no
<zmatt>
systemd-nspawn is generally used to spawn a full-OS container, I have no idea how you'd use it to spawn a containerized service
Wagner has joined #beagle
Guest81 has joined #beagle
Guest81 has quit [Client Quit]
<zmatt>
just to emphasize our container images are not OS images but contain just the bare minimum needed to run the service, e.g.: https://pastebin.com/raw/pAmJnw8V (along with some stuff that's bind-mounted from the host OS, as the service file shows)
otisolsen70 has quit [Quit: Leaving]
ikarso has quit [Quit: Connection closed for inactivity]
vagrantc has joined #beagle
azarubkin has quit [Quit: Client closed]
demirok has joined #beagle
M-blaise has quit [Read error: Connection reset by peer]
ikarso has joined #beagle
v0n has joined #beagle
set_ has joined #beagle
vagrantc has quit [Quit: leaving]
zjason` has joined #beagle
zjason has quit [Ping timeout: 240 seconds]
xet7 has quit [Ping timeout: 272 seconds]
xet7 has joined #beagle
GenTooMan has quit [Ping timeout: 264 seconds]
GenTooMan has joined #beagle
buzzmarshall has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]