ModuleNotFoundError: No module named 'bleach' - latest-dev tag (docker image)

[seminip]

Using docker to run Apache Supset locally. No issue with other tags such as 2.1.0
But getting this error (following screenshot shows logs of superset-init container) for latest-dev tag:

Sorry first time opening a ticket.

[matheusbsilva]

@seminip what was the solution?

[seminip]

@seminip what was the solution?

It got fixed when I completely removed the docker images, associated volumes, and pulled and upped everything again. I also cloned a fresh superset repository and ran npm ci locally as well in superset-frontend.

[roxxrroy]

Hello @seminip ,
I am doing these step to first clone,install and run the superset code repo in my local system for creating visualization plugin-

git clone https://github.com/apache/superset.git
cd superset
git checkout 2.1.0
docker-compose up

but i am getting error that - superset_worker | ModuleNotFoundError: No module named 'bleach'

What exactly do i need to do ??

Even i asked question here on below link -
https://stackoverflow.com/questions/76668038/facing-issue-in-installation-of-superset2-1-0-for-creating-visualization-plug

[seminip]

Hi @roxxrroy
Can you try these steps:

(Note that I used node version 16.10.0)
Make sure you are in the branch you want (2.1.0). Go to superset-frontend folder and remove your node modules if you have them.
rm -rf node_modules
then install node modules using:
npm ci

Then:

docker-compose down -v
docker-compose build --no-cache
docker-compose up -d --force-recreate

[roxxrroy]

Thanks a lot @seminip Above Steps worked ,FInally i was able to open the Superset dashboard in development mode.Now i can proceed with my development work.

[seminip]

Thanks a lot @seminip Above Steps worked ,FInally i was able to open the Superset dashboard in development mode.Now i can proceed with my development work.

No worries, glad to help! Also, hope you don't mind if I post the answer in your stackoverflow link as well (over there, my username is Jolly Good)

[roxxrroy]

Yes sure, please add your answer there as well.

[m-usai-almaviva]

For others getting here from google, the solution for me was adding TAG=2.1.0 before any docker compose up command.

e.g.

TAG=2.1.0 docker compose up -d --force-recreate

From this issue

P.S.: please also don't forget to run the init script, otherwise the default credentials won't work:

TAG=2.1.0 docker compose exec superset bash /app/docker/docker-init.sh

(this command won't work in windows environments, you will have to use dos2unix

More info about this in this issue

[alephpt]

none of the above worked for me on 2.1.1 or 2.1.0

simply adding it to to docker/requirements-local.txt fixed it

bleach==6.0.0