Lagoon Build Errors and Warnings#
Newer releases of Lagoon have the capability to identify potential issues with the build, and highlight them as warnings without failing. This is also a way for the Lagoon team to inform users of pending deprecations and changes to functionality.
For example, if the Lagoon team makes a change to a setting in lagoon.yml, and there’s something that users need to change, the warning will mention it, so users will be able to change it before it becomes a breaking change. They should be resolved ASAP wherever possible, as future releases of Lagoon may not be able to handle the errors, but they shouldn't stop your build.
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.
Docker Compose Errors#
Please also see the section on Common Docker Compose Issues, as some of these issues may be covered there
> 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.
> 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.
> 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.