> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/configure-the-integration-with-docker-hub.md).

# Configure the integration with Docker Hub

How to configure the Snyk integration with Docker Hub

This page explains how to enable and configure the integration between Docker Hub and Snyk. When the integration is complete, you can start managing your vulnerabilities.

{% hint style="info" %}
For the integration with Docker Hub, Snyk does not support Organization Access Tokens (OAT).
{% endhint %}

## Enable the integration with Docker Hub

1. Navigate to **Integrations**.
2. Click **Docker Hub**.
3. Enter your Docker Hub username and Access Token.
4. Click **Save**.\
   The page reloads with new options. The **Access Token** field is blank.\
   A confirmation message that the details were saved also appears in green at the top of the screen.

If the connection to Docker Hub fails, an error notification appears.

## Troubleshooting with the Docker Hub integration

If issues occur, such as failure to import Projects, failure to connect, and no error shown, first try generating a new Access Token and resaving the Docker Hub integration on the Snyk settings page.

### Generate Docker Hub Access Token

1. Navigate to <https://hub.docker.com/settings/security>
2. Select **New Access Token**.
3. Enter the Access Token description.
4. Set the permissions (Read is required and sufficient), and click **Generate**.
5. Select **Copy Access Token** for use with the username when you [enable integration with Docker Hub](#enable-the-integration-with-docker-hub).

More information on [Docker Hub Access Tokens](https://docs.docker.com/docker-hub/access-tokens/) is available in the Docker Hub docs.

### Unauthorized access or Resource does not exist

This error occurs when importing images from Docker Hub fails, and you receive the error `Unauthorized access or Resource does not exist`*.*

![Unauthorized access or Resource does not exist error message](https://2730497224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBJO0IZx7zB6bOkotxQP2%2Fuploads%2Fgit-blob-a1c3112f762f53d94a382899b02ad544e09eb106%2Fscreen-shot-2021-04-28-at-2.13.11-am.png?alt=media)

This error occurs because your image is private on your Docker Hub account. To resolve this, navigate to your repository's **Settings** > **Visibility settings** section in Docker Hub and make the image public.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/configure-the-integration-with-docker-hub.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.