So, I'm going to give the talk first to multi-shrader, here you go, you have five minutes.
Thank you.
I'm going to talk about a container platform and how you might want to use it for robotics.
Probably most of you know that the different was releases are targeted to specific you
do versions.
So, when I first started using us, I wanted to we move as much friction as possible.
So, I did a dual boot between my daily OS and the specific you want to version.
But at some point I wanted to interact with the robot that uses was to jazzy.
So, what do I do now?
I could do a triple boot and that's actually what I did.
But at that point it was kind of annoying to switch between the different OSs.
And during the same time we started a robotics club and but mobile robot that uses the NVIDIA Jets
and those support only you want to 22.
So, there's no option to install you want to 24.
So, but luckily there's Docker.
And the open source of robotics foundation maintains and makes available all the different
the different was versions.
So, that's great.
But for me at least it is kind of hard to get GUI programs to work in from inside the container.
And it is even harder to connect to devices to connect to network and whatever.
If you're not Docker expert.
So, when I want to learn was to I don't want to learn Docker as well.
And in general we might want to ask ourselves the question.
Do we use containers in robotics because we want to send boxes software as much as possible?
Or is it more about packaging and environment?
And if it's for the latter, a container might be a great alternative that simplifies the
containerization setup.
Because, first of all, what is a container?
A container is a container platform that is originally made for high performance computing.
But it is also compatible with images from Docker, other OCI registers.
It is demoneless, just like potman.
And as a fun fact, all the different containers are stored as one single fire.
So, you can easily move them around between PCs.
But the main selling point for obtainer for robotics is their philosophy.
That is integration of our isolation by default.
And what that means is that you are the same user inside the container as you are outside.
So, if you had access to a device and can't read and write from it, you can do the same from inside.
And in addition to that, in a container, there are a lot of default amounts.
So, with those GUI programs, just work and the connection to a serial device that is connected to a slash death or something,
also just work for the configuration.
So, in the end, we can simplify a Docker command like this to just this and a container.
And, yeah, doing the privilege fact, if you install Docker just as root is kind of dangerous.
So, we have to install Docker as non-wood.
So, this is like the main takeaway.
Uptainer is still compatible with OCI images.
And, the philosophy behind it integration of isolation by default is great for robotics,
because we might not want to use the sandboxing feature of containers in the first place.
Yeah, lastly, I want to give a small referral to Pixie, the new package manager that is out there.
And this right now, the preferred way to install was to on Windows.
And that might also be a great alternative to containerization in general to get a was to set up done.
And there, I think we will also be a talk later that touches Pixie with.
Yeah, so you might want to check that out as well.
Thanks, that was already it.
And I will do a small appainer, robotics guide.
If you want to check that out and get started with appainer.
Thanks.
Thank you.