859
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + Line 25:
Line 27: + + Line 49:
Line 53: + + + + + + + + + + + + + + + + + +
Docker design concept (view source)
Revision as of 14:26, 22 November 2022
, 14:26, 22 November 2022no edit summary
{{WIP box}}
{{WIP box}}
{{Note box|Various configuration entries may be deprecated}}
__TOC__
__TOC__
[[File:Docker_design_conceptv0.1.png]]
[[File:Docker_design_conceptv0.1.png]]
a CPAN perl library for managing images and containers
a CPAN perl library for managing images and containers
http://search.cpan.org/~alambike/Eixo-Docker-1.103/lib/Eixo/Docker.pod
http://search.cpan.org/~alambike/Eixo-Docker-1.103/lib/Eixo/Docker.pod
https://github.com/alambike/eixo-docker
The Eixo library interacts with Docker API via a TCP socket. By default Docker starts without a TCP socket attached, so we have to add it to the Docker service arguments in /etc/sysconfig/docker. The default port via which the Docker API communicates is 4243 but it can be any port. Below is an example /etc/sysconfig/docker file:
The Eixo library interacts with Docker API via a TCP socket. By default Docker starts without a TCP socket attached, so we have to add it to the Docker service arguments in /etc/sysconfig/docker. The default port via which the Docker API communicates is 4243 but it can be any port. Below is an example /etc/sysconfig/docker file:
===B. Docker options===
===B. Docker options===
* TBA
* TBA
* Docker cluster?? (Multiple SME Servers load balancing docker containers)
===C. Image options===
===C. Image options===
* Linked containers
* Linked containers
To inspect an image and with what (networking) options it was constructed, one can inspect the image by:
docker inspect [imagename]
==SME Databases==
==SME Databases==
===Container options===
===Container options===
Container options can be passed to the container at 'boot' time. These options can include the following aspects:
* network (ports, port mapping)
* 'cpu' (load)
* memory allocated (size)
* Storage (mount paths, both inside container and (remote) host)
* Domain names (FQDN (sub)domains, Web server Aliases)
* Links to other containers (container wordpress automatically starts container MySQL)
Unlike containers, images themselves do not carry this information, but only the exposed (open) ports.
Hence the usage of SME Server db system to store preferred options per container.
Syntax:
Syntax:
db docker_containers [name]
db docker_containers [name]