Closed kamzata closed 2 years ago
Can you get the logs of that container? Seems like the status is running, so I wonder if the container initialized incorrectly...
Can you get the logs of that container? Seems like the status is running, so I wonder if the container initialized incorrectly...
How can I get it?
The output of dokku mongo:info vidlydb
should have the container ID there :)
The output of
dokku mongo:info vidlydb
should have the container ID there :)
dokku@dokku:~$ dokku mongo:info vidlydb
=====> vidlydb mongo service information
Config dir: /var/lib/dokku/services/mongo/vidlydb/config
Config options: --storageEngine wiredTiger --auth
Data dir: /var/lib/dokku/services/mongo/vidlydb/data
Dsn: mongodb://vidlydb:14a301e949ea563ce655c406a4434ec6@dokku-mongo-vidlydb:27017/vidlydb
Exposed ports: -
Id: 110ad2faceaf88956167f0ad13a887888ae201076f67c9ca29b515ccf030d87e
Internal ip:
Links: vidly
Service root: /var/lib/dokku/services/mongo/vidlydb
Status: restarting
Version: mongo:5.0.3
dokku@dokku:~$ docker logs 110ad2faceaf88956167f0ad13a887888ae201076f67c9ca29b515ccf030d87e
WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
see https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2
see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814
Edit: I changed the VM CPU from kvm64 to host and now it works. Thanks!
Description of problem
I cannot create any Mongo database with Dokku. I receive this error: "Waiting for container to be ready ERROR: unable to connect"
Steps to Reproduce
Actual Results
Environment Information
dokku report Vidly
outputHow (deb/make/rpm) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Self-Hosted: Virtual Machine on Proxmox
Additional information
dokku ps:inspect vidly