You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docker-compose.yml configuration file for setting up Frappe contains two issues:
1. Invalid version Field:
The version is set to 15.37, which is unsupported. Valid versions include "3.8" or "2.4".
2. Unsupported name Field:
The name field is not recognized by Docker Compose and should be omitted or set using the -p flag during execution.
Module
HR
Version
Frappe Version: Latest ERPNext Version: Not applicable Browser Version: Not applicable
Installation method
docker
Relevant log output / Stack trace / Full Error Message.
➜ docker git:(develop) ✗ docker-compose up
ERROR: Version "15.37"in"./docker-compose.yml" is invalid.
➜ docker git:(develop) ✗ docker-compose up
ERROR: The Compose file './docker-compose.yml' 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.For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/➜ docker git:(develop) ✗ sudo apt git python-is-python3 python3-dev python3-pip redis-server --version
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Information about bug
The docker-compose.yml configuration file for setting up Frappe contains two issues:
1. Invalid version Field:
2. Unsupported name Field:
Module
HR
Version
Frappe Version: Latest
ERPNext Version: Not applicable
Browser Version: Not applicable
Installation method
docker
Relevant log output / Stack trace / Full Error Message.
Code of Conduct
The text was updated successfully, but these errors were encountered: