-
Notifications
You must be signed in to change notification settings - Fork 126
Docker Using Portainer
This is just an overview to roughly explain how Docker / Portainer works for someone who has never used Docker before. The following menu entries provide a simple overview of the Host and list of Events
- Dashboard
- Host
- Events
-
Endpoints
Each endpoint can be thought of as a connection to a docker server.
Typically in a small setup there will just be a local endpoint for the local docker server daemon -
Registries
Each registry is a list of available images that can be deployed as a container.
DockerHub is the general online source of images, but personal / private registries can be added here also
-
Volumes
these are typically directories on the disk which are used for data storage outside of the container.
The idea is to keep data out of the container, such as database content.
A volume can be shared between multiple containers.
If you destroy a container and bring it back up again (as part of an upgrade) the volume will keep the data secure outside of the container. -
Containers
A container can be thought of as similar to a virtual machine.
It's the server instance running or stopped inside of docker that might be a database or wiki or something else.
These are created from images which need to be downloaded if they're not already present.
Also the image needs to remain on disk while the container is in use. -
Networks
This can be used to alter or change the internal network used by Docker images. -
Images
An image can be thought of as a template or image of data that can be deployed out as a container.
These are used for setting up new instances of a container.
Wiki content license: Creative Commons Attribution-ShareAlike 4.0 International License