The way I think of a container: It's an individual OS with a filesystem of its own, based on the "image" and what is pre-installed (such as an OS, plus, if you

The way I think of a container: It's an individual OS with a filesystem of its own, based on the "image" and what is pre-installed (such as an OS, plus, if you choose: some extras pre-installed based on your project need.). You can link your laptop or server (AKA your "host" computer) to it through Docker Volumes. And, you can link containers together through Docker Networks, for example. So, you can see how a single compartmentalized OS (a "container") can: 1. interact with another computer's file system and 2. interact with another computer on a network. And, each one can be quite customized. So, a container is an OS + filesystem* + network* * = can be connected to others to transfer data