I just finished an amazing call.

[regendans@todon.eu]

@stefano Excellent👌

(And I am wondering now whether I would be tempted to say "I don't support DockerOS, bye" in such a case 😇)

[synlogic4242@social.vivaldi.net]

@mvilain @stefano TBF I think one common point of confusion comes from folks who get like Docker Desktop and run it like an app on Mac. by default on Mac if you "run" a Docker image the container runs under a Linux instance running on a VM. For total newbs its hard to make distinction between processes, containers, OS, hypervisors, VMs etc. blurs together. on Windows the UX might be similar. on Linux the Docker impl is much thinner because it doesnt need to add a full VM on top of the host.

Now add the complicating factor that many Linux instances reachable on the Internet may themselves be running on VMs rather than bare metal, etc

turtles all the way down

lots of newbs think Docker is an OS+VM when in reality its much thinner than that. its the Desktop/non-Linux versions

[frang@meow.social]

@mvilain @stefano "Do you _actually_ understand _anything_, or can we both go home now?"

[furicle@mastodon.social]

@stefano docker os, or DOS for short.
Invented by Steve Jobs right?

[strog@social.strog.org]

Theseus's Operating System:

If I swap out docker for nerdctl, ctr, etc. and later swap out containerd for CRI-O, youki, etc. then is it still Docker OS? 🙂

Funny how the container and host unames match. 😉

[yendolosch@23.social]

@stefano

> I told the guy that I couldn’t help him, since I'm not experienced enough with operating systems.

The only winning move is not to play.

[webhat@infosec.exchange]

@mvilain @stefano I was asked an interview question at an interview. Interviewer kept telling me I was explaining it wrong, and told me how it worked. I didn't get the job, obviously

I was a little confused, so when I got home, looked it up to make sure. And one would explain it in the way I explain it if one understands memory management, if one's never had to deal with memory management issues they explain it the way the interviewer explained it

The same when I was explaining how the threading model worked in a higher level programming language, at a different interview. They were convinced that it worked in the way the marketing materials said. Obviously the interviewer had never had to debug and step through the thread manager with a debugger. Didn't get that job either

[paul_ipv6@infosec.exchange]

@mvilain @stefano

docker has a better logo? <ducks rapidly>

yeah... the world doesn't need to be able to write low level device drivers in assembly but you should at least have a conceptual understanding of the stuff you use if that's your job.

[lispi314@udongein.xyz]

@stefano Said person sure bought the party line without scrutinizing it at all.

Even the Docker documentation makes no secret about how it works.

[feralhousewife@mastodon.social]

@stefano wow. I've been out of the business for over ten years and even I know that Docker has to run *on* something. Hilarious.

[vaneshi@bitbang.social]

@stefano The good ol' "not for all the tea in china" side step.

[tforcworc@todon.nl]

@stefano this is a synptom of a much larger problem - i had an argument with some people recently who want to use "AI for 6G". I asked "so what's your platform to run the AI on? like do you have server racks in cell towers and run the AI on unikernels, or re-implement the AI on top of Cloud RAN and tolerate the latency, or do you have a non-GenAI tech in mind for your smart cellular service?". you could hear the tumbleweed rolling through their empty heads...stack free

[raymaccarthy@mastodon.ie]

@bsdtv @stefano
SSD Supersonic Spinning Disc 😆

It's amazing how they fit motors to spin it and move the head on platters into a tiny 1.5mm x 12 mm package (approx). A miracle of nanotechnology!

In a way the reality is much stranger.

I remember when some people thought the CRT was the computer and the cased PC was the "hard disk". Some thought a 3.5" floppy was a hard disk (if they had first encountered cassettes and 5.25" floppies.
.

[maysonic@twit.social]

@paul_ipv6 @mvilain @stefano As one who has written device-driving code in assembly languages, I don’t really know how Docker works, but if you’ll pay me, I’d be quite willing to research it and explain it to you at whatever level of detail you’d like…

[paul_ipv6@infosec.exchange]

@maysonic @mvilain @stefano

i have every confidence that if using docker became part of your job, you'd spend the time to learn what was going on under the hood. :)

[nickbergencomputerquest@mastodon.social]

@Yendolosch @stefano Maybe Stefano could still offer him a nice game of chess

[maysonic@twit.social]

@paul_ipv6 @mvilain @stefano Given that the main computer-related income I’ve received since #y2K has been a shareware check for a Mac INIT I wrote in the 80’s, and a few free lunches from a friend whose Windows machine I removed a few viruses from, the likelihood of my employment requiring using Docker is fairly slim. It is possible that I may want to learn it anyway, if some side project (not that these days I really have any non-side projects) seems to need it.

[rasur@mastodon.social]

Oof, cubed 🥴

[release_candidate@mastodon.bsd.cafe]

@mvilain @stefano I ask sometimes what exactly is a container. If the candidate never mentions cgroups or namespaces, then I conclude that she/he doesn't really know.

Most of the times I just get answers like methaphores of sandboxing and how it's 'not a vm, but like a vm'.

[angel@triptico.com]

The voice of stupidity is always self-confident and loud.