11 mo. ago • 66%

Mealie/Docker: Additional property is not allowed

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

9 comments

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
1
- 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/
  
  1
- That's the old 0.5.x version if Mealie which I already have running but want to migrate to V1.
  
  1
seems like you have a networks.networks key in your yaml, is that intended?

1
- 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: ipv4_address: 192.168.178.200
  
  networks: mvl: external: true
  
  at the end of the yaml
  
  1
  
  networks.mvl Additional property volumes is not allowed"
  
  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.
  
  1
Network Mvl External: true

Should be at the end and on the left like the storage part, that's what's blocking

1
Your YAML is formatted incorrectly. Under volumes you have three spaces to indent the item - mealie-data:/app/data/ and it should be two. Same with all the items under environment.

1

You've viewed 9 comments.