The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Docker! More specifically, testing out the .NET Framework 4.7 image.
So first I had to enable Hyper-V. No problem, methinks. Riiight. After rebooting the computer, my multimonitor setup is totally trashed, thrashes, and 'ed. As are my Fences icons. And there's these extra monitors suddenly showing up.
Get that finally squared away, download the image (the instructions on the github repo are fubar'd) and launch VS2017.
Where is it? I get the VS2017 splash screen, then nothing. me, it looks like VS2017 & VS2015 are blown away. Uninstall both, reinstall both.
Same. ing. Behavior.
Just by chance, I hit Alt-Tab and I see Visual Studio is one of the running applications. Where the is it??? So I think, maybe it's on one of those weird extra monitors I saw. So I poke around, and there's this "disconnect monitor" option in the display settings. So I try that for one of the "ghost" monitors. OMFG. Suddenly VS appears.
Next, I discover the BS that is Microsoft's attempt at bringing .NET onto Docker. Oh sure, there's .NET Core (or is .NET Standard or is it .NET Creator or is it .NET Next Gen???) but no, I wanted to try the full blown .NET Framework 4.7, because that's what I write in, and I don't want any of this "Core" BS.
So there's this image. OK. Docker tells me it's downloading some 10 GIGA (yes, that's GIGA) bytes of data for the image.
When all is said and done, my poor little 256GB SSD only has 1.4GB free (it was pretty stuffed already) but it turns out the whole Docker/Windows/.NET thing sucks up 17GB of disk space uncompressed (then again, maybe those compressed files are still lying around somewhere???)
Well, at least the stupid demo Microsoft gives you compiled.
Oh, but I forgot to tell you, you need to switch to "Windows containers" in the Docker applet. Oh, and what I really forgot to tell you was the three install attempts for Docker for Windows because I had a previous "Docker Toolbox" installation (which I did uninstall before doing anything!!!) but that left various breadcrumbs - PATH entries (I might have added those), and a ".docker" folder in the Users\Marc folder. All of which caused Docker For Windows to be "No Docker For You". Two separate SO posts resolved those issues.
So, we finally get to compiling. Fine. Then we get to running.
And We wait (at this point, it's the royal WE)
And We Wait
And We Wait
And it ran! There's the output of the stupid "bot" in the console window.
So, it takes something like 15 seconds on my 8 core 16GB fast machine to spin up the container, undoubtedly because I'm running a near full instance of Windows.
So I decide to try a few other things, all of which work, and finally landing on "let's write a simple HttpListener" as a container. Great, 20 lines of code later and I have something that works in Windows. Let's see if it works in the container.
The last one, http://*:5001/ seemed to help. I haven't tried localhost again. Who knows. So I go to my browser, to "localhost:5001" and...
Hours later, I discover some interesting things. By now, after fussing with Dockerfile EXPORT and that http://*:5001, I discover that entering the container's local IP into my browser works. But that's container's local IP, which changes every time the container is fired up, for each container that is fired up, all hail Mary to the container that never rules anything.
Various posts say you can't access a container from the host. Some posts say you're not using a container correctly if you're doing this, you should use a VM instead (and indeed, I had a VM of this working with Python.) Some say other BS, but at the end of the day, they're all saying BS, but I still can't figure out the problem.
I make a post on the Docker forum. I refuse to give up. The oxygen tank is redlining, but I refuse to give up. And then I find it.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself."
Next, I discover the BS that is Microsoft's attempt at bringing .NET onto Docker
Fully accept I'm speaking form ignorance here, but why is it Microsoft's problem to bring .NET onto Docker? Docker is not a product I'm familiar with, but on the face of it, I'd have assumed it was Docker's problem to bring .NET onto it.
My experience using Docker Toolbox (which uses Oracle's Virtual Box instead of Hyper-V) is pretty good, and as long as you stay in the Linux world, it's actually pretty cool. But I really would like to get to a place where I can use C# in a Linux Docker container, so the next rabbit hole is .NET Core (or is it standard?) And then discovering how much of my core code base that I want to use doesn't work. Maybe there's a reason why Python is ranked so high.
The bricks: you also have to add in the CO2 the manufacturing adds to the atmosphere (even if indirectly from electric power). Seeing as more people are concerned with greenhouse gasses than animal welfare the weight of guilt is also higher on the bricks.
Do not switch off your computer.
Alternative answer: 200 kg of standard bricks is approx. 60-odd, so you could, assuming you’re strong enough, make pile say 4x4x15 high and carry them all at once.
I’d like to see anyone carry 200kg of feathers without them being in some sort of container (or maybe held together by some sort of adhesive) – no matter how light it is, that’d make the total weight you have to carry greater than the bricks!
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Last Visit: 22-May-19 11:19 Last Update: 22-May-19 11:19