You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For your issue with the 'docker-init' container being stuck in a loading state, here are a few steps you can take to troubleshoot:
Verify Service Status: Use docker-compose ps to check if all services, especially 'db' and 'redis', are running correctly. These services are dependencies for the 'docker-init' container [2].
Inspect Logs: Check the logs for the 'docker-init', 'db', and 'redis' services using docker-compose logs <service_name> to identify any errors or issues during startup [2].
Resource Allocation: Ensure that your Docker environment has sufficient resources allocated. Given your system's CPU and memory usage, you might need to adjust Docker's resource settings to provide more memory or CPU if necessary.
Configuration Files: Double-check your .env and .env-local files for any misconfigurations that might affect the startup process [3].
These steps should help you identify and resolve the issue with the 'docker-init' container.
Bug description
I followed the instructions through Docker-Compose from the documentation provided by the Website.
Currently, I have some issues, but after hours of waiting the Container: 'docker-init' is still loading. Any ideas?
Screenshots/recordings
Superset version
master / latest-dev
Python version
Not applicable
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: