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
Standard docker naming conventions suggest the file should be docker-compose.dev.yml. At the moment however, Balena CLI uses that file naming convention for a different use case which would conflict if the file was renamed.
Balena also doesn't support specifying a specific docker-compose file to use for building. Ideally the development environment would be docker-compose.yml and the production docker-compose.prod.yml. Feature request has already been made to specify a docker-compose file for production building: balena-io/balena-cli#1142
The text was updated successfully, but these errors were encountered:
Standard docker naming conventions suggest the file should be docker-compose.dev.yml. At the moment however, Balena CLI uses that file naming convention for a different use case which would conflict if the file was renamed.
Have requested the conflicting Balena feature be changed to follow standard docker conventions:
balena-io/balena-cli#2241 (comment)
balena-io/balena-cli#1142 (comment)
Balena also doesn't support specifying a specific docker-compose file to use for building. Ideally the development environment would be docker-compose.yml and the production docker-compose.prod.yml. Feature request has already been made to specify a docker-compose file for production building: balena-io/balena-cli#1142
The text was updated successfully, but these errors were encountered: