May 6, 20242 yr Hi all, I was cleaning up some docker networks I had created on my unraid box and in the process deleted the br0 docker network. Is there a way to get it back? I tried re-adding the bridge with the below command. That took my server networking down until I deleted the docker network. docker network create -d bridge --subnet=192.168.0.0/24 --gateway=192.168.0.1 br0 I also tried clearing out the docker networks with the below without any effect: rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart Finally, I tried deleting the network.cfg with, which also had no effect: /boot/config/network.cfg Any suggestions? I want to set up a docker container with a dedicated IP address, which is how I noticed I'd deleted br0. I'm running Unraid Pro 6.12.10. Thanks, Ben Edited May 6, 20242 yr by BenjaminMetzler Add unraid version
May 6, 20242 yr Community Expert to reset the docker networks you need to clear another file. br0 is also created via unraid not docker. turn off dockers, turn off vms go to network settings and turn off bridging and turn off bonding. then delete the network config to rebuild teh network along with the docker database file.. Quote 2. In unraid console remove the docker network database : rm /var/lib/docker/network/files/local-kv.db Reboot server Fix network settings reboot again then enable docker with setting you want.
May 6, 20242 yr Community Expert There are quite a few networking commands. to make br0 or a bridge interface.... brctl addbr br0 ip link set dev <tap-iface> master br0 ^replace <tap-ifcae> with interface you want ie eth0..... to show the bridges: bridge link show we have prepackaged tools ifconfig, ip and brctl for networking in unraid... Edited May 6, 20242 yr by bmartino1 can't type
May 7, 20242 yr Author Well, I got it working, though now I have an eth0 instead of a br0. I'm sure my system is in some weird state now, completely off what the Unraid developers designed. I'll plug at it a bit more after I create a backup and feel a bit safer. Is there a way to do a soft-reset, resetting unraid without losing the data? I'd like to get back to a factory default state and start building things again.
May 7, 20242 yr Community Expert kinda. Do at your risk kind of thing. First, make a usb backup. Main Flash Everything that is Your Unraid system is in the config folder. Pools, disk configuration, templates, plugins etc... Including your UIUD key! *if you format the same drive the UUID is the same. the key is still valid for the new flash format of the same USB disk. With the backup created. Format the usb and make a fresh unraid and copy the entire config folder from that backup. Its been a while and pulling from new and old notes and my experiences: iscsi is the folder from the iscsi plugin... modprobe.d is info on vfio/custom modprobe configs. Plugins is all you currently installed plugins plugin-erros are bad plugins that limetech said failed and moved their plugins-removed are dead plugins that failed pools folder is info on you unraid disk layout shares are your samba shares settings. ssh is you info for the sshd daemon ssl is your inform and certificate for your device. wiregurad is the config data for unraids openvpn *.key is you license file tied to the uuid. I have a basic grandfathered license. disk.cfg is the settings in the webui that auto start the array disk.old is a backup of the disk config settings docker.cfg are the docker web ui settings domain.cfg are the qemu/kvm web ui settings drift is - couldn't figure it out... may be disk related... editor.cfg is a webui file for mime types flash.cfg is the smb share setting. foresync is the file used for parity and is disk related go is a script file at preboot to run other setting. this also started the webui back end service for unraid. hosts is a custom file that I use to replace the unraid host file ident.cfg is a disk/array needed file that identifies what disk is what. machine-id is a unraid file used in NetBIOS/smb network.cfg is your saved network settings - i would delete this! to make sure you get a proper setup... parit-check.log log is a log passwd is the root password file delete to regain access to unraid root user also continues password of other users added random-seed is a p rng used with encryption like ssh and other processes this is your mod p secrets.tbd is the database for login credentials and hashes shadow is a disk unraid file of data share.cfg is the web ui for disk share and smb may be added form unassigned plugin smb-extra is the webusi for samba extras smb-overide is my user script to replace and set specific smb settings i want to run on my network smb-conf is a backup of unraids original smb config i made... smbpasswd is you share users and access to unraids smb super.dat is required to maintain your disk configuration super.old is a previous disk configuration and is needed to maintain you disk configuration vfio-pci.cfg is the bind for vm/hardware passthrough You may have other or different files. Since Unraid is a mutable OS. similar to have to delete the database file for the docker networks, there is a database file for network configs. I don't know where it is at! as such, a fresh format and a copy of your config folder should be fine with no data loss. Do at your own risk.
May 7, 20242 yr Community Expert 16 hours ago, BenjaminMetzler said: Well, I got it working, though now I have an eth0 instead of a br0. I'm sure my system is in some weird state now, completely off what the Unraid developers designed. I'll plug at it a bit more after I create a backup and feel a bit safer. Is there a way to do a soft-reset, resetting unraid without losing the data? I'd like to get back to a factory default state and start building things again. in truth, you can stop all dockers. Delete that network and recreate a docker macvlan network... https://docs.docker.com/reference/cli/docker/network/rm/ https://docs.docker.com/network/drivers/macvlan/#:~:text=To create a macvlan network,through on the Docker host. docker network create -d macvlan \ --subnet=192.168.1.x/24 \ --gateway=192.168.1.1 \ -o parent=br0 pub_net ^Which has been known to cause macvaln trace kernel panics... this is why bridging is off... if bridging is off and bonding is off that is normal to see as the default custom docker. Edited May 7, 20242 yr by bmartino1
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.