Regular shares get affected by timemachine

[alparr]

I'm using timemachine withouth zeroconf, with a mix of shares. This is a simplified docker-compose setup:

  samba:
    image: ghcr.io/servercontainers/samba:smbd-only-latest
    container_name: samba
    environment:
      ACCOUNT_alpar: ...
      SAMBA_VOLUME_CONFIG_downloads: "[Downloads]; path=/shares/downloads; valid users = alpar; guest ok = no; read only = no; browsable = yes"
      SAMBA_VOLUME_CONFIG_timemachine: "[Timemachine]; path=/shares/timemachine; valid users = alpar; guest ok = no; read only = no; browsable = yes; fruit:time machine = yes"
    volumes:
      - /somepath/downloads:/shares/downloads:ro
      - /somepath/timemachine:/shares/timemachine:rw
    ports:
      - 445:445/tcp
    restart: unless-stopped

If I'm connecting to the timemachine share then the other "regular" shares get affected. I'm able to read and write to the root directory, but I'm not able to access any of the subdirectories.

If I disconnect from everything and don't connect to the timemachine share then those other ones are also working. Is it not supported to have both regular and timemachine shares in the same container?

[kigakree]

I have the same issue. After I've added
SAMBA_GLOBAL_STANZA: "vfs objects = catia fruit streams_xattr"
everything is ok.

Also in documentation it is said
Be careful when mixing shares with and without vfs_fruit. OS X clients negotiate SMB2 AAPL protocol extensions on the first tcon, so mixing shares with and without fruit will globally disable AAPL if the first tcon is without fruit.

@MarvAmBass Is there any reason not to enable vfs_fruit globally?

[MarvAmBass]

sounds like I should implement those settings as default, once a timemachine share is detected.
maybe even without a timemachine share...

[MarvAmBass]

I've added the option to the global config as default