Selfhosted

40767 readers

1061 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

No luck getting my Lemmy instance up and running, is this a good place to get some help? (lemmy.world)

submitted 2 years ago by IchNichtenLichten@lemmy.world to c/selfhosted@lemmy.world

45 comments fedilink hide all child comments

I'm not exactly a linux beginner but I'm far from an expert and I could use some pointers. I have a domain and a VPS through Namecheap, I chose Ubuntu 20.04 LAMP and I've tried several guides to get this working but something always goes wrong sooner or later.

My latest attempt is to follow along with this guide: https://join-lemmy.org/docs/administration/install_docker.html

No errors until the docker-compose up -d command, then

ERROR: yaml.constructor.ConstructorError: while constructing a mapping in "./docker-compose.yml", line 26, column 12 found unhashable key in "./docker-compose.yml", line 26, column 13

which leads to image: {{ lemmy_docker_image }}

I guess I could start over with a different guide but I'm just chasing my tail at this point. Could any kind soul suggest where to go from here?

you are viewing a single comment's thread
view the rest of the comments

[–] slashzero@hakbox.social 1 points 2 years ago* (last edited 2 years ago) (1 children)

Hi there! This sounds like you might just have a typo in your docker-compose.yml file. It might be helpful if you posted your docker-compose.yml contents here (be sure to remove any sensitive information).

Line 26 of my docker-compose.yml file is the volume block/map for letsencrypt. Did you perhaps mix tabs and spaces, or have one too many spaces in your indentations, in your yaml file? That's a no-no...

Personally, I setup my instance using the same guide as you, opting for the docker containers. There were definitely a few pitfalls to deal with.

[–] IchNichtenLichten@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 children)

Here you go! There shouldn't be any sensitive info in there, I haven't modified it. The command in the instructions:

wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/docker-compose.yml

obtained the file and there's no instruction to modify it prior to running docker-compose up -d which is where it fails.

Edit: Lemmy screws up the formatting. It looks fine pasted into to text area but is messed up when I post. See the above link, that's what I'm using.

[–] slashzero@hakbox.social 1 points 2 years ago* (last edited 2 years ago)

Sorry I didn’t get a chance to look at this, but I’m mostly on mobile and the link doesn’t work.

For future reference you can put it in a code block and lemmy-ui should be able to render it for you.

Example code block