cpuguy83

69 ms·

841.
by cpuguy83 10y ago
Why do you say it depends on docker-machine?
842.
by cpuguy83 10y ago
Indeed, would definitely be cool to be able to export a specific machine config to a tarball that can be imported on another machine. I don't work on machine, but anyone made a proposal for this (probably with warnings about copying ss
843.
by cpuguy83 10y ago
Yes. The filesystem in the container is a real filesystem backed by the disk. How this happens is dependent on the storage driver used. The `aufs` driver (default when available), as well as `overlay(2)` and `vfs` drivers just sit on top of
844.
by cpuguy83 10y ago
Yes, you have to rebuild your image to deploy a new version. But are you really changing code in production on the fly? This seems dangerous. Also something that can technically be done with Docker, just it's really not a good idea (an
845.
by cpuguy83 10y ago
Maintainer here, can you please point to a production issue that is WONTFIX?
846.
by cpuguy83 10y ago
It's clear documentation is not up to snuff and something we need to work on (and are working on). I agree with the article that many of the official docs around use-cases (non-reference material) is outdated and difficult to keep up t
847.
by cpuguy83 10y ago
All these statements are patently false. 1. Containers are not ephemeral. They have a lifecycle. Data written in the container is persisted to disk and available after the container is stopped and then started again. 2. Processes/files
848.
by cpuguy83 10y ago
go errors are generally backed by structs as well (though not necessarily), even `fmt.Errorf("some error")` is a struct (called `errorString`). `Error() string` is just the interface that things that want to be errors must impleme
849.
by cpuguy83 10y ago
Probably from the perspective of someone who doesn't know either language, go is easier to infer what is happening. Ultimately once you are actually writing code it doesn't matter.
850.
by cpuguy83 10y ago
The only thing bad about Go's version (other than the usual repetitive code complaints) is it's easy to ignore (ie forget) to handle an error. And really much of the error handling in Go is by convention (ie, `if err != nil { retu
851.
by cpuguy83 10y ago
That's a fair statement, especially with d4mac/d4win and auto-update. Posting a pull request and thinking about a problem are two very different things. The project has chosen to err on the side of safety (ie, user asked for some
852.
by cpuguy83 10y ago
More detail on actual security issues (real CVE's) prevented just by using docker: https://docs.docker.com/engine/security/non-events/
853.
by cpuguy83 10y ago
Work is being done here: https://github.com/docker/docker/pull/25540
854.
by cpuguy83 10y ago
Yes, Docker does not provide storage infrastructure services. If all you are looking for is advice on how to handle storage, this is not a problem of the platform but rather education. All someone can do is educate on the pros and cons of d
855.
by cpuguy83 10y ago
I do not think this is a reason to not use replication. In this sense, no distributed system guarantees consistency. If a node goes down (particularly a leader!) while trying to distribute a new update, you are very likely to run into issue
856.
by cpuguy83 10y ago
Care to clarify issues you have with volume management? I think the biggest issue is around the `-v` syntax (and the corrosponding API). In the UX we call things a volume which are actually a mount (which happen to use a volume). I like the
857.
by cpuguy83 10y ago
github.com/docker/containerd
858.
by cpuguy83 10y ago
Docker relies on the already existing storage providers (ebs, gce, azure, netapp, emc, etc) to manage multi-host data. Ultimately how do you manage data when it's not in a container? This is how you should be managing data inside the c
859.
by cpuguy83 10y ago
Hard problems are hard. We are looking at all kinds of issues related to this, and in reality reports from that issue are likely caused by different things (some things are fixed, others obviously not). There are several people looking how
860.
by cpuguy83 10y ago
This is a caused by a race condition in the kernel that is not particularly easy to solve. The way to solve this is not use the `--userland-proxy=false` function.
861.
by cpuguy83 10y ago
Disagree... Also disclaimer, I work at Docker, and particularly spend a large amount of time working on storage for the docker engine. Volumes are exactly what you should be using to have data that lives beyond the life of the container. Es
862.
by cpuguy83 10y ago
This is very much the wrong way to approach storage (and sorry, for being so blunt, not sure how else to say it!). Docker has support for a wide-array of storage solutions, everything from the various providers solutions (ebs, s3, gce stora
863.
by cpuguy83 11y ago
I guess the only thing that would prevent this from working is having the linux subsystem available on the host (and of course support for all the syscalls being made).
864.
by cpuguy83 11y ago
I do not work on this project, but perhaps this was the move to have the "VPN compatibility mode" enabled by default. Have you tried going to the settings menu and disabling?
865.
by cpuguy83 11y ago
Already a thing: https://msdn.microsoft.com/en-us/virtualization/windowsconta... Native Docker support in Windows will be available in the next Windows server release, and is already available in the Windows techn
866.
by cpuguy83 11y ago
Still need to either set the envvar or pass the equivalent flag.
867.
by cpuguy83 11y ago
Please make sure to report any issues so they can be fixed.
868.
by cpuguy83 11y ago
Sounds likely to be https://github.com/docker/docker/issues/18180 If so, it's a bug with a particular (newer) version of AUFS that has been fixed in most distros.
869.
by cpuguy83 11y ago
Oh gosh, I thought it was a super odd comment :)
870.
by cpuguy83 11y ago
Docker on Windows (with native Windows containers) is also a very real thing and will ship with the next Windows Server release (you can download a technical preview from Microsoft now).

More ›