-
Notifications
You must be signed in to change notification settings - Fork 150
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Lagoon Build Errors pages (#3608)
- Loading branch information
1 parent
c99a3b5
commit 8e7272e
Showing
3 changed files
with
57 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
24 changes: 24 additions & 0 deletions
24
docs/using-lagoon-the-basics/lagoon-build-errors-and-warnings.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Lagoon Build Errors and Warnings | ||
|
||
Newer releases of Lagoon have the capability to identify build errors, and highlight them as warnings without failing the build. They should be resolved wherever possible, as future releases of Lagoon may not be able to handle the errors. | ||
|
||
If you aren't sure how to resolve these errors, please reach out to your Lagoon administrator, or ask a question in the [Lagoon community](../community/discord.md). | ||
|
||
## Docker Compose Errors | ||
|
||
Please also see the section on [Common Docker Compose Issues](docker-compose-yml.md#common-docker-compose-issues), as some of these issues may be covered there | ||
|
||
``` shell title="Lagoon Build output indicating env_file error" | ||
> an env_file is defined in your docker-compose file, but no matching file found | ||
``` | ||
Docker Compose expects a referenced env file to be present at build time, but that env file is only present in local development, or has been excluded from the Dockerfile. The Lagoon team is working to hopefully allow Docker Compose to ignore this error, so this warning will remain until we have a resolution. | ||
|
||
``` shell title="Lagoon Build output indicating string key error" | ||
> an invalid string key was detected in your docker-compose file | ||
``` | ||
There is an error in your Docker Compose file, most likely relating to a malformed or misused alias or anchor. The error message should help you understand where. | ||
|
||
``` shell title="Lagoon Build output indicating yaml validation error" | ||
> There are yaml validation errors in your docker-compose file that should be corrected | ||
``` | ||
There is an error in your Docker Compose file, most likely relating to a malformed or misused alias or anchor. The error message should help you understand where. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters