Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker for Mac and Windows Beta

blog.docker.com

Post reply on HN
Print view View original

221–230 of 250 posts

Re: Docker for Mac and Windows Beta

#221

Post by colemickens »

hinkley wrote: post #170
ownagefool wrote: post #167

Earlier quoted context omitted.

They have build args for this in now. Thus, you'd do something like: docker build --build-arg OAUTH_TOKEN=blah -t example .

From the horse: The build-time environment variables were not designed to handle secrets. By lack of other options, people are planning to use them for this. To prevent giving the impression that they are suitable for secrets, it's been decided to deliberately not encrypt those variables in the process.

How would they "encrypt" them that wouldn't be trivial to undo?

I think people aren't concerned about it because it doesn't make sense to try to put secrets into container images. Whatever you're using to deploy your Docker containers should make those secrets available to the appropriate instances at runtime. This is how Kubernetes handles secrets and provides them.

http://kubernetes.io/docs/user-guide/secrets/

(For example, what if you have two instances of a service and they need to have different SSL certs? Are you going to maintain two different containers that have different certs? Or would you have a generic container and mount the appropriate SSL cert as a volume at runtime?)

Re: Docker for Mac and Windows Beta

#222

Post by colemickens »

hinkley wrote: post #218
morgante wrote: post #206

Earlier quoted context omitted.

I don't see how that's a compelling argument at all. All that's keeping you from committing your credentials is a .gitignore file. They have the file, it works reliably, don't worry about it.

You should know there was a pretty big bug fixed in .dockerignore in just the last release. [edit] That bug was in the logic for white-listing files, which is generally the safest way to keep from accidentally publishing things (that is, if it works). And it's possible a similar issue still exists in docker-compose but it's still open. .gitignore keeps me from checking my files into git, but it doesn't keep me from p…

Can you link to this bug? I thought .dockerignore specifically didn't allow whitelisting and only allowed for blacklisting files that weren't to be included.

Are you saying that docker would include files that should have been excluded by .dockerignore? I'd be interested to learn more. Thanks in advance.

Re: Docker for Mac and Windows Beta

#223

Post by nevir »

justincormack wrote: post #95
nevir wrote: post #63

Earlier quoted context omitted.

One thing I'm immediately concerned about is having some way of "pausing" xhyve. Purely because of Android development :( Intel's HAXM doesn't (seem to?) play nice, and asks for an exclusive lock. See https://github.com/mist64/xhyve/issues/88 and https://code.google.com/p/android/issues/detail?id=197915

You can quit and restart (its very quick). There isn't a pause at present though.

That's probably good enough

Re: Docker for Mac and Windows Beta

#224

Post by cwyers »

overgryphon wrote: post #168
djsumdog wrote: post #133

Earlier quoted context omitted.

Docker uses LXC containers. In Linux, these aren't VMs and are light weight user-land separations that use things like cgroups and lots of really special kernel modules for security. Unfortunately, this means Docker only runs on Linux .. not even Linux...special Docker Kernel Linux (all the features they need are in the stock Kernel tree, but it's still a lot of modules). In Windows/Mac, you still need to run in a vi…

The two most recent technical previews for Windows Server support containers natively. You don't need a VM to run containers on Windows.

It supports Windows containers. You still need a Linux VM to run Linux containers.

Re: Docker for Mac and Windows Beta

#225

Post by hyperhopper »

JustSomeNobody wrote: post #16
reustle wrote: post #9

Earlier quoted context omitted.

They said simplest :)

If you purchase a laptop knowing that you will be running Linux and doing a little bit of research up front, it is every bit as simple as running a laptop with Windows or OS X.

Until you start to deal with things like graphics cards, and switching between integrated and gaming graphics cards for different tasks.

Or when you want a distro like arch on a laptop...

Re: Docker for Mac and Windows Beta

#226

Post by was_boring »

philip1209 wrote: post #155

Does anybody have any guides on setting up dev environments for code within Docker? I recall a Dockercon talk last year from Lyft about spinning up microservices locally using Docker. We're using Vagrant for development environments, and as the number of microservices grows - the feasibility of running the production stack locally decreases. I'd be interested in learning how to spin up five to ten docker services loc…

I use docker, specifically docker-compose to do just that. So far it's 7 containers spread across 5 code bases all brought up with one command, `docker-compose up`.

The django quickstart guide is a good starting point for wrapping your head around it, https://docs.docker.com/compose/django/

Re: Docker for Mac and Windows Beta

#228

Post by dancompton »

avsm wrote: post #18
tzaman wrote: post #3

If I had a yearly quota on HN for upvotes, I'd use all of them on this. > Volume mounting for your code and data: volume data access works correctly, including file change notifications (on Mac inotify now works seamlessly inside containers for volume mounted directories). This enables edit/test cycles for “in container” development. This (filesystem notifications) was one of the major drawbacks for using Docker on M…

We'd love to get your feedback on the new filesystem engine in the Docker for Mac app. It's been a ton of work to get right, and there a few corner cases in the current beta that we're squashing, but overall things "just work" for my day-to-day Linux development on my Mac using the current beta. At this stage, pointing it to the weirdest and most wonderful filesystem stressers you can find is welcome. We'll leap on a…

I really appreciate you guys working on that. I have since moved to a debian VM, but might eventually move back if I don't need to frequently restart docker machine hosts.

Re: Docker for Mac and Windows Beta

#229

Post by newman314 »

This is strange. I just created a Docker ID and as able to log into the regular hub but when I try to log into the beta, it keeps saying error.

Is there a user/password length limit? (I used a 30char user/password. 1password FTW).

Re: Docker for Mac and Windows Beta

#230

Post by Estragon »

colemickens wrote: post #222
hinkley wrote: post #218

Earlier quoted context omitted.

You should know there was a pretty big bug fixed in .dockerignore in just the last release. [edit] That bug was in the logic for white-listing files, which is generally the safest way to keep from accidentally publishing things (that is, if it works). And it's possible a similar issue still exists in docker-compose but it's still open. .gitignore keeps me from checking my files into git, but it doesn't keep me from p…

Can you link to this bug? I thought .dockerignore specifically didn't allow whitelisting and only allowed for blacklisting files that weren't to be included. Are you saying that docker would include files that should have been excluded by .dockerignore? I'd be interested to learn more. Thanks in advance.

You could probably whitelist with a .dockerignore like

    *           # exclude everything
    !README.md  # include the README.
    !run.sh     # include the initiation script
You would want to check exactly what the globbing rules are for the .dockerignore file, though. I don't know whether '*' will catch .dotfiles, for instance.

  https://docs.docker.com/engine/reference/builder/#dockerignore-file
  https://golang.org/pkg/path/filepath/#Match
Post reply on HN