198
Getting worn out with all these docker images and CLI hosted apps (reddthat.com)
submitted 9 months ago by to c/selfhosted@lemmy.world
127 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 9 months ago (3 children)

You can still use VMs and do containers in there. That's what I do, makes separating different services very easy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 9 months ago (2 children)

    This is what I currently do with non-specialized services that require Docker. I have one container, which runs Docker Engine, and I throw everything on there, and then if I have a specialized container that needs Docker, I will still run its own CT. But then I use Docker Agent, So I can use one administration panel.

    It's just annoying because I would rather just remove Docker from the situation because when you're running Proxmox, you're essentially running a virtualized system in a virtualized system because you have Proxmox, which is the bare bones running a virtualized environment for the container, which is then running a virtualized environment for the Docker container.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 9 months ago (1 child)

    running a virtualized environment for the container, which is then running a virtualized environment for the Docker container.

    Neither Linux containers nor Docker containers are virtualized.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 9 months ago*

    I think we might have a different definition of Virtualized and containers. I use IBM's and Comptias definitions.

    IBM's definition is

    Virtualization is a technology that enables the creation of virtual environments from a single physical machine, allowing for more efficient use of resources by distributing them across computing environments.

    The IBM page themselves acknowledges that containers are virtualization on their Containers vs Virtual Machines page. I call virtualization as an abstraction layer between the hardware and the system being run.

    Comptia's definition of containers would be valid as well. Which states that containers are a virtualization layer that operates at the OS level and isolates the OS from the file system. Whereas virtual machines are an abstraction layer between the hardware and the OS.

    I grew this terminology from my comptia networking+ book from 12 years ago though, which classifies Virtualization as "a process that adds a layer of abstraction between hardware and the system" which is a dated term since OS level virtualization such as Containers wasn't really a thing then.

  • permalink
  • fedilink
  • source
  • parent