fxp555

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by fxp555

  1. I think this is a known issue: Go to Settings -> Docker -> Disable Docker -> Apply -> Enable Docker -> Apply. Edit: Now that I realized that you already recreated docker.img I am not that sure. You could try disabling and enabling VMs as well.
  2. I disabled bonding some time ago, now the dashboards shows a warning: The diagnostics file was generated after updating to 6.9-beta24. The problem exists also in latest stable release.
  3. After reading that the privacy extension setting should now work I wonderd why I am getting random IPv6 interface identifiers even after updating. Turns out UNRAID uses dhcpcd to get the addresses and there slaac is set to private instead of hwaddr. Maybe it should be considerd to change this by default to hwaddr because it makes it very hard to configure a firewall properly to allow traffic to the UNRAID System. (Or at least provide a option to do so) Uncommenting slaac hwaddr instead of slaac private in /etc/dhcpcd.conf and restarting networking with php -q /usr/local/emhttp/plugins/dynamix/scripts/netconfig eth0 does the trick. See my feature request:
  4. Since it seems UNRAID OS is generating IPv6 interface identifiers randomly (if not let me know how these are actually generated) it would be very nice to add the possibilities to: 1) set the IPv6 address freely (already there) 2) use/enforce DHCPv6 2) use/enforce SLAAC but allow 2.1) setting the interface identifier accordingly to EUI-64 2.2) set tokenized interface identifiers (see man-pages) 2.3) setting the interface identifier randomized
  5. Hi, I have MariaDB running for a private Nextcloud Instance (also linuxserver). When uploading files or gererating thumbnails I am seeing around 80-100MB/s Write-IO on my Cache Drive. Netdata showd that this is caused by the MariaDB cgroup. Is this normal behavior? The DB is only around 200MB, I am wondering where the data gets written. I already played around with some settings in the .cnf file with no luck. Is there something I missed?
  6. One last try could be docker system prune --all --volumes this deletes ALL STOPPED containers, images, volumes. Took my image from 70% to about 15% because of many old volumes.