Help with yml, values do not match any regexes

General
1

This is now solved, it was an indentation issue, which I had thought I had figured out, but missed.

I hope this is the right place. I am very new to Docker, and am following this guide. I tried copy/pasting the yml directly from the site but ran into some indentation errors/problems. I think I have all those worked out, and am now encountering the errors below.

 # docker-compose --verbose -f docker-compose.new.yml config
compose.config.config.find: Using configuration files: ./docker-compose.new.yml
ERROR: compose.cli.main.main: The Compose file './docker-compose.new.yml' is invalid because:
networks.healthcheck value 'disable', 'restart' do not match any of the regexes: '^x-'
networks.dns_net value 'ipv4_address', 'ports', 'volumes' do not match any of the regexes: '^x-'

Here is the yml I am using:

version: '3'

networks:
  dns_net:
    driver: bridge
  ipam:
    config:
    - subnet: 172.20.0.0/16

services:
  pihole:
    container_name: pihole
    hostname: pihole
    image: pihole/pihole:latest
networks:
  dns_net:
    ipv4_address: 172.20.0.6
  ports:
  - "53:53/tcp"
  - "53:53/udp"
  - "80:80/tcp"
  - "443:443/tcp"
  environment:
  - 'TZ=Australia/Sydney'
  - 'WEBPASSWORD=yourpasswd'
  - 'DNS1=172.20.0.7#5053'
  - 'DNS2=no'
  volumes:
  - '/home/pi/pihole/etc-pihole/:/etc/pihole/'
  - '/home/pi/pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/'
  restart: unless-stopped

  unbound:
  container_name: unbound
  image: mvance/unbound:latest
networks:
  dns_net:
    ipv4_address: 172.20.0.7
    volumes:
     - /home/pi/unbound:/opt/unbound/etc/unbound
    ports:
    - "5053:5053/tcp"
    - "5053:5053/udp"
  healthcheck:
    disable: true
    restart: unless-stopped

Can someone tell me what is wrong, or point me in a direction? This is on a ODROID-N2 running CoreELEC 9.2.5. I have ran this exact yml through a few different yml validators/checkers online, and it passes, and Google is no help with the two errors I am getting.

2

Your indentions are wrong. If you compare your compose.yml with the one from the tutorial, you should immediatly see whats wrong… Only the first 14 lines have correct indention.

Visual Studio Code has a nice plugin to support yaml editing: indent-rainbow
It will add different vertical colours for every two columns, which allows to niceley see how each line is indented.

3

Thank you, I thought I had the indentation right, but now I know I was wrong. I will go back, and try again. Thank you for the suggestion on Visual Studio Code, I might have to try it out, but for now I will stick with what I know Notepad++.

4

Is there a lint for compose.yml?

For example if one is creating JSON, then there is a lint for JSON, i.e. JSONLint

5

I know that docker-compose has a build in command to verify compose.yml. It is quite usefull if you work with extending a base config with additional configs, as it will render the final compose.yml to be applied during deployment.

[update] I missed that the first line of the first code block actualy leverages the validation. Even though it addresses the offending configuration items in a flattend representation, the lack of line numbers isn’t realy beginner friendly…[/update]

https://github.com/adrienverge/yamllint looks promissing. Though, not sure if there actualy is a docker-compose specific linter that covers all file versions. In reality it should be easy to implement: extend one of the existing linters, create a validation schema (v3 schemas can be found as json schema here) and make the linter validate the yml against the schema.

1 Like
6

I had a few paragraphs written but then read further and noticed you noted config_schema_v3.0.json which I fully agree should be a check done in the pipeline before using a compose.yml. I don’t know if I would consider it a full semantic check but it is better than a basic yml syntax check. :slightly_smiling_face: