Allow running borgmatic without root access #50

New Issue

Closed

opened 2018-01-12 06:15:25 +00:00 by gnujedi · 5 comments

gnujedi commented 2018-01-12 06:15:25 +00:00

Copy Link

I recently reinstalled my GNU/Linux machine and to my surprise found that simply running borgmatic yielded Error: No configuration files found in: /etc/borgmatic/config.yaml /etc/borgmatic.d. If I used sudo borgmatic, it would start a backup. Personally, I only want to backup ~/, and I don't want to invoke root privileges. Is there anyway of doing this? I saw the -c method, but I'm also interested in using the systemd.service file to run backups in the background. I could be just missing somethings obvious. Thanks for your time.

I recently reinstalled my GNU/Linux machine and to my surprise found that simply running `borgmatic` yielded `Error: No configuration files found in: /etc/borgmatic/config.yaml /etc/borgmatic.d`. If I used `sudo borgmatic`, it would start a backup. Personally, I only want to backup `~/`, and I don't want to invoke root privileges. Is there anyway of doing this? I saw the `-c` method, but I'm also interested in using the `systemd.service` file to run backups in the background. I could be just missing somethings obvious. Thanks for your time.

witten commented 2018-01-12 06:49:30 +00:00

Owner

Copy Link

As far as I know, running borgmatic as non-root should totally be possible. Your instinct is correct that you'd need to select a non-root configuration file with -c.

I haven't used systemd.service myself, but if it's possible to set that up as a non-root user to run scheduled jobs, then that should work for your needs. I know for instance that crond is configurable as a non-root user.

Let me know if this all works for you or if you run into any roadblocks.

As far as I know, running borgmatic as non-root should totally be possible. Your instinct is correct that you'd need to select a non-root configuration file with `-c`. I haven't used `systemd.service` myself, but if it's possible to set that up as a non-root user to run scheduled jobs, then that should work for your needs. I know for instance that crond is configurable as a non-root user. Let me know if this all works for you or if you run into any roadblocks.

witten added the

question / support

label 2018-01-12 06:49:36 +00:00

gnujedi commented 2018-01-12 19:56:27 +00:00

Author

Copy Link

Okay, I'll do some more testing later today. Question: is running borgmatic supposed to be from an unprivileged user (ie no sudo borgmatic)?

Okay, I'll do some more testing later today. Question: is running `borgmatic` supposed to be from an unprivileged user (ie no `sudo borgmatic`)?

witten commented 2018-01-14 23:56:58 +00:00

Owner

Copy Link

Yes, as far as I know, it should be able to run as a non-root user as long as that user has permissions to do everything it needs to do (read config files, write to the selected Borg repository, etc).

I'll close this in favor of #51, but if you encounter any other issues while running as non-root, please let me know.

Yes, as far as I know, it should be able to run as a non-root user as long as that user has permissions to do everything it needs to do (read config files, write to the selected Borg repository, etc). I'll close this in favor of #51, but if you encounter any other issues while running as non-root, please let me know.

witten closed this issue 2018-01-14 23:56:58 +00:00

gnujedi commented 2018-01-16 02:47:52 +00:00

Author

Copy Link

Thanks for the input. The issue stemmed from running sudo generate-borgmatic-config. It didn't give any account access permission to read the contents of /etc/borgmatic/config.yaml. After comparing the permissions with other directories in /etc (like /etc/apt), I changed the permission to "Access Files" (which is the same as the other directories in the /etc tree). Now, it runs great.

Thanks for the input. The issue stemmed from running `sudo generate-borgmatic-config`. It didn't give any account access permission to read the contents of `/etc/borgmatic/config.yaml`. After comparing the permissions with other directories in `/etc` (like `/etc/apt`), I changed the permission to "Access Files" (which is the same as the other directories in the `/etc` tree). Now, it runs great.

witten commented 2018-01-16 05:08:58 +00:00

Owner

Copy Link

Great, glad to hear it!

Great, glad to hear it!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#50

No description provided.