Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-24 12:05:51 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #466] docker-compose up -d --build failed with invalid docker-compose.yml #265

New Issue
Closed
opened 2026-02-22 18:18:38 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:18:38 -05:00
Owner
Copy Link
Copy Source

Originally created by @songkq on GitHub (Dec 17, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/466

Could you please give some advice for this issue?
My Env:

CentOS Linux version 3.10.0-1160.11.1.el7.x86_64
docker-compose version 1.27.4, build 40524192
docker-py version: 4.3.1
docker Version:           23.0.3

ERROR: The Compose file './docker-compose.yml' is invalid because:
Invalid top-level property "name". Valid top-level sections for this Compose file are: version, services, networks, volumes, secrets, configs, and extensions starting with "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.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
Originally created by @songkq on GitHub (Dec 17, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/466 Could you please give some advice for this issue? My Env: ``` CentOS Linux version 3.10.0-1160.11.1.el7.x86_64 docker-compose version 1.27.4, build 40524192 docker-py version: 4.3.1 docker Version: 23.0.3 ``` ``` ERROR: The Compose file './docker-compose.yml' is invalid because: Invalid top-level property "name". Valid top-level sections for this Compose file are: version, services, networks, volumes, secrets, configs, and extensions starting with "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. For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/ ```
yindo closed this issue 2026-02-22 18:18:38 -05:00
yindo commented 2026-02-22 18:18:38 -05:00
Author
Owner
Copy Link
Copy Source

@jamsnrihk commented on GitHub (Dec 18, 2023):

try to upgrade your docker-compose to lastest version

@jamsnrihk commented on GitHub (Dec 18, 2023): try to upgrade your docker-compose to lastest version
yindo commented 2026-02-22 18:18:38 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Dec 18, 2023):

Docker compose version is too low

@timothycarambat commented on GitHub (Dec 18, 2023): Docker compose version is too low
yindo commented 2026-02-22 18:18:39 -05:00
Author
Owner
Copy Link
Copy Source

@songkq commented on GitHub (Dec 18, 2023):

@timothycarambat @jamsnrihk Thanks.

@songkq commented on GitHub (Dec 18, 2023): @timothycarambat @jamsnrihk Thanks.
yindo changed title from docker-compose up -d --build failed with invalid docker-compose.yml to [GH-ISSUE #466] docker-compose up -d --build failed with invalid docker-compose.yml 2026-06-05 14:34:22 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#265
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?