Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #665] [CLOSED] Fixed docker-compose report error: Additional property name is not al… #3449

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

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/665
Author: @phuang07
Created: 2/1/2024
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (1)

  • 1c6ee1e Fixed docker-compose report error: Additional property name is not allowed

📊 Changes

1 file changed (+0 additions, -2 deletions)

View changed files

📝 docker/docker-compose.yml (+0 -2)

📄 Description

…lowed

Pull Request Type

  • ✨ feat
  • [x ] 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Relevant Issues

resolves #xxx

What is in this change?

Remove invalid property in the docker-compose.yaml

Additional Information

When run docker-compose up there's an error: Additional property name is not allowed.
This patch fix this.

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/665 **Author:** [@phuang07](https://github.com/phuang07) **Created:** 2/1/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`1c6ee1e`](https://github.com/Mintplex-Labs/anything-llm/commit/1c6ee1e12f3dc9195da2edc6700fbc1123db331b) Fixed docker-compose report error: Additional property name is not allowed ### 📊 Changes **1 file changed** (+0 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docker/docker-compose.yml` (+0 -2) </details> ### 📄 Description …lowed ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [ ] ✨ feat - [x ] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #xxx ### What is in this change? Remove invalid property in the docker-compose.yaml ### Additional Information When run `docker-compose up ` there's an error: Additional property name is not allowed. This patch fix this. ### Developer Validations <!-- All of the applicable items should be checked. --> - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:33:48 -05:00
yindo closed this issue 2026-02-22 18:33:48 -05:00
yindo changed title from [PR #665] Fixed docker-compose report error: Additional property name is not al… to [PR #665] [CLOSED] Fixed docker-compose report error: Additional property name is not al… 2026-06-05 15:13:29 -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 pull-request
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#3449
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?