• randomaside@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    I’m fooling around with a few samba AD docker containers. I ask because I’ve phased almost everything else out of my lab environment.

    • Possibly linux@lemmy.zipOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      The problem with Samba AD in a container or Samba in container is that Samba isn’t designed to be run in a temporary environment. You could run it in a LXC container but anything beyond that will break things in the short or long term.

      • randomaside@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        I figured you could get around some of the storage limitations with something like persistent volume claims. I’m testing it out at the moment. I am a big fan of LXC.

        I see a few people have created docker Samba Containers and I’m giving them a whirl. Can’t say much for stability but I think it’s an interesting experiment.

        I know in the past smb server didn’t work in LXC containers because certain kernel modules caused conflicts.

        A man can dream.

        • Possibly linux@lemmy.zipOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          5 months ago

          If you manage to create persistent containers how are you going to update them down the road? Like I have said previously, Samba isn’t designed in a way that allows for effectively hot swapping system components.

          It seems like it would better to create a VM template and then setup a fail over cluster. Just make sure you have a time server somewhere on the network.

          If you are dead set on containers you could try LDAP in a container. I just don’t think active directory was built for Linux containerization.