odarriba
Samba version
Note that all references on the README to docker run commands are not valid yet as the image is not pushed, so you have to build them locally in order to test it.
Solves #41
Container seems to work fine with samba btw. I tested it and works just fine by following the instructions in the new README. I didn't try an upgrade afs->smb since i didn't haven an afs to begin with.
Tried this branch last weekend, works great. The only issue is one missing part in the documentation. If you dont use timemachine as the share name you need to update the avahi services config.
Thanks for this :)
I downloaded the .zip and trying to compile the image and run the container for RPI but always get: docker: invalid reference format.
I downloaded the .zip and trying to compile the image and run the container for RPI but always get: docker: invalid reference format.
I have to rectify, now everything works but: My Mac sees the drive mounted (through finder) at the correct smb://Time Capsule of mine/TimeDrive
Time machine app settings displays the hostname address like: smb//raspberrypi.local/TimeDrive
Is this normal? Anyway, when I add it through time machine settings, and then mount it by finder as a drive on desktop, even in time machine app it Is being loaded the custom HDD icon drive I chose, so this is sign the drive is seen as unique, despite of different smb addresses.
The only problem I'm experiencing is that when flagging "encrypt backups", then I have on desktop two mounted drives that are the same... without flagging it I can see for 2 seconds a drives that appears on desktop named TimeDrive-1 and the in disappears automatically.
And additionally it seems that if I don't manually mount the drive through finder before setupping encrypted time machine, the latter then mounts it by itself only one time and it is correct.
I don't know if any other of you is experiencing a set behaviour and it is osx and finder bugging
Okay, one update regarding the home folder showing along the drive, in the avahi config one line is required to force the shares enumeration by the NetShareEnumAll IOCTL, 0x100 :
<type>_adisk._tcp</type>
<txt-record>sys=waMa=0,adVF=0x100</txt-record>
<txt-record>dk0=adVN=TimeMachine,adVF=0x82</txt-record>