Hi team, experiencing this issue on my Docker Desk...
# troubleshoot
c
Hi team, experiencing this issue on my Docker Desktop environment on a Mac M1. @brainy-tent-14503 I’m posting the image to see if this can help based on our conversation this morning, thanks!!
📖 1
🔍 1
✅ 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
c
This is the command that keeps failing: ./gradlew quickstartDebug --stacktrace -x yarnTest -x yarnLint Unable to run quickstart - the following issues were detected: - broker is not running - mysql is not running - elasticsearch is not running - zookeeper is not running - datahub-frontend-react is not present - kafka-setup is not present - elasticsearch-setup is not present - schema-registry is not present - mysql-setup is not present - datahub-gms is not present - datahub-actions is not present - datahub-upgrade is not present If you think something went wrong, please file an issue at https://github.com/datahub-project/datahub/issues or send a message in our Slack https://slack.datahubproject.io/ Be sure to attach the logs from /var/folders/g4/jttgbd410h9d8yx2p4k540x80000gn/T/tmp6ki_0my8.log
Task dockerquickstartDebug FAILED
FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ‘dockerquickstartDebug’.
Process ’command ‘bash’' finished with non-zero exit value 1
a
Yes, this is definitely not right. These are images that are not built by us and are 3rd party dependencies. They should not have the warning and be a green color. These images are not even built by the build system and are merely referred to by their general name. Docker itself is responsible for pulling the correct image from dockerhub’s repo.
Attachment Links:

Screenshot 2023-04-11 at 3.52.39 PM.png▾

Make sure you did not enable rosetta
Attachment Links:

Screenshot 2023-04-11 at 3.55.34 PM.png▾

c
Okay, I appreciate it @brainy-tent-14503 !