default login/password not known after bringing up the Docker container

[wtian]

[SIP] Proposal for make the Docker image login/password clear

Motivation

After successfully installing the Docker image, bringing up the container and pointing my browser to http://localhost:8088, I am asked to login. But I have no idea what the default login/password combo is.

Proposed Change

Make it clear what the default login/password is, either by mentioning it in the install guide or using greyed-out placeholder in the input fields.

[maksimu]

And what is the default username and password?

[dancrew32]

So I missed this during install as well, but it prompts you to create a username, first, last, email, and password at this phase:

~/src/superset/contrib/docker$ docker-compose run --rm superset ./docker-init.sh
Starting superset_postgres_1 ... 
Starting superset_redis_1 ... done
+ '[' 1 -ne 0 ']'
+ exec ./docker-init.sh
+ export FLASK_APP=superset:app
+ FLASK_APP=superset:app
+ flask fab create-admin
Username [admin]: admin
User first name [admin]: admin
User last name [user]: admin
Email [admin@fab.org]: admin@fab.org
Password: 
Repeat for confirmation: 

you can try docker exec -it superset_superset_1 bash and run ./docker-init.sh to trigger this same prompt:
https://github.com/apache/incubator-superset/blob/master/contrib/docker/docker-init.sh#L22

[stale]

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.

[ManuelLevi]

Try admin:admin. Couldn't find it on the documentation, to find them, I had to investigate and find them in the docker-init.sh script.
This should be in the documentation.

[sibblegp]

This should absolutely be documented. It's like hitting a brick wall.

[daniel-zahariev]

I used docker-compose exec superset bash /app/docker-init.sh

[KuriaMaingi]

I used docker-compose exec superset bash /app/docker-init.sh

This worked for me but with a slight modification directly to the superset app:
docker-compose exec incubator-superset_superset_1 bash /app/docker-init.sh

[willbarrett]

Thanks all for bringing this to the community's attention. I've opened a PR to update our docs.

[willbarrett]

Documentation PR has been merged, the default username/password will appear on https://superset.incubator.apache.org/installation.html on the next update.

[Zonalds]

I am running the image on GKE but when I try the admin and admin for the username and password it doesn't work. I suppose the admin was not created. Any idea how to create the admin?

I read a few posts that suggest I need to navigate to contrib/docker to create the admin. Any idea how to navigate to contrib/docker on GKE?

[jonahbenton]

As of early June, for GKE, the stable channel helm chart for superset defaults to production-mode, which does not create an initial admin user.

I am working through getting the chart to start with development-mode, which does, but the chart templates have some problems, including hard-coding the production port. Will post again when I get them working.

[mirwaisx]

As of early June, for GKE, the stable channel helm chart for superset defaults to production-mode, which does not create an initial admin user.

I am working through getting the chart to start with development-mode, which does, but the chart templates have some problems, including hard-coding the production port. Will post again when I get them working.

yes I can confirm, for me just for testing purpose I created the user manually as mentioned here #10149

[tomrod]

I followed the instructions here with fresh install and git pull and admin:admin does not work:

https://superset.incubator.apache.org/docs/installation/installing-superset-using-docker-compose

[nytai]

@tomrod do you have logs for the superset_init container? That container should run a script that creates the admin user. Either that script hasn't finished running or it has errored out.

[tomrod]

Happy to check. Apologies for being a bit a newb, how do I grab that?

[nytai]

https://docs.docker.com/engine/reference/commandline/logs/

[tomrod]

$ docker logs e9417a5c1755
/usr/bin/env: ‘bash\r’: No such file or directory
/usr/bin/env: ‘bash\r’: No such file or directory

[nytai]

@tomrod are you running this on a windows machine by chance?

[tomrod]

Giving it a go with docker+wsl

…

On Tue, Sep 22, 2020, 9:54 PM ʈᵃᵢ ***@***.***> wrote: @tomrod <https://github.com/tomrod> are you running this on a windows machine by chance? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7336 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAND3FBA4RC3EWV53ECWIFLSHFPPRANCNFSM4HHJHB2Q> .

[tomrod]

That said, why would installing on windows make admin:admin user account not be created?

[nytai]

because the script that creates the admin user is erroring out due to the way windows formats files.

see https://stackoverflow.com/questions/29045140/env-bash-r-no-such-file-or-directory

[nytai]

I'm surprised you even got the app stood up running on windows

[tomrod]

Looks like the login issue was related to carriage returns -- fetching the repo via WSL and rebuilding fresh removed the login issue.

However, the app does not appear to be running after login, which is beyond scope of this issue :) -- I'll give it a go in a VM instead

[nytai]

@tomrod the app is running, the frontend hasn't finish building yet so you're getting this blank page. Give it a while longer and it should load up. The logs from superset_node should give you a clue as to the progress

[tomrod]

Thanks! Will do. We're looking to evaluate this for our healthcare R&D group -- visually looks nice, looking forward to evaluating.

…

On Tue, Sep 22, 2020 at 10:31 PM ʈᵃᵢ ***@***.***> wrote: @tomrod <https://github.com/tomrod> the app is running, the frontend hasn't finish building yet so you're getting this blank page. Give it a while longer and it should load up. The logs from superset_node should give you a clue as to the progress — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7336 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAND3FEVQ37QLWG4W6M4ME3SHFTZPANCNFSM4HHJHB2Q> .

[tomrod]

Up and running on Windows 10 Home w/ Docker Desktop +WSL

[ShaileshAdhikari]

Looks like the login issue was related to carriage returns -- fetching the repo via WSL and rebuilding fresh removed the login issue.

However, the app does not appear to be running after login, which is beyond scope of this issue :) -- I'll give it a go in a VM instead

Up and running on Windows 10 Home w/ Docker Desktop +WSL

Hello tomrod, I am having the same issue and using the same system Windows 10 Docker Desktop + WSL. I followed many fixes but nothing is working ! Can yo provide some insights, how do you make it work !

[tomrod]

I pulled the repo using git in Debian Linux WSL instead of Windows. This fixed the carriage return issues. I then let it run for several minutes after docker said setup was done before attempting to log in. There may be some background processes that should be logged.

…

On Mon, Oct 19, 2020, 10:49 AM ShaileshAdhikari ***@***.***> wrote: Looks like the login issue was related to carriage returns -- fetching the repo via WSL and rebuilding fresh removed the login issue. However, the app does not appear to be running after login, which is beyond scope of this issue :) -- I'll give it a go in a VM instead [image: image] <https://user-images.githubusercontent.com/1719700/93962997-aa3b9100-fd21-11ea-8419-94f499439ab2.png> Up and running on Windows 10 Home w/ Docker Desktop +WSL Hello tomrod, I am having the same issue and using the same system Windows 10 Docker Desktop + WSL. I followed many fixes but nothing is working ! Can yo provide some insights, how do you make it work ! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7336 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAND3FC52JZKDNY7T4CZTB3SLRNYXANCNFSM4HHJHB2Q> .