A lot of people greatly paid attention to Docker. I am asked that "What is different as for LXCF and Docker?". I will easily describe the difference point. About Docker, I have been variously looked at with Web and heard information and the experience actually used.
Both Docker and LXCF are based with container technologies. However, the target that should be aimed is different respectively, and the mechanism and the usage, etc. are different greatly for that.
When someone makes the image once, it comes to be able to use it a lot though a peculiar setting to the system of Docker different from usual system management etc. are necessary when it is Docker. However, knowledge concerning Docker is necessary for making the first image. Moreover, it is necessary to set the difference of the installed individual environment (ip address, parallel number, and ssh key, etc.) more individually again.
LXCF is as follows for it.
Changeable system
It is generated based on OS environment on HOST, and LXCF is made to the system environment besides HOST in addition and can be done by the technique of usual system management.
The system that makes it once can be maintained and be used by remodeling it long.
There is no overhead and you may locate LXCF to efficient VM.
The same environment as HOST
LXCF is generated the same environment as the host. Therefore, the installation is easy.
Moreover, the system based on OS image that anonymous others made is uneasy security. As for LXCF, it is always generated with the HOST environment, and it is easier to keep security.
One container, and it is a variegated function, and a lot of processes of the server.
The process of the server is started as a system daemon in LXCF by way of systemd.
Each container can be stopped by operating systemd.
When the event is waited by the daemon or the stopping process is started, it is necessary to add some method for Docker.
I think that I have the following features by Docker.
Immutable system
When "Update and maintenance" is not done but the system of a new version leaves the image made as a system in docker, the system of an old version throws it away.
The latest system is always used. It uses it without changing contents as "Immutable system". If the container breaks, it only has to throw away, and thought that it only has to substitute it for the new one if becoming old.
Will such operation increase on Cloud in the future?
Portable application
Docker bundles all necessary libraries and the commands for the application. As a result, the application operates even if it takes it to any environment. Moreover, because it only has to bundle only the one that the application uses, the size of the image can be reduced.
It is one function, and one process in one container.
To execute the aimed application, the container of one Docker need not execute various programs. Moreover, it is an idea that even a minimum process only has to operate to execute the application. As a result, the application can be compactly efficiently executed.
As for LXCF, the vice of past VM is designed.
LXCF starts in a few seconds, and the overhead of LXCF is 0.
Moreover, LXCF is not taking the place of Docker based on the same container technology. Similarly, Docker does not substitute for LXCF.
You should use it by the right place.
However, it is possible in LXCF not to be able to do in Docker.