Getting 500 Internal Server Error when pulling superset-cache image

[grg-ya-dot]

Trying to start superset, cloned repo from github, when starting docker compose -f docker-compose-non-dev.yml getting error couldn't download apache/superset-cache.
When running docker pull apache/superset-cache, getting error last 2 days:
latest: Pulling from apache/superset-cache
received unexpected HTTP status: 500 Internal Server Error

[dosubot[bot]]

Hey there, @grg-ya-dot! 👋 I'm here to help you with any bugs, questions, or contributions while waiting for a human maintainer. Let's squash those bugs together!

To troubleshoot and resolve a 500 Internal Server Error when pulling Docker images from Docker Hub, you can follow these steps:

1. Check Docker Hub Status: Verify if Docker Hub is experiencing any outages or issues by visiting Docker Hub Status.

2. Retry the Pull Command: Sometimes, the issue might be temporary. Retry the command:

   docker pull apache/superset-cache

3. Check Network Connectivity: Ensure that your network connection is stable and that there are no firewall or proxy settings blocking the connection to Docker Hub.

4. Docker Login: Make sure you are logged in to Docker Hub. Run:

   docker login

5. Clear Docker Cache: Clear Docker's cache to remove any corrupted or outdated data:

   docker system prune -a

6. Use Alternative Tags: Try pulling a different tag of the apache/superset-cache image. For example:

   docker pull apache/superset-cache:latest-dev

7. Manually Build the Image: If the issue persists, you can manually build the apache/superset-cache image. Follow the steps outlined here to create a Dockerfile and build the image locally.

If none of these steps resolve the issue, it might be a problem with the Docker Hub repository itself, and you may need to wait for Docker Hub to resolve the issue.

To continue talking to Dosu, mention @dosu.