92 likes! so bullish  at this rate i have to do the dac test. i hope my rsync finishes in time
 at this rate i have to do the dac test. i hope my rsync finishes in time 
yikes nearing the end of the video he explains you cannot encrypt the dataset if u didnāt do it when u first made it.
but it allows you to do it for a new nested (though thats not what i want).
i had already restored data, now i have to delete, make the dataset encrypted and restore again? omg 
doing this slowly but looks easy enough to follow along
iām familiar with bind mounts. i used them in portainer for dockers
i hope ix makes this official 
noticed this error message in qnap qts logs for hbs
Encountered error "client_loop: send disconnect: Broken pipe
" Attempting to retry. Error code: 1.
if i am not mistaken this is related to the ssh timing out, so this happens. so what they suggested was, increase the time limit or something.
that said, seems hbs is set to re-attempt connection when something like this happens. so it continued on itās merry way restoring from where it left of. so doesnāt seem to be an issue 
usage is here
tbh i usually find it easier when a youtuber goes through this rather than documentation. in doc they usually just say this does this, or that. but they sometimes donāt give you a real example, so the rest is left to you to figure it out which could be a problem if youāre a newbie like me.
hopefully that is not the case here 
pfsense can do the same thing with its haproxy plugin
You just locally copy (or move) the data from one dataset to another.
Have you got SSH setup to your TNS yet?
u mean for the rsync?
ya⦠sort of 
got it to connect between the ts-877 and the ts-253d to do rsync over port 22.
i wish i could do it without port 22 for faster speed but i donāt know how x-x;
before that i was trying to get rsync to work between the ts-877 and the ts-653a, both using truenas scale rc1 dragonfish.
i think the truenas ssh assist worked, because i see the keypair populate on the other nas as well, meaning the login worked, so they managed to setup the ssh keypair for a successful connection.
i tried a few rsync methods.
rsync module, didnāt work. rsync ssh keypair login? didnāt work.
rsync daemon, got stuck authentication issue. must have messed up on setting that up but i couldnāt figure what i missed or did wrong.
so that is when i went back to trying to get the rsync to ts-253d to work and i figured it out. I simply had to enable ssh for root (not good security but it was what got it to work). Thought i could have ssh to a non root account, but that didnāt work no idea why  If i had to guess, i probly had to do another ssh but using that credentials?
 If i had to guess, i probly had to do another ssh but using that credentials?
anyway waiting for the rsync job to complete shouldnāt be long. i had to redo it because i forgot to enabled change permissions to destination settings. which caused sync to get stuck at 100%
so i did a basic setup for the jailmaker but didnāt start anything. Cauz some part relied on restarting smb, and stuff so i canāt do that mid rsync ongoing 
actually, i enabled smb for the jailmaker. not sure if i am supposed to do that. but i needed to access the share/dataset for the jailmaker where i plan to place my docker configs/files. Only way i know to do that is use file explorer to edit the files in notepad++
yes there is a way to edit via commandline using VI and stuff, but i try to avoid when possible cauz thatās not really my thing 
finally completed
re-running rsync to check if it really 100% copied. this is what i normally do. Run it twice, and if itās all ok, it would quickly go to 100%
in the past in QTS HBS, sometimes you would notice it didnāt quite finishā¦(despite showing 100% the first run) so you only catch that if you had ran it twice⦠go figure 
Use SSH instead of the web gui to login.
Use nano instead of vi. Itās simpler.
Once you have SSH installed you might be able to use Visual Studio Code to edit via ssh, but actually, I think that didnāt work when I tried it last.
last rsync to go. moving my docker container files.
Will delete the container station, donāt need that anymore 
as for how to deploy the dockersā¦
from what i read in the jailmaker instructions, i need to install docker into the jail, and also setup the os (debian?) using the jailmaker script.
That script also sets up the basic networking default it recommends.
The non default networking is a choice between DHCP bridging or macvlans. But iām not sure how to do the DHCP bridging because it seems rather wonky based on the description by the author. Afraid i will be locked out if i mess up, so didnāt dare to do that.
So i will stick to the basic networking using the jailmaker script for now.
I will do that after the rsync, because i imagine it will require restarting certain services or something 
well i have to brush up my commandline then, cause i forgot 
There is a docker template, which sets up Debian instance with docker.
Use that.
But note the current issue with the brand new latest version of docker.
Iād setup a bridge.
Follow this guide:
Then you can put the jail on that bridge (and your TNS is also)
And any VMs you make.
I use a pfsense router for dhcp which means I can set the a MAC address to be static. Most routers/dhcp servers have this feature.
The sandboxes MAC address is hashed from its name, so is stable.
Bridging vs MacVLAN.
As I understand it, when you setup the bridge, itās like making a virtual Ethernet switch inside your NAS, and then every VM, jail, sandbox etc connected to the bridge effectively has a virtual NIC on that virtual switch.
And the VMs can then talk to the host (ie TrueNAS)
Meanwhile, MacVLAN shares a NIC, without the switch. The VMs etc are on the LAN, but not internally connected to the host, and have to communicate via an external switch.
Ie, just use a bridge.
i want to but, based on instructions iām not sure if would be able to 
never had that kind of thing happen in QTS to set bridge or macvlan up (may or may not work, have to try a few times. have to connect nas to monitor even??? wtf xd)
Will see 


 
  

 
  