this post was submitted on 18 Jun 2023
167 points (99.4% liked)

Selfhosted

40041 readers
728 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
167
Having trouble deploying Lemmy? Try my new script! Get up and running in minutes! (github.com)
submitted 1 year ago* (last edited 1 year ago) by ubergeek77@lemmy.ubergeek77.chat to c/selfhosted@lemmy.world
96 comments fedilink hide all child comments
 

In the past few days, I've seen a number of people having trouble getting Lemmy set up on their own servers. That motivated me to create Lemmy-Easy-Deploy, a dead-simple solution to deploying Lemmy using Docker Compose under the hood.

To accommodate people new to Docker or self hosting, I've made it as simple as I possibly could. Edit the config file to specify your domain, then run the script. That's it! No manual configuration is needed. Your self hosted Lemmy instance will be up and running in about a minute or less. Everything is taken care of for you. Random passwords are created for Lemmy's microservices, and HTTPS is handled automatically by Caddy.

Updates are automatic too! Run the script again to detect and deploy updates to Lemmy automatically.

If you are an advanced user, plenty of config options are available. You can set this to compile Lemmy from source if you want, which is useful for trying out Release Candidate versions. You can also specify a Cloudflare API token, and if you do, HTTPS certificates will use the DNS challenge instead. This is helpful for Cloudflare proxy users, who can have issues with HTTPS certificates sometimes.

Try it out and let me know what you think!

https://github.com/ubergeek77/Lemmy-Easy-Deploy

you are viewing a single comment's thread
view the rest of the comments
[–] ubergeek77@lemmy.ubergeek77.chat 1 points 1 year ago* (last edited 1 year ago) (1 children)

Docker Compose is just a frontend script for Docker, it doesn't provide the engine. Is it possible you don't have Docker itself installed? I will add an additional check to my script to guide users into making sure Docker is installed.

Regardless of if you have Docker installed or not, if you are on Ubuntu, the Ubuntu version of Docker is usually several versions out of date. I recommend following this guide to help you uninstall everything Docker related from your system, then reinstalling the most stable and up to date version of Docker.

https://docs.docker.com/engine/install/ubuntu/

After doing this, reboot your server, then try again. Make sure you can run:

docker run hello-world

If that errors too, then unfortunately there is not a lot I can do to help you. But hopefully reinstalling from the official Docker sources works for you.

If you aren't on Ubuntu, you can get specific instructions for different distributions directly on this page:

https://docs.docker.com/engine/install/

For the guide you're following, you should be sure to follow the "Uninstall old versions" part, then proceed with the rest of the commands on the page.

EDIT: I've updated the script to add some additional checks and messages that may help avoid this for future users!

[–] BlueEther@no.lastname.nz 2 points 1 year ago

It looks like I had to enable nesting in proxmox