31–40 of 65 posts
Edit: On topic, just test k8s config changes in prod :^)
Just in time for the end of jan Docker Desktop grace period ( https://www.docker.com/blog/the-grace-period-for-the-docker-... ). I played with this when first announced, and then now and all the things I wanted when i first tried it out are now fixed (mainly transparent networking..) and the option for dockerd container engine makes migrating pretty simple.
This is something I find exciting! I was looking at our infrastructure and between all the various services, we basically have recreated k8s only more expensive and fragmented and tied explicitly to AWS. On top of that, our local test env is based on docker-compose so it often has issues matching exactly to the deployed env in the cloud once you add all the networking. I've wanted to start moving us to Kubernetes so…
I blogged about using Linux containers on macOS, including research into the operation and features of solutions like minikube, lima/nerdctl, Rancher Desktop, and Docker Desktop. You may find it helpful. https://cameronnemo.gitlab.io/posts/mac-os-containers/
Earlier quoted context omitted.
There is Podman Compose which will what you want. I particularly like Podman, because you can use it for Minikube, independently, rootless, etc.
FWIW podman does not work as a driver for minikube on Apple Silicon. Really hoping it gets sorted out because that’s probably what I would use.
These desktop applications look nice, but personally I’m much more comfortable with CLI tools. I have no idea what my colleagues are doing that use GUI git programs. I can’t even stand editor integration plugins. Edit: On topic, just test k8s config changes in prod :^)
These desktop applications look nice, but personally I’m much more comfortable with CLI tools. I have no idea what my colleagues are doing that use GUI git programs. I can’t even stand editor integration plugins. Edit: On topic, just test k8s config changes in prod :^)
They installed their own halfbaked inhouse CloudNative Storage Provider, then quoted the client 50k to try to stabilize it. Their sales people were also nonstop trying to sell them on more consulting hours on top of the 50k they were taking in license fee for a 3 node cluster.
The whole thing left such a bad taste in my mouth that whenever I see Rancher I tell my clients to look for other options and run away as far as possible.
Now that Suse owns them I'm a bit more open to it, but I imagine there are still a lot of old rancher people in there.
Can anyone enlighten me on the current state of affairs?
Can it be used to run Docker Compose workloads? As I understand, the tool is launched because at the end of January the Docker Desktop grace period elapses and it becomes paid for large business.
On macOS
brew install docker-composeWhat's the state of Rancher these days? I was handing over a clients project and looking for someone to maintain it long term. I chose Rancher in my ignorance, but all Rancher did was tank the project. They installed their own halfbaked inhouse CloudNative Storage Provider, then quoted the client 50k to try to stabilize it. Their sales people were also nonstop trying to sell them on more consulting hours on top of th…
What's the state of Rancher these days? I was handing over a clients project and looking for someone to maintain it long term. I chose Rancher in my ignorance, but all Rancher did was tank the project. They installed their own halfbaked inhouse CloudNative Storage Provider, then quoted the client 50k to try to stabilize it. Their sales people were also nonstop trying to sell them on more consulting hours on top of th…