nerbonne

Thanks. Can't remember why I was using folders over the image. I changed it to the image and pulled the containers down again. I appreciate it.

To be fair, the linked guide does not cover docker directories and there is no delete button.

Hello, i'm receiving this error when trying to re-install a previous container. "docker: Error response from daemon: Failed to create btrfs snapshot: invalid argument" docker run -d --name='brave-frontier' --net='br0' --ip='10.10.11.89' --pids-limit 2048 --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="ISOT0" -e HOST_CONTAINERNAME="brave-frontier" -e 'TCP_PORT_5800'='5800' -e 'TCP_PORT_5900'='5900' -e 'DISPLAY_WIDTH'='1920' -e 'DISPLAY_HEIGHT'='1080' -e 'VNC_PASSWORD'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5800]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/P3R-CO/unraid/master/Brave-P3R-256px.png' -v '/mnt/user/appdata/brave-frontier':'/config':'rw' -v '/mnt/user/appdata/brave-frontier/downloads':'/Downloads/':'rw' --shm-size=2g 'p3rco/brave:latest' docker: Error response from daemon: Failed to create btrfs snapshot: invalid argument Run 'docker run --help' for more information The command failed. The cache drive is formatted as encrypted btrfs, it's been that way for over a year. I am still using USB boot. I am using docker folders not docker img. Google searches recommend changing the format to xfs but it's odd it would have work fine and now I need to change the format? No errors in the syslog and a btrfs scrub completed with no errors. Cache drive has 450 Gb of 500 Gb free, no smart errors and 85% life left. Attached are diags. Thanks for the help! isot0-diagnostics-20260705-2023.zip

I run multiple unraid servers and I'm curious why there is no samba container. The issue I'm facing is that if the server that has samba shares goes down, I can bring up samba on a new server but then the IP address is different and I have to go around changing mappings on PCs. If it were a container, I could have it use a static IP regardless of what physical server the samba share is up on. Local DNS is really an option as some users access the share over tailscale (I know, it's a terrible experience). Thoughts on how to keep the samba share IP static during server changes?

I commented out the Monitor Service and the log entries stopped. The screen no longer works so thats kinda sucky. Anyone planning to buy a lincstation be aware you can have a working status screen or a clean system log.

Thanks all. I found the go file and the LincStation S1 has alot of stuff in that shipped with it. I assume it's to power the small LCD touch screen that comes with it. I'll comment the items out one by one and see what happens.

This is the go file on my main server: And this is the LincPlus LincStation S1:

I just setup my 4th unraid server and I'm seeing this scroll thru the logs constantly, never seen this before. Does anyone know why? It's a LincPlus LincStation S1. May 7 22:46:12 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 7 22:46:12 Tower sudo: pam_unix(sudo:session): session closed for user root May 7 22:46:12 Tower sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl --scan May 7 22:46:12 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 7 22:46:12 Tower sudo: pam_unix(sudo:session): session closed for user root May 7 22:46:19 Tower sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/lshw -json -c video May 7 22:46:19 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 7 22:46:21 Tower sudo: pam_unix(sudo:session): session closed for user root May 7 22:46:22 Tower sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl --scan May 7 22:46:22 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 7 22:46:22 Tower sudo: pam_unix(sudo:session): session closed for user root May 7 22:46:22 Tower sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl --scan May 7 22:46:22 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 7 22:46:22 Tower sudo: pam_unix(sudo:session): session closed for user root May 7 22:46:23 Tower sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/lshw -json -c video May 7 22:46:23 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 7 22:46:23 Tower sudo: pam_unix(sudo:session): session closed for user root May 7 22:46:32 Tower sudo: root : PWD=/ ; USER=root ; COMMAND=/usr/sbin/smartctl --scan

Does this error mean my json file is incorrect? The subdomain to be updated is 4.domain.com

I just installed this container and the web gui isn't working. I don't see any errors in the container log or the system log. On first run, the container log indicated that database setup went ok. I'm very confused.

I have 3 unraid servers, slackpkg does not exist on any of them. root@:~# slackpkg bash: slackpkg: command not found root@:~# You didn't say un-get, you said nerdtools. Please don't put out bad info then attack me like I'm the problem.

Sorry off topic, but can you tell me how you are getting iftop via unget?

Is this like chatGPT or something? slackpkg isn't a command that runs on unraid and NerdTools is deprecated in unraid 7

Ok, so for anyone else having this issue, here's what worked. Stop the array, change ipvlan to macvlan in the docker settings, and then reboot. After reboot and starting the arrays and containers, open terminal and type "docker network inspect br0". Find the mac address assigned and add a static lease in the OPNsense router. Then the container can ping the router and vice versa.

Thanks for the help! Here are the answers. have you enabled host access on custom networks? A. yes, checked and verified. in opnsense is the network lan or vlan ? By default inter vlan is blocked. A. lan. what mode is your ipvlan network L2 or L3 ? A. I don't understand this question, it's whatever the setting in Settings -> Docker is. what is your network address ? what is the result of docker network inspect br0 ? A. My lan network is 10.10.6.0/23. The router is 10.10.6.66, the unraid host is 10.10.6.2 and the container that cannot be pinged is 10.10.6.180. I also have a pi-hole at 10.10.6.25 but I doubt this has anything to do with it. Docker inspect shows ipvlan but thats because I changed it back so that my containers would start. When you switch from ipvlan to macvlan in unraid you have to check if your ipvlan network still exists. You can't have overlapping networks. A. I don't understand what this means, its only a drop down and can only be one or the other. Do I need to delete the network config and reboot?