Closed philippelt closed 12 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there any information missing ? No one have an idea :smiley: For the moment, I will force use of 27.x so there is no big issue for me but I would have like to understand the problem and possibly find a work-around or solution...
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
I added an avahi ressource to advertise a samba share used for time machine. When using an image with 28.x tag, the samba share is displayed as attached to xxx-2 (xxx is the appropriate hostname) and time machine do not find the backup disk. If I start a 27.4 image, the samba share is displayed as attached to xxx without any suffix and time machine works. I tried 28.4 and 28.5 and both do not work.
Expected Behavior
I expected that the host did not change and was not added a -2 suffix that avoid mac stations to find time machine share.
Steps To Reproduce
Start daapd container with latest version. Even on an empty server, no need to run samba or anything else.
My compose file is mounting a volume for avahi resources :
<server path>:/etc/avahi/services:ro
Add an avahi resource (file
timemachine.service
) in the mounted service directory :Test broadcast using
mdns-scan
Invalid output :xxx-2._adisk._tcp.local
Expected output:xxx._adisk._tcp.local
xxx being the hostname of the server.Running the same configuration with the 24.7 image provide the expected output
Environment
CPU architecture
x86-64
Docker creation