Cannot launch DynamoDB on Mac M1 architecture
See original GitHub issueActual Behaviour
When running dynamodb locally on my Macbook M1 Pro 2021 I get an unsatisifed link due to sqlite libs not being available for my archiecture:
Caused by: java.lang.UnsatisfiedLinkError: /foo/.dynamodb/DynamoDBLocal_lib/libsqlite4java-osx.dylib:
dlopen(/foo/.dynamodb/DynamoDBLocal_lib/libsqlite4java-osx.dylib, 0x0001): tried:
'/foo/.dynamodb/DynamoDBLocal_lib/libsqlite4java-osx.dylib'
(fat file, but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
'/usr/local/lib/libsqlite4java-osx.dylib' (no such file), '/usr/lib/libsqlite4java-osx.dylib' (no such file)
Expected Behaviour
Should start DynamoDB java program
Steps to reproduce it
Add steps to reproduce bugs or add information on the place where the feature should be implemented. Add links to a sample deployment or code.
LogCat for the issue
Provide logs for the crash here
Screenshots of the issue
Where-ever possible attach a screenshot of the issue.
Would you like to work on the issue?
Please let us know if you can work on it or the issue should be assigned to someone else.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:13 (4 by maintainers)
Top Results From Across the Web
Dynamodb local setup on M1 apple silicon mac - Stack Overflow
I was able to run DynamoDB installing a java version x86-64 architecture rather than arm64 and starting it up from a rosetta terminal...
Read more >DynamoDB-local on Apple Silicon - Justin Mason's Weblog
It allows you to run a local instance of the data store, ... using one of the new MacBooks with M1 Apple silicon,...
Read more >Using Jest-Dynamodb in Apple Silicon Platform Workaround
I have received a new 14″ Macbook Pro with M1 Pro CPU from work. ... Internal log WARNING: [sqlite] cannot open DB[1]: ...
Read more >Deploying DynamoDB locally on your computer
jar file. The application runs on Windows, Linux, macOS, and other platforms that support Java. Follow these steps to set up and run...
Read more >The project cannot built on M1 mac. Missing compatible ...
15. Error is not on import, when it tries to build (parse the structure), this comes up in the sbt window: / ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@helenabenatar, @VirtualVirtuoso, @RyanCCollins, @terozio, @ikeller96, @StampixSMO, @AndrewKeig, @patricksalazar
Hi all, Since we seem stuck on the maintainer trying to obtain credentials I published my forks of the two required modules so that people can move on with their business:
There are two ways to use the forks:
1. Reference my forked package on NPM
Replace your devDependency to
serverless-dynamodb-local
inpackage.json
with:NOTE Since serverless references plugins by name declared in
package.json
, this also means you must replace the plugin name inserverless.yml
:Note also that using
@
as the first character in a yaml string requires quotes to be present as well.2. Reference fork directly via
git+ssh
URIThis fetches the
serverless-dynamodb-local
module directly from my fork on github, which in turns uses the forked version ofdynamodb-localhost
which I’ve published to NPM as@henhal/dynamodb-localhost
. Since you may still name the pluginserverless-dynamodb-local
inpackage.json
, no need to rename the plugin inserverless.yml
.I hope the maintainers are OK with me doing this; I mean no disrespect but lots of people have been waiting for nearly 7 months for a version to be published now.
@henhal I can merge the PRs, but let me check who has the credentials for publishing to NPM and sort it out.