-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Unable to start localstack #514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I had the same issue on Ubuntu. I had to do the following then reinstall localstack to get things working:
|
Thanks for reporting @lyenliang . This looks like a transient installation error, for some reason the
|
Hi, I have the same issue but when I run localstack inside the docker container. If I try locally instead, it works fine. Any suggestions? |
I have a similar issue while attempting to start kinesis on localstack within docker container.
UPDATE* |
Same here. In my case, it only occurred when launching all services and data persistency enabled. |
In case it's helpful for anyone, I was getting this error when running with
I was able to resolve it by running |
$ localstack start
on running command 'localstack start' it ran fine but when I hit any url like dynamodb |
Hey could you resolve that issue ? |
@lyenliang After a lot of time waste looking everywhere for the solution I found the following. Note: I'm using Win10 and WSL, I can't guarantee would be the same on a genuine linux distro. After installing nodejs, npm, pip, java and localstack using:
when running
Using
Reading around I found that there are some files that have to be removed before reinstalling localstack. My problem was that none of the path indicated was existing in my environment
I decided to remove the whole
And running again
For now I don't need ElasticMQ, but obviously there are still some problems with that I can confirm that now when hitting
I believe this is a problem with the parameters of the get request maybe, isn't it? Last update I can say that despite of this error:
I send commands to DynamoDb, S3 and API Gateway using AWS cli and receive correct responses. So, everything seems working perfectly
|
I had this issue also and even after deleting the I'm running on Mac and found that the files were in the tmp directory under To find them just run:
Delete these files and the |
I solved the issue to delete the image and pull again. I hope it helps you π
|
I solved the issue by installing on JDK 8 and maven (my bad for not reading the prerequisits properly).
|
I was having this same issue and simply deleting the local data/ folder mapped by $DATA_DIR, then starting Local Stack again fixed this problem for me. |
I solved the issue. Basically I was zipping a file during the container initialization and that was causing me issues. |
Got the error after upgrading to a new nodejs version and for me, the solution was |
Thanks all for posting the solutions here. Closing this issue as outdated/fixed. Please open a follow-up issue if the problem persists. Thanks |
I'm behind the times, but hit this issue on MacOs and resolved with:
|
Hi, I get the following error when starting localstack using
DEBUG=1 localstack start
command:I've read #241 and tried the following command to see if it can solve my problem, but it fails.
I add
--user
option because I'm using macOS. (see #248 for how to install localstack on macOS)It seems like that the error has something to do with
DynamoDBLocal.jar
. Because localstack cannot find this file.Anyone knows how to solve this problem?
The text was updated successfully, but these errors were encountered: