Hey all!

 

I have been using Tailscale on my containers with little to no issues at all until this most recent deployment. It is a container with no stateful disk mapped to the container itself. That being the case, I opened up the advanced Tailscale options and used the setting "Tailscale State Directory:" to define a place for it to create the persistent files for Tailscale (/mnt/cache/appdata/container-name/).

 

My question is first of all, am I using that correctly and is that what it is for?

 

I ask this question, because despite having supplied that path, which does exist and is owned by nobody:users with 777 permissions, no files have been written to that directory. Every time I upgrade or make a change to, and restart the container, I have to re-authenticate Tailscale, delete the old node from the Tailscale console and rename the new one to the proper name without a -1 since it was duplicated.

 

Is there a bug in this feature, or am I using it wrong? I imagine it probably isn't used all that much within the Unraid user base.

 

Thanks for any pointers!

Edited April 15, 20251 yr by harshl

@EDACerton Any thoughts on this? I don't know if you were involved in writing this or not, just saw your sticky post and thought I would see if you had any thoughts?

I had the same Problem.

The path is set wrong, it needs to be the container path.

Found the Solution her:

https://forums.unraid.net/topic/184793-unraid-7-add-container-error-couldnt-detect-persistent-docker-directory-for-tailscale_state/

Edited July 29, 2025Jul 29 by PwnTwoFace