Section 4. Under the hood
parent
5e549b1451
commit
91202103e4
|
@ -96,3 +96,35 @@ Set limit for
|
||||||
* Scheduling CPU time
|
* Scheduling CPU time
|
||||||
* Memory allocation limits
|
* Memory allocation limits
|
||||||
* Inherited limitations and quotas (summed total cannot exceed the limit)
|
* Inherited limitations and quotas (summed total cannot exceed the limit)
|
||||||
|
|
||||||
|
## Storage
|
||||||
|
|
||||||
|
Discuss how container storage work
|
||||||
|
|
||||||
|
### Unix Storage in Brief
|
||||||
|
* Actual storage devices are binary info on hardware, managed by kernel
|
||||||
|
* Logical storage devices (logical groups, like partition drive into different parts)
|
||||||
|
* Filesystems
|
||||||
|
* FUSE filesystems and network filesystems
|
||||||
|
|
||||||
|
### The Secret of Dockers: COWs
|
||||||
|
|
||||||
|
Copy on Write layer: Container see the combined result of real file and a its own file system layer. When writing to file, instead of directly write on file, we write on the file system layer
|
||||||
|
|
||||||
|
???? Need more understanding
|
||||||
|
|
||||||
|
### Moving Cows
|
||||||
|
|
||||||
|
* The contents of layers are moved between containers in gzip files
|
||||||
|
* Containers are independent of the storage engine
|
||||||
|
* Any container can be loaded (almost) everywhere
|
||||||
|
* It's possible to run out of layers on some of the storage engines
|
||||||
|
|
||||||
|
### Volumes and Bind Mounting
|
||||||
|
|
||||||
|
* The Linux VFS (Virtual File System)
|
||||||
|
* Mounting devices on the VFS
|
||||||
|
|
||||||
|
????
|
||||||
|
|
||||||
|
TODO: relearn these content (networking, process, storage of docker, etc)
|
Loading…
Reference in New Issue