• IronKrill@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    14 days ago

    Well that sucks. IIRC a lot of my docker images are alpine based, but they’d be safe due to never having their SSH ports exposed I assume.

    • fonix232@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      14 days ago

      Why would you even have an SSH server running in a Docker container (unless the purpose of the container is being a jumpbox or similar)?

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        0
        ·
        13 days ago

        Not just rootless and read-only, but distroless/chiseled too. There’s no reason to have unneeded parts of an OS in your Docker containers. It should just be one app along with any libraries it needs (or just statically compile the app)

      • IronKrill@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        14 days ago

        While I have not done it, I could see it being appealing as it’s quicker than SSHing into the parent box first for a commonly used tool. I had a direct SSH into a systemd container for a while before deciding the extra config wasn’t worth it.

      • MonkderVierte@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        13 days ago

        unless the purpose of the container is being a jumpbox or similar

        What’s wrong with a rootless jumpbox?

        • fonix232@fedia.io
          link
          fedilink
          arrow-up
          0
          ·
          13 days ago

          Nothing, my point was that SSH in a container is unnecessary unless it’s for the specific purpose of the container.