search

kuwala-io / kuwala

Kuwala is the no-code data platform for BI analysts and engineers enabling you to build powerful analytics workflows. We are set out to bring state-of-the-art data engineering tools you love, such as Airbyte, dbt, or Great Expectations together in one intuitive interface built with React Flow. In addition we provide third-party data into data science models and products with a focus on geospatial data. Currently, the following data connectors are available worldwide: a) High-resolution demographics data b) Point of Interests from Open Street Map c) Google Popular Times
https://kuwala.io
Apache License 2.0
788 stars 52 forks source link

ERROR: The Compose file './docker-compose.yml' is invalid because #75

Open patilauminfi opened 2 years ago

patilauminfi commented 2 years ago

when I try to run this command I get following issue. sudo docker-compose build osm-poi osm-parquetizer


ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.admin-boundaries: 'profiles'
Unsupported config option for services.database-importer: 'profiles'
Unsupported config option for services.database-transformer: 'profiles'
Unsupported config option for services.google-poi-api: 'profiles'
Unsupported config option for services.google-poi-pipeline: 'profiles'
Unsupported config option for services.google-trends: 'profiles'
Unsupported config option for services.jupyter: 'profiles'
Unsupported config option for services.osm-parquetizer: 'profiles'
Unsupported config option for services.osm-poi: 'profiles'
Unsupported config option for services.population-density: 'profiles'
Unsupported config option for services.postgres: 'profiles'
Unsupported config option for services.torproxy: 'profiles'

However it runs successfully if I comment out profile and its subitems in .yml file. Is it right to do so? Would it create a problem ahead?

mattigrthr commented 2 years ago

Hi @patilauminfi! Removing the profile attribute in the .yml file would indeed cause issues and break things in the pipelines as they sometimes depend on each other.

I could not reproduce the error but my guess would be that your docker-compose version might not be the latest. Are you running docker-compose v2? We had people on Windows running into that so we've added the hint to the documentation.