![time machine backup mac address time machine backup mac address](https://i.stack.imgur.com/Av4PP.png)
Note: If you are already running Samba/Avahi on your Docker host (or you're wanting to run this on your NAS), you should be aware that using -net=host will cause a conflict with the Samba/Avahi install. Conflicts with Samba and/or Avahi on the Host This issue has been observed on Raspberry Pi OS (formerly known as Raspbian) based on Debian 10 (Buster) but may also be found on other distros as they may commonly use the libseccomp2 package version 2.3.3-4. If you are running the armv7l image, you may see and error when trying to start the container: Known Issues Unable to start the armv7l image See below for another workaround if you do not wish to change the Samba port. Using -net=host only works if you do not already run Samba or Avahi on the host! Alternatively, you can use the SMB_PORT option to change the port that Samba uses. Otherwise, you will need to expose the above ports and then you must manually map the share in Finder for it to show up (open Finder, click Shared, and connect as smb://hostname-or-ip/TimeMachine with your TimeMachine credentials). This works best with -net=host so that discovery can be broadcast. The images are also compatible with Kubernetes.Ĭheckout timemachine-k3s.yaml as an example for running a TimeMachine backup server on a single-node k3s cluster running (on a Raspberry Pi 4). v timemachine-var-cache-samba:/var/cache/samba \ v timemachine-var-lib-samba:/var/lib/samba \ v /path/on/host/to/backup/to/for/timemachine:/opt/timemachine \ e SMB_VFS_OBJECTS="acl_xattr fruit streams_xattr" \ I do not plan on adding any new features to the AFP based config and I switched the default image in the latest tag to the SMB variant on October 15, 2020.ĭocker pull mbentley/timemachine:smb Example usage for SMBĮxample usage with -net=host to allow Avahi discovery all available environment variables set to their default values: Warning: I would strongly suggest migrating to the SMB image as AFP is being deprecated by Apple and I've found it to be much more stable. latest-smb-arm64, smb-arm64 - SMB image based off of alpine:latest for the arm64 architecture.latest-smb-armv7l, smb-armv7l - SMB image based off of alpine:latest for the armv7l architecture.Deprecated but still available not being regularly built - This image may have unpatched security vulnerabilities.afp, afp-amd64 - AFP image based off of debian:jessie.
![time machine backup mac address time machine backup mac address](https://i.stack.imgur.com/bypb6.png)
#Time machine backup mac address update
You will need to update to newer tags as they are published in order to get updated images. Please note that these tags will remain available on Docker Hub for 6 months and will not receive security fixes. Each one of these tags will be generated daily and is essentially a point in time snapshot of the smb tag's manifest that you can pin to if you wish. smb-20210730) and can be viewed on Docker Hub. These are in the format smb-YYYYMMDD (e.g. The smb tags also have unique manifests that are generated daily. Note: The afp tag has been deprecated in terms of new feature updates and is only available for amd64.
![time machine backup mac address time machine backup mac address](https://support.apple.com/library/content/dam/edam/applecare/images/en_US/macos/monterey/macos-monterey-time-machine-menu-backup-progress.jpg)
The following tags have multi-arch support for amd64, armv7l, and arm64 and will automatically pull the correct tag based on your system's architecture: Docker image to run Samba or AFP (netatalk) to provide a compatible Time Machine for MacOS Image Tags Multi-arch Tags