I spent two hours today trying to figure out why Nextcloud couldn’t read my data directory. Docker wasn’t mounting my data directory. Moved everything into my data directory. Docker couldn’t even see the configuration file.

Turns out the Docker Snap package only has access to files under the /home directory.

Moral of the story: never trust a Snap package.

  • redcalcium@lemmy.instituteEnglish
    471·
    1 year ago

    I also like to run my container platform as a containerized application in another container platform.

    • thanksforallthefishEnglish
      241·
      1 year ago

      Lol. Yeah that was my reaction to the headline as well. “You did what ?”

      • redcalcium@lemmy.instituteEnglish
        311·
        1 year ago

        Why does Docker has a snap version in the first place anyway? Did Canonical pester them to do it?

        Edit:

        Nope, it’s just Canonical went ahead and publish it there by themselves.

        This snap is built by Canonical based on source code published by Docker, Inc. It is not endorsed or published by Docker, Inc.

        • thesmokingman@programming.devEnglish
          7·
          1 year ago

          It’s also offered as part of the installation process at least for Ubuntu server. If you don’t know better it bites you real quick.

        • GenderNeutralBro@lemmy.sdf.orgEnglish
          1·
          1 year ago

          It’s insane how many things they push as Snaps when they are entirely incompatible with the Snap model.

          I think everyone first learns what Snaps are by googling “why doesn’t ____ work on Ubuntu?” For me, it was Filebot. Spent an hour or two trying to figure out how the hell to get it to actually, you know, access my files. (This was a few years ago, so maybe things are better now. Not sure. I don’t live that Snap life anymore, and I’m not going back.)