On 11/19/2024 at 8:26 PM, ich777 said:

I assume your path to the mount or better speaking share is /mnt/user/... correct? If you move data from one Dataset to another use the real file path /mnt/diskN/... or the real path to the location where the folder is located, I assume something checks the space and it couldn't find any available space or it might want to go through the cache, I'm not too sure what could cause this.

Yes, you are right. That works. Not on user level, but on pool level, resolves the issue

How can the ports be mapped using the RustDeskServer-AiO container?

 

I'm trying to specify an ip on my custom network, like normal when setting up containers.

 

The ports are only mapped when using the Bridge network, and those are internal docker ips.

 

 

Also, using network Host doesn't map ports.

 

Edit:  Well, it works using host even without ports mapped, but doesn't with custom bridges.

Edited December 8, 20241 yr by jenga201

35 minutes ago, jenga201 said:

Well, it works using host even without ports mapped, but doesn't with custom bridges.

It does actually work with all networks but on host and custom br0 the ports aren‘t listed with my containers (that‘s by design in my containers. Actually the Unraid Docker page lists the ports wrong when using host and custom br0 networks <- this is fixed in Unraid 7.0.0-rc.1 and will show „all“).

 

Anyways when using the host network you have to use the default ports from the template alongside with the host IP, when using a custom br0 network you have to use the default ports in the template alongside with the specified fixed IP from the template.

Please note that port mappings with custom br0 containers are not honored and you always have to use the default ports because a custom br0 network sinply exposes all ports from the container and port mappings from the Docker template in Unraid are not working.

 

…and no there is no webinterface because this is just the Server part from RustDesk.

Hi.

I've setup a pool-to-disk manual Sync using DirSyncPro, before seeing your post mentioning it's no longer supported as the main site is down.

I noted you also have luckyBackup, which seems to be able to do the same thing - although it seems to have less settings/features, didn't dig too much into it but it seems it will also serve me.

 

Is there a problem if I keep using DirSyncPro? Any benefit to change to luckyBackup?

 

Thank you.

1 minute ago, ffleps said:

Is there a problem if I keep using DirSyncPro? Any benefit to change to luckyBackup?

No, use whever you prefer most, non of the two applications are actually receiving updates any more, but that doesn't mean that the container doesn't get updates.

 

DirSyncPro is still the prefered application by many users, luckyBackup is "just" a fancy gui for rsync.

I would like to back up the directories to an external HDD. 
The disk is formatted via UD to xfs and can also be found in unraid under mnt/disk/.
Only luckybackup does not show me the disk.
I had also passed it through in the container as device sde.
Why doesn't it show me the disk from Destination?

 

or is dirsync better suited for this? The program shows me the disk

Edited December 9, 20241 yr by hYtas

5 hours ago, hYtas said:

and can also be found in unraid under mnt/disk/.

may a typo ? should be /mnt/disks/...

 

and yes, lucky is also just a docker and mounting is the same as on any other, may rather post

 

1/ your docker run <<click<< from luckybackup

2/ the output from ls -la /mnt/disks/

9 hours ago, hYtas said:

Only luckybackup does not show me the disk.

Please post a screenshot from your Docker template and also from the mount point that are you using in your Docker template.

If anyone else is having issues with the stun-turn server here is how I set mine up. The one issue I really found is that nextcloud never gave me a good test for the turn server, however I was able to test my instance and verify it was working with my settings. Here is everything I did to make it work.

 

Unraid Stun-Turn-Server With NextCloud Talk Instructions

 

This assumes that you already have a working nextcloud installation with correctly working reverse proxy.

 

1.     Install and configure the Stun-Turn-Server Docker Container

         a.     Install Stun-Turn-Server from community applications

         b.     It is suggested to use a custom IP address for this docker container. This will make port forwarding easier and.                        you don’t have to worry about conflicting IP addresses and ports.  

         c.     Read through the different options when installing, but you will need to change the following.

                    i.     Static Secret – follow the instructions as listed. Keep this value as it will need to be used later in the.                                        nextcloud instance.

                    ii.     Realm – In most cases this should be the same as your reverse domain name for you nextcloud                                                instance that points to your public IP. In my example it is: turn:nextcloud.yourdomain.com

                   iii.     Certificate Generation – Country – Put in your two character country code. For United States it will be: US

                   iv.     Certificate Generation – State or Providence– Put in your state or providence

                   v.     Certificate Generation – Locality – A more specific location than state or Providence

                   vi.     Certificate Generation – Origination – What the nextcloud instance is called

         d.     Those should be all of the required values. Apply the config and allow the docker to pull down

2.     Port forward UDP and TCP port 5349 from your firewall to the custom IP used for the Stun Turn server. It is suggested to use this port but it can be changed if needed. The exact steps to port forward depend on your network configuration and firewall. I won’t cover the specific steps for this.

3.     Test the server is working correctly

        a.     Visit the website below to test the server: https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

        b.     Click on the default stun server and remove it.

        c.     In the STUN or TURN URI input the following values individually then click add server. Note for my instance I’m                          using the default stun server. I was not able to get the installed server stun option to work.

                  i.     stun: stun.nextcloud.com:443

                  ii.     turn:nextcloud.yourdomain.com:5349

        d.     Scroll down to ICE options, and use all IceTransport Values

        e.     Click gather candidates

        f.      If successful you should see multiple hosts listed for UDP and TCP as well as your public IP address as srflx                              type. The hosts indicate a working turn server and srflx with IP address indicates a working stun server.

4.     Nextcloud Integration

        a.     Login to your nextcloud account as admin.

        b.     Go to admin > administration settings > Under administration go to talk

        c.     Scroll down to STUN and TURN server settings

        d.     For Stun I’m using the default: stun.nextcloud.com:443

        e.     For TURN fill out the fields as follows:

                i.     Turn and Turns:

                ii.     Turn server URL:

                        1.     nextcloud.yourdomain.com:5349

                iii.     Turn Server Secret:

                        1.     The value from step one that was generated with a terminal command.

                iv.     UDP and TCP

         f.      NOTE: During my setup I was not able to get a successful test using the button next to the UPD and TCP                                selection. There may be a bug with how it operates. I was able to verify correct operation through various tests.

 

There is a good chance I did something wrong but I will update this as I get feedback. In the mean time I hope it helps others with confusion they may have.

13 hours ago, ich777 said:

Please post a screenshot from your Docker template and also from the mount point that are you using in your Docker template.

sde = external HDD

fileformat is xfs

 

Dirsnycpro external disk path:

Edited December 10, 20241 yr by hYtas

23 minutes ago, hYtas said:

Dirsnycpro external disk path:

 

you add in lucky as device and not as path ... and as /dev/sde ...

 

just use like in dirsync pro and as path like

 

/mnt/disks/JMicron_Generic/ <> /external_disk

 

then you can access the drive in lucky by /external_disk ...

 

or as often recommended, just use /mnt <> /mnt ... so you have the same path inside the docker like on host ...

It now works with the path.
Thanks

What are the pros and cons of luckybackup and dirsyncpro?

I just want to make a daily nightly backup to the Synology NAS and occasionally to an external drive

7 hours ago, hYtas said:

What are the pros and cons of luckybackup and dirsyncpro?

Please see this post:

 

Debian bookworm 

can this container use nvidia gpu ?

I also have Lxc container , but im not getting how to use gpu in that

41 minutes ago, drmetro said:

can this container use nvidia gpu ?

No.

 

41 minutes ago, drmetro said:

I also have Lxc container , but im not getting how to use gpu in that

Please see the pinned posts on top of the thread:

 

4 hours ago, ich777 said:

No.

 

Please see the pinned posts on top of the thread:

 

I have docker containers using gpu so if i turn on lxc linux container with gpu support will the gpu automatically switch to lxc container or it will cause crash ?
 

43 minutes ago, drmetro said:

I have docker containers using gpu so if i turn on lxc linux container with gpu support will the gpu automatically switch to lxc container or it will cause crash ?
 

If the container doesn‘t support HW acceleration it won‘t work anyways however if you have multiple containers, regardless if they are LXC or Docker you won‘t crash your host.

Does the ubuntu lxc container have webUi ? If not which lxc container have webui 

5 minutes ago, drmetro said:

Does the ubuntu lxc container have webUi ? If not which lxc container have webui 

LXC containers are always as light as possible and come with pretty much no packages/dependencies installed, so to speak, no they doesn't have a WebUI, non of theme comes with a WebUI.

 

Can you please go a bit more in detail what you want to do or what you want to accomplish?

7 minutes ago, ich777 said:

LXC containers are always as light as possible and come with pretty much no packages/dependencies installed, so to speak, no they doesn't have a WebUI, non of theme comes with a WebUI.

 

Can you please go a bit more in detail what you want to do or what you want to accomplish?

I plan to use the lxc container to run AI apps and OCR apps which require gpu and having a webui would have been more helpful 

 

9 minutes ago, ich777 said:

LXC containers are always as light as possible and come with pretty much no packages/dependencies installed, so to speak, no they doesn't have a WebUI, non of theme comes with a WebUI.

 

Can you please go a bit more in detail what you want to do or what you want to accomplish?

Initially i was planning to do it on VM but i have only one GPU in my system ( no igpu) , and its used by unraid and dockers and if I start the VM with gpu without vfio bind and reboot everything crashes… there is no way the gpu can switch from dockers to vm .. so i am thinking of using LXC container for the same

2 minutes ago, drmetro said:

I plan to use the lxc container to run AI apps and OCR apps which require gpu and having a webui would have been more helpful 

 

The WebUI won't help because you most of the times have to interact with the console anyways.

 

Just pass through the GPU to the container and start installing whever you need, are you sure that there aren't any Docker containers out there with the apps you want to use? Most of them even have GPU support baked into them.

 

However I think you should first look into what suits you the best and then continue the conversatzion because this is also the wrong thread if you where thinking about LXC.

Hi

 

Where is the correct location for me to save the DirSyncPro jobs I create to make sure they don't disappear??

 

I saved my job at the normal location that appears when you hit Save inside the tool (it shows as /dirsyncpro, which if I understood correctly it's actually /mnt/local?) 

Clearly this isn't a good place because 2 days after the job disappeared and the docker has the default "job" only when opening it (I think the tool was auto-updated or something? Or was my other plugin Fix Commons Problems?)

 

On the app settings source directory is /, and data is /mnt/local.

 

Sorry if this is a stupid question, I'm new to this stuff.

 

Thanks