You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/06/02 14:05:50 UTC
[GitHub] [superset] shawnzhu commented on issue #14867: Docker apache/superset:latest not working
shawnzhu commented on issue #14867:
URL: https://github.com/apache/superset/issues/14867#issuecomment-853057418
I can not reproduce this problem when `apache/superset:latest` with digest `414cf8967ba2`:
```SHELL
$ docker images --digests | grep apache/superset
docker.io/apache/superset latest sha256:414cf8967ba22fc50e86a0545ae14e26be7745bab0d1d8fe9c827cdebc752d93 fea52a0010a2 4 minutes ago 1.48 GB
$ docker run -d -p 8080:8088 --name superset apache/superset
ec75e84e25151536d729399568ece529da0328c4ee952d0dbaa6b2ecae952b1c
$ docker logs ec75e84e2515
[2021-06-02 13:59:32 +0000] [2] [INFO] Starting gunicorn 20.0.4
[2021-06-02 13:59:32 +0000] [2] [INFO] Listening at: http://0.0.0.0:8088 (2)
[2021-06-02 13:59:32 +0000] [2] [INFO] Using worker: gthread
[2021-06-02 13:59:32 +0000] [5] [INFO] Booting worker with pid: 5
logging was configured successfully
2021-06-02 13:59:33,908:INFO:superset.utils.logging_configurator:logging was configured successfully
2021-06-02 13:59:33,922:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
```
@pinduvn Do you mind delete the image `apache/superset:latest` then fetch it again? this issue should be fixed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org