Totally agree, the post was written almost a year ago across 3 days while preparing a talk (see intro) and while still learning about Docker. Thanks for the feedback :)
if you want a more technical review of the Windows beta, read this: http://docker-saigon.github.io/post/Docker-Beta/
But note that beta 8 was released a few days after that review and already introduced some changes.
if you want a more technical review of the Windows beta, read this: http://docker-saigon.github.io/post/Docker-Beta/
But note that beta 8 was released a few days after that review and already introduced some changes.
Also, for the Windows beta, it very much is still a beta.
true in the way that "you should watch out for these issues when you deploy Docker to production"?
the creator himself and everyone agree that containers are a way forward, but you can't just jump on them and expect magic to happen.
I think the main reason for a lack of comments is the usage of a controversial historical figure... (at least, that's why it can't be pushed through official channels)
it seems the original video submission was removed from HN, I was looking forward to an in-depth discussion of the issues raised as I think it is both funny and brilliant. I hoped to achieve a discussion through this blog post :)
for the HTML parsing - I was able to pass all the test cases using a stack (push the tags when they open and pop them as they close). I was doing zero validation as the challenge was to take valid html. (I didn't verify that the proper tag was being closed, I knew I'd get out of bound errors due to this, but it should work for valid html)
I was using a string builder to eat the input as I had parsed it... but I got an error on submitting my result - it gave "unexpected termination" even when I had replicated the "unexpected termination" error with a custom test case and caught the error - I still got an unexpected termination error when submitting - sigh - maybe it's related to using C# for the challenge... overall not so hard though...
I've been running Docker on Hyper-V since the start (VBox never worked for me as I had a requirement on Hyper-V) - can you provide a little more info on how unikernel experience was used to make a difference? Is this a custom compiled linux kernel with Alpine distro on top?
How would volume mounts compare to something like using the netshare (cifs) with a samba share from the windows host? (which is what I'm currently using)?
agreed, I used a bash script based on glowmachine github repo[1], but switching to docker-compose made everything much easier - as long as you have the knowledge of the docker cli.