• Posts

  • Joined

  • Last visited

About VRx

  • Birthday November 30


  • Gender
  • Location

Recent Profile Visitors

4295 profile views

VRx's Achievements


Apprentice (3/14)



  1. There is no good solution. eth0 inside container is not the same as host interface. You could use host network with zabbix agent container, but macvlan not allow to connect from other vlans/subnets configured on Unraid server, if You use some.
  2. czy polecenie zfs list pokazuje w/w udziały na liście ? jeśli nie to oznacza że to są zwykłe foldery, a nie datasety, musisz je przekształcić
  3. There is an additional change, currently there is no need to define the "Apache log path". Web interface logs currently go to the container (docker) logs.
  4. Application: Bacula - https://www.bacula.org/ Baculum App - https://www.baculum.app/ / Bacularis - https://bacularis.app/ Docker Hub: https://hub.docker.com/r/pwa666/bacula-server GitHub: https://github.com/vrx-666/bacula-server Bacula is a client / server backup application. Baculum/Bacularis is a web application that allows you to easily manage the bacula application. This container combines these applications to form a backup tool with a graphical interface. This container can be run in 5 different versions. Bacula server consists of several components: storage daemon - responsible for saving backups to disk or removable media (tape) bacula director - responsible for the entire backup process, contacts agents on client devices, indicates what resources should be backed up, how and where to send them (storage daemon) file daemon - is a bacula client available for many operating systems, responds to requests from bacula director. A relational database is necessary, where the bacula stores all information related to the performed backups. During installation, you can choose Bacula version 9.6 or 11. Version 9.6 allows you to use the mysql or postgresql database as well as sqlite3. Version 11 allows you to use the postgresql or sqlite3 database. The sqlite3-enabled version is not recommended for larger environments, but allows you to run this application without running mysql / postgresql as a separate container or server. If you already have postgresql or mysql running as your VM or docker application, I recommend choosing this version of the application. If you plan to use the PostgreSQL or MySQL version you should first create an empty database named "bacula", create a password user for that database and grant full privileges to this database for the created user.For mySQL: CREATE USER 'USERNAME' @ '%' IDENTIFIED BY 'PASSWORD'; CREATE DATABASE bacula; GRANT ALL PRIVILEGES ON `bacula`. * TO 'USERNAME' @ '%'; flush privileges; For postgreSQL: create user USERNAME with password 'PASSWORD'; create database bacula encoding 'SQL_ASCII' owner "USERNAME" template = template0; When running container there is some mandatory environment variables. Most important is to set up: SD_Host - should define the IP address at which the Bacula Server will be reachable for computers. If you are using a bridge network this parameter should be the ip of your UnRAID. If you set custom bridge, You shuld type in assigned IP. This variable is passed to the Bacula configuration and later during the backup it is passed to the clients so they can communicate with the Bacula server. The following are necessary when using an external database (postgreSQL, mySQL) DB_Host - database ip DB_Port - database port (could be omitted if default) DB_User - database user DB_Password In addition, there are two important ports that must be exposed: 9095 - Bacula Web 9103 - Bacula Storage The first allows access to the webUI Baculum App. The second is used to receive backups by the server from clients / computers. It can be changed, but you have to change the configuration of Storage Daemon and Bacula Director e.g. via webUI. I recommend that you leave these ports unchanged. There are also necessary paths to folders where configuration files, logs and backups will be saved, these variables are transparent in the UnRaid's docker form, I think that they do not need to be described here. If you have any questions, please ask below. [ Update 2022.05.30 ] End of development for Bacula 9.6 images versions! Older versions of the client work well with the newest server version. The last update of the bacula9.6 code was in December 2020. [ Update 2022.09.15 ] Email notification added. If You want Your's bacula could send emails, first of all You should set container hostname!!! Some of email providers could reject email, if sender will not introduce himself. Container hostname should be Your public reverse dns. Below You have environment variables that must be set to send bacula messages: EMAIL_Recipient - email address where You want bacula send notifications SMTP_Host - address of Your email provider's smtp server SMTP_Port - Your email provider smtp port (check provider documentation) SMTP_User - Email sender login (could be: user@domain or user, check Your email provider documentation) SMTP_Password - Password for email sender account SMTP_Port - smtp port for Your email provider smtp server (check provider documentation) - Yes this is ENV Variable not Docker Port Additionally, it is possible to set email log path pointing to container path /var/log/exim4 [ Update 2022.10.06 ] In the next image update, it will contain postgres client v14.5 (it gives possibility to use a newer version of the postgres server) [ Update 2024.01.02 ] Version 13 available. New Web UI interface Upgrade from version 11 requires change two params: 1. "Bacula WEB port" 9095 -> 9097 (container port) 2. "Baculum config" - path for persistent web configuration: there was /etc/baculum inside container at v11, in version 13 there is /etc/bacularis Be careful, configurations vary! You cannot map the same host folder for /etc/bacularis that was used for /etc/baculum. At the same time, this change forces to create any custom users if you created any in version 11. Unraid template will be updated soon, but it not update if You run it before. [ Update 2024.01.08 ] Postgresql Client v16 Bacularis/Baculum logs redirected to container (docker) logs - no need to bind path for apache (bacularis/baculum) logs
  5. @mikeyosm You could try to bind paths: /usr/bin/sensors from host to /usr/local/bin/sensors /usr/lib64/libsensors.so.5 to /usr/lib64/libsensors.so.5 [RO] And lmsensors should work inside the container
  6. @ars92 It should work if you create the "rpz" zone via webmin as other zones. Yyou would just need to edit the named.conf.options file adding response-policy { zone "rpz_zone_name" }
  7. Oh damn but docker as well as qemu doesn't touch the cache at all. Ddoes this mean btrfs errors are for the server?
  8. Another crash, this time the container that was using all the RAM allocated to it was completely disabled. There is no information about OOM in the logs. I'm curious about your conclusions now Mr @JorgeB wolverine-diagnostics-20230612-0726.zip
  9. And ? After all, containers don't have their own kernel, so how would they have an oom killer. I do not see the connection. There is a limited ram for the container, the container has reached the limit, the process of this container has been annihilated by the oom-killer, everything was done according to the assumptions of docker. Did you find somewhere in the logs that docker daemon was stopped by oom-killer?
  10. OOM is within one container due to the memory limit for this container (8GB), the entire server is 64GB and is far from using all the operational memory.
  11. I have the following problem from time to time. It happens that the problem occurs two days in a row, and then does not occur for a month. wolverine-diagnostics-20230522-1837.zip
  12. So why You are using gui image? Get some bind9 image from docker hub You can try to copy config files. db.local and db.127 are files for loopback interface db.0 and db.255 are for broadcast You can create all of them but are not required to run the container, check their contents, you probably don't have entries there. Maybe you haven't verified yet, but my image doesn't provide any configuration files or zone files. I don't impose any configuration, you can create each zone, including loopback and broadcast, as you wish. The named.conf file also doesn't come with the image, it's only created when you click after logging into the GUI. Bind is very flexible in terms of configuration, you can put the contents of all these files inside named.conf or include hundreds of files if that's more convenient for you. Default configuration depends on the webmin, which in this case acts as webUI. I don't remember if the configuration is different for other base images, I've made some tests on ubuntu, but alpine linux is much smaller. I suppose that the creator of the image you used so far decided for you and used to include several configuration files in his image.
  13. @tuxbass there is no simple way to migrate 1. You should backup Your bind/etc 2. Run container from my image 3. Create config from GUI 4. Create zones 5. Compare and update configuration in named.conf* files 6. Copy CONTENT zone files About Your second question: Host and custom bridge should work properly. Bridge could not work because there is dnsmasq listenning on port 53
  14. official image repository is available low demand end of support
  15. @chaosratt "You may write a command that retrieves the data you need and include it in the user parameter in the agent configuration file ('UserParameter' configuration parameter)." docs "Allowed volumes for the Zabbix agent container /etc/zabbix/zabbix_agentd.d The volume allows include *.conf files and extend Zabbix agent using UserParameter feature." more info So You should add another docker volume /etc/zabbix/zabbix_agentd.d And make some .conf files inside