Virtual appliances?
-
@stacksofplates What the what?
- Install Fedora
sudo dnf install -y kubernetes- `systemctl enable --now podman1
That's all it takes.
-
@stacksofplates said in Virtual appliances?:
What do you mean about third party applications? That's pretty much what most people use it for unless you're an enterprise and writing micro services.
Meaning an application that's coming from an outside vendor rather than an internal team. When I see Docker being used by developers who are accountable (because they are internal) to the operations team, it seems to get used when. But too often what I see is developers just using Docker to presumably skip the due diligence in making things deployable and the result is a mess that "works for them" but no one else can figure out how to get to work as no one knows what their dependencies were that made it work.
Docker makes it easy to feel like you don't have to do anything and can just throw the product "over the wall" and not have to deal with it. And when devs aren't accountable to anyone, there's nothing to stop them from doing that.
-
@stacksofplates said in Virtual appliances?:
@JaredBusch said in Virtual appliances?:
@stacksofplates said in Virtual appliances?:
@JaredBusch said in Virtual appliances?:
@stacksofplates said in Virtual appliances?:
This day and age Id just prefer a container. They're so much easier to deploy and manage.
Only when done right, which is still not often, IMO.
Btw not trying to argue with you. People def do it wrong. I'm just saying I've seen them do it wrong with VMs too.
Oh I completely understand. Docker is super abused though.
What do you mean by abused?
I think he means it's used as I'm describing... as an excuse for devs to not test or know how things work and package something that works in their test environment but isn't documented, tested, etc.
-
@travisdh1 said in Virtual appliances?:
@stacksofplates What the what?
- Install Fedora
sudo dnf install -y kubernetes- `systemctl enable --now podman1
That's all it takes.
Yeah I see you haven't actually done that.
- Podman is not Kubernetes. Also when you install Kubernetes you don't get a podman1 service (or any type of podman service).
- When you install Kubernetes that way you don't get a Kubernetes service. You seemingly have to start the kube-proxy, kube-scheduler, kube-controller-manager, kube-api-server, and the kubelet separately.
- It installs docker, which is deprecated in k8s now. They have switched to using containerd which is pretty much the standard runtime now.
So I'll stick with my original recommendation.
-
@scottalanmiller said in Virtual appliances?:
@stacksofplates said in Virtual appliances?:
What do you mean about third party applications? That's pretty much what most people use it for unless you're an enterprise and writing micro services.
Meaning an application that's coming from an outside vendor rather than an internal team. When I see Docker being used by developers who are accountable (because they are internal) to the operations team, it seems to get used when. But too often what I see is developers just using Docker to presumably skip the due diligence in making things deployable and the result is a mess that "works for them" but no one else can figure out how to get to work as no one knows what their dependencies were that made it work.
Docker makes it easy to feel like you don't have to do anything and can just throw the product "over the wall" and not have to deal with it. And when devs aren't accountable to anyone, there's nothing to stop them from doing that.
I'd have to see an example of what you mean about "works for them but no one else can figure it out". Everything is defined in the Dockerfile. Its not hidden from anyone. So you can clearly see the dependencies.
Coming from a large enterprise that still wrote some legacy apps that weren't containerized, the throwing over the wall happened way more often on the not containerized side. I'd have to see an example of how that would work in the container space to understand what you mean here.
-
Side note just found out a former coworker just wrote a book on containers. https://www.amazon.com/dp/183921340X/ref=cm_sw_r_cp_apa_fabc_4Wn1FbVQZAEEV
-
@stacksofplates said in Virtual appliances?:
@travisdh1 said in Virtual appliances?:
@stacksofplates What the what?
- Install Fedora
sudo dnf install -y kubernetes- `systemctl enable --now podman1
That's all it takes.
Yeah I see you haven't actually done that.
- Podman is not Kubernetes. Also when you install Kubernetes you don't get a podman1 service (or any type of podman service).
- When you install Kubernetes that way you don't get a Kubernetes service. You seemingly have to start the kube-proxy, kube-scheduler, kube-controller-manager, kube-api-server, and the kubelet separately.
- It installs docker, which is deprecated in k8s now. They have switched to using containerd which is pretty much the standard runtime now.
So I'll stick with my original recommendation.
Yep, this is why I need to mess with this stuff in my home lab. I can't even talk about it intelligently yet!
