this post was submitted on 03 Nov 2025
53 points (96.5% liked)

Fediverse

37666 readers
67 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 2 years ago
MODERATORS
ruud@lemmy.world
Xylinna@lemmy.world
MrCenny@lemmy.world
TragicNotCute@lemmy.world
automodbeta@lemmy.world
woelkchen@lemmy.world
53
Could anyone help me set up a lemmy instance? (ttrpg.network)
submitted 2 days ago* (last edited 2 days ago) by revoirwinery@ttrpg.network to c/fediverse@lemmy.world
12 comments fedilink hide all child comments
 

I'm trying to follow the guide here https://join-lemmy.org/docs/administration/install_docker.html

I get an error when I run docker compose up -d. It happens after docker outputs ⠹ Container lemmy-postgres-1 Starting

Error response from daemon: failed to create task for container: failed to create shim task: OCI
runtime create failed: runc create failed: unable to start container process: error during container
init: error mounting "/home/user/lemmy/volumes/postgres" to rootfs at "/var/lib/postgresql/data":
change mount propagation through procfd: open o_path procfd: open /var/lib/docker/
overlay2/238f1ac3ed9eac5f9c1fdc9ee1851634765c83da087baccc4dfbf4fcc4316b32/merged/
var/lib/postgresql/data: no such file or directory: unknown

I'm not really sure what this means, and trying all of AIs suggestions didn't fix it.

I'm kinda new to all of this, so any help would be appreciated.

you are viewing a single comment's thread
view the rest of the comments
[–] asudox@lemmy.asudox.dev 8 points 2 days ago (3 children)

Are you using postgresql 18? I tried upgrading yesterday from 17.6 and got an identical error message.

[–] poVoq@slrpnk.net 10 points 2 days ago (1 children)

Indeed, Postgres 18 introduced some breaking changes and AFAIK Lemmy isn't compatible with them yet. This will probably be fixed in the next release.

[–] revoirwinery@ttrpg.network 6 points 2 days ago

That'd be a relief if that's the case.

I've been getting a bit demoralized trying to figure this out.

[–] revoirwinery@ttrpg.network 9 points 2 days ago

Yes, it looks like the supplied docker-compose.yml points to pgautoupgrade/pgautoupgrade:18-alpine for the postgres image.

[–] jivandabeast@lemmy.browntown.dev 2 points 2 days ago

try this

But, make a backup of your db beforehand. I don't know how it would work when upgrading an existing database