this post was submitted on 22 Oct 2023
1 points (66.7% liked)

Self-Hosted Main

515 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

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

founded 1 year ago
MODERATORS
communick@selfhosted.forum
1
Mealie/Docker: Additional property is not allowed (alien.top)
submitted 1 year ago by RockingGamingDe@alien.top to c/main@selfhosted.forum
9 comments fedilink hide all child comments
 

Hi,

​

I'm fairly new to docker and ran in an issue settig up Mealie using Portainer on my Synology. I've altered their documentation here to include a specific IP in my home network using macvlan but when deploying the stack I get the error:

"Deployment error

failed to deploy a stack: validating /data/compose/24/docker-compose.yml: services.mealie.networks.networks Additional property mvl is not allowed"

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 # 
    volumes:
      - mealie-data:/app/data/
    environment:
    # Set Backend ENV Variables Here
      - ALLOW_SIGNUP=true
      - PUID=1024
      - PGID=100
      - TZ=Europe/berlin
      - MAX_WORKERS=1
      - WEB_CONCURRENCY=1
      - BASE_URL=https://mealie.yourdomain.com
    restart: always

volumes:
  mealie-data:
    driver: local

​

Other stacks I've deployed hadn't had an issue when adding the networks tab this way. What am I doing wrong? Thanks in advance

​

you are viewing a single comment's thread
view the rest of the comments
[–] krawhitham@alien.top 1 points 1 year ago (2 children)

This is what I use

  mealie-frontend:
    image: hkotel/mealie:frontend-nightly
    container_name: mealie-frontend
    environment:
      - API_URL=http://mealie-api:9000
    restart: always
    networks:
      - caddy
      - mealie-api
    volumes:
      - /home/docker/configs/mealie:/app/data
  mealie-api:
    image: hkotel/mealie:api-nightly
    container_name: mealie-api
    networks:
      - mealie-api
    volumes:
      - /home/docker/configs/mealie:/app/data
    environment:
    # Set Backend ENV Variables Here
      - ALLOW_SIGNUP=false
      - PUID=1000
      - PGID=1000
      - TZ=America/Anchorage
      - MAX_WORKERS=1
      - WEB_CONCURRENCY=1
      - BASE_URL=https://mealie.tom42.pw
    restart: always
[–] marwanblgddb@alien.top 1 points 1 year ago

You should review the new docker compose file, there have been some changes on how the app is built, there is no need for frontend and api anymore

there might be some breaks during the migration, be careful

https://nightly.mealie.io/documentation/getting-started/migrating-to-mealie-v1/

load more comments (1 replies)