- Nov 18, 2005
- 28,799
- 359
- 126
I've been sinking a ton of time into ESXi and vCenter getting everything spun up (new homelab, finally got one started), but of course I want to do it all.
I was getting really excited to start playing around with Docker in my homelab, but after I got VMware Photon OS, vSphere Integrated Containers, and a VCH installed, and then proceeded to have a few hangups? I had to step back and pause a moment.
Did some more research, and started thinking, maybe what I want to do shouldn't be done in Docker just yet, I think I may have actual use for maybe one or two real containers. What I wanted is a light CentOS instance to run Caddy server, as well as HomeAssistant. Now I know HomeAssistant comes in a Docker variant, as does CentOS for that matter, but it is at least a basically standard Docker container I think, it's really just software that runs on top of Python.
But the question I really have: sure CentOS has a full containerized OS, but is that really a good practice for containers? Are containers persistent? It sounds like they weren't really designed to be but that some persistent data may be possible now? Where I'm really confused would be the idea of the docker file, is it designed to create what are essentially temp configs until the system gets shutdown, then recreates on next boot? Can you actually effectively run a persistent OS within a container if all that is the case?
Obviously I don't NEED Docker, lol no, but I can imagine I'd find other things to put on there. That is exactly what has happened with vSphere - I only had a few main things I planned to use, but of course I'm installing far more because now I have a dedicated platform to play around with. And I want it all. hahaha
I was getting really excited to start playing around with Docker in my homelab, but after I got VMware Photon OS, vSphere Integrated Containers, and a VCH installed, and then proceeded to have a few hangups? I had to step back and pause a moment.
Did some more research, and started thinking, maybe what I want to do shouldn't be done in Docker just yet, I think I may have actual use for maybe one or two real containers. What I wanted is a light CentOS instance to run Caddy server, as well as HomeAssistant. Now I know HomeAssistant comes in a Docker variant, as does CentOS for that matter, but it is at least a basically standard Docker container I think, it's really just software that runs on top of Python.
But the question I really have: sure CentOS has a full containerized OS, but is that really a good practice for containers? Are containers persistent? It sounds like they weren't really designed to be but that some persistent data may be possible now? Where I'm really confused would be the idea of the docker file, is it designed to create what are essentially temp configs until the system gets shutdown, then recreates on next boot? Can you actually effectively run a persistent OS within a container if all that is the case?
Obviously I don't NEED Docker, lol no, but I can imagine I'd find other things to put on there. That is exactly what has happened with vSphere - I only had a few main things I planned to use, but of course I'm installing far more because now I have a dedicated platform to play around with. And I want it all. hahaha
Facebook
Twitter