1
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Oct 2023
1 points (66.7% liked)
Self-Hosted Main
504 readers
1 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.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
founded 1 year ago
MODERATORS
seems like you have a networks.networks key in your yaml, is that intended?
Even after changing that (at least I assume you meant that)
version: "3.7" services: mealie: image: ghcr.io/mealie-recipes/mealie:v1.0.0-RC1.1 container_name: mealie ports: - "9000:9000" # networks: mvl: ipv4_address: 192.168.178.196 networks: mvl: external: true deploy: resources: limits: memory: 2000M #
I still get
"Deployment error
failed to deploy a stack: validating /data/compose/39/docker-compose.yml: networks.mvl Additional property volumes is not allowed"
Is there something I'm misunderstanding? Other containers I've deployed successfully just include
networks: mvl: external: true
at the end of the yaml
Now your indentation is wrong. It assumes volumes as a option of networks, which doesnt work.
You should use sites like https://www.pastebin.com if you struggle with formatting YML on Reddit, because YML is very sensitive. And for Docker support use /r/Docker.
Got it working with another comment. I’ll dig deeper into the yaml/docker documentation, it’s 5:21am here so I‘ll definitely need to get some sleep