uroni / urbackup-server-docker-old

Docker image for UrBackup Server

Image to run UrBackup in Docker.

Caveats:

• Image mounting is disabled
• ZFS snapshotting cannot be used

Building

 docker build -t urbackup-server .

Running

 docker run -d --name urbackup-server-1 -v /media/backups:/backups -v /media/database:/var/urbackup -p 55413-55415:55413-55415 -p 35623:35623/udp urbackup-server

BTRFS support

For BTRFS support you have to run the container in privileged mode.

 docker run -d --privileged --name urbackup-server-1 -v /media/backups:/backups -v /media/database:/var/urbackup -p 55413-55415:55413-55415 -p 35623:35623/udp urbackup-server

urbackup-server-docker-old's Issues

Upgrade database failed

Hi. Trying to run this, but get this error. I am on windows 10

docker logs -f urbackup-server-1
2019-01-14 13:04:42: Starting HTTP-Server on port 55414
2019-01-14 13:04:42: HTTP: Server started up successfully!
2019-01-14 13:04:42: Generating Server identity...
Raising nice-ceiling to 35 failed. (errno=1)
2019-01-14 13:04:42: Generating Server private/public ECDSA key...
2019-01-14 13:04:42: Calculating public key...
2019-01-14 13:04:42: Generating Server private/public DSA key...
2019-01-14 13:04:42: Calculating public key...
2019-01-14 13:04:42: Generating Server token...
2019-01-14 13:04:42: WARNING: Upgrading...
2019-01-14 13:04:42: WARNING: Upgrading database to version 8
2019-01-14 13:04:43: WARNING: SQLite: os_unix.c:38287: (22) fsync(/var/urbackup/backup_server.db-mj978EED96C) -  errorcode: 1290
2019-01-14 13:04:43: ERROR: Error in CQuery::Execute - disk I/O error  Stmt: [END;]
2019-01-14 13:04:43: ERROR: SQL: disk I/O error Stmt: [END;]
2019-01-14 13:04:43: WARNING: Upgrading database to version 9
2019-01-14 13:04:43: ERROR: Upgrading database failed. Shutting down server.
Raising nice-ceiling to 35 failed. (errno=1)
2019-01-14 13:05:56: Starting HTTP-Server on port 55414
2019-01-14 13:05:56: HTTP: Server started up successfully!
2019-01-14 13:05:56: WARNING: Upgrading...
2019-01-14 13:05:56: WARNING: Upgrading database to version 9
2019-01-14 13:05:57: WARNING: SQLite: os_unix.c:38287: (22) fsync(/var/urbackup/backup_server.db-mj852506903) -  errorcode: 1290
2019-01-14 13:05:57: ERROR: Error in CQuery::Execute - disk I/O error  Stmt: [END;]
2019-01-14 13:05:57: ERROR: SQL: disk I/O error Stmt: [END;]
2019-01-14 13:05:57: WARNING: Upgrading database to version 10
2019-01-14 13:05:57: ERROR: Upgrading database failed. Shutting down server.
Raising nice-ceiling to 35 failed. (errno=1)
2019-01-15 11:34:25: Starting HTTP-Server on port 55414
2019-01-15 11:34:25: HTTP: Server started up successfully!
2019-01-15 11:34:26: WARNING: Upgrading...
2019-01-15 11:34:26: WARNING: Upgrading database to version 10
2019-01-15 11:34:36: WARNING: SQLite: os_unix.c:38287: (22) fsync(/var/urbackup/backup_server.db-mj3E6C089DE) -  errorcode: 1290
2019-01-15 11:34:36: ERROR: Error in CQuery::Execute - disk I/O error  Stmt: [END;]
2019-01-15 11:34:36: ERROR: SQL: disk I/O error Stmt: [END;]
2019-01-15 11:34:36: WARNING: Upgrading database to version 11
2019-01-15 11:34:36: ERROR: Upgrading database failed. Shutting down server.

file permissions

Hi,
Can you make the user/group urbackup runs as/writes files as configurable? Most dockers let you set PGID and PUID environment variables that are respected and it would be super useful if this did as well because right now it all works great except it's writing files as the UID/GID outside of docker that corresponds to a user/group that isn't in use and it's really messing a bunch of other things up for me.

Thanks

net="host" for client-discovery

if you run the container with the --net="host" Command the server can detect online-clients and doesn´t need to keep the IP-hints forever.
And you don´t need to state the ports with the run-command.

docker run -d --name urbackup-server-1 -v /media/backups:/backups -v /media/database:/var/urbackup --net="host" urbackup-server

how can we enable ssl connection for the web interface outside container?

Hello, most containers I have encountered provide some sort of ssl configuration outside of docker container by passing parameters or mounting some files like certs, htaccess.passwd etc. Could give users some kind of option to configure ssl or provide a ready to use port for that?

start script should be chmod'd in Dockerfile

The execute bit on start is not assured with the current Dockerfile, hence it might happen that it is not executable and the image fails:

docker run -d --name urbackup-server-1 -v  /srv/backups/data:/backups -v /srv/backups/database:/var/urbackup -p 55413-55415:55413-55415 -p 35623:35623/udp uroni/urbackup-server
--
docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"/usr/bin/start\": permission denied".

This is easy to fix with:

diff --git a/Dockerfile b/Dockerfile
index 718778a..e0f21f0 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -30,6 +30,8 @@ RUN echo 'deb http://download.opensuse.org/repositories/home:/uroni/Debian_9.0/
     rm -rf /var/lib/apt/lists/*

 COPY start /usr/bin/start
+RUN chmod 755 /usr/bin/start
+

 EXPOSE 55413/tcp 55414/tcp 55415/tcp 35623/udp

Server shows version 2.3.7 although image contains version 2.3.8

Hi,

I have noticed that my server is informing me about an update to version 2.3.8 (current version shown as 2.3.7). I have therefore pulled the latest image again from DockerHub but the admin page still shows version 2.3.7 in the lower right corner.

Am I missing a step here?

Regards,
Martin

Version tags on docker image

Hi! 👋 It looks like the only version on Docker Hub is latest. It'd be awesome to have latest and version tags like uroni/urbackup-server:v2.3.9.

Is this something that might be possible? 🙏

Thanks!