Thanks for the help. It now seems to work correctly for connecting remotely. It still wouldn't work on my local network on devices without tailscale, but after installing tailscale on the pc I use most frequently it now works there too. So I guess I'll call that good enough, and once again I really appreciate the help.
Ya that’s not what happens. Only devices authorized to your Tailscale can reach your LAN but whatever you feel comfortable with.
Ya that’s not what happens. Only devices authorized to your Tailscale can reach your LAN
Thanks for this. I ended up going with your method of setting up the subnet routing, as I was still having some other issues. It took a few tries to find the right way to set it up in the NAS. But I was able to get there eventually mostly following this info from Tailscale on setting it up. Seems like everything works great now. And once again, I really appreciate those of you who took the time to help me out.
1 Like
So, not sure what I am missing and I am sure there is something I am doing wrong on the setup step in the webui or something else I am supposed to add in the docker compose?
If I set it up and then restart docker fully or restart my computer that docker is running on, the data doesn't persist. I tried looking it up online but I don't really see any documentation for this after it's initially setup. So, basically, if I setup everything after I restart docker I have to do the whole setup in the webui again.
I have tried two methods of setting this up - using project one-click in Olivetin and directly installing in Portainer with the docker compose at the top of the page.
The most likely thing with what you're describing is that your HOST_DIR value isn't valid. This is a parent directory for sub-directory called organizr, and that parent must be a valid, writable location.
Ok. No idea where to find that.
What OS does your Docker host run?
EDIT: I see in the YouTub3r thread that you're running Windows.
@jasonmcroy In the Windows world, you can use either Linux paths (if you have a WSL Linux distro installed -- like Debian or Ubuntu) or Windows paths. Ideally you do, but some people don't, and others are using Windows 10 still where Docker Desktop WSL integration can become corrupted.
So, if HOST_DIR=/data isn't working, you can use a Windows path. Usually, you can set this value to same one you used for OliveTin, then under that parent you'll have one directory called olivetin and another called organizr.
Thanks. I will see if I can figure that out. Out of curiosity, when I try to install it via olivetin one-click, a pop-up window allows me to input 4 or 5 fields. One of them is listed as persistent data. I assume that is the path we're talking about. So, could I create a folder on my hard drive as well and use that windows path there?
By the way, I am on Windows 11 and all I did was install Docker Desktop then Portainer (not the extension). Not sure if that data helps you explain this to me. I believe I am using WSL (I recall selecting that somewhere) and the Docker is set to use Linux containers.
That tells us you don't have a WSL Linux distro installed. Not ideal, but not a big deal either. We may have to experiment with a couple of paths to see what works.
I'd first look in your OliveTin stack and see what value you used for HOST_DIR there, as it'd be best to use that same value. Otherwise, I'd think something like /mnt/c/data or /mnt/d/data (if you have a D: drive). But, as I said, check your OliveTin value first and let me know what you used there.
Thanks again for your direction on this.
In the editor section of the stack there is this line:
volumes:
- ${HOST_DIR}/organizr:/config
Then, in the environmental variables section using the advanced tab I see: HOST_DIR=/data
This is using the one-click button in Olivetin
Well, we'll fix a couple of things then, as your OliveTin data wouldn't per persistent either. Let's get organizr done first, and then we'll fix Olivetin.
Try something that starts with /mnt/c or /mnt/d (if you have a D: drive), and then check and see if a directory called organizr was created in that location. So, if you use /mnt/c/data, look on drive C: for a path of C:\data\organizr. If that doesn't work, try C:/data to see if that creates the directory we're looking for...
Ok, I used /mnt/d since I do have a d drive. I updated the stack and when I navigate to that folder via the linux path in explorer I do now see it created a folder there callled organizr. There are folders in that folder as well. Here is a screenshot:
However, it seems the data is still not persisting as when I do the setup page in the webui for organizr, then restarts Docker then go back to the Organizr page it starts at the window for me to set everything up again.
docker-desktop is not a real distro, it's kind of a very stripped down version of Linux. You don't want to use that. If you had a real distro, you'd see linux/debian or linux/ubuntu.
Try the other approach I suggested using D:/data as the HOST_DIR value. Then look on your D: drive for \data
Well, that did indeed create a data folder on the D drive and an Organizr folder in there with more folders in it. However, the stack shows as unhealthy in portainer:
One additional piece of data - I do use Stablebit drivepool. Not sure if that may cause an issue. I am going to try using my C drive and see if that works better.
I wonder if I should just install a linux distro to use like you mentioned above.
Click the refresh button next to where it says Container list. It takes a minute for that container to show healthy.
Aha. You're correct. It now shows healthy.
I'd recommend that in the long run, as the best way to run Docker Desktop and WSL. You can get the Debian distro from the Microsoft Store when you're ready.