QuarantineDrive Posted December 31, 2022 Share Posted December 31, 2022 There's been quite number of frequent updates but I could not find any details about the changes. Is there any way to look up update/change logs? Quote Link to comment
QuarantineDrive Posted January 2, 2023 Share Posted January 2, 2023 Hmm another update. It is almost updating every 1-2 days. However, running the following command for the docker image history shows no changes between the last 2 updates. docker history mbentley/timemachine Before the update: # docker history mbentley/timemachine:latest IMAGE CREATED CREATED BY SIZE COMMENT 7d2f0320dc4a 2 weeks ago CMD ["s6-svscan" "/etc/s6"] 0B buildkit.dockerfile.v0 <missing> 2 weeks ago ENTRYPOINT ["/entrypoint.sh"] 0B buildkit.dockerfile.v0 <missing> 2 weeks ago VOLUME [/var/lib/samba /var/cache/samba /run… 0B buildkit.dockerfile.v0 <missing> 2 weeks ago COPY entrypoint.sh / # buildkit 15.7kB buildkit.dockerfile.v0 <missing> 2 weeks ago COPY s6 /etc/s6 # buildkit 669B buildkit.dockerfile.v0 <missing> 2 weeks ago RUN /bin/sh -c apk add --no-cache attr avahi… 96.3MB buildkit.dockerfile.v0 <missing> 2 weeks ago LABEL maintainer=Matt Bentley <mbentley@mben… 0B buildkit.dockerfile.v0 <missing> 3 days ago CMD ["/bin/sh"] 0B buildkit.dockerfile.v0 <missing> 3 days ago LABEL maintainer=Matt Bentley <mbentley@mben… 0B buildkit.dockerfile.v0 <missing> 3 days ago COPY / / # buildkit 7.04MB buildkit.dockerfile.v0 After the update: # docker history mbentley/timemachine IMAGE CREATED CREATED BY SIZE COMMENT 48b195cf362a 2 weeks ago CMD ["s6-svscan" "/etc/s6"] 0B buildkit.dockerfile.v0 <missing> 2 weeks ago ENTRYPOINT ["/entrypoint.sh"] 0B buildkit.dockerfile.v0 <missing> 2 weeks ago VOLUME [/var/lib/samba /var/cache/samba /run… 0B buildkit.dockerfile.v0 <missing> 2 weeks ago COPY entrypoint.sh / # buildkit 15.7kB buildkit.dockerfile.v0 <missing> 2 weeks ago COPY s6 /etc/s6 # buildkit 669B buildkit.dockerfile.v0 <missing> 2 weeks ago RUN /bin/sh -c apk add --no-cache attr avahi… 96.3MB buildkit.dockerfile.v0 <missing> 2 weeks ago LABEL maintainer=Matt Bentley <mbentley@mben… 0B buildkit.dockerfile.v0 <missing> 3 days ago CMD ["/bin/sh"] 0B buildkit.dockerfile.v0 <missing> 3 days ago LABEL maintainer=Matt Bentley <mbentley@mben… 0B buildkit.dockerfile.v0 <missing> 3 days ago COPY / / # buildkit 7.04MB buildkit.dockerfile.v0 Am I missing something? Quote Link to comment
Linxawakening Posted January 3, 2023 Share Posted January 3, 2023 On 12/31/2022 at 4:35 AM, QuarantineDrive said: There's been quite number of frequent updates but I could not find any details about the changes. Is there any way to look up update/change logs? I came here for this same question. Also the github page has the last commit as August 2022. So I also have no clue why this needs updating almost daily. Quote Link to comment
wgstarks Posted January 3, 2023 Share Posted January 3, 2023 1 hour ago, Linxawakening said: I came here for this same question. Also the github page has the last commit as August 2022. So I also have no clue why this needs updating almost daily. Actually, I think it's weekly. It's not uncommon for docker maintainers to setup a weekly update so that updates to the app (which is maintained by someone else) get installed. Many (or maybe all) of the LSIO dockers do the same thing. Quote Link to comment
QuarantineDrive Posted January 4, 2023 Share Posted January 4, 2023 (edited) 6 hours ago, wgstarks said: Actually, I think it's weekly. It's not uncommon for docker maintainers to setup a weekly update so that updates to the app (which is maintained by someone else) get installed. Many (or maybe all) of the LSIO dockers do the same thing. Nope, I'm pretty sure it is daily since we just got another update today. So what you are saying is that the maintainer for this docker is using a script to fetch the original repo and updating here automatically? If this is true (which seems likely), I have two concerns: Too much unnecessary writes/updates on cache (or whatever volume the appdata is installed). As @Linxawakening mentioned, the last commit was pushed on August 2022. Thus, all these daily updates were nothing but making more disk wears. Yeah, I could opt not to update the app for that case. But then I would miss if there was any actual update that includes important changes. And this kills the purpose of updating the app. Is it safe to assume that everything will work 100% on unraid without any human involvement? I am not an expert on how to maintain dockers or anything but shouldn't we concern about OS/library compatibilities? Also what if there was any harmful or broken codes pushed in the original repo? Does the maintainer for this docker fully trust any changes that are made to the original repo? Edited January 4, 2023 by QuarantineDrive Quote Link to comment
JonathanM Posted January 4, 2023 Share Posted January 4, 2023 6 hours ago, QuarantineDrive said: we just got another update today. A docker container is like a small VM, it has parts of an OS as well as the target application. If the base OS is one that gets frequent updates... 6 hours ago, QuarantineDrive said: Is it safe to assume that everything will work 100% on unraid without any human involvement? No, and there are some containers where it's foolish to use the :latest tag because you are pretty much guaranteed to get an update that breaks something, the linuxserver/unifi-controller container is one example. Quote Link to comment
QuarantineDrive Posted January 5, 2023 Share Posted January 5, 2023 14 hours ago, JonathanM said: A docker container is like a small VM, it has parts of an OS as well as the target application. If the base OS is one that gets frequent updates... I see. Just a question though, if the docker gets updated due to update in base OS, wouldn't it show under `docker history`? I checked the os of the docker, and it is using Alpine Linux 3.17 which does get frequent (daily) commit merges. I wish there is a simple way to compare/diff two versions of the docker image but I assume that isn't possible Quote Link to comment
BR0KK Posted January 21, 2023 Share Posted January 21, 2023 You will need to set the filesystem permissions on disk. By default, the timemachine user is 1000:1000. Granting Permissions to write to the directory can be achieved by executing the following command on the host (Unraid): sudo chown -R 1000:1000 /mnt/user/timemachine/ The backing data store for your persistent time machine data must support extended file attributes (xattr). Usually for shares in the Unraid Array this is not a problem. Remote file systems, such as NFS, will very likely not support xattrs. This image will check and try to set xattrs to a test file in /opt/${TM_USERNAME} to warn the user if they are not supported but this will not prevent the image from running. Also note that if you change the User Name (TM_USERNAME) value that it will change the data path for backup data inside of the container from /opt/timemachine to /opt/value-of-TM_USERNAME. Is there a linux newb proof human readable version of this .... I know I need to set some permissions but where in what shell? Thx Quote Link to comment
wgstarks Posted January 21, 2023 Share Posted January 21, 2023 56 minutes ago, BR0KK said: You will need to set the filesystem permissions on disk. By default, the timemachine user is 1000:1000. Granting Permissions to write to the directory can be achieved by executing the following command on the host (Unraid): sudo chown -R 1000:1000 /mnt/user/timemachine/ The backing data store for your persistent time machine data must support extended file attributes (xattr). Usually for shares in the Unraid Array this is not a problem. Remote file systems, such as NFS, will very likely not support xattrs. This image will check and try to set xattrs to a test file in /opt/${TM_USERNAME} to warn the user if they are not supported but this will not prevent the image from running. Also note that if you change the User Name (TM_USERNAME) value that it will change the data path for backup data inside of the container from /opt/timemachine to /opt/value-of-TM_USERNAME. Is there a linux newb proof human readable version of this .... I know I need to set some permissions but where in what shell? Thx You would just run the command on the unRAID terminal. Quote Link to comment
BR0KK Posted January 23, 2023 Share Posted January 23, 2023 On 1/21/2023 at 5:36 PM, wgstarks said: You would just run the command on the unRAID terminal. The shell tells me "no such file or directory" Sorry I'm a newb and thx for the help. Quote Link to comment
wgstarks Posted January 23, 2023 Share Posted January 23, 2023 2 hours ago, BR0KK said: The shell tells me "no such file or directory" Sorry I'm a newb and thx for the help. Did you start the docker before running the command? It should have created the directory. If that doesn’t work please post your docker run command and also the terminal command you are trying to run. Quote Link to comment
M2Pilot Posted February 1, 2023 Share Posted February 1, 2023 I also am troubled by the seemingly unnecessary updates to this app. Gets my 'have I been hacked' antennae wiggling. Quote Link to comment
Shantarius Posted February 25, 2023 Share Posted February 25, 2023 Hi, the Timemachine docker spams into my unraid syslog. How can I prevent for this? Which log level can I use for the container settings (now it is set to 1)? Feb 25 16:05:49 Avalon nmbd[64984]: ***** Feb 25 16:05:49 Avalon nmbd[64984]: Feb 25 16:05:49 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:05:49 Avalon nmbd[64984]: Feb 25 16:05:49 Avalon nmbd[64984]: ***** Feb 25 16:17:27 Avalon nmbd[64984]: [2023/02/25 16:17:27.047518, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce) Feb 25 16:17:27 Avalon nmbd[64984]: process_local_master_announce: Server TIMEMACHINE at IP 192.168.2.139 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Feb 25 16:17:27 Avalon nmbd[64984]: [2023/02/25 16:17:27.047676, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success) Feb 25 16:17:27 Avalon nmbd[64984]: ***** Feb 25 16:17:27 Avalon nmbd[64984]: Feb 25 16:17:27 Avalon nmbd[64984]: Samba name server AVALON has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:17:27 Avalon nmbd[64984]: Feb 25 16:17:27 Avalon nmbd[64984]: ***** Feb 25 16:17:47 Avalon nmbd[64984]: [2023/02/25 16:17:47.344230, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 25 16:17:47 Avalon nmbd[64984]: ***** Feb 25 16:17:47 Avalon nmbd[64984]: Feb 25 16:17:47 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:17:47 Avalon nmbd[64984]: Feb 25 16:17:47 Avalon nmbd[64984]: ***** Feb 25 16:29:28 Avalon nmbd[64984]: [2023/02/25 16:29:28.202819, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce) Feb 25 16:29:28 Avalon nmbd[64984]: process_local_master_announce: Server TIMEMACHINE at IP 192.168.2.139 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Feb 25 16:29:28 Avalon nmbd[64984]: [2023/02/25 16:29:28.202973, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success) Feb 25 16:29:28 Avalon nmbd[64984]: ***** Feb 25 16:29:28 Avalon nmbd[64984]: Feb 25 16:29:28 Avalon nmbd[64984]: Samba name server AVALON has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:29:28 Avalon nmbd[64984]: Feb 25 16:29:28 Avalon nmbd[64984]: ***** Feb 25 16:29:48 Avalon nmbd[64984]: [2023/02/25 16:29:48.037595, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 25 16:29:48 Avalon nmbd[64984]: ***** Feb 25 16:29:48 Avalon nmbd[64984]: Feb 25 16:29:48 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:29:48 Avalon nmbd[64984]: Feb 25 16:29:48 Avalon nmbd[64984]: ***** Feb 25 16:41:30 Avalon nmbd[64984]: [2023/02/25 16:41:30.678485, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce) Feb 25 16:41:30 Avalon nmbd[64984]: process_local_master_announce: Server TIMEMACHINE at IP 192.168.2.139 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Feb 25 16:41:30 Avalon nmbd[64984]: [2023/02/25 16:41:30.678645, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success) Feb 25 16:41:30 Avalon nmbd[64984]: ***** Feb 25 16:41:30 Avalon nmbd[64984]: Feb 25 16:41:30 Avalon nmbd[64984]: Samba name server AVALON has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:41:30 Avalon nmbd[64984]: Feb 25 16:41:30 Avalon nmbd[64984]: ***** Feb 25 16:41:48 Avalon nmbd[64984]: [2023/02/25 16:41:48.997249, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 25 16:41:48 Avalon nmbd[64984]: ***** Feb 25 16:41:48 Avalon nmbd[64984]: Feb 25 16:41:48 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:41:48 Avalon nmbd[64984]: Feb 25 16:41:48 Avalon nmbd[64984]: ***** Thank you! Quote Link to comment
defected07 Posted February 27, 2023 Share Posted February 27, 2023 On 2/25/2023 at 7:50 AM, Shantarius said: Hi, the Timemachine docker spams into my unraid syslog. How can I prevent for this? Which log level can I use for the container settings (now it is set to 1)? Feb 25 16:05:49 Avalon nmbd[64984]: ***** Feb 25 16:05:49 Avalon nmbd[64984]: Feb 25 16:05:49 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:05:49 Avalon nmbd[64984]: Feb 25 16:05:49 Avalon nmbd[64984]: ***** Feb 25 16:17:27 Avalon nmbd[64984]: [2023/02/25 16:17:27.047518, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce) Feb 25 16:17:27 Avalon nmbd[64984]: process_local_master_announce: Server TIMEMACHINE at IP 192.168.2.139 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Feb 25 16:17:27 Avalon nmbd[64984]: [2023/02/25 16:17:27.047676, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success) Feb 25 16:17:27 Avalon nmbd[64984]: ***** Feb 25 16:17:27 Avalon nmbd[64984]: Feb 25 16:17:27 Avalon nmbd[64984]: Samba name server AVALON has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:17:27 Avalon nmbd[64984]: Feb 25 16:17:27 Avalon nmbd[64984]: ***** Feb 25 16:17:47 Avalon nmbd[64984]: [2023/02/25 16:17:47.344230, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 25 16:17:47 Avalon nmbd[64984]: ***** Feb 25 16:17:47 Avalon nmbd[64984]: Feb 25 16:17:47 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:17:47 Avalon nmbd[64984]: Feb 25 16:17:47 Avalon nmbd[64984]: ***** Feb 25 16:29:28 Avalon nmbd[64984]: [2023/02/25 16:29:28.202819, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce) Feb 25 16:29:28 Avalon nmbd[64984]: process_local_master_announce: Server TIMEMACHINE at IP 192.168.2.139 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Feb 25 16:29:28 Avalon nmbd[64984]: [2023/02/25 16:29:28.202973, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success) Feb 25 16:29:28 Avalon nmbd[64984]: ***** Feb 25 16:29:28 Avalon nmbd[64984]: Feb 25 16:29:28 Avalon nmbd[64984]: Samba name server AVALON has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:29:28 Avalon nmbd[64984]: Feb 25 16:29:28 Avalon nmbd[64984]: ***** Feb 25 16:29:48 Avalon nmbd[64984]: [2023/02/25 16:29:48.037595, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 25 16:29:48 Avalon nmbd[64984]: ***** Feb 25 16:29:48 Avalon nmbd[64984]: Feb 25 16:29:48 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:29:48 Avalon nmbd[64984]: Feb 25 16:29:48 Avalon nmbd[64984]: ***** Feb 25 16:41:30 Avalon nmbd[64984]: [2023/02/25 16:41:30.678485, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce) Feb 25 16:41:30 Avalon nmbd[64984]: process_local_master_announce: Server TIMEMACHINE at IP 192.168.2.139 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election. Feb 25 16:41:30 Avalon nmbd[64984]: [2023/02/25 16:41:30.678645, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success) Feb 25 16:41:30 Avalon nmbd[64984]: ***** Feb 25 16:41:30 Avalon nmbd[64984]: Feb 25 16:41:30 Avalon nmbd[64984]: Samba name server AVALON has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:41:30 Avalon nmbd[64984]: Feb 25 16:41:30 Avalon nmbd[64984]: ***** Feb 25 16:41:48 Avalon nmbd[64984]: [2023/02/25 16:41:48.997249, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Feb 25 16:41:48 Avalon nmbd[64984]: ***** Feb 25 16:41:48 Avalon nmbd[64984]: Feb 25 16:41:48 Avalon nmbd[64984]: Samba name server AVALON is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.126 Feb 25 16:41:48 Avalon nmbd[64984]: Feb 25 16:41:48 Avalon nmbd[64984]: ***** Thank you! You could try `0`: Quote At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out. Sources: https://www.samba.org/samba/docs/current/man-html/nmbd.8.html https://www.samba.org/samba/docs/current/man-html/smbcontrol.1.html The value will override any value that is set for loglevel in `<prefix>/etc/smb.conf` Hope that helps! 1 Quote Link to comment
Shantarius Posted February 28, 2023 Share Posted February 28, 2023 19 hours ago, defected07 said: You could try `0`: Sources: https://www.samba.org/samba/docs/current/man-html/nmbd.8.html https://www.samba.org/samba/docs/current/man-html/smbcontrol.1.html The value will override any value that is set for loglevel in `<prefix>/etc/smb.conf` Hope that helps! I think the Problem was that the Unraid Samba Service and the Timemachine Samba Service had the same workgroup name. I have changed the workgroup name for the Container and now it is all ok. Quote Link to comment
defected07 Posted March 4, 2023 Share Posted March 4, 2023 On 2/28/2023 at 2:52 AM, Shantarius said: I think the Problem was that the Unraid Samba Service and the Timemachine Samba Service had the same workgroup name. I have changed the workgroup name for the Container and now it is all ok. I'm having similar problems. I have a different user account for Timemachine Docker share, and for the rest of the unRAID shares. I may be overcomplicating things, but should I use one LAN port for Docker (including Timemachine container), and the other for the rest of the user shares? Curious how people approach this. Also, since AFP is deprecated, should I disable the avahi process? Or is avahi necessary for TimeMachine/SMB? Quote Link to comment
Jeffrey Meng Posted April 27, 2023 Share Posted April 27, 2023 I got this setup on my local network, but when I try to access my server remotely via wireguard, I can't see .local domains, and so I can't access the time machine share (but I can connect to normal unraid shares via my ip). Does anybody know how to set this up so it can be accessed remotely with wireguard? I'm guessing I need to route it to use my ip and some port but I'm not sure where to set that up. Quote Link to comment
Msan Posted June 8, 2023 Share Posted June 8, 2023 On 4/26/2023 at 6:22 PM, Jeffrey Meng said: I got this setup on my local network, but when I try to access my server remotely via wireguard, I can't see .local domains, and so I can't access the time machine share (but I can connect to normal unraid shares via my ip). Does anybody know how to set this up so it can be accessed remotely with wireguard? I'm guessing I need to route it to use my ip and some port but I'm not sure where to set that up. Did you get anywhere with this? I am trying to do the exact same thing without success so far.. Quote Link to comment
ScottAS2 Posted June 17, 2023 Share Posted June 17, 2023 On 4/27/2023 at 2:22 AM, Jeffrey Meng said: I got this setup on my local network, but when I try to access my server remotely via wireguard, I can't see .local domains, and so I can't access the time machine share (but I can connect to normal unraid shares via my ip). Does anybody know how to set this up so it can be accessed remotely with wireguard? I'm guessing I need to route it to use my ip and some port but I'm not sure where to set that up. On the Unraid side, all you need to do is edit the container and specify a fixed IP address of your choosing. Then on your Mac you'll probably need to set up Time Machine again to bind it to the IP address and not the .local hostname that isn't available through Wireguard. Don't worry: you can retain your backup history when doing so. Firstly, go to your Time Machine preferences and delete your current .local backup destination. Then go to the Finder and do "Go" -> "Connect to Server...". In the dialogue box that comes up type "smb://[fixed IP address]/[share name]" and click "Connect". Sign in and the share should mount on your desktop. Now go back to Time Machine in System Preferences and select a backup destination. Make sure you pick the fixed IP address, not the .local hostname. Possibly Time Machine will be clever and collapse both destinations together, so you may have to do this when you're connected through Wireguard so that the IP address is the only option. IIRC, at this point it will notice that there are existing backups and will ask if you want to re-use them or start from scratch; presumably you want the former. The backup destination will now be sitting with a status of "Waiting to complete first backup" or similar. Don't panic! Your backup history is still there. Go back to the desktop and unmount the share. Then, the first time you run a backup, it'll rediscover the history and continue as if nothing had happened. Quote Link to comment
d3rax Posted August 5, 2023 Share Posted August 5, 2023 (edited) I got it setup with the standard settings. I am able to connect to the timemachine.local backup disk, but some how the connection interrupts. I have not been able to finish the initial backup and when i click make backup now it cannot connect. Only when I restart the dock container the back up starts again but only for a few minutes? In the log of the timemachine dock i do get the following error: INTERNAL ERROR: smbd_scavenger_parent_dead in pid 75 (4.18.5) and I see this line: INFO: SET_PERMISSIONS=false; not setting ownership and permissions for /opt/timemachine But I did run sudo chown -R 1000:1000 /mnt/user/timemachine/ Edited August 5, 2023 by d3rax Quote Link to comment
Quantumed Posted August 12, 2023 Share Posted August 12, 2023 On 6/17/2023 at 1:33 PM, ScottAS2 said: On the Unraid side, all you need to do is edit the container and specify a fixed IP address of your choosing. Then on your Mac you'll probably need to set up Time Machine again to bind it to the IP address and not the .local hostname that isn't available through Wireguard. Don't worry: you can retain your backup history when doing so. Firstly, go to your Time Machine preferences and delete your current .local backup destination. Then go to the Finder and do "Go" -> "Connect to Server...". In the dialogue box that comes up type "smb://[fixed IP address]/[share name]" and click "Connect". Sign in and the share should mount on your desktop. Now go back to Time Machine in System Preferences and select a backup destination. Make sure you pick the fixed IP address, not the .local hostname. Possibly Time Machine will be clever and collapse both destinations together, so you may have to do this when you're connected through Wireguard so that the IP address is the only option. IIRC, at this point it will notice that there are existing backups and will ask if you want to re-use them or start from scratch; presumably you want the former. The backup destination will now be sitting with a status of "Waiting to complete first backup" or similar. Don't panic! Your backup history is still there. Go back to the desktop and unmount the share. Then, the first time you run a backup, it'll rediscover the history and continue as if nothing had happened. Has anyone managed to successfully connect to the TM share via Tailscale? After setting a fixed IP as instructed, I'm unable to connect to it with the following generic error: Quote Link to comment
BeardElk Posted August 21, 2023 Share Posted August 21, 2023 So, for some reason, whenever the I run timemachine on my mac, my docker.img is filling up? I'm not sure what I've done wrong! I've run sudo chown -R 1000:1000 /mnt/user/timemachine/ and everything seems to be working as it should except that it fills up my docker.img. Quote Link to comment
wgstarks Posted August 21, 2023 Share Posted August 21, 2023 1 hour ago, BeardElk said: So, for some reason, whenever the I run timemachine on my mac, my docker.img is filling up? I'm not sure what I've done wrong! I've run sudo chown -R 1000:1000 /mnt/user/timemachine/ and everything seems to be working as it should except that it fills up my docker.img. This usually means that you are mapping the backup to a destination in the image. Attach your docker run command to your next post. Quote Link to comment
unn4m3d Posted August 23, 2023 Share Posted August 23, 2023 Using the TimeMachine docker prevents my drives from spinning down. Anyone else having this issue? Using the File Activity Script shows regular activities on my TimeMachine share. How can I prevent this? Quote Link to comment
ScottAS2 Posted August 23, 2023 Share Posted August 23, 2023 4 minutes ago, unn4m3d said: Using the TimeMachine docker prevents my drives from spinning down. Anyone else having this issue? I find it can fiddle around for a few minutes after each backup has completed, but it eventually stops and the disk spins down (sometimes just in time for the next backup to spin it back up 😕). I’ve no idea what it’s doing, though. Updating cached indexes or some other metadata perhaps? How long after your backup does the activity persist? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.