I know that architecturally it is. And that's what I

Question

I know that architecturally it is. And that's what I

thought exactly. But how are the use cases different? It seems to me like you can use both for essentially the same things. I can't think of a use case where one would be the undebatable way to go.
Docker is more portable than LXC containers, while LXC is architectually closer to VMs. I guess that maybe PCIe pass through is something you'd need to do with LXC?

0

09.08.2021

8 ответов

16 просмотров

Tobias🐾🚲

Raptor Blue Bear
It all really depends on what you're running. Cont...

That has been alleviated with podman - explicit support for systemd and even cgroup/resource management inside the container itself.

0

09.08.2021

Raptor Blue Bear

Tobias🐾🚲
That has been alleviated with podman - explicit su...

alleviated is such a strong term. It's just muddied the waters even more.

0

09.08.2021

niklas Автор вопроса

Tobias🐾🚲
That has been alleviated with podman - explicit su...

I just read a little about podman, and holy fuck it does sound great

0

09.08.2021

Tobias🐾🚲

niklas
I just read a little about podman, and holy fuck i...

Replaces docker entirely (now with optional docker socket support, dont pass that tho) full user namespaces explicit systemd as init binary support

0

09.08.2021

niklas Автор вопроса

Tobias🐾🚲
Replaces docker entirely (now with optional docker...

can It pull docker images from dockerhub?

0

09.08.2021

Tobias🐾🚲

niklas
can It pull docker images from dockerhub?

yes

0

09.08.2021

niklas Автор вопроса

Tobias🐾🚲
yes

I'm sold

0

09.08.2021

Raptor Blue Bear · Accepted Answer

Raptor Blue Bear

It all really depends on what you're running. Containers are very much geared towards "One application/service per container"; With LxC the approach is more along the lines of "Everything I need for this service consisting of multiple applications or services"

0

09.08.2021

Похожие чаты

I know that architecturally it is. And that's what I

8 ответов

Похожие вопросы