cpuguy83

72 ms·

1. 871.▲
   by cpuguy83 11y ago

   There are no custom kernel modules, everything is in a stock kernel since 3.10 (which not-so-coincidentally is the minimum supported kernel version). Containers are run with whatever user you tell it to run as, the default is root because t
2. 872.▲
   by cpuguy83 11y ago

   vbox4 caused issues with xhyve when xhyve first came out (not sure if it's still an issue), vbox5 coexists just fine.
3. 873.▲
   by cpuguy83 11y ago

   This is one of the features mentioned in the announcement.
4. 874.▲
   by cpuguy83 11y ago

   I have not experienced this crash, and even had a container running last night, put the laptop to bed, woke it up this morning and the container is still there, running and interactive. Running OSX 10.11.3
5. 875.▲
   by cpuguy83 11y ago

   But the reality is, on larger projects voting doesn't help, won't work, etc. I guess for the 90% it's ok. It'd be nice to be able to turn off.
6. 876.▲
   by cpuguy83 11y ago

   This is true, but what if the thing that spins up the actual container process sets this?
7. 877.▲
   by cpuguy83 11y ago

   Which volume driver? Wasn't aware mesos was providing one.
8. 878.▲
   by cpuguy83 11y ago

   Well, seccomp already does this, no?
9. 879.▲
   by cpuguy83 11y ago

   Neat!
10. 880.▲
    Docker Networking: Reborn(container42.com)

    1 points by cpuguy83 11y ago|0 comments
11. 881.▲
    by cpuguy83 11y ago

    I'm not sure the completeness of the support as I don't run BSD, but I know it's being worked on and at least compiles on BSD. There's actually quite a bit of BSD-only code in.
12. 882.▲
    by cpuguy83 11y ago

    Load balancing and failover are generally a requirement in clustered environments, but are really different jobs. LB's "schedule" connection requests, cluster schedulers schedule the things that those connections are going to
13. 883.▲
    by cpuguy83 11y ago

    Hipache is a reverse proxy, swarm is for managing/scheduling a cluster of docker engines.
14. 884.▲
    by cpuguy83 11y ago

    Indeed. This is why we've developed the plugin ecosystem, and a proper volumes API in docker. With plugins your volume can either live locally or on some other storage management system, like ceph, gluster, s3, etc. These are all worki
15. 885.▲
    It's the community, stupid(integratedcode.us)

    23 points by cpuguy83 11y ago|1 comments
16. 886.▲
    by cpuguy83 11y ago

    Yes, it's docker that was holding on to these exec instances (and cluttering up the `docker inspect` output if you do a bunch). We now do GC on these. ps, you can add `reastart: always` to your compose file, and docker daemon will auto
17. 887.▲
    by cpuguy83 11y ago

    And is also not the silver-bullet people hope it to be, being that there is absolutely no FS level support for userns.
18. 888.▲
    by cpuguy83 11y ago

    Memory issues can be caused by a number of things. There's been a lot of work done to improve some leakages around the logging -- both by being able to disable logging if you don't need it or switch to a different logger, and gene
19. 889.▲
    by cpuguy83 11y ago

    Filesystem events don't propagate across any networked filesystem (at least none that I've seen). FYI, vagrant is probably just using NFS. The default boot2docker setup uses vbox shared folders. Events should work just fine when t
20. 890.▲
    by cpuguy83 11y ago

    I don't see how containerization changes your security strategy in this regard, except instead of ssh'ing into a system and running `apt-get update && apt-get install ...`, you `docker build && docker run`
21. 891.▲
    by cpuguy83 11y ago

    Yes, we have changed response codes when the old ones were just wrong. Like returning a 500 when really it should be a 404, that kind of stuff. As far as start/create params, these should not be changed at all, other than that you can
22. 892.▲
    by cpuguy83 12y ago

    Why not use a comment?
23. 893.▲
    by cpuguy83 12y ago

    The unused imports thing seems to be a common complaint, however I just use go-imports, and imports are added/removed automatically when I save the file. I never ever have to even touch imports, except sometimes when two different pack
24. 894.▲
    Linux or Death, aka How to Install Linux on a Mac (2014)(blog.jessfraz.com)

    15 points by cpuguy83 12y ago|0 comments
25. 895.▲
    by cpuguy83 12y ago

    I've created a tool to help with migrating volume data: github.com/cpuguy83/docker-volumes and also this PR to help bring forward volume management within Docker: https://github.com/docker/docker/pul
26. 896.▲
    by cpuguy83 12y ago

    These are completely separate projects, not baked into Docker. github.com/docker/machine github.com/docker/swarm
27. 897.▲
    by cpuguy83 12y ago

    I believe to start off with, anything with volumes won't be moved... at least this was what was said during the POC demo given for hack day last month.
28. 898.▲
    by cpuguy83 12y ago

    swarm and machine are separate binaries. Compose is still a proposal. EDIT -- link to compose proposal https://github.com/docker/docker/issues/9459
29. 899.▲
    by cpuguy83 12y ago

    Docker can import any tarball as a rootfs for a container, essentially allowing you to use whatever build tool you want. Dockerfiles/`docker build` is an implementation of a build system which uses the docker engine to make said rootfs
30. 900.▲
    by cpuguy83 12y ago

    This is exactly the model being proposed in Docker.