Docker taps unikernel brains to emit OS X, Windows public betas

Docker will kick off its DockerCon 2016 conference in Seattle this morning with a bunch of announcements: its OS X and Windows Docker clients will be made publicly available as beta software for anyone to try out; out-of-the-box orchestration is coming to Docker 1.12; and integration with Amazon's AWS and Microsoft's Azure is in …

[Stephen W Harris]

Every time you call "docker run" you're firing up a new container instance, so the /proc/cpuinfo and free commands were run in different instances.

And all those "docker run" commands are gonna leave traces behind ("docker ps -a"). It's better to use "docker run --rm" to clean up after your instance shuts down if you don't need to inspect the results ("docker log", "docker diff", etc).

[diodesign]

Thanks for the top tip!

[Wensleydale Cheese]

Not so fast

"Yeah, we know it's called macOS these days, not OS X."

Early days yet. I'm planning on using "macOS" to refer to the new version, not the current one.

[John Sanders]

Wondering how long...

Will it take for MS to start messing up things.

This "container thing" is technically "let's bypass Windows".

If you write a Linux application and it can run anywhere regardless of the OS, why do you want to pay MS?

Just thinking.

[Alan Bourke]

Re: Wondering how long...

Why indeed. Unfortunately nobody wants to. What *would* be extremely useful is running Windows software on Linux.

[richardcox13]

Re: Wondering how long...

> What *would* be extremely useful is running Windows software on Linux.

That is coming: http://www.hanselman.com/blog/DevelopersCanRunBashShellAndUsermodeUbuntuLinuxBinariesOnWindows10.aspx

[kryptylomese]

Re: Wondering how long...

Greater than 60% of Azure is Linux and that is growing.....

Linux using WINE already can run lots of Windows software too (and the compatibility might improve faster now that Microsoft has released their own BSD).

The thing is that commercially, it is better to Linux run code on Linux than it is to run Microsoft code on Microsoft or on Linux.

[420Penguin]

Windows client?

No details of the Windows client in the article. Is there something that makes OS X simpler to set up a docker client on than Windows, or is that what Windows Subsystem for Linux is for?

[Ed Courtenay]

Re: Windows client?

The experience with Docker for Windows is almost exactly the same, and unlike the previous Docker Toolbox versions uses Hyper-V for virtualisation (Docker Toolbox relied on VirtualBox instead).

Windows Subsystem for Linux is a completely different kettle of fish.

[Black Road Dude]

Linux on Windows?

As far as I was aware the windows version of docker can only run windows containers?

Is this still true or are we saying we can now run linux containers on windows?

EDIT::

Nope I was wrong.... ignore this....

https://docs.docker.com/docker-for-windows/

it means now windows is as useful as linux but isnt free or open source ...... oh well

[kryptylomese]

Re: Linux on Windows?

Actually, it is not as useful because Linux on Windows is feature incomplete. Simply put Windows cannot do what Linux can do due to the way that Linux is designed. Windows is more limited in functionality.

O.K. what about an example? Have a look on "iftop" on Linux - you cannot do that on Windows, even when it is running the Ubuntu layer.

Windows is not that useful as an operating system. Sure, you can by applications that have some functionality but businesses realised a while ago that Windows just cannot cut the mustard.

[Anonymous Coward]

Single address space? Wtf?

"all-in-one software stacks that roll kernels and microservices into single address spaces"

I think thats called DOS. Why would I want to go back to the 90s even if running on a hypervisor? There's a good reason for using seperate address spaces for kernel and processes you mongs.