Selfhosted
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:
- 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!
view the rest of the comments
Threw an error:
Creating lemmy-easy-deploy_pictrs_1 ... Creating lemmy-easy-deploy_postgres_1 ... error
ERROR: for lemmy-easy-deploy_postgres_1 Cannot start service postgres: failed to create task for container: failed to create shim task: OCI runtime create failed: runc cr Creating lemmy-easy-deploy_pictrs_1 ... error: permission denied: unknown
Does your user have permission to use Docker? You could try running the script as root and seeing if that helps?
Is there any other info about your system that you can provide? For example, are you using a non-standard OCI runtime, such as
podman? I've added detection forpodman-composein the script, but I haven't tested it yet. If you're using something like that, you'll need to ensure all the permissions are set up correctly.Shouldn't be anything odd, I had used the ansible script but had run the install from that.
From a quick Google search, it looks like there may have been a bug in the Docker engine a few months ago that might cause this. If possible, please update your Docker engine.
If the issue still occurs, unfortunately this is a core Docker engine/Docker Compose issue, and outside of my ability to fix :(
Re-installed docker-compose for different source and still not working
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:
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!
It looks like I had to enable nesting in proxmox