Git Product home page Git Product logo

pve-backup-server-dockerfiles's Introduction

Proxmox Backup Server in a Container

GitHub release (latest by date) GitHub release (latest by date including pre-releases)

Docker Image Version (tag latest semver) Docker Image Version (latest semver)

This is an unofficial compilation of Proxmox Backup Server to run it in a container for AMD64 and ARM64.

Running in a container might result in some functions not working properly. Feel free to create an issue to debug those.

Buy me a Coffee

Buy Me a Coffee at ko-fi.com

If you found it useful :)

Common problems

  • Some people see authentication failure using admin@pbs: Ensure that /run is mounted to tmpfs which is requirement of 2.1.x
  • Some Synology devices use a really old kernel (3.1), for such the #15 is needed, and image needs to be manually recompiled.

Pre-built images

For starting quickly all images are precompiled and hosted at https://hub.docker.com/r/ayufan/proxmox-backup-server.

Or:

docker pull ayufan/proxmox-backup-server:latest

Run

docker-compose up -d

Then login to https://<ip>:8007/ with admin / pbspbs. After that change a password.

Features

The core features should work, but there are ones do not work due to container architecture:

  • ZFS: it is not installed in a container
  • Shell: since the PVE (not PAM) authentication is being used, and since the shell access does not make sense in an ephemeral container environment
  • PAM authentication: since containers are by definition ephemeral and no /etc/ configs are being persisted

Changelog

See Releases.

Configure

1. Add to Proxmox VE

Since it runs in a container, it is by default self-signed. Follow the tutorial: https://pbs.proxmox.com/docs/pve-integration.html.

You might need to read a PBS fingerprint:

docker-compose exec server proxmox-backup-manager cert info | grep Fingerprint

2. Add a new directory to store data

Create a new file (or merge with existing): docker-compose.override.yml:

version: '2.1'

services:
  pbs:
    volumes:
      - backups:/backups

volumes:
  backups:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /srv/dev-disk-by-label-backups

Then, add a new datastore in a PBS: https://<IP>:8007/.

3. Configure TZ (optional)

If you are running in Docker it might be advised to configure timezone.

Create a new file (or merge with existing): docker-compose.override.yml:

version: '2.1'

services:
  pbs:
    environment:
      TZ: Europe/Warsaw

4. Allow smartctl access

To be able to view SMART parameters via UI you need to expose drives and give container a special capability.

Create a new file (or merge with existing): docker-compose.override.yml:

version: '2.1'

services:
  pbs:
    devices:
      - /dev/sda
      - /dev/sdb
    cap_add:
      - SYS_RAWIO

5. Persist config, graphs, and logs (optional, but advised)

Create a new file (or merge with existing): docker-compose.override.yml:

version: '2.1'

volumes:
  pbs_etc:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /srv/pbs/etc
  pbs_logs:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /srv/pbs/logs
  pbs_lib:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /srv/pbs/lib

Install on bare-metal host

Docker is convienient, but in some cases it might be simply better to install natively. Since the packages are built against Debian Buster your system needs to run soon to be stable distribution.

You can copy compiled *.deb (it will automatically pick amd64 or arm64v8 based on your distribution) from the container and install:

cd /tmp
docker run --rm ayufan/proxmox-backup-server:latest tar c /src/ | tar x
apt install $PWD/src/*.deb

Recompile latest version or master

Refer to PROCESS.md.

Build on your own

Refer to PROCESS.md.

Author

This is just built by Kamil Trzciński, 2020-2023 from the sources found on http://git.proxmox.com/.

pve-backup-server-dockerfiles's People

Contributors

ayufan avatar simoncaron avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

pve-backup-server-dockerfiles's Issues

authentication failure [...] msg=path "/run/proxmox-backup/shmem" is not on tmpfs

Hi,

I've tried to install the latest docker image to my Synology via Portainer.
there were 4 Folders created on the host system and mapped into docker volumes:
Bildschirmfoto 2022-02-13 um 10 47 12

These 4 volumes are created with following options (in Portainer called "drive options":
Bildschirmfoto 2022-02-13 um 10 48 57

after start the container, logs seems to be fine and data were created in the folders.

But, the login (admin/pbspbs) is not working:
in PBS2/logs/api I found a file "auth.log" including this:
2022-02-13T09:39:05+00:00: authentication failure; rhost=[::ffff:172.17.0.1]:52784 user=admin@pbs msg=path "/run/proxmox-backup/shmem" is not on tmpfs

I think there is something wrong what I did, but I'm not sure what.
Also I checked the tmpfs inside the container:
Bildschirmfoto 2022-02-13 um 10 53 33

any suggestions how to handle this?

Missing docker configuration file in latest-arm64v8?

I'm not sure if I'm noobing hard at Docker, but I have pulled this image

Following the guide, running docker compose up -d gets me this result: no configuration file provided: not found

Invoking docker images gets me this result.

REPOSITORY                     TAG              IMAGE ID       CREATED       SIZE
ayufan/proxmox-backup-server   latest-arm64v8   8385a2b9ec77   6 weeks ago   1.31GB

I'm suspecting that there is no docker-compose.yml file and unsure if this is expected (and I just know the correct proces) or my use case is just undocumented?

Trying to install this on a Raspberry Pi 4 with Raspbian 11 (Bullseye).

Cannot connect

I have created a docker container and everything seems to be running smoothly according to portainer but I cannot connect to :8007. It says "The connection was reset".

Any help is much appreciated.

Screenshot 2024-02-02 175858

2 out of 2 hunks FAILED

Hey folks, trying to build from the Dockerfile and it's failing at step 11:

Step 11/39 : RUN /scripts/apply-patches.bash /patches/server/*.patch
 ---> Running in 9ec6da8051c6
/patches/server/proxmox-backup.patch => proxmox-backup...
patching file Cargo.toml
Hunk #1 FAILED at 52.
Hunk #2 FAILED at 79.
2 out of 2 hunks FAILED -- saving rejects to file Cargo.toml.rej
patching file debian/proxmox-backup-server.install
patching file debian/rules
The command '/bin/sh -c /scripts/apply-patches.bash /patches/server/*.patch' returned a non-zero code: 1

Unfortunately I'm not a Rust person 😅

Any ideas?

Backup files are not stored in backup volume

Hi,

I'm running docker in libreelec and installed pbs. I postet my stack config here:
#16 (comment)

After install i'v created a datastore and set the path to "/backup"

As far as i can see my backups are not stored in the volume that is givven for "backups".
/storage/.kodi/userdata/addon_data/service.system.docker/docker/volumes/proxmox-backup-server_pbs-backup

Instead they are stored somewhere in the docker file system. For example:
./.kodi/userdata/addon_data/service.system.docker/docker/overlay2/a79eca3f3ea79af097926bb97bf3a16ba14e848af430de826278562314af1bda/diff/backup/.chunks/41b7

How can i fix this?

Best Regards

Manuel

Can't use the Shell

When I tried to use the Shell (to change root@pam password), I got this error :
image

This is not a critical problem because we can access the shell by doing a "docker exec -it bash".

Also, if you want to make PAM users permanent, you can do it in the docker-compose :
volumes:
- ...
- ./shadow:/etc/shadow

or use your host users :
volumes:
- ...
- /etc/shadow:/etc/shadow:ro

Cant login after deploying docker

Hello,

I'm trying to use your image. The deployment goes fine (without errors, at least), the webui (https://xyz:8007) loads fine, but then the credentials do not work:

admin
pbspbs

Am I doing something wrong?
Thanks

How to configure smtp?

on the docker-host i have a working postfix configured and running.

can i somehow put that to use or do i have to add a postfix to the docker-container? what would be the best approach so i can send the system-notifications?

Replace postfix with ssmtp

Currently the container has postfix installed but does not start it and provides no way to start the postfix daemon to allow PBS to send emails. I think a possible solution would be to replace postfix with a simpler MTA. Looking through the MTA options available on Debian, I found that ssmtp is daemonless and could be a suitable simple MTA to provide /usr/sbin/sendmail as used by PBS. Any users that wanted to make use of ssmtp would need to have a persistent /etc and configure ssmtp themselves.

Mesh central consent

Could it be possible to have an option for user consent but only for workstation.
Today i'm going to mesh central and change manually option for all new PC.
Is there a script for this?

read_meminfo failed - unable to read ...pages_sharing"

Hey there! I've been using PBS through Docker for a while now with no issues, but today I can't get it to start.

It's repeatedly spitting out the below to the logs but not booting up.

read_meminfo failed - unable to read "/sys/kernel/mm/ksm/pages_sharing" - No such file or directory (os error 2)

Any idea as to what may be causing this?

I'm running the latest debug version (although it was showing up on :latest too) on a Pi 4 with Debian Buster.

backup client v2.1.5 armv7 block device image backup failed with "Error: blkgetsize64"

I have compiled the armv7 backup client from the source code at github. It works great for file backup but failed for block device image mode:

root@odroid:~# proxmox-backup-client.sh backup odroid.img:/dev/mmcblk1 --verbose
Error: blkgetsize64 failed for "/dev/mmcblk1" - EINVAL: Invalid argument

root@odroid:# cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS"
NAME="Ubuntu"
VERSION="18.04.6 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.6 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@odroid:
# uname -a
Linux odroid 4.14.180-178 #1 SMP PREEMPT Wed Sep 2 12:39:45 -03 2020 armv7l armv7l armv7l GNU/Linux

2.0.4 in-memory communication file (?)

After upgrade from 1.1.10 to 2.0.4 I can see only this in web browser:

failed to create new in-memory communication file at /run/proxmox-backup/proxmox-backup-memcom.11 - EEXIST: File exists

Downgrade helped... :-)

Cannot login to newly created container "permission check failed."

Issue:
I'm getting "Login failed" with "permission check failed." in dev tools when logging in with admin and pbspbs.

HTTP Request:

POST /api2/extjs/access/ticket HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: de,de-DE;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6
Connection: keep-alive
Content-Length: 36
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Host: 10.1.250.206:8007
Origin: https://10.1.250.206:8007
Referer: https://10.1.250.206:8007/
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.53 Safari/537.36 Edg/103.0.1264.37
X-Requested-With: XMLHttpRequest
sec-ch-ua: " Not;A Brand";v="99", "Microsoft Edge";v="103", "Chromium";v="103"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"

Form Data:
username: admin@pbs
password: pbspbs

Response:

{"errors":{},"message":"permission check failed.","success":false}

Steps to reproduce:

  • Create new docker container with latest image from today
  • Login with admin and pbspbs.

Open dev tools of browser to see the error messages

Installing bare metal

Hi have RPI3 running debian bullseye and version 2.2.5 of pbs installed as bare metal.

I would like to upgrade to 3.0.2: I get to the point of having all .deb packages in a folder but when trying t install them by
sudo apt install /home/pi/pbs/*.deb

i get various error complaining dependencies are not satisfied, below and example:
proxmox-mini-journalreader : depends: libc6 (>= 2.34) but version 2.31-13+rpt2+rpi1+deb11u7 is going to be installed

should I upgrade to bookworm first?

network_mode and traffic control

Hello,
first of all thank you for the very fast response to issues! Great project.
While playing with pbs I also tested the "bridge" mode. In itself, this works great and has the nice side effect that I do not constantly have messages in the log from my NAS. But unfortunately the traffic control doesn't work anymore.

do you have an idea how to solve this?

network_mode: "host" #network_mode: "bridge" #ports: # - "8007:8007"

ENOSYS: Function not implemented

Hey, i just setup this in Unraid and i keep getting this in my logs:

Error: failed to move file at "/var/log/proxmox-backup/api/access.tmp_7MN95t" into place at "/var/log/proxmox-backup/api/access.log" - ENOSYS: Function not implemented
Error: failed to move file at "/var/lib/proxmox-backup/rrdb/rrd.tmp_xzcB5h" into place at "/var/lib/proxmox-backup/rrdb/rrd.journal" - ENOSYS: Function not implemented
rm: cannot remove '/etc/proxmox-backup/.*.lck': No such file or directory
rm: cannot remove '/etc/proxmox-backup/*.lock': No such file or directory
And that continues on and on forever and nothing happens

tmpfile in "/run/proxmox-backup/shmem" failed - EISDIR: Is a directory

auth failed at the first login,
the error is
2021-12-16T12:34:33+00:00: authentication failure; rhost=[::ffff:172.17.0.1]:57456 user=root@pam msg=path "/run/proxmox-backup/shmem" is not on tmpfs

the image is the latest prebuilt,
"Created": "2021-11-30T15:37:34.74490427Z",

how to make "/run/proxmox-backup/shmem" on a tmpfs?

Add datastore, uses only 10% of the disk

Hi,

I have a total clean install of buster lite on a RPI 4 and got all up and running (docker) and also connected to my VM server, BUT im struckling with a fresh USB mounted disk, i triede EXT4 and NTFS (both shows over 240GB free space (250GB disk), when i add storage, it only uses 28.43GB
Udklip

Any hints on what to do?

Error: Address family not supported by protocol (os error 97)

Is there any way to get this running on a host that has ipv6 disabled? According to the proxmox backup server documentation it should be possible.

I tried disabling it in the container as described here but no changes in the output of docker-compose up

pbs_1  | Error: Address family not supported by protocol (os error 97)
pbs_1  | PROXY: Starting...
pbs_1  | Error: Address family not supported by protocol (os error 97)
pbs_1  | PROXY: Starting...
pbs_1  | Error: Address family not supported by protocol (os error 97)
pbs_1  | PROXY: Starting...
pbs_1  | Error: Address family not supported by protocol (os error 97)
pbs_1  | PROXY: Starting...
pbs_1  | Error: Address family not supported by protocol (os error 97)
pbs_1  | PROXY: Starting...
pbs_1  | Error: Address family not supported by protocol (os error 97)
...

New setup won't start on Portainer

I initially made this comment on another issue before I realized it wasn't exactly the same.

I set up a new stack in Portainer with the details below and the container log showed the copy of default files and they appear on my mounted volume so that seems good. However, despite dropping the stack and redeploying (once with v2.4.1) I get the same output:

PROXY: Starting...
rm: cannot remove '/etc/proxmox-backup/.*.lck': No such file or directory
rm: cannot remove '/etc/proxmox-backup/*.lock': No such file or directory
/etc/proxmox-backup is a mountpoint
/var/lib/proxmox-backup is a mountpoint
/var/log/proxmox-backup is a mountpoint
/run is a mountpoint
API: Starting...

I've let it sit like this for over 30 minutes without any movement. I'm guessing I'm doing something wrong, any ideas?

image

docker-compose.yml:

version: '2.1'

services:
  proxmox-backup:
    image: ayufan/proxmox-backup-server:latest
    network_mode: host
    mem_limit: 2G
    volumes:
      - backups:/backups
      - pbs_etc:/etc/proxmox-backup
      - pbs_logs:/var/log/proxmox-backup
      - pbs_lib:/var/lib/proxmox-backup
    environment:
      TZ: America/Detroit
    tmpfs:
      - /run
    cap_add:
      - SYS_RAWIO
    devices:
      - /dev/mmcblk0
      - /dev/sda
    restart: unless-stopped
    stop_signal: SIGHUP
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.proxmox-http.rule=Host(`proxmox.it-clowd`)"
      - "traefik.http.routers.proxmox-http.entrypoints=web"
      - "traefik.http.routers.proxmox-https.rule=Host(`proxmox.it-clowd`)"
      - "traefik.http.routers.proxmox-https.entrypoints=websecure"
      - "traefik.http.routers.proxmox-https.tls.certresolver=basic"
      - "traefik.http.services.proxmox-service.loadbalancer.server.port=8007"

volumes:
  backups:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /media/data/proxmox/backups
  pbs_etc:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /media/data/proxmox/etc
  pbs_logs:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /media/data/proxmox/logs
  pbs_lib:
    driver: local
    driver_opts:
      type: ''
      o: bind
      device: /media/data/proxmox/lib

Let me know if you need any other details
Thanks!

backup register image failed: command error: EINVAL: Invalid argument

Hi,

I am trying to use the cool docker image on a QNAP ARM based NAS (TS-382X), however I have an issue when backing up VMs (but NOT CTs). I get the error

ERROR: VM 200 qmp command 'backup' failed - backup register image failed: command error: EINVAL: Invalid argument

I tried to run the container privileged and with all rights, but still get the error.

I found some similiar issues on the proxmox forum for a different NAS type:

https://forum.proxmox.com/threads/virtualized-pbs-with-shared-mount.100455/

However, I am successfully using a LXC container on a x64 based QNAP NAS which uses the same underlying file system.

In the above link, they talk about missing functions of the file system, however not which are missing and I was so far unable to determine more detail on this error.

Had anyone else this error and maybe has some additional ideas how to possibly circumvent it?

Would be sad to abandon the idea of using the NAS as PBS...

Thanks!

Login Issue on Synology

Hi,
I try pve-backup on my Synology via Docker. Installation ok. But impossible to login. I try admin@pbs with pbspbs but it doesn't work. Any idea?

Receiving "pipelined request failed: update atime failed for chunk/file" when backing up to backup proxmox server?

Hi there,

one of my vms im hosting with proxmox its receiving this error when running a backup to my backup proxmox server over the network.

INFO: creating Proxmox Backup Server archive 'vm/107/2023-02-01T05:34:56Z'
INFO: started backup task '5fa01ab2-b4ef-4ad4-ae0b-2beaa9554452'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (5.7 GiB of 100.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 5.7 GiB dirty of 100.0 GiB total
INFO: 9% (556.0 MiB of 5.7 GiB) in 3s, read: 185.3 MiB/s, write: 184.0 MiB/s
INFO: 20% (1.1 GiB of 5.7 GiB) in 6s, read: 206.7 MiB/s, write: 204.0 MiB/s
INFO: 29% (1.7 GiB of 5.7 GiB) in 9s, read: 190.7 MiB/s, write: 189.3 MiB/s
INFO: 37% (2.1 GiB of 5.7 GiB) in 12s, read: 138.7 MiB/s, write: 137.3 MiB/s
INFO: 47% (2.7 GiB of 5.7 GiB) in 15s, read: 197.3 MiB/s, write: 192.0 MiB/s
INFO: 54% (3.1 GiB of 5.7 GiB) in 18s, read: 150.7 MiB/s, write: 149.3 MiB/s
ERROR: backup write data failed: command error: write_data upload error: pipelined request failed: update atime failed for chunk/file "/backups/.chunks/2625/2625304352cd863348c8036333b6312afbcd100ec5a4ce9bf913d46229fceed5" - EPERM: Operation not permitted
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 107 failed - backup write data failed: command error: write_data upload error: pipelined request failed: update atime failed for chunk/file "/backups/.chunks/2625/2625304352cd863348c8036333b6312afbcd100ec5a4ce9bf913d46229fceed5" - EPERM: Operation not permitted
INFO: Failed at 2023-02-01 16:35:15INFO: Backup job finished with errors
TASK ERROR: job errors

Not Sure why this is happening since my other vms are backing up regularly like scheduled and are not having any issues.

Docker user permissions - change from backup

Apologies if this is obvious, I am fairly new to docker - but can you explain how to change the permissions that the docker container uses to write to the host file system?

I currently see the user as backup with read/write perms, the group as backup but without any perms and other without any perms. If the group had read/write perms this would make it easier as I could just add my user to that group, or ideally, a way to specify the user instead of using backup.

I was expecting to see some reference to the backup user in the compose, as it is my understanding that usually when no user is specified that docker will use the root account but I cannot see anything that allows me to change this?

Any idea how to do this?

lqGUaya

PBS 3.0.2 - desn't start

Hi!

Faced with the next after update to the latest container v3.0.2:

rm: cannot remove '/etc/proxmox-backup/*.lock': No such file or directory
rm: cannot remove '/etc/proxmox-backup/.*.lck': No such file or directory
/run is a mountpoint
PROXY: The proxmox-backup is not yet configured!
API: Starting...
/var/lib/proxmox-backup is a mountpoint
/etc/proxmox-backup is a mountpoint
/var/log/proxmox-backup is a mountpoint
thread 'main' panicked at /src/proxmox-backup/build/debian/cargo_home/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.32.0/src/runtime/scheduler/multi_thread/worker.rs:447:13:
OS can't spawn worker thread: Operation not permitted (os error 1)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This logs I get after deploy a new instance (without current 2.4.1 update) also.

I don't c any breaking changes at this update, but a fresh container have the same behaviour... Someone can suggestion? Maybe host system or something.

Odd issue, not sure if its expected?

Thanks for creating these docker files :)

I have create a backup share for the docker image,mounted at /backup, but in the proxmox backup gui, it can see all of my separate disks contained in my external raid disk array on the server?

I don't want proxmox backup touching those and wondered how it could be seeing them in the first place?

I have /backup mounted to an external share for the docker, but am not sure how to reference that from within proxmox backup; is it through a new datastore at /backup?

Thanks in advance :)

PBS armv7 build failure

I am trying to build the armv7 PBS but failed. The whole output is too long and I am attaching it as a file.

pbs-armv7-compile.txt

root@odroid:/#
root@odroid:/# cd /home/tonypang/pbs/pve-backup-server-dockerfiles/
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles# ls
Dockerfile Dockerfile.client Makefile README.md RELEASE.md dev-scripts docker-compose.yml pbs
runit scripts versions
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles# vi Makefile
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles# make arm32v7-docker-build
docker build
--tag ayufan/proxmox-backup-server:v2.1.5-arm32v7
--build-arg ARCH=arm32v7/
--build-arg TAG=v2.1.5
--build-arg VERSION=v2.1.5
-f Dockerfile
.
Sending build context to Docker daemon 650.8kB
Step 1/42 : ARG ARCH=
Step 2/42 : FROM ${ARCH}debian:bullseye AS builder
---> aaabdee60d04
Step 3/42 : RUN apt-get -y update && apt-get -y install build-essential git-core lintian pk
g-config quilt patch cargo nodejs node-colors node-commander libudev-dev libapt-pkg-dev l
ibacl1-dev libpam0g-dev libfuse3-dev libsystemd-dev uuid-dev libssl-dev libclang-dev libjson-
perl libcurl4-openssl-dev dh-exec wget
---> Using cache
---> 6e2fc80e3279
Step 4/42 : RUN wget https://static.rust-lang.org/rustup/rustup-init.sh && chmod +x rustup-init.sh
&& ./rustup-init.sh -y --default-toolchain nightly
---> Using cache
---> 8623ad7d607f

...... too long, trucated.......

Compiling udev v0.4.0
Compiling pam v0.7.0
Compiling proxmox-time v1.1.2 (/src/proxmox/proxmox-time)
Compiling cexpr v0.4.0
Compiling crypto-common v0.1.3
Compiling block-buffer v0.10.2
error[E0308]: mismatched types
--> /src/proxmox/proxmox-time/src/posix.rs:18:8
|
18 | Ok(epoch)
| -- ^^^^^ expected i64, found i32
| |
| arguments to this enum variant are incorrect
|
help: you can convert an i32 to an i64
|
18 | Ok(epoch.into())
| +++++++

error[E0308]: mismatched types
--> /src/proxmox/proxmox-time/src/posix.rs:32:8
|
32 | Ok(epoch)
| -- ^^^^^ expected i64, found i32
| |
| arguments to this enum variant are incorrect
|
help: you can convert an i32 to an i64
|
32 | Ok(epoch.into())
| +++++++

Compiling endian_trait_derive v0.6.0
error[E0308]: mismatched types
--> /src/proxmox/proxmox-time/src/posix.rs:56:30
|
56 | if libc::localtime_r(&epoch, &mut result).is_null() {
| ----------------- ^^^^^^ expected i32, found i64
| |
| arguments to this function are incorrect
|
= note: expected raw pointer *const i32
found reference &i64
note: function defined here
--> /src/proxmox-backup/debian/cargo_home/registry/src/github.com-1285ae84e5963aae/libc-0.2.125/s
rc/unix/mod.rs:1211:12
|
1211 | pub fn localtime_r(time_p: *const time_t, result: *mut tm) -> *mut tm;
| ^^^^^^^^^^^

error[E0308]: mismatched types
--> /src/proxmox/proxmox-time/src/posix.rs:69:27
|
69 | if libc::gmtime_r(&epoch, &mut result).is_null() {
| -------------- ^^^^^^ expected i32, found i64
| |
| arguments to this function are incorrect
|
= note: expected raw pointer *const i32
found reference &i64
note: function defined here
--> /src/proxmox-backup/debian/cargo_home/registry/src/github.com-1285ae84e5963aae/libc-0.2.125/s
rc/unix/mod.rs:1207:12
|
1207 | pub fn gmtime_r(time_p: *const time_t, result: *mut tm) -> *mut tm;
| ^^^^^^^^

For more information about this error, try rustc --explain E0308.
error: could not compile proxmox-time due to 4 previous errors
warning: build failed, waiting for other jobs to finish...
make[2]: *** [Makefile:172: .do-cargo-build] Error 101
make[2]: Leaving directory '/src/proxmox-backup'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" PROXY_USER=backup LIBDIR=/usr/l
ib/arm-linux-gnueabihf returned exit code 2
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 25
make[1]: Leaving directory '/src/proxmox-backup'
make: *** [debian/rules:22: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
The command '/bin/sh -c . /root/.cargo/env && cd proxmox-backup/ && dpkg-buildpackage -us -uc -b' ret
urned a non-zero code: 2
Makefile:22: recipe for target 'arm32v7-docker-build' failed
make: *** [arm32v7-docker-build] Error 2
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles#
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles#
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles#
You have new mail in /var/mail/root
root@odroid:/home/tonypang/pbs/pve-backup-server-dockerfiles#

Unable to log in

I installed this in Containner station on my Qnap NAS. I can access it using web interface but I am not able to login. I tried using admin for user and pbspbs for password but its not working.

Am i doing anything wrong or doing it in a wrong way?

Im unable to sign-in

How to mount "/run" as "tmpfs" in the pve-backup-server container? How can I check it?
Im able to access the PVE-Backup UI but im unable to sign in.

Note:

  • Raspberry Pi 4 (4GB)
  • OS: Ubuntu 20.04.4 LTS (64bit)
  • Portainer (v2.0.1)
  • Docker Compose (v2.9.0).

PBS Version 2.2 - Release?

Hi,

thanks for that awesome build and making it able to run on a RPI!😃

Any idea when version 2.2 gets released?

Error when docker-compose up

Hello,

When I try to run this image by using the docker-compose example or a handmade one, I get this error in a loop :
pbs_1 | PROXY: Starting...
pbs_1 | Error: unable to create rrdb stat dir - EACCES: Permission denied

storing login ticket failed: $XDG_RUNTIME_DIR must be set

Hi guys,

I just successfully got PBS running on my synology. I only had to correct the sore permission with "chmod 700".

However, I noticed that during the backup job I get the following message over and over again. "storing login ticket failed: $XDG_RUNTIME_DIR must be set".

Also it would be interesting how I can configure the PBS a mailserver for infomail. I have an extra mail to Telegram container for this. On PVE I only have to adjust the postfix.

Remotes

Cant seem to get 2 docker setups on Truenas Scale to show the remote stores on sync tasks.

Backups Work Flawless to Each Setup, just cant get replication working.

Source Datastore : Communication Failure after 60 seconds when attempting to setup Sync Job

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.