# "rake aborted!" on "sudo bundle exec rake db:create" cmd (macOS M1)

**URL:** <https://meta.discourse.org/t/rake-aborted-on-sudo-bundle-exec-rake-db-create-cmd-macos-m1/238475>\
**Category:** Self-hosting\
**Created:** [September 8, 2022, 3:10pm UTC](https://meta.discourse.org/t/rake-aborted-on-sudo-bundle-exec-rake-db-create-cmd-macos-m1/238475 "2022-09-08T15:10:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![steinhh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/steinhh/32/242776_2.png) [@steinhh](https://meta.discourse.org/u/steinhh)\
**Post date:** [March 18, 2023, 2:08pm UTC](https://meta.discourse.org/t/rake-aborted-on-sudo-bundle-exec-rake-db-create-cmd-macos-m1/238475/9 "2023-03-18T14:08:18Z")

</div>

Hi @techAPJ, @YAN!

Has anything happened with this? I’m facing the same problem now, trying to upgrade from (stable branch) 3.0.1 to 3.0.2. This is on RHEL8 which I have to use given the security policies in place.

I’ve also tried to switch to the tests-passed branch, but to no avail. Something tells me “this has to be a versioning issue”… is it possible to get a dump of the Gemfile.lock from a functional installation?

Should probably mention that this happens during rake db:migrate, not db:create as for @YAN

Cheers,  
Stein Haugan

---

_[View the full topic](https://meta.discourse.org/t/rake-aborted-on-sudo-bundle-exec-rake-db-create-cmd-macos-m1/238475)._