Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run as particular user #12

Closed
luke-barnett opened this issue Feb 6, 2018 · 3 comments
Closed

Run as particular user #12

luke-barnett opened this issue Feb 6, 2018 · 3 comments

Comments

@luke-barnett
Copy link

By default this seems to be running as the root user, and so creates permissions just for root.

I'm wanting to then sync backup files remotely which requires that a different user is given access to the backed up files. Can we get this so we can specify the user to run the duplicity commands as?

@blacklabelops
Copy link
Owner

I have never tried this. The alpine base image has a script for this. I can try to hook this up.

@blacklabelops
Copy link
Owner

Okay I have tried this but It's not possible. Whereas duplicity is able to run under a specific user, jobber is not able to not run under root.

I will have to replace jobber with crow in order to achieve this.

@sven-weber
Copy link
Contributor

I was facing the same issue today.
I found another solution to make the backup files accessible for synchronization programs.

You can automatically execute a script after the backup was performed which will adjust the file permissions.

Add a Script with the following content:

#!/bin/bash 
echo "Post Execute" 
chmod -R a+rw /backup

This will change the permissions for all files located in the backup folder of the docker container.

This script can then be mounted to the container via the following volume:

-v <localePathToScript>:/postexecute/backup 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants