3 ms·

I hope this one works better than kitematic! I'm really excited by the implications of docker, but the practicality of using it on windows has proved to be trou

by alexc05 11y ago

I hope this one works better than kitematic! I'm really excited by the implications of docker, but the practicality of using it on windows has proved to be troublesome. It is very difficult to get docker containers running locally (at least using the gui tools) I know that MS believes in it wholesale so am really looking forward to the day when the tools catch up to their promises. So far I've been bashing my head against the wall whenever I've gotten past "tutorial phase 1" Getting a webhost, database, memcached, rabbitmq, load balancer etc... All talking to each other on a local 'dev' system... theoretically a perfect mirror of the thing that will be the super scalable production system. Difficult. I'm undoubtedly doing stuff wrong, but if there are any docker wizards out there, please point me to your blogs! I'm dying to finally wrap my head around the promises of scalable containerization. EDIT: I just watched their youtube video. This interface is honestly amazing. To be able to arrange virtual machines in 3d space. What a phenomenal tool. This will really help me learn how to use docker effectively.

smegel 11y ago
Kubernetes. Specifically, running kubelet locally is a great way to bring up a "pod" of just the containers you want, configured the way you want. It's actually pretty conveniant, and as dev I have started preferring it as a way of quickly bringing up new things to test on my dev machine. And Kubernetes was designed to scale...you should be able to take your local config file and make it part of the broader client/server based Kubernetes setup...and it will bring your containers up across a cluster of servers.
- alexc05 11y ago
  Thanks for the lead! I'll look this up today.
politician 11y ago
> It is very difficult to get docker containers running locally. Don't try to wade upstream, docker is a Solaris/Linux technology. Just go with the flow. Soon enough, we'll have C#/.NET running on Linux in containers with the CoreCLR project. And also, SSH works!
- alexc05 11y ago
  I've actually had "small projects" running .net in docker locally. Compiles and runs fine, kick off the kestrel web server and you're great. That is however, specifically, the boiler plate stuff. As soon as I started trying to build a multi project solution with various nuget dependencies, things started to fall apart at compile time. What was interesting to me was the fact that it was nuget transfers that started timing out and failing in the docker build. I can't actually explain what was happening ... and as a weekend d project it was just non critical to make it work in docker. (As opposed to just make it work "full stop".) When I have more time and confidence, as well as after the tools have matured a little more, I'm definitely going to take another pass at it.

by alexc05 11y ago

smegel 11y ago

Kubernetes. Specifically, running kubelet locally is a great way to bring up a "pod" of just the containers you want, configured the way you want. It's actually pretty conveniant, and as dev I have started preferring it as a way of quickly bringing up new things to test on my dev machine. And Kubernetes was designed to scale...you should be able to take your local config file and make it part of the broader client/server based Kubernetes setup...and it will bring your containers up across a cluster of servers.

alexc05 11y ago
Thanks for the lead! I'll look this up today.

politician 11y ago

> It is very difficult to get docker containers running locally. Don't try to wade upstream, docker is a Solaris/Linux technology. Just go with the flow. Soon enough, we'll have C#/.NET running on Linux in containers with the CoreCLR project. And also, SSH works!

alexc05 11y ago
I've actually had "small projects" running .net in docker locally. Compiles and runs fine, kick off the kestrel web server and you're great. That is however, specifically, the boiler plate stuff. As soon as I started trying to build a multi project solution with various nuget dependencies, things started to fall apart at compile time. What was interesting to me was the fact that it was nuget transfers that started timing out and failing in the docker build. I can't actually explain what was happening ... and as a weekend d project it was just non critical to make it work in docker. (As opposed to just make it work "full stop".) When I have more time and confidence, as well as after the tools have matured a little more, I'm definitely going to take another pass at it.