-
[beta 7.2] Turning on tailscale results in docker not starting
I did a better search. I found this: https://forums.unraid.net/bug-reports/prereleases/720-beta1-breaks-tailscale-r4003/ So wait for beta2 I assume?
-
[beta 7.2] Turning on tailscale results in docker not starting
I’m curious if this is related to the new responsive update. I installed Unraid 7.2 beta 1, and now it seems that in some of my containers, I can no longer activate Tailscale. It throws an error (see example below for SABnzbd). The same issue occurs with other *arr containers as well. I tried cd-ing into the directory mentioned in the error, but it doesn’t exist—so I’m assuming that’s the root of the problem. How should I go about fixing this? Wait for a tailscale update? docker run -d --name='binhex-sabnzbd' --entrypoint='/opt/unraid/tailscale' --net='br0.100' --ip='10.0.100.124' --pids-limit 2048 -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Unraid" -e HOST_CONTAINERNAME="binhex-sabnzbd" -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8090'='8090' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e TAILSCALE_HOSTNAME='sab-test' -e TAILSCALE_ALLOW_LAN_ACCESS='false' -e TAILSCALE_USE_SSH='false' -e TAILSCALE_USERSPACE_NETWORKING='false' -e TAILSCALE_SERVE_PORT='8080' -e ORG_ENTRYPOINT="/usr/bin/dumb-init --" -e ORG_CMD="/bin/bash init.sh" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png' -l net.unraid.docker.tailscale.webui='https://[hostname][magicdns]/' -l net.unraid.docker.tailscale.hostname='sab-test' -v '/mnt/user/data/usenet/':'/data/usenet':'rw' -v '/mnt/nvme/appdata/binhex-sabnzbd':'/config':'rw' -v '/usr/local/share/docker/tailscale_container_hook':'/opt/unraid/tailscale' --cap-add=NET_ADMIN --device='/dev/net/tun' 'binhex/arch-sabnzbd' 2e2849aa42cd2d65b06ee3b8bb903a4b84c6e7c516b82fc96074e1ddb05a76ce docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/opt/unraid/tailscale": is a directory: unknown: permission denied. The command failed.
-
[Support] binhex - SABnzbd
When enabling tailscale (in unraid 7 rc2) it breaks this docker: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-12-27 20:42:27.848045 [info] Host is running unRAID 2024-12-27 20:42:27.875767 [info] System information: Linux ad87d6021abb 6.6.66-Unraid #1 SMP PREEMPT_DYNAMIC Mon Dec 16 16:09:03 PST 2024 x86_64 GNU/Linux 2024-12-27 20:42:27.903309 [info] Image tags: BASE_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=4.4.1-1-01 2024-12-27 20:42:27.934835 [info] PUID defined as '99' 2024-12-27 20:42:27.986736 [info] PGID defined as '100' 2024-12-27 20:42:28.031544 [info] UMASK defined as '000' 2024-12-27 20:42:28.061737 [info] Permissions already set for '/config' 2024-12-27 20:42:28.093931 [info] Deleting files in /tmp (non recursive)... 2024-12-27 20:42:28.184223 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no' 2024-12-27 20:42:28.212182 [info] Starting Supervisor... 2024-12-27 20:42:28,418 INFO Included extra file "/etc/supervisor/conf.d/sabnzbd.conf" during parsing 2024-12-27 20:42:28,418 INFO Set uid to user 0 succeeded 2024-12-27 20:42:28,422 INFO supervisord started with pid 240 2024-12-27 20:42:29,424 INFO spawned: 'start-script' with pid 293 2024-12-27 20:42:29,424 INFO reaped unknown pid 241 (exit status 0) 2024-12-27 20:42:29,509 DEBG 'start-script' stdout output: Not all required Python modules are available, please check requirements.txt Missing module: sabctools You can read more at: https://sabnzbd.org/wiki/installation/install-off-modules If you still experience problems, remove all .pyc files in this folder and subfolders 2024-12-27 20:42:29,510 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-12-27 20:42:29,519 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23088742217920 for <Subprocess at 23088742213552 with name start-script in state RUNNING> (stdout)> 2024-12-27 20:42:29,519 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23088740811152 for <Subprocess at 23088742213552 with name start-script in state RUNNING> (stderr)> 2024-12-27 20:42:29,519 WARN exited: start-script (exit status 1; not expected) 2024-12-27 20:42:29,519 DEBG received SIGCHLD indicating a child quit simply unchecking tailscale fixes this issue. Seems like sabctools is no longer present when enabling TS?
-
{SOLVED} Docker Mac Address
Sorry to kick this old topic. But did you ever find a solution for this? I have the same issue on my unifi controller. No dockers visible.
-
Dockers not showing up on unifi controller
Hi I run my dockers on a separate vlan (100). I can ping these from any computer i.e. ping 10.0.100.200. But they are not showing up in my unifi controller. This controller is running on a UDM pro so not on unraid (docker) itself. I was thinking it maybe had to do because of an invalid mac address so i tried to add it in the extra parameter part of the contrianer. However as soon as i add this the contrainer breaks. Any idea?
-
Moving files on same disk
Yes it is. But no parity.
-
Moving files on same disk
Using mc it is not really faster. Weird. Although it is a slightly older drive i was hoping/suspecting this should go way faster. this is using the "renmove" command inside mc.
-
Moving files on same disk
alright ill give it a try. "DFM does a copy, then remove" is this a safety precaution i assume?
-
Moving files on same disk
In cli for example? mv /mnt/disk1/folder1 /mny/disk/folder2
-
Moving files on same disk
Hello, Total n00b here. But when moving files on the same disk what should be the expected speed? For the record, Im talking about a sata platter drive. No parity active on a ZFS formated drive/share. It should only change the location in the files table not physically move it? I.e. it should be instant? Im seeing 40MB read/writes. Im using the internal file explorer in unraid 7 beta. Moving from /mnt/disk1/folder1/* > /mnt/disk1/folder2/*
lowfi
Members
-
Joined
-
Last visited