friism

dyno types for build processes use Perf-M? Not configurable

What are you looking for here? Larger build dynos? Heroku provides the build service for free so we use perf-m dynos to get fast builds with reasonable cost (for us).

(I work at Heroku) Do you have more details on what sucks? Anything we're not already tracking to fix in our public roadmap? https://github.com/heroku/roadmap/issues

Works great so far. The iOS app was janky at first (it would forget about the hub it was connected to) but seems better now. I don't really use the app though - a recent update added Alexa support, and that works great. I've mounted the remote control on the wall and either use that or Alexa to turn the lights on and off.

I don't want purple or green lights in my living room, so the fact that IKEA bulbs are limited to warmth and brightness is fine for me (I like to just keep them on "warm").

I have IKEA Trådfri (which is ZigBee-based). While the hub does connect to the internet for software updates (using ethernet - no WiFi, and no WiFi password to update), there's no "cloud" component. You can't create an "IKEA account", even if you wanted. If IKEA went out of business tomorrow, my switches and bulbs would keep working. I like that approach a lot.

It would be perfectly feasible to leave the IKEA hardware in the house if we were to move.

Oh, and to answer your question: Yes, Swarm is core part of Docker and is in Docker Community Edition too!

Thanks, this is excellent feedback.

Docker is trying to alleviate this concern by spinning out and trying to foster alternative runtimes, check out containerd and runc:

* https://blog.docker.com/2016/12/introducing-containerd/ * https://runc.io/

Docker CE and EE are based on the Docker open source project and work the same way. You can also use a Docker CE client to talk to Docker EE host or swarm, and vice-versa.

The Docker Cloud team is working on improvements to reduce segmentation too - stay tuned.

We take backwards compatibility seriously. If you encounter problems updating from one version of Docker to the next (whether from 1.13.1 to 17.03 or from 17.03 to the upcoming 17.04), please open an issue on docker/docker so that can fix the incompatibility and improve our change process.

Quoting from the blog post:

    The Docker API version continues to be independent of the
    Docker platform version and the API version does not
    change from Docker 1.13.1 to Docker 17.03. Even with the
    faster release pace, Docker will continue to maintain 
    careful API backwards compatibility and deprecate APIs and 
    features only slowly and conservatively. And in Docker 
    1.13 introduced improved interoperability between clients 
    and servers using different API versions, including 
    dynamic feature negotiation.

Fixed now, thanks for reporting: https://store.docker.com/editions/community/docker-ce-server...

Also check out the full docs: https://docs.docker.com/engine/installation/linux/centos/

Here's a link to resources on how to start publishing content: https://success.docker.com/store

I'm sorry you don't like the new versioning.

Echoing @shykes below[1], Docker had premium paid products before this launch, but we're trying to make that clearer and to simplify the product lineup.

Note that Docker CE is _just_ as good as the Docker you were using yesterday. In addition, the version lifecycle improvements are designed to get new features into Docker users' hands faster (with monthly Edge releases) and to improve maintainability by overlapping the maintenance windows of free Docker CE quarterly releases.

[1] https://news.ycombinator.com/item?id=13774420

Both the main and the emergency spillway send water into the Feather river.

When the reservoir is at capacity, the dam operator has no control over how much water goes into the Feather River nor whether downstream towns are flooded or not. Any water not going down the main spillway will go down the emergency spillway and into the river.

(edit for typo)

Do you have the support ticket ID? I can follow up.

No, you can also run Docker Windows Server containers on Windows 10. This means that the Docker daemon is running natively on Windows (either Windows 10 anniversary edition or 2016). Details here:

* https://blog.docker.com/2016/09/build-your-first-docker-wind... * https://blog.docker.com/2016/09/dockerforws2016/

No, you can also run Docker Windows Server containers on Windows 10. The easiest way to do this is to install the public beta version of Docker for Windows:

* https://github.com/docker/labs/blob/master/windows/windows-c... * https://docs.docker.com/docker-for-windows/release-notes/#/b...

Beta26 of Docker for Windows (public, free) setups up both Linux and Windows Docker daemon on Windows 10: https://docs.docker.com/docker-for-windows/release-notes/#/b...

Details here:

* https://blog.docker.com/2016/09/build-your-first-docker-wind... * https://stefanscherer.github.io/run-linux-and-windows-contai...

Docker running on Windows comes with the same layering and CoW semantics as on Windows. If you're curious about the details, John Starks' session at DockerCon is really great: https://www.youtube.com/watch?v=85nCF5S8Qok

If you have details on the problems you've had, feel free to drop me a line at michael.friis@docker.com

RDP actually worked in early tech previews, and I think Microsoft is trying to use some of this for browser-process isolation in Microsoft Edge, so maybe some day :-)

Here's a blog post: https://blog.docker.com/2016/09/build-your-first-docker-wind...

Since all your containers will be based on `windowsservercore` (and perhaps some on the much smaller `nanoserver` base image), you could choose to bake the image into your container host image.

You can install the free Windows Server 2016 evaluation version in VirtualBox (which should run fine on Home). Download here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-...

There's not a lot yet, but you can take a look at the shim used by Docker Engine: https://github.com/Microsoft/hcsshim

The `docker pull` payload is 358MB: https://hub.docker.com/r/microsoft/nanoserver/tags/

Express works fine listening on TCP. While I haven't tried I don't see any reason it wouldn't work. And I've see the full SQL Server running in a Linux Docker container :-)

The public beta version (which has all the latest and greatest) has support for Windows containers too: https://stefanscherer.github.io/run-linux-and-windows-contai...

GUI apps (and remote desktop use cases) is not supported for Docker Windows containers, at least not yet.

Yes, it works great!

I built a sample with MusicStore. It doesn't use ISS (but could), just a self-hosting ASP.NET Core MVC app: https://github.com/friism/Musicstore/

You might find the SQL Server Dockerfile interesting (hopefully it'll be an image on Hub soon): https://github.com/friism/MusicStore/blob/master/docker/mssq...

Here's now to run it:

    docker build -t sqlserver:2016 -f .\docker\mssql-server-2016-express\Dockerfile .\docker\mssql-server-2016-express\.
    docker-compose -f .\src\MusicStore\docker-compose.yml up

IIS runs in both nanoserver and windowsservercore-based containers. Here's and IIS sample image (I suspect Microsoft will be updating it soon): https://hub.docker.com/r/microsoft/iis/

Post author here: people at Docker and Microsoft have worked on this for years. More to come during the day, also happy to answer any questions here.