elivepatch-server-docker is a docker instance for the server-side of elivepatch
You can get the elivepatch client-side
It handles the automated creation of live patch object for the Linux kernel (currently working only for gentoo-sources).
- Automated creation of Live patch object using kpatch
- Client/Server configuration with the possibility of automated update
- SSL security configuration
- Supporting any gentoo-sources version and configuration
- Work with all versions of docker
We added docker-compose.yml for a really simple usage.
$ docker-compose up -d
The previous command will start elivepatch server on the port 5000, where you can communicate with elivepatch-client.
Let's start by building a example live patch object.
We can do it from the elivepatch-client repository like this.
elivepatch-client -p example/2.patch -k example/config_5.1.6 -a 5.1.6 --url http://localhost:5000
$ git checkout development
$ docker-compose build
We need to clone the elivepatch-server repository that we want to work on.
In this case we are using the official repository as example but you can use a fork.
$ git clone git@github.com:gentoo/elivepatch-server.git elivepatch-server
$ docker-compose up -d
$ docker-compoes exec gentoo /bin/bash
bbd875c1561b /elivepatch_development $ python setup.py install
bbd875c1561b /elivepatch_development $ elivepatch-server -d
Let's start by building a example live patch object.
We can do it from the elivepatch-client repository like this.
elivepatch-client -p example/2.patch -k example/config_5.1.6 -a 5.1.6 --url http://localhost:5000
Feel free to send pull requests to elivepatch-server or elivepatch-client. Welcome to the project.
Please check the elivepatch wiki