Default docker-compose invalid #3

New issue

Closed

opened 2025-11-28 21:38:28 +00:00 by middaymoon · 4 comments

middaymoon commented

2025-11-28 21:38:28 +00:00

If I copy and paste the file at https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/src/branch/main/docker-compose.yaml and try to docker-compose up I get the following:

ERROR: The Compose file './docker-compose.yaml' is invalid because:
'name' does not match any of the regexes: '^x-'

You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.

Thankfully the returned error is very helpful but ideally the docker-compose would just work out of the box (plus or minus any custom mount paths).

If I copy and paste the file at https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/src/branch/main/docker-compose.yaml and try to `docker-compose up` I get the following: ``` ERROR: The Compose file './docker-compose.yaml' is invalid because: 'name' does not match any of the regexes: '^x-' You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1. ``` Thankfully the returned error is very helpful but ideally the docker-compose would just work out of the box (plus or minus any custom mount paths).

lonhdoan commented

2025-11-29 02:10:51 +00:00

I used "docker compose up" and it works well. Did you try to remove the "-" in the command?

spotizerrphoenix commented

2025-11-29 03:44:32 +00:00

Owner

@middaymoon you might want to try:
docker compose up -d

@middaymoon you might want to try: `docker compose up -d`

❤️ 1

middaymoon commented

2025-11-29 06:14:16 +00:00

Author

@lonhdoan wrote in #3 (comment):

I used "docker compose up" and it works well. Did you try to remove the "-" in the command?

That might work. I forgot that docker-compose is deprecated now. I'll mark as closed since it seems reasonable that's the solution. Use an up-to-date version of docker and don't bother with the separate docker-compose tool.

@spotizerrphoenix the -d isn't related. That's just the flag for running in detached mode. I was purposefully not detaching so I could see the container logs and check for errors.

@lonhdoan wrote in https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/issues/3#issuecomment-805: > I used "docker compose up" and it works well. Did you try to remove the "-" in the command? That might work. I forgot that docker-compose is deprecated now. I'll mark as closed since it seems reasonable that's the solution. Use an up-to-date version of `docker` and don't bother with the separate `docker-compose` tool. @spotizerrphoenix the `-d` isn't related. That's just the flag for running in detached mode. I was purposefully not detaching so I could see the container logs and check for errors.

🎉 1

middaymoon closed this issue

2025-11-29 06:14:16 +00:00

spotizerrphoenix commented

2025-11-29 21:02:04 +00:00

Owner

yup, just included that since it sounded like you were just trying to run the compose based on your original post

as you probably know, for running detached containers you can always tail logs with: docker logs -f --tail 100 {container_name}

to prevent confusion for other contributors, next time please clarify or include your full intended purpose in your original post

thank you

yup, just included that since it sounded like you were just trying to run the compose based on your original post as you probably know, for running detached containers you can always tail logs with: `docker logs -f --tail 100 {container_name}` to prevent confusion for other contributors, next time please clarify or include your full intended purpose in your original post thank you

👍 2