4 ms·
That's what throwaway accounts are for... and this, of course: http://bugmenot.com/view/store.docker.com http://bugmenot.com/view/store.docker.com In any case
by userbinator 8y ago
That's what throwaway accounts are for... and this, of course:
http://bugmenot.com/view/store.docker.com http://bugmenot.com/view/store.docker.com
In any case, "to make sure we can improve the Docker for Mac and Windows experience for users moving forward" is yet another example of the official-sounding-yet-bullshit, vague and meandering language that seems to permeate into everything these days. (Is there a specific term for it? "Business-speak" doesn't have enough of a negative connotation for the "We did it this way and you will like it. If you don't, fuck off." that they really want to say.)
- sfoblows2017 8y agoIf you are too much of a douche to give a thowaway account for docker service, then they dont want you anyway. Your kind are not savvy, your kind are just douches that would shit on their own gma for a dollar.
- yalue 8y agoProbably the slightly better term here would be "weasel words". (Or better yet, "bullshit")
- jchw 8y agoFWIW, as far as I know, Docker for Windows and Docker for Mac really are closed source freeware. My honest opinion is we should move away from it. As for what to move to... That's definitely an open question. Docker for Windows is definitely one of the best developer experiences I've had on Windows because they put actual engineering work into it. All the same, I still found it buggier and less supported than Docker for Mac. At least on Windows, I wish we could combine the cool LXSS work with a development-only Docker implementation. Ultimately, Docker should not be synonymous with containers anyway. Future versions of Kubernetes will not use Docker and instead run their own containers on top of libcontainer by default, as I understand it. I also feel rkt has a much nicer design than Docker, doing away with the daemon aspect of it. Hoping to see more development in the future.
- gshulegaard 8y agoIf you want lightweight virtual machine functionality I would recommend LXD/LXC. If you want app virtualization and packaging, I have been pretty intrigued by what I have found out experimenting with `snaps`. The biggest issue for me that I have hit with LXD/LXC is that host-to-container mount sharing is not as easy...which means I had to do some workflow alteration for moving from `docker` containers to `lxd` ones for existing projects...but otherwise I have been really happy with LXD. Edit: And just to be clear, host-to-container mount sharing is possible, I just had to work at it and slightly alter my workflow to get the best solution.
- jchw 8y agoWell, what I really want is to develop, test and utilize containers as part of my development process. For example, doing work in Docker containers allows reproducible, hermetic builds (importantly, it allows this, though it certainly doesn't guarantee or force it.) Many containers that I develop or use will also be used in a Kubernetes cluster or at least as part of CD, so most importantly I want a local setup that mirrors to a degree what the remote setups look like. Snaps provide something a bit different, more geared toward end users. I have no huge opinion regarding them, the isolation aspect is novel but unfortunately a bit of a PITA as of today.
- gshulegaard 8y agoSounds like you would be more interested in LXD then.
- jchw 8y agoLXD is more like virtual machines than containers, though. Also, in context of this thread, it doesn't solve much that Docker doesn't; after all, Docker for Linux is in fact fully open source, and even if it wasn't, Linux has no shortage of mature container implementations (like rkt.) For a developer on Mac or Windows, it'd be nice to have a universal dev tool, even if only to handle Linux containers.
- ur-whale 8y ago> http://bugmenot.com/ http://bugmenot.com/ Oooh, thanks for this, hugely useful.