maaximal / jottadocker Goto Github PK

Thanks for the great docker image!
I just had a successful run on Synology DS916+
Tried many different solutions but yours is the only only works.

Anyway the page on docker hub doesn't have any content, and I was a little bit confused before coming to this github repo.

It'd be really nice if you can copy-and-paste the README content to docker hub. (and only you have the permission to do that)

Thanks for the great work, again!

When scaninterval set to a time, everything works fine.
But when it set to 0 (as mentioned in Document), it shows the error below and stopped backup.

UNABLE TO FIND WATCH FOR /some/path/to/file "/some/path/to/file": WRITE
UNABLE TO FIND WATCH FOR /some/path/to/file "/some/path/to/file": REMOVE

Hi,
I'm trying out your very nice package. Thank you.

I am, however, not able to get it to upgrade to the latest package. The installation starts with jotta-cli 0.7.33634 and it stays there. The console says "jotta-cli is already the newest version (0.7.33634)." when I restart the container but that it not the latest version.

$ sudo docker exec -it jotta /bin/bash
root@jotta:/src# apt list --upgradable
Listing... Done
root@jotta:/src# # apt-get update
[...]
Get:4 https://repo.jotta.us/debian debian InRelease [9417 B]
[...]
root@jotta:/src# apt list --upgradable
Listing... Done  
[...]
jotta-cli/debian 0.8.36055 amd64 [upgradable from: 0.7.33634]
[...]
root@jotta:/src# 

I am wondering if an "apt-get update" is needed in entrypoint.sh before "apt-get install jotta-cli" ?

entrypoint.sh checks "$(jotta-cli status)" =~ ERROR.* to determine if the user is logged in. This does not catch the error output, since this is sent to stderr, not stdout. This was probably changed recently.

jotta-cli status seems to give exit code 0 if it fails, so a more robust version could be

jotta-cli status >/dev/null 2>&1
if [ $? -ne 0 ]; then
  echo "First time login"

Or, to keep the same solution:

if [[ "$(jotta-cli status 2>&1)" =~ ERROR.* ]];
  echo "First time login"

The same problem exists at cliout=$(jotta-cli status | tail -1). It is easy to verify by running jotta-cli status | grep -c OK, which returns "OK" and "0". jotta-cli status 2>&1 | grep -c OK returns 1.