2 ms·
1. You don't understand what I mean by complex system, and i'm talking about changes to a single file in a container. Running a new container does not change th
by peterwwillis 13y ago
1. You don't understand what I mean by complex system, and i'm talking about changes to a single file in a container. Running a new container does not change the old container.
2. Compiling a binary is not a 'monolithic change' (?), it is a static configuration with dynamic elements. And please quote the line where I called myself an expert of anything.
3. Uh, I don't have a "ghetto deployment script", but thank you for the kind words. Like I was saying before, your only option is to continue adding on more unions every time you change a file, which I bet will lead to performance degradation, if not just general application headaches in the future. If somehow Docker also prevents the need to stop and restart the container when adding a new layer (which should be possible with Union), that's great too! It still leaves a world of cruft behind in the form of old filesystem layers and a maintenance hassle.
Awesome, you have real world performance numbers! So how many layers can you add to a container without it going down before there's performance degredation? How does it affect memory, or disk space from added layers? Does aufs have an upper bound on the number of layers, or any other metrics? Would love to see some numbers on this.