The issue was found at 1:00 PM EDT on October 15, 2019 and impacts users attempting to:
- Launch workflows that depend on Docker images hosted on Dockerhub
- Create new Notebook Runtime Environments
Dockerhub's status can be monitored at this link: https://status.docker.com. See the Timeline section for the latest troubleshooting and resolution updates and the Impact section to understand how this could impact your use of the system.
October 17, 2019 6:03 PM EDT - Issue Resolved - The 10/15 Docker Hub outage had an impact on Cromwell that extended into 10/16 and 10/17. This impact has now been resolved.
October 16, 2019 6:07 PM EDT - Issue Update - This Featured Post describes updated information on the status of the issue plus a workaround until DockerHub stabilizes. Runtime Environment creation does not seem to be affected at this time.
October 16, 2019 11:00 AM EDT - Issue Recurrence - DockerHub instability is resulting in KeyNotFound errors while running Workflow referencing images hosted on DockerHub.
October 15, 2019 2:36 PM EDT - Issue Resolved - Dockerhub outage has been fixed and workflows and new Runtime Environment creation should now be working as expected.
October 15, 2019 1:00 PM EDT - Issue discovered - Our internal team received notification of Dockerhub's downtime. This results in failed workflows dependent on docker images hosted on Dockerhub as well as creation of new Notebook Runtime Environments.
Users launching workflows that require a docker image hosted on Dockerhub will be blocked. Submitted workflows will fail until further notice.
Please follow this article to get the most up to date information on this incident. If you would like to be notified of all service incidents or upcoming scheduled maintenance, click Follow on this page.