Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

docker-init.sh is hanging when initializing in docker

See original GitHub issue

I have run docker-compose up for several times and the issue was still there. It will stuck in the same issue.

Superset version

latest commit in master

Expected results

Initialization was executed correctly.

Actual results

The log prints the below info and it will stuck there forever:

INFO [alembic.runtime.migration] Running upgrade bebcf3fed1fe, 705732c70154 -> ec1f88a35cc6, empty message INFO [alembic.runtime.migration] Running upgrade 4451805bbaa1, 1d9e835a84f9 -> e3970889f38e, empty message INFO [alembic.runtime.migration] Running upgrade 705732c70154, e3970889f38e -> 46ba6aaaac97, empty message INFO [alembic.runtime.migration] Running upgrade 46ba6aaaac97, ec1f88a35cc6 -> c18bd4186f15, empty message INFO [alembic.runtime.migration] Running upgrade c18bd4186f15 -> 7fcdcde0761c, Reduce position_json size by remove extra space and component id prefix INFO [alembic.runtime.migration] Running upgrade 7fcdcde0761c -> 0c5070e96b57, add user attributes table INFO [alembic.runtime.migration] Running upgrade 0c5070e96b57 -> 1a1d627ebd8e, position_json INFO [alembic.runtime.migration] Running upgrade 1a1d627ebd8e -> 55e910a74826, add_metadata_column_to_annotation_model.py INFO [alembic.runtime.migration] Running upgrade 55e910a74826 -> 4ce8df208545, empty message INFO [alembic.runtime.migration] Running upgrade 4ce8df208545 -> 46f444d8b9b7, remove_coordinator_from_druid_cluster_model.py INFO [alembic.runtime.migration] Running upgrade 46f444d8b9b7 -> a61b40f9f57f, remove allow_run_sync INFO [alembic.runtime.migration] Running upgrade a61b40f9f57f -> 6c7537a6004a, models for email reports INFO [alembic.runtime.migration] Running upgrade 6c7537a6004a -> 3e1b21cd94a4, change_owner_to_m2m_relation_on_datasources.py`

Steps to reproduce

Run git clonne the repo
cd contrib/docker
run docker-compose up
run docker exec -it <<superset id>> /bin/bash
run ./docker-init.sh and it will hang on the above line forever.

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:7 (1 by maintainers)

Top GitHub Comments

1reaction

nickwareingcommented, Jan 24, 2019

Same here. It would be really helpful if someone could point users at a branch or revision where the docker setup works. I’ve never been able to get this thing running (last tried back in December and got some other error, now this).

0reactions

stale[bot]commented, Jun 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

Top Results From Across the Web

docker-init.sh is hanging when initializing in docker #6733

I have run docker-compose up for several times and the issue was still there. It will stuck in the same issue.

Why is my Docker-Compose getting stuck after initializing ...

I have written a script that creates the base images for the DB and weblogic server and then proceeds to use the docker-compose...

docker swarm init

docker swarm init: Initialize a swarm. The docker engine targeted by this command becomes a manager in the newly created single-node swarm.

kind – Known Issues - Kubernetes

This is a issue that frequently occurs when running kind alongside Docker For Mac. ... [0116 08:30:53] 1: /go/src/k8s.io/kubernetes/hack/lib/golang.sh:614 ...

Debugging a Broken Docker Compose Service Which ...

Here's my favourite: One of your docker-compose services keeps crashing, with an obscure error message which isn't enough to fix the issue. Unfortunately,...