121
submitted 10 months ago by hperrin@lemmy.world to c/selfhosted@lemmy.world

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.

you are viewing a single comment's thread
view the rest of the comments
[-] thanksforallthefish@literature.cafe 23 points 10 months ago

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

[-] redcalcium@lemmy.institute 30 points 10 months ago* (last edited 10 months 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.dev 7 points 10 months 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.

[-] hperrin@lemmy.world 3 points 10 months ago

Now I know better. No more Ubuntu Server.

[-] GenderNeutralBro@lemmy.sdf.org 1 points 10 months 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.)

[-] Turbo@lemmy.ml 1 points 10 months ago
this post was submitted on 05 Jan 2024
121 points (93.5% liked)

Selfhosted

39677 readers
460 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS