Hello,
sob., 9 mar 2024 o 12:38 Ismael Matos <iabma...@gmail.com> napisał(a):
> Hello all,
>
> First, thanks to Radosław Korzeniewski for helping me with the BPIPE
> plugin. It's working now with the changes of a few things within the
> scripts and the .conf file, as per his suggestions..
>
No problem.
>
> Now, it is the Docker plugin. I've been using Docker Desktop for a low
> priority application and got a container/image running on:
> - Ubuntu 23.10
> - Docker Engine: 25.0.3
> - Compose: v2.24.5-desktop.1
> - Credential Helper: v0.8.1
> - Kubernetes: v1.29.1
> - Bacula: 13.0.4, including the 2 modules of Docker plugin.
> - The relevant section of the bacula-dir file:
> Include {
> Plugin = "docker:"
> Options {
> Compression = "Gzip"
> Signature = "Md5"
> }
> }
>
> When I run a Full backup, I get:
> IMCSERV24 JobId 2131: Error: docker: No Docker containers or objects to
> backup found.
>
Bacula Docker Plugin (AFAIK) uses docker command to manage backup/restore
jobs. This error means the plugin was unable to list containers or images
on your installation.
You can set debug in bconsole:
* setdebug level=500 trace=1 client=IMCSERV24
run backup/estimate job and review trace log created at $WORKINGDIR/*.trace.
In this log you should get info why the plugin is unable to list docker.
But, when I run an Incremental Backup, I also get:
> IMCSERV24 JobId 2129: Error: docker: Unsupported backup level. Doing FULL
> backup.
>
Yes, the docker plugin does not support Incremental level backup for
containers.
> Since the container is actually running
>
show me
> and the Docker plugin starts, I wonder if there is some access
> authorization issue to some resource;
>
Plugin needs the permissions to execute docker command, which needs access
to docker.sock. It could be the main cause of this issue.
> Bacula-fd is running as root, and some Docker processes are running as
> root, while other processes are running with my user (I guess those
> processes are the Docker Desktop front-end).
>
It has nothing to do with docker processes, but the permissions to execute
docker commands and access to docker.sock.
> Still on the Docker, what files can be safely excluded during the
> backups? Suggestions and recomendations are welcome
>
It does not work that way. Docker uses a very different way to execute
processes and access the data.
You can backup docker containers as docker images, no single file backup
possible.
If you need (why?) to backup single files in docker containers then add
bacula file daemon to docker container and do backups (silly idea).
Additionally you can backup docker persistent volumes contents as simple
tar files.
I hope it helps.
--
Radosław Korzeniewski
rados...@korzeniewski.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
