I'm having trouble getting quickstart to run again...
# troubleshoot
r
I'm having trouble getting quickstart to run again.
Caught exception while executing bootstrap step IngestDataPlatformsStep. Exiting...
📖 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? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button 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!
r
Attaching log file
tmp_51l3xvj.log
prune and nuke don't help
o
Putting out a fix for this shortly
a
@red-painter-89141 I ended up deleting my virtual env folder and all installed packages. Deleted All containers in docker, along with Volumes. It did fix the issue, at the cost of losing everything in the instance.
o
This was a bug, I put out a fix for it. By doing the above you would have broken docker cache and gotten the new fixed images.
a
That's what I figured when I saw the default Quickstart behaviour is to take the master branch.
Thanks for the fix @orange-night-91387! I'm demoing to the team in 1h and was able to put out a local demo instance with the help of your fix 😛
a
Nice 😄 🎉
r
I still can't get it to work. I did a
datahub docker nuke
, then a
docker container prune
, then a
rm -rf ~/.datahub
@adorable-daybreak-45557 am I missing something?
@orange-night-91387 Any advice here? I'm fairly new here, and I don't know how to make sure I'm pulling the fix you mentioned. I've tried nuke/prune, removing .datahub, and a full pip uninstall and reinstall, still stuck.
a
I recall deleting Docker Volumes also. And as per Ryan's comment, your docker daemon need to pull newer images. Maybe there's a cache to clear on your side...