shykes

56 ms·

601.
by shykes 12y ago
I agree that Docker is easier to deploy than Openstack :) However... It always astounds me how some people massively over-estimate the size and influence of Docker's marketing... Why yes, of course! The way we got Google, Microsoft,
602.
by shykes 12y ago
If you have found an official Docker image that is still shellshock vulnerable, the library maintainers [1] would love to hear from you as they take that stuff quite seriously. As far as I know the entire library is fully patched. [1] http
603.
by shykes 12y ago
If you're specifically looking for a convenient way to use Docker for development, don't use Vagrant. It tries too hard to abstract Docker away, so it's not a good choice if you care about compatibility with the rest of the e
604.
by shykes 12y ago
Docker volumes are just bind-mounted directories. Of all the things you should worry about when running HA systems, bind-mounts is definitely not one of them. They are essentially overhead-free and completely stable. This is completely orth
605.
by shykes 12y ago
You're right, we're still missing dynamic volume mounts to do the same thing in Docker. My bad.
606.
by shykes 12y ago
As of Docker 1.3 you can simply 'docker exec' :)
607.
by shykes 12y ago
Glad someone agrees with me :) For what it's worth, I resisted adding .dockerignore as long as I could, basically for the same reason (why not add .gitignore support instead?) but the demand for it was simply too overwhelming to ignore
608.
by shykes 12y ago
You're right, ideally you could get the best of both worlds: 1) multi-container stack that mimics the production setting, and 2) something you can 'docker pull' and 'docker run' as a single unit. For now you need 3d
609.
by shykes 12y ago
Yeah, build caching makes it much more practical to rebuild in many cases. But there are still some workflows where even waiting a few seconds is too long - most commonly when you're writing frontend code and want to just refresh the b
610.
by shykes 12y ago
Absolutely, the full implementation will allow each user to sign with their own keys, and provide user-configurable trust rules ("allow images only signed by this key"). The Docker CA will be used as a default convenience to provi
611.
by shykes 12y ago
Noteworthy features: * Feature preview of digitally signed images * Process injection with `docker exec` * More flexible container lifecycle with `docker create` * Shared directories on Mac OS X thanks to boot2docker * Fine-grained security
612.
by shykes 12y ago
Yes, but often you are better off isolating these processes from each other, and only allow communication over the network. Most of the time these processes only need the network to communicate with each other. When there is a legitimate re
613.
by shykes 12y ago
We moved the cadence to every other month, because packagers complained we were shipping too fast :)
614.
Docker 1.3: signed images, process injection, Mac shared directories(blog.docker.com)
6 points by shykes 12y ago|0 comments
615.
by shykes 12y ago
Looks a lot like webshell ( http://webshell.io ). I wonder if there are other similar tools out there?
616.
by shykes 12y ago
Docker and Heroku use the exact same sandboxing technology under the hood (Linux namespaces and cgroups). This is not surprising since Docker came out of Dotcloud, a direct Heroku competitor. The pros and cons of linux namespaces have been
617.
by shykes 12y ago
When we introduced pluggable storage drivers in Docker 0.7, we wanted all existing data to work as usual (full compatibility of data at rest), but we also wanted to migrate the layout of the legacy storage system (based on AUFS) so that it
618.
by shykes 12y ago
Note that the image maintainers (starting with tianon above) reserve the right to change the base distro they use for the images. So they can truly use the best tool for the job, now and in the future.
619.
by shykes 12y ago
Jake, you're being disingenuous. Back in April I gave a detailed explanation [1] as to why I hesitated to make the proposed change. When comments kept rolling in I followed up in June with a possible solution and a conclusion that &quo
620.
by shykes 12y ago
Yes, you can definitely share volumes between any number of containers, it's a common usage pattern. You don't need to make a container persistent: Docker, by design, will never remove anything unless you explicitly ask it to. If
621.
by shykes 12y ago
I would love to take you up on that. I want to bake vxlan support into Docker upstream (as an optional plugin, like everything else). Edit: Hi Joseph! Just realized it was you :)
622.
by shykes 12y ago
I totally agree that containers in general, and Docker in particular, could play a big role in moving the status quo towards IPV6 and a more sane approach to service-oriented networking. I would love to turn on IPV6 by default on every Dock
623.
by shykes 12y ago
The first application that comes to mind is vehicles. Picture a car driving at full speed, or an airplane about to land. With a 10 second early warning, at the very least the driver/pilot could receive a clear visual and audible alert
624.
by shykes 12y ago
Ah, you are correct. Every container can now modify its own /etc/resolv.conf and /etc/hosts, but these changes are not kept when a new image is committed from the filesystem of that container. Even if they were committed
625.
by shykes 12y ago
I think it is supported. The feature we are discussing allows the container to change its own resolv/host files, from the inside. I'm pretty sure that works from build also. But it's possible that I missed one of the patche
626.
by shykes 12y ago
It's no longer supported. I use the standard Mac setup (boot2docker + Virtualbox) and it works quite well for me. It's my primary environment for developing Docker :)
627.
by shykes 12y ago
Definitely a reasonable question. The answer is yes, there are plans to do exactly that :)
628.
by shykes 12y ago
The boot2docker devs are running their build right now. The QA for that part is harder to automate (mac, windows, virtualbox etc). I think starting with the next release we'll need to pull in b2d builds as a gateway to the main release
629.
by shykes 12y ago
Yeah that one was super-high on the request list, there were 3 competing patches before we finally got it right.
630.
by shykes 12y ago
Hi all, no World-changing features in this one, but we believe that over time, relentless incremental improvements can make a huge difference. This week we are freezing all feature merges and focusing on refactoring, code cleanup and genera

More ›