License? I see none listed in the repo.
Still VMware. “Not Supported” in this context just means it’s not continually tested.
Okay, let’s talk about that. That was worst moment of my career. It still leaves a sour taste in my mouth just talking about it. I loved working with those folks. No one in VMware was happy about that decision, (the…
Startup and build performance of containers are both expected to be slower than docker, but it varies by how much. Mostly a byproduct of limitations with 9pfs and multi-threading, and we're working on it. Once running…
That wasn't the intended use case, but it might be possible. I haven't tried personally, but if someone attempts something like that and they run into a blocker I can certainly take a look.
Using the -p flag tells the vmnet to create a NAT rule, and yes only the Pro license can do that, but you can still fire up the container on the local vmnet. So the way vctl works is that it launches a new VM for each…
License? I see none listed in the repo.
Still VMware. “Not Supported” in this context just means it’s not continually tested.
Okay, let’s talk about that. That was worst moment of my career. It still leaves a sour taste in my mouth just talking about it. I loved working with those folks. No one in VMware was happy about that decision, (the…
Startup and build performance of containers are both expected to be slower than docker, but it varies by how much. Mostly a byproduct of limitations with 9pfs and multi-threading, and we're working on it. Once running…
That wasn't the intended use case, but it might be possible. I haven't tried personally, but if someone attempts something like that and they run into a blocker I can certainly take a look.
Using the -p flag tells the vmnet to create a NAT rule, and yes only the Pro license can do that, but you can still fire up the container on the local vmnet. So the way vctl works is that it launches a new VM for each…