Warning
Maybe something is not working, use this image with caution, bad things can happens. YHBW
Proxmox Virtual Environment on a Docker container
Postfix is not working- (and maybe many other things)
./run.sh
;-)
What does run.sh do:
- set docker ENV vars if they are set in the script or in the
.envs
file - set shell script vars if they are set in the script or in the
.shell-vars
file (see example) - check if datastore exists; if not, it exits prior to run the container (maybe in future i'll make it more smart, see To DO section)
- run the container
or
docker run -d --name pve neomediatech/pve
Name | Description | Default |
---|---|---|
ADMIN_PASSWORD | Password to access PVE web interface (mandatory) | (none) |
RELAY_HOST | Hostname to use to relay email from Postfix | |
PVE_ENTERPRISE | If set to "yes", enterprise repository will be retained | no |
ENABLE_PVE_FIREWALL | If set to "no", PVE firewall service will be disabled | yes |
Set vars in run.sh
script and/or set them in .envs
file.
Example .envs
file:
ADMIN_PASSWORD=myrealsecretpassword
RELAY_HOST=10.40.50.4
Name | Description | Default |
---|---|---|
INTERACTIVE | Run the container in "interactive mode" (run it in foreground) CTRL+C will end the container |
no |
NAME | Proxmox VE name | pve |
BASE_PATH | Path where to store PVE configurations, users, etc... | /srv/pve |
.shell-vars
example file:
NAME="myserver-pve"
BASE_PATH="/srv/pve"
INTERACTIVE="no"
Put your docker bindmount in the script run.sh or in the .volumes
file
.volumes
example file:
${BASE_PATH}/data/logs:/var/log
${BASE_PATH}/data/pve_cluster:/var/lib/pve-cluster
${BASE_PATH}/data/pve_manager:/var/lib/pve-manager
${BASE_PATH}/data/bin:/srv/bin
- Make Postfix working, to send emails