volumerize jobber not working in docker-compose

[bereska]

manual backup with docker exec nextcloud-backup backup works just fine but jobber is not triggered neither with default nor with custom setting https://gist.github.com/bereska/e0586b6062472f4633b2f759c17b648e

[magenticia]

When running command "docker exec volumerize backup" Ihave an error

Also it seems that jobber is not running I have no periodic backups just the manual one that works and only if I run the hole docker run command with all parameters not the shortest one (mentioned above)

[blacklabelops]

@bereska Jobber Cron is out commented in your gist.

[blacklabelops]

@magenticia looks like pydrive api is outdated.

[bereska]

@blacklabelops thank you for the great backup tool and your response. It wouldn't run if uncommented either. This is just the final docker-compose.yml without jobber as it did't work. For now I've ended up with a workaround of running a system backup script as a cron job. Is there a way to debug this jobber not running in docker?

[blacklabelops]

please check for errors when building the image. perhaps there are already installation errors.

you can also check for jobber commands here: https://github.com/dshearer/jobber

[blacklabelops]

I have rechecked the image, looks like Jobber is running fine.

You can test jobber jobs easily from inside the image:

jobber list

List all jobs

jobber test jobName

Test your job

[bereska]

@blacklabelops thank you for the tip. I uncommented - VOLUMERIZE_JOBBER_TIME=0 0 3 * * * in docker-compose.yml and rebuild the image with docker-compose up -d. But it does not seem to have any effect. jobber list inside the container shows NO jobs

[blacklabelops]

If it does not appear in the jobber list it can't be created. Must be the cron time.

You can also put the container scripts in debug mode with the environment variable DEBUG

- DEBUG=true

Try with quotes:

- "VOLUMERIZE_JOBBER_TIME=0 0 3 * * *"

[bereska]

@blacklabelops quotes did not help. https://gist.github.com/bereska/4531031d3342f776fbf3ca020fcb9b79

[blacklabelops]

Yes, it's a bug. I will solve it.

[blacklabelops]

The container only creates the jobber configuration, when the following environment variable is set:

VOLUMERIZE_SOURCE

But this does not work with multiple sources:

VOLUMERIZE_SOURCE1 VOLUMERIZE_SOURCE2

Correct:

Jobber configuration is necessary when then environment variable VOLUMERIZE_JOBBER_TIME is set.

[bereska]

@blacklabelops Danke)