Skip to content
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

When starting with Docker Compose I only see "Congratualtions, you ran your First Container" Page #31967

Open
3 tasks
brianndjojo opened this issue Jan 23, 2025 · 1 comment
Labels
install:docker Installation - docker container

Comments

@brianndjojo
Copy link

brianndjojo commented Jan 23, 2025

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

Image

Image

Superset version

master / latest-dev

Python version

Not applicable

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Copy link

dosubot bot commented Jan 23, 2025

I found a similar unsolved discussion titled Docker for testing Superset Failed in local, which might provide some insights or shared experiences [1].

For your issue with the 'docker-init' container being stuck in a loading state, here are a few steps you can take to troubleshoot:

  1. 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].

  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].

  3. 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.

  4. 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.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot dosubot bot added the install:docker Installation - docker container label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
install:docker Installation - docker container
Projects
None yet
Development

No branches or pull requests

1 participant