search

mbentley / docker-timemachine

Docker image to run Samba (compatible Time Machine for macOS)
Apache License 2.0
527 stars 65 forks source link

[Bug]: My MacBook cannot find TimeMachine #131

Closed ams158 closed 1 year ago

ams158 commented 1 year ago

Describe the Bug

Hi:

I'm running the Time Machine container using MacVlan but my MacBook cannot find it, these are my docker commands:

docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o parent=eth0 macvlan1

$ route | grep ^default | awk '{print $NF}'
eth0

docker run -d --restart=always   --name timemachine   --net=macvlan1   --ip 192.168.1.200  -e enable-reflector="yes" -e cache-entries-max="0" -e CUSTOM_SMB_CONF="false"   -e CUSTOM_USER="false"   -e DEBUG_LEVEL="1"   -e MIMIC_MODEL="TimeCapsule8,119"   -e EXTERNAL_CONF=""   -e HIDE_SHARES="no"   -e TM_USERNAME="timemachine"   -e TM_GROUPNAME="timemachine"   -e TM_UID="1000"   -e TM_GID="1000"   -e PASSWORD="timemachine"   -e SET_PERMISSIONS="false"   -e SHARE_NAME="TimeMachine"   -e SMB_PORT="445"   -e VOLUME_SIZE_LIMIT="0"   -e WORKGROUP="WORKGROUP"   -v /timemachine:/opt/timemachine   -v /timemachine-var-lib-samba:/var/lib/samba   -v /timemachine-var-cache-samba:/var/cache/samba   -v /timemachine-run-samba:/run/samba   mbentley/timemachine:latest-smb-arm64

I'm already running Samba for other propose, so I'm trying the MacVlan option.

Any idea why I cannot see it? Am I missing something? Thank you in advanced, BR Abel

Expected Behavior

Timemachine server found in MacBook configuration

Steps to Reproduce

Run the commented commands

How You're Launching the Container

docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o parent=eth0 macvlan1

docker run -d --restart=always   --name timemachine   --net=macvlan1   --ip 192.168.1.200  -e enable-reflector="yes" -e cache-entries-max="0" -e CUSTOM_SMB_CONF="false"   -e CUSTOM_USER="false"   -e DEBUG_LEVEL="1"   -e MIMIC_MODEL="TimeCapsule8,119"   -e EXTERNAL_CONF=""   -e HIDE_SHARES="no"   -e TM_USERNAME="timemachine"   -e TM_GROUPNAME="timemachine"   -e TM_UID="1000"   -e TM_GID="1000"   -e PASSWORD="timemachine"   -e SET_PERMISSIONS="false"   -e SHARE_NAME="TimeMachine"   -e SMB_PORT="445"   -e VOLUME_SIZE_LIMIT="0"   -e WORKGROUP="WORKGROUP"   -v /timemachine:/opt/timemachine   -v /timemachine-var-lib-samba:/var/lib/samba   -v /timemachine-var-cache-samba:/var/cache/samba   -v /timemachine-run-samba:/run/samba   mbentley/timemachine:latest-smb-arm64

Container Logs

Docker log:

dbus-daemon[585]: Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": No such file or directory

Additional Context

No response

mbentley commented 1 year ago

This should now be fixed; looks like something changed in Alpine 3.18 so it wasn't creating a parent directory it was expecting to be there so the container was never really starting.