Part 2 - Setting up DDNS, Reverse Proxy and SSL. Part 1 - Setting up the container via the DSM GUI. It is a great way to self-host a password manager it gives you complete control over your passwords and allows you to have automatic syncing across web, desktop and mobile apps. It is compatible with all the official Bitwarden apps and Browser extensions. Vaultwarden is a rewrite of the official Bitwarden server using the Rust language, it was created to reduce the need for the number of containers required for the official server. Historic updates now at the end of the guide. Tailscale: Remote Access to Synology and Its Services Made Easy. Step 3: Setting Up a Docker Bridge Network. Deluge with GlueTUN VPN in ‘Container Manager’. qBittorrent with GlueTUN VPN in ‘Container Manager’. Step 3: Setting Up a Docker Bridge Network in Container Manager. Step 2: Setting up a restricted Docker user and obtaining IDs. Updating Containers in Container Manager. DSM 7.2 Container Manager open child menu. The end goal here is for Pi-Hole to do my DHCP and so that I can see the dynamic hostnames instead of inputting them manually into the /etc/hosts file. For the most paranoid, it should even be possible to explicitly drop the NET_RAWĬapability to prevent FTLDNS from automatically gaining it." However, if DHCP and IPv6 Router Advertisements are not in use, it should be safe to skip it. This image automatically grants those capabilities, if available, to the FTLDNS process, even when run as non-root.īy default, docker does not include the NET_ADMINĬapability for non-privileged containers, and it is recommended to explicitly add it to the container using -cap-add=NET_ADMIN : we need to be able to change ownership of log files and databases in case FTL is started as a different user than pihole : FTL sets itself as an important process to get some more processing time if the latter is running low : modify routing tables and other network-related operations (in particular inserting an entry in the neighbor table to answer DHCP requests using unicast packets) : use raw and packet sockets (needed for handling DHCPv6 requests, and verifying that an IP is not in use before leasing it) : Allows FTLDNS binding to TCP/UDP sockets below 1024 (specifically DNS service on port 53) PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47ĭo I need to have these in somewhere ? If so, where ?ĭNSMasq / FTLDNS expects to have the following capabilities available: However, I now get this when disabling the DHCP capability from my router and enabling the one from the Pi-Hole: 
Which I have resolved by changing the username environmental variable to root as per here: How can I have Pi-Hole doing DHCP via Docker on my Synology NAS ?ĭNSMASQ_CONFIG FTL failed to start due to process is missing required capability NET_ADMIN
0 kommentar(er)
