-
Notifications
You must be signed in to change notification settings - Fork 136
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
dynamodb-admin stopped working #473
Comments
What the |
I'm probably experiencing a similar issue. ECONNREFUSED error occurs from Docker image version 5.0.1. services:
dynamodb:
container_name: dynamodb-local
image: "amazon/dynamodb-local:latest"
command: "-jar DynamoDBLocal.jar -sharedDb -dbPath ./data"
ports:
- "8000:8000"
volumes:
- "./data/dynamodb:/home/dynamodblocal/data"
working_dir: /home/dynamodblocal
dynamodb-admin:
container_name: dynamodb-admin
image: aaronshaf/dynamodb-admin:latest
environment:
- DYNAMO_ENDPOINT=dynamodb:8000
ports:
- 8001:8001
depends_on:
- dynamodb It looks like dynamodb-admin is failing to connect to the dynamodb container. |
I found this tool instead and have been using it since 2 years. It has frequent updates as well. It has really good UI. |
dynamodb-admin docker image stopped working. My colleagues in the team also have this problem. We guess that it is due to the implementation — we swapped the docker image 'aaronshaf/dynamodb-admin:latest' with the outdated image 'instructure/dynamo-local-admin:latest', and it worked again.
If you now try to open 'dynamo-db' on 'localhost' under the correct port, this is what it looks like.
![image](https://private-user-images.githubusercontent.com/69196971/394653986-31eb07be-091b-4a67-84d6-8eb33c61ab5a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzExMzcsIm5iZiI6MTczOTMzMDgzNywicGF0aCI6Ii82OTE5Njk3MS8zOTQ2NTM5ODYtMzFlYjA3YmUtMDkxYi00YTY3LTg0ZDYtOGViMzNjNjFhYjVhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAzMjcxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWEyY2U5ZDJkM2M2NTQ4YzBhYTJiMzNlZWFhYjc2NmRlMzAyMmEwMmMwNDlkOWM5MjU5MTExM2E1ZGZmM2IxYzYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.9fBIbJE67rKBtxFK9xO2QLXQ4J50R87wH7GjM1tZT5U)
The container starts and throws no other errors.
![image](https://private-user-images.githubusercontent.com/69196971/394655130-c5b8ed05-c66b-443e-ae06-624feeebcf1a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzExMzcsIm5iZiI6MTczOTMzMDgzNywicGF0aCI6Ii82OTE5Njk3MS8zOTQ2NTUxMzAtYzViOGVkMDUtYzY2Yi00NDNlLWFlMDYtNjI0ZmVlZWJjZjFhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAzMjcxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTUzNjNjMjUyZDRlMmY1YjU1ZGI0M2MyYzc4MmM5OWFlOTc2ODE5ZDVmMjRiNjdjZGU3NjY3ZjYyNjkzMTc3NDImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.vdq4V7Fp2P_56op_IlnUW3BkbZcZzHyu3Jh9G_6RJWY)
This is the configuration in 'docker-compose.yaml'
![image](https://private-user-images.githubusercontent.com/69196971/394656125-a0da6d80-bbb0-46b6-b22d-5767461a6881.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzExMzcsIm5iZiI6MTczOTMzMDgzNywicGF0aCI6Ii82OTE5Njk3MS8zOTQ2NTYxMjUtYTBkYTZkODAtYmJiMC00NmI2LWIyMmQtNTc2NzQ2MWE2ODgxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAzMjcxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk4MTYxM2EyMTFkMDRlNzJmMTA2YjdhM2Y5Y2FhZGI5OTAzODVmOWVhZDhlOWViMjEyNDFlNzJiZWYwMjZhOWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.JwaUssmRNPddVCZhvc5RuGXH-G_7sXOsO9QRmA31Hng)
Current local setup
The text was updated successfully, but these errors were encountered: