Samba share is not announced about samba HOT 6 CLOSED

Is Avahi installed on your host? Do you see the samba config on your host? Maybe you just need to restart avahi on your host

You know that you explicitly disabled the container avahi by mounting the avahi volume from the outside.

Please check if anything from above might be the problem

Thanks and have fun with the container

Maybe you can also post the contents of your avahi samba service

from samba.

The interesting thing is, I also need to click twice on my Mac

Sometimes it seems to no connect
But after manual connect it also works via the detected server

Maybe this really is an issue I need to look into - I think I got blind and got used to this workaround

Also sometimes my server icon changes

Do you see your raspberry pi on your network as samba/network share server? Or is it missing completely

You could also check using some zeroconf inspector if and what is announced

from samba.

I think I figured it out now. I removed the mount of the host avahi and removed the file on the pi's /etc/avahi/service/samba.conf location to make use of the avahi instance from the docker container. Furthermore, I have to have a time machine share to have the "complete" setup.

Here is the samba.service without timemachine:

<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
 <name replace-wildcards="yes">StorageServer</name>
 <service>
   <type>_smb._tcp</type>
   <port>445</port>
 </service>

And here with:

<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
 <name replace-wildcards="yes">StorageServer</name>
 <service>
   <type>_smb._tcp</type>
   <port>445</port>
 </service>

 <service>
  <type>_device-info._tcp</type>
  <port>0</port>
  <txt-record>model=MacPro7,1@ECOLOR=226,226,224</txt-record>
 </service>

 <service>
  <type>_adisk._tcp</type>
  <txt-record>sys=waMa=0,adVF=0x100</txt-record>
  <txt-record>dk0=adVN=TimeMachine,adVF=0x82</txt-record>
 </service>
</service-group>

from samba.

So is everything working as expected? Or did you have to add the samba config manually?

from samba.

Now everything is working as expected, and the samba config is created automatically. However, it seems to generate a correct samba service config only if I have a time machine share configured. Without that, the samba config file is still generated but not working.

from samba.

As far as I know, it doesn't overwrite, so maybe your raspberry pi default samba config is conflicting with my container. there could also be an issue with some kind of avahi version conflict between host and container

from samba.