Ephemeral Docker-based PBS instance for testing. Sets up a basic PBS environment with predefined users, tokens, and datastore structure to use for testing, demo purposes or development.
Obviously do not use this near production, it's completely unsafe by default, bypasses a number of security features (e.g. randomly generated token secrets) for testing purposes, and it'll likely delete all the data that's backed up to it at some point, just go to dockurr/proxmox-backup for a proper production setup.
The default deterministic secret used for generated API tokens is:
12345678-1234-1234-1234-1234567890ab
This is the value written into the autogenerated yescrypt hash stored in PBS for each token. The basic container uses this secret directly.
A container with just the user structure and basic elements created.
Contains the following static resources
Root User: root
Root Password: demo
Datastore: data
Namespaces:
/
level1/
level2/
level3/
level1-2/
Users:
- root (Root User)
- backupuser@pbs (Password backupuser)
- User permissions: Datastore.Backup on all levels in datastore data
- Tokens (same permissions as user backupuser)
- backupuser@pbs!backup: 12345678-1234-1234-1234-1234567890ab
- restoreuser@pbs (Password restoreuser)
- User permissions: Datastore.Reader on all levels in datastore data
- Tokens (same permissions as user restoreuser)
- restoreuser@pbs!restore: 12345678-1234-1234-1234-1234567890ab
The advanced container reads YAML from /etc/pbs-static-config.yml and creates the namespace and user model at startup.
Example:
default_token_secret: "12345678-1234-1234-1234-1234567890ab"
namespaces:
level1:
level2:
level3:
level1-2:
users:
userA:
namespaces: [level1, level1-2]
permissions: [DatastoreBackup]
token:
- useratoken
token_secret: "12345678-1234-1234-1234-1234567890ab"
userB:
namespaces: []
permissions: [DatastoreRead]
token:
- userbtokenFor more information, see the readme in the advanced directory