mirror of
https://github.com/puppetlabs/vmpooler.git
synced 2026-01-26 10:08:40 -05:00
Add instructions for running in a Docker container
This commit is contained in:
parent
833e34ce37
commit
d85f84011f
2 changed files with 18 additions and 0 deletions
10
Dockerfile
10
Dockerfile
|
|
@ -1,3 +1,13 @@
|
||||||
|
# Run vmpooler in a Docker container! Configuration can either be embedded
|
||||||
|
# and built within the current working directory, or stored in a
|
||||||
|
# VMPOOLER_CONFIG environment value and passed to the Docker daemon.
|
||||||
|
#
|
||||||
|
# BUILD:
|
||||||
|
# docker build -t vmpooler .
|
||||||
|
#
|
||||||
|
# RUN:
|
||||||
|
# docker run -e VMPOOLER_CONFIG -p 80:4567 -it vmpooler
|
||||||
|
|
||||||
FROM jruby:1.7-jdk
|
FROM jruby:1.7-jdk
|
||||||
|
|
||||||
RUN mkdir -p /var/lib/vmpooler
|
RUN mkdir -p /var/lib/vmpooler
|
||||||
|
|
|
||||||
|
|
@ -57,6 +57,14 @@ The following YAML configuration sets up two pools, `debian-7-i386` and `debian-
|
||||||
|
|
||||||
See the provided YAML configuration example, [vmpooler.yaml.example](vmpooler.yaml.example), for additional configuration options and parameters.
|
See the provided YAML configuration example, [vmpooler.yaml.example](vmpooler.yaml.example), for additional configuration options and parameters.
|
||||||
|
|
||||||
|
### Running via Docker
|
||||||
|
|
||||||
|
A [Dockerfile](Dockerfile) is included in this repository to allow running vmpooler inside a Docker container. A `vmpooler.yaml` configuration file can be embedded in the current working directory, or specified inline in a `VMPOOLER_CONFIG` environment variable. To build and run:
|
||||||
|
|
||||||
|
```
|
||||||
|
docker build -t vmpooler . && docker run -e VMPOOLER_CONFIG -p 80:4567 -it vmpooler
|
||||||
|
```
|
||||||
|
|
||||||
### Template set-up
|
### Template set-up
|
||||||
|
|
||||||
Template set-up is left as an exercise to the reader. Somehow, either via PXE, embedded bootstrap scripts, or some other method -- clones of VM templates need to be able to set their hostname, register themselves in your DNS, and be resolvable by the vmpooler application after completing the clone task and booting up.
|
Template set-up is left as an exercise to the reader. Somehow, either via PXE, embedded bootstrap scripts, or some other method -- clones of VM templates need to be able to set their hostname, register themselves in your DNS, and be resolvable by the vmpooler application after completing the clone task and booting up.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue