• Burn1ngBull3t@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      It’s actually how people build their images, in which some include sensitive data (when they should definitely not). It’s the same problem as exposed S3 buckets actually, nothing wrong with docker in itself.

        • Burn1ngBull3t@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Actually yes, I had a look at them since i wanted to write HelmCharts for the community. That’s also where the community can step up, it can only be better 😊

          • 𝘋𝘪𝘳𝘬@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            I actually started looking into creating own Docker images because of how bad Lemmy’s Docker instructions are. I’m not even close to anything usable, though …

    • Laser@feddit.de
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I guess it depends, if it’s a secret in use for the image, an attacker might use it to attack a pulled instance if the user deploying it didn’t change the secret. Kind of like an unchanged initial password.