Docker Invalid Configuration File

[porter75]

Docker Compose is all new to me. I recently setup a UGREEN NAS and have deployed a handful of projects at this point that have been successful. UGREEN makes it extremely simple to deploy dockers on their devices. Now trying to setup the Project-NOMAD using the docker compose file from https://github.com/Crosstalk-Solutions/project-nomad/blob/main/install/management_compose.yaml and running into an issue. I keep getting the error "Invalid configuration file" with no indication of where the error is occuring.

I have replaced all the "replaceme" entries, updated the access URL, changed the APP KEY, and left everything else default. I haven't changed any of the port numbers or anything like that. I am not a programmer, so I don't know all the language or why something might cause it to behave this way. I put the code into AI and it told me Dozzle was only up to v5.0 and to change the v10.0 to "latest." That didn't fix it.

Then it spit back something about older versions of Docker Compose not liking the multi-option volume string in the "/:/host:ro,rslave" line of the disk-collector service. I haven't tried to make any changes to that because I'm not sure what to change it to as the notes indicate both the ro and rslave are necessary.

I feel like I'm missing a step somewhere.

Any help would be appreciated!

[NspxMiguel]

I checked the current management_compose.yaml from main. The unedited file passes:

docker compose -f management_compose.yaml config --quiet

with Docker Compose v5.3.1. I also checked amir20/dozzle:v10.0: that tag exists and has a multi-platform manifest. An image tag would fail during the pull rather than produce an "Invalid configuration file" message, so changing it to latest will not fix this validation error. The /:/host:ro,rslave mount is valid Compose short syntax as well.

That narrows this down to either UGREEN's Compose parser or an edit made while replacing the placeholders. If SSH is enabled on the NAS, the most useful next step is to run:

docker compose version
docker compose -f /path/to/management_compose.yaml config

The second command should print the actual unsupported key or YAML line that the UGREEN UI hides.

For a compatibility test in the UGREEN Project editor, remove only these entries:

name: project-nomad

and each of the three occurrences of:

pull_policy: always

UGREEN already asks for the project name, and removing pull_policy only means updates need an explicit pull; neither change alters NOMAD's services or data. Some embedded Compose frontends reject these newer fields even though current Docker Compose accepts them. Keep /:/host:ro,rslave unchanged unless the validator specifically identifies that line.

Also check the replaced values:

• APP_KEY must be at least 16 characters.
• DB_PASSWORD and MYSQL_PASSWORD must match exactly.
• Do not paste a value containing a newline.
• If a value contains YAML-significant punctuation, quote the whole list item, for example - "APP_KEY=your-value".

If the compatibility edit still fails, paste the exact output of docker compose ... config plus docker compose version (with passwords removed). That will identify the remaining line without guessing.

[porter75]

Thank you for the input.

So I ran:
docker compose version
It says Docker Compose v5.1.3

docker compose -f /path/to/management_compose.yaml config
I changed the path to where the management_compose.yaml is and it said
"open /home//shared folder/docker/project-nomad/opt/project-nomad/management_compose.yaml"
"unknown docker command compose folder/docker/project-nomad/opt/project-nomad/management_compose.yaml"

I realized it was looking in my User Folder before the path I gave it rather than on the volume and in the correct folder. Neither here nor there, but I did manage to get it to look in the correct directory, it found the file and the command just spit back the entire contents of the .yaml file, minus the # notes.

I proceeded to delete the "name: project-nomad" and the three instances of "pull_policy: always." No change in result.

I also noted that port 8080 happened to be the same port as another container that I am unable to change, so I changed all the listening ports to 9090 as described in the notes, while leaving the one PORT=8080 alone. Still no change. I then changed that port to 9090 as well, still no change.

I'm kind of at a loss at this point.

[porter75]

As I said in my previous response, I recognized there were some issues with pointing to the correct folders, so I went through some of my other containers and noted that I had actually given the full path on the volume in some cases. So I went through and changed all of those paths. In addition, I changed all the 8080 listening ports to 9090, leaving the admin and health check port alone. After that, I was still having issues so I put it into Google AI. It gave me some other commands to run and based on the error it determined I had another port conflict with Dozzle. Once I changed that port and ran the docker compose up -d from a terminal it took off.

Everything seems to be working now. As much as I gripe about AI, it's actually useful for something.