Issue on pulling the docker and accessing it #24464
Replies: 4 comments
-
Can any one suggest what would be the fix for this |
Beta Was this translation helpful? Give feedback.
-
Hi @nk8291! Your issue title is misleading. This is a customizing question rather than a bug. You can join Superset Slack to ask for help in #customizing-superset. There you can provide more context. |
Beta Was this translation helpful? Give feedback.
-
Hi @sebastianliebscher , I have not done any customizations. Below are the steps followed for the setup and deployment:
after this we tried to access the dashboards in superset portal, and faced the attached issue. Although all the charts, dataset, database connection, users, roles are fine only dashboards were impacted and given issues occurred. So, I Suspect this must be related to re-deployment of the application/ restarting the docker container of the application related issue. |
Beta Was this translation helpful? Give feedback.
-
Can you share relevant parts of your docker-compose logs as I am not able to reproduce this issue with the provided steps? |
Beta Was this translation helpful? Give feedback.
-
Dear Community,
I have cloned the git and deployed the superset on centos server. After this over development team has created multiple dashboard and published it in superset portal.
Now we have done some changes in branding logos and executed the below commands for accessing the superset:
cd superset
docker-compose -f docker-compose-non-dev.yml down
docker-compose -f docker-compose-non-dev.yml pull
docker-compose -f docker-compose-non-dev.yml up -d
so when we accessed the superset portal, all charts are present and accessible. also I can see the list of dashboard created by developer. but when I try to open I get below error:
Unexpected error
Unexpected error: TypeError: Cannot convert undefined or null to object
Can you please how to fix this asap???
Beta Was this translation helpful? Give feedback.
All reactions