Hello Release v0.9.6 docker build is failing with below error: Commands Executed

cd datahub
git clone <https://github.com/datahub-project/datahub.git> .
git checkout tags/v0.9.6 -b datahub_v0.9.6

DATAHUB_VERSION=v0.9.6 COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose -f docker/docker-compose.yml -f docker/docker-compose.override.yml -p datahub build datahub-frontend-react

Error

The artifacts need to be built outside the docker containers. I need the

-PuseSystemNode=false

since my system has a nodejs that is too new.

./gradlew -P useSystemNode=false dockerTag-version

$ docker image ls | grep v0.9.7
linkedin/datahub-elasticsearch-setup                                       v0.9.7-SNAPSHOT    1f42048cb864   10 minutes ago   26.3MB
acryldata/datahub-mysql-setup                                              v0.9.7-SNAPSHOT    906ea9111e86   10 minutes ago   58.4MB
linkedin/datahub-gms                                                       v0.9.7-SNAPSHOT    84f0fe2ae840   14 minutes ago   393MB
linkedin/datahub-mae-consumer                                              v0.9.7-SNAPSHOT    c65cb51c47da   14 minutes ago   391MB
linkedin/datahub-mce-consumer                                              v0.9.7-SNAPSHOT    15fba7f094b0   14 minutes ago   393MB
linkedin/datahub-kafka-setup                                               v0.9.7-SNAPSHOT    07c6bfa49e94   20 minutes ago   661MB

If you are just interested in the frontend container

./gradlew -P useSystemNode=false :datahub-frontend:dockerTag-version

If you are interested in building and running similar to quickstart, the following will build all the images and run the docker-compose

./gradlew -P useSystemNode=false quickstart

This was not the case with v0.9.5. Any specific reason for making this change in v0.9.6 ?

If I recall there was an issue with the gha action build which involved having to move the frontend zip, rather than the picking it up from where it was normally being built. Need to revisit it, since ideally that zip file is left where it is and everything builds correctly from the project root. See 1 and 2 - docker should be able to pickup the artifact from its original location and it did work locally however not when run via gha. Likely there is something to be fixed there which would allow both to work from the root of the project.