Fix small issues

This commit is contained in:
Jeffrey Morgan 2018-11-21 16:49:26 -05:00
parent c0656fa7fa
commit 3602540596
33 changed files with 194 additions and 302 deletions

View File

@ -3647,8 +3647,6 @@ manuals:
title: Testing in Builds
- path: /docker-hub/builds/advanced/
title: Advanced Builds
- path: /docker-hub/builds/webhooks/
title: Build Webhooks
- path: /docker-hub/builds/github/
title: Connecting GitHub
- path: /docker-hub/builds/bitbucket/
@ -3657,7 +3655,7 @@ manuals:
section:
- path: /docker-hub/customer_faq/
title: Subscriptions
- path: /docker-store/publish/publisher_faq/
- path: /docker-hub/publish/publisher_faq/
title: Publishers
- path: /docker-hub/publish/
title: Publish Images & Plugins

View File

@ -85,9 +85,7 @@ bash _scripts/fetch-upstream-resources.sh -l
# Currently, this is:
# /samples/
# /docker-id/
# /docker-cloud/
# /docker-hub/
# /docker-store/
# These rely on _layout/archive-redirect.html
only_live_contents=("samples" "docker-id" "docker-cloud" "docker-hub" "docker-store")
@ -145,5 +143,3 @@ echo " and get back to master, run the following:"
echo
echo " git reset --hard; git clean -fd; git checkout master; git branch -D v$version"
echo

View File

@ -17,7 +17,7 @@ DTR installation:
## Download your license
Go to [Docker Store](https://store.docker.com/editions/enterprise/docker-ee-trial)
Go to [Docker Hub](https://hub.docker.com/editions/enterprise/docker-ee-trial)
and download your license.
![](../../images/license-1.png){: .with-border}

View File

@ -16,7 +16,7 @@ access.
Before you begin, make sure that you or your organization has purchased a DTR
license that includes Docker Security Scanning, and that your Docker ID can
access and download this license from the Docker Store.
access and download this license from the Docker Hub.
If you are using a license associated with an individual account, no additional
action is needed. If you are using a license associated with an organization
@ -36,7 +36,7 @@ this step and proceed to [enable DTR Security Scanning](#enable-dtr-security-sca
If your current DTR license doesn't include scanning, you must first download the new license.
1. Log in to the Docker Store using a Docker ID with access to the license you need.
1. Log in to the Docker Hub using a Docker ID with access to the license you need.
2. In the top right corner, click your user account icon, and select **My Content**.
3. Locate **Docker Enterprise Edition** in the content list, and click **Setup**.
4. Click **License Key** to download the license.
@ -141,12 +141,12 @@ Your choice is saved automatically.
To update the CVE database for your DTR instance when it cannot contact the update server, you download and install a `.tar` file that contains the database updates. To download the file:
1. Log in to the [Docker Store](https://store.docker.com/).
1. Log in to the [Docker Hub](https://hub.docker.com/).
If you are a member of an Organization managing licenses using Docker Store,
If you are a member of an Organization managing licenses using Docker Hub,
make sure your account is a member of the `Owners` team. Only Owners can
view and manage licenses and other entitlements for Organizations from the
Docker Store.
Docker Hub.
2. In the top right corner, click your user account icon, and select **My Content**.
3. If necessary, select an organization account from the **Accounts** menu at the upper right.

View File

@ -39,7 +39,7 @@ To sign images in a way that UCP trusts them, you need to:
* Initialize trust metadata for the repository
* Delegate signing to the keys in your UCP client bundle
In this example we're going to pull an NGINX image from Docker Store,
In this example we're going to pull an NGINX image from Docker Hub,
re-tag it as `dtr.example.org/dev/nginx:1`, push the image to DTR and sign it
in a way that is trusted by UCP. If you manage multiple repositories, you
need to do the same procedure for every one of them.
@ -56,11 +56,11 @@ the easiest way to do it is by pushing an image to that repository. Navigate to
the **DTR web UI**, and create a repository for your image.
In this example we've created the `dev/nginx` repository.
From the Docker CLI client, pull an NGINX image from Docker Store,
From the Docker CLI client, pull an NGINX image from Docker Hub,
re-tag it, sign and push it to DTR.
```bash
# Pull NGINX from Docker Store
# Pull NGINX from Docker Hub
docker pull nginx:latest
# Re-tag NGINX

View File

@ -9,7 +9,7 @@ collection that contains one service.
1. Create an organization and a team.
2. Create a collection for the view-only service.
3. Create a grant to manage user access to the collection.
3. Create a grant to manage user access to the collection.
![](../images/view-only-access-diagram.svg)
@ -22,9 +22,9 @@ who isn't an administrator to the team.
1. Log in to UCP as an administrator.
2. Navigate to the **Organizations & Teams** page and click
**Create Organization**. Name the new organization "engineering" and
click **Create**.
click **Create**.
3. Click **Create Team**, name the new team "Dev", and click **Create**.
3. Add a non-admin user to the Dev team.
3. Add a non-admin user to the Dev team.
## Create a collection for the service
@ -36,7 +36,7 @@ who isn't an administrator to the team.
![](../images/deploy-view-only-service-1.png)
The `/Shared/View-only services` collection is ready to use for access
The `/Shared/View-only services` collection is ready to use for access
control.
## Deploy a service
@ -48,7 +48,7 @@ collection.
1. Navigate to the **Services** page and create a new service, named
"WordPress".
2. In the **Image** textbox, enter "wordpress:latest". This identifies the
most recent WordPress image in the Docker Store.
most recent WordPress image in the Docker Hub.
3. In the left pane, click **Collection**. The **Swarm** collection appears.
4. Click **View children** to list all of the collections. In **Shared**,
Click **View children**, find the **View-only services** collection and
@ -71,7 +71,7 @@ Currently, users who aren't administrators can't access the
and click **Select Collection**.
3. Click **Roles**, and in the dropdown, select **View Only**.
4. Click **Subjects**, and under **Select subject type**, click **Organizations**.
In the dropdown, select **engineering**.
In the dropdown, select **engineering**.
5. Click **Create** to grant permissions to the organization.
![](../images/deploy-view-only-service-4.png)
@ -80,21 +80,21 @@ Everything is in place to show role-based access control in action.
## Verify the user's permissions
Users in the `engineering` organization have view-only access to the
Users in the `engineering` organization have view-only access to the
`/Shared/View-only services` collection. You can confirm this by logging in
as a non-admin user in the organization and trying to delete the service.
1. Log in as the user who you assigned to the Dev team.
1. Log in as the user who you assigned to the Dev team.
2. Navigate to the **Services** page and click **WordPress**.
3. In the details pane, confirm that the service's collection is
**/Shared/View-only services**.
![](../images/deploy-view-only-service-2.png)
4. Click the checkbox next to the **WordPress** service, click **Actions**,
and select **Remove**. You get an error message, because the user
doesn't have `Service Delete` access to the collection.
## Where to go next
- [Isolate volumes between two different teams](isolate-volumes-between-teams.md)
- [Isolate volumes between two different teams](isolate-volumes-between-teams.md)

View File

@ -78,7 +78,7 @@ system:
# Restart the Docker daemon
$ sudo /bin/systemctl restart docker.service
```
* For SUSE SLES 12:
```bash
@ -105,11 +105,11 @@ images from your local Docker installation to DTR.
![](/datacenter/ucp/2.2/guides/images/dtr-integration-1.png)
2. Pull the `hello-world` image from Docker Store, re-tag it, and push it to the
2. Pull the `hello-world` image from Docker Hub, re-tag it, and push it to the
DTR repository you created.
```none
# Pull hello-world from Docker Store
# Pull hello-world from Docker Hub
docker image pull hello-world:latest
# Re-tag it

View File

@ -9,7 +9,7 @@ installation. Here's how to do it.
## Download your license
Go to [Docker Store](https://www.docker.com/enterprise-edition) and
Go to [Docker Hub](https://www.docker.com/enterprise-edition) and
download your UCP license, or get a free trial license.
![](../../images/license-ucp-1.png){: .with-border}
@ -17,7 +17,7 @@ download your UCP license, or get a free trial license.
## License your installation
Once you've downloaded the license file, you can apply it to your UCP
installation.
installation.
In the UCP web UI, log in with administrator credentials and
navigate to the **Admin Settings** page.

View File

@ -79,7 +79,7 @@ To install UCP:
Now that UCP is installed, you need to license it.
1. Go to the
[Docker Store](https://www.docker.com/enterprise-edition)
[Docker Hub](https://www.docker.com/enterprise-edition)
and buy a Docker EE subscription, or get a free trial license.
2. In your browser, navigate to the UCP web UI, log in with your

View File

@ -443,7 +443,7 @@ to change context so that `kubectl` is pointing to `docker-for-desktop`:
> kubectl config use-context docker-for-desktop
```
You can also change it through the Docker for Windows menu:
You can also change it through the Docker for Windows menu:
![Change Kubernetes Context](images/docker-menu-context-switch.png){:width="600px"}
@ -487,7 +487,7 @@ Visit our [Logs and Troubleshooting](troubleshoot.md) guide for more details.
Log on to our [Docker for Windows forum](https://forums.docker.com/c/docker-for-windows) to get help from the community, review current user topics, or join a discussion.
Log on to [Docker for Windows issues on GitHub](https://github.com/docker/for-win/issues) to report bugs or problems and review community reported issues.
Log on to [Docker for Windows issues on GitHub](https://github.com/docker/for-win/issues) to report bugs or problems and review community reported issues.
To give feedback on the documentation or update it yourself, use the Feedback options at the bottom of each docs page.

View File

@ -2,6 +2,8 @@
description: Automated builds
keywords: automated, build, images
title: Advanced options for Autobuild and Autotest
redirect_from:
- /docker-cloud/builds/advanced/
---
The following options allow you to customize your automated build and automated test processes.

View File

@ -3,6 +3,7 @@ description: Automated builds
keywords: automated, build, images
redirect_from:
- /docker-cloud/feature-reference/automated-build/
- /docker-cloud/builds/automated-build/
title: Automated builds
---

View File

@ -3,6 +3,7 @@ description: Automated tests
keywords: Automated, testing, repository
redirect_from:
- /docker-cloud/feature-reference/automated-testing/
- /docker-cloud/builds/automated-testing/
title: Automated repository tests
---

View File

@ -2,6 +2,8 @@
description: Docker Hub Automated Builds using Bitbucket
keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation, trusted, builds, trusted builds, automated builds, bitbucket
title: Configure automated builds with Bitbucket
redirect_from:
- /docker-hub/bitbucket/
---
If you've previously linked Docker Hub to your Bitbucket account, skip to

View File

@ -1,235 +0,0 @@
---
description: Docker Hub Automated Builds
keywords: Dockerfile, Hub, builds, trusted builds, automated builds
title: Configure automated builds on Docker Hub
---
You can build your images automatically from a build context stored in a
repository. A *build context* is a Dockerfile and any files at a specific
location. For an automated build, the build context is a repository containing a
Dockerfile.
Automated Builds have several advantages:
* Images built in this way are built exactly as specified.
* The `Dockerfile` is available to anyone with access to your Docker Hub repository.
* Your repository is kept up-to-date with code changes automatically.
Automated Builds are supported for both public and private repositories on both
[GitHub](http://github.com) and [Bitbucket](https://bitbucket.org/). This
document guides you through the process of working with automated builds.
## Prerequisites
To use automated builds, you must have an [account on Docker Hub](accounts.md)
and on the hosted repository provider (GitHub or Bitbucket). If you have
previously linked your Github or Bitbucket account, you must have chosen the
Public and Private connection type.
To view your current connection settings, log in to Docker Hub and choose
**Profile > Settings > Linked Accounts & Services**.
## Limitations
- Currently Docker Hub does not support Git LFS (Large File Storage). If you have
binaries in your build context that are managed by Git LFS, only the pointer
file is present in the clone made during the automated build, which is not
what you want.
Subscribe to the [GitHub issue](https://github.com/docker/hub-feedback/issues/500)
tracking this limitation.
- Building Windows containers is not supported.
## Link to a hosted repository service
1. Log into Docker Hub.
2. Navigate to **Profile > Settings > Linked Accounts & Services**.
3. Click the service you want to link.
The system prompts you to choose between Public and Private and Limited Access. The Public and Private connection type is required if you want to use the Automated Builds.
4. Press **Select** under Public and Private connection type.
The system prompts you to enter your service credentials (Bitbucket or GitHub) to login. For example, Bitbucket's prompt looks like this:
![Bitbucket](images/bitbucket_creds.png)
After you grant access to your code repository, the system returns you to Docker Hub and the link is complete.
![Linked account](images/linked-acct.png)
## Create an automated build
Automated build repositories rely on the integration with your code repository
To build. However, you can also push already-built images to these
repositories using the `docker push` command.
1. Select **Create** > **Create Automated Build** (from the drop down, upper right) on [Docker Hub](https://hub.docker.com/).
The system prompts you with a list of User/Organizations and code repositories.
2. Select from the User/Organizations.
3. Optionally, type to filter the repository list.
4. Pick the project to build.
The system displays the **Create Automated Build** dialog.
![Create dialog](images/create-dialog1.png)
The dialog assumes some defaults which you can customize. By default, Docker
builds images for each branch in your repository. It assumes the Dockerfile
lives at the root of your source. When it builds an image, Docker tags it with
the branch name.
6. Customize the automated build by pressing the **Click here to customize** this behavior link.
![Create dialog](images/create-dialog.png)
Specify which code branches or tags to build from. You can add new
configurations by clicking the + (plus sign). The dialog accepts regular
expressions.
![Create dialog](images/regex-help.png)
9. Click **Create**.
The system displays the home page for your AUTOMATED BUILD.
![Home page](images/home-page.png)
Within GitHub, a Docker integration appears in your repositories Settings > Webhooks & services page.
![GitHub](images/docker-integration.png)
A similar page appears in Bitbucket if you use that code repository. Be
careful to leave the Docker integration in place. Removing it causes your
automated builds to stop.
### Understand the build process
The first time you create a new automated build, Docker Hub builds your image.
In a few minutes, you should see your new build on the image dashboard. The
Build Details page shows a log of your build systems:
![Pending](images/first_pending.png)
During the build process, Docker copies the contents of your `Dockerfile` to
Docker Hub. The Docker community (for public repositories) or approved team
members/orgs (for private repositories) can then view the Dockerfile on your
repository page.
The build process looks for a `README.md` in the same directory as your
`Dockerfile`. If you have a `README.md` file in your repository, it is used in
the repository as the full description. If you change the full description after
a build, it's overwritten the next time the Automated Build runs. To make
changes, modify the `README.md` in your Git repository.
You can only trigger one build at a time and no more than one every five
minutes. If you already have a build pending, or if you recently submitted a
build request, Docker ignores new requests.
### Build statuses explained
You can view the status of the builds for a specific repository by looking at
the Build Details screen. If you have builds that are queued or in progress, you
can click **Cancel** to end them.
![Build statuses](images/build-states-ex.png)
The statuses are:
* **Queued**: You're in line for your image to be built. Queue time varies depending on number of concurrent builds available to you.
* **Building**: The image is building.
* **Success**: The image has been built with no issues.
* **Error**: There was an issue with your image. Click the row to go to the Builds Details screen. The banner at the top of the page displays the last sentence of the log file, which indicates what the error was. If you need more information, scroll to the bottom of the screen to the logs section.
## Use the Build Settings page
The Build Settings page allows you to manage your existing automated build
configurations and add new ones. By default, when new code is merged into your
source repository, it triggers a build of your DockerHub image.
![Default checkbox](images/merge_builds.png)
Clear the checkbox to turn this behavior off. You can use the other settings on
the page to configure and build images.
## Add and run a new build
At the top of the Build Dialog is a list of configured builds. You can build
from a code branch or by build tag.
![Build or tag](images/build-by.png)
Docker builds everything listed whenever a push is made to the code repository.
If you specify a branch or tag, you can manually build that image by
pressing the Trigger. If you use a regular expression syntax (regex) to define
your build branch or tag, Docker does not give you the option to manually build.
To add a new build:
1. Press the + (plus sign).
2. Choose the Type.
You can build by a code branch or by an image tag.
3. Enter the Name of the branch or tag.
You can enter a specific value or use a regex to select multiple values. To
see examples of regex, press the Show More link on the right of the page.
![Regexhelp](images/regex-help.png)
4. Enter a Dockerfile location.
5. Specify a Tag Name.
6. Press **Save Changes**.
If you make a mistake or want to delete a build, press the - (minus sign) and then **Save Changes**.
## Repository links
Repository links let you link one Automated Build with another. If one Automated
Build gets updated, Docker triggers a build of the other. This makes it easy to
ensure that related images are kept in sync. You can link more than one image
repository. You only need to link one side of two related builds. Linking both
sides causes an endless build loop.
To add a link:
1. Go to the Build Settings for an automated build repository.
2. In the Repository Links section, enter an image repository name.
A remote repository name should be either an official image name such as `ubuntu` or a public repository name `namespace/repoName`.
3. Press **Add**.
![Links](images/repo_links.png)
## Remote Build triggers
To trigger Automated Builds programmatically, you can set up a remote build
trigger in another application such as GitHub or Bitbucket. When you Activate
the build trigger for an Automated Build, it supplies you with a Token and a
URL.
![Build trigger screen](images/build-trigger.png)
You can use `curl` to trigger a build:
```bash
$ curl --data build=true -X POST https://registry.hub.docker.com/u/svendowideit/testhook/trigger/be579c
82-7c0e-11e4-81c4-0242ac110020/
OK
```
To verify everything is working correctly, check the **Last 10 Trigger Logs** on
the page.

View File

@ -2,6 +2,8 @@
description: Docker Hub Automated Builds with GitHub
keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation, trusted, builds, trusted builds, automated builds, GitHub
title: Configure automated builds from GitHub
redirect_from:
- /docker-hub/github/
---
If you've previously linked Docker Hub to your GitHub account,
@ -23,7 +25,7 @@ GitHub account. This allows the registry to see your GitHub repositories.
To add, remove or view your linked account, log in to your Docker Hub account. Select **Settings > Linked Accounts & Services**.
Linking to Github grants Docker Hub access to all of your repositories. Follow the
onscreen instructions to authorize and link your GitHub account to Docker Hub.
onscreen instructions to authorize and link your GitHub account to Docker Hub.
Once it is linked, you can choose a source repository from which to create the Automatic Build.
You can review and revoke Docker Hub's access by visiting the
@ -181,5 +183,3 @@ The image below shows the **Webhooks/Add webhook** form with the above settings
If configured correctly, you'll see this in the **Webhooks** view
![github-webhook](images/github-webhook.png)

View File

@ -3,6 +3,10 @@ description: Getting Started with Builds
keywords: builds, images, Hub
title: Getting Started with Builds
notoc: true
redirect_from:
- /docker-cloud/builds/
- /docker-cloud/builds/repos/
- /docker-cloud/builds/push-images/
---
Docker Hub provides a hosted registry service where you can create
@ -15,8 +19,8 @@ image on each `git push` to the source code. You can also create automated
tests, and when the tests pass use autoredeploy to automatically update your
running services when a build passes its tests.
* [Repositories in Docker Hub](repos.md)
* [Link to a source code repository](link-source.md)
For more information, see:
* [Automated builds](automated-build.md)
* [Automated repository tests](automated-testing.md)
* [Advanced options for Autobuild and Autotest](advanced.md)

View File

@ -3,6 +3,7 @@ description: Link to your source code repository
keywords: sourcecode, github, bitbucket
redirect_from:
- /docker-cloud/tutorials/link-source/
- /docker-cloud/builds/link-source/
title: Link Docker Hub to a source code provider
---

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

View File

@ -1,9 +1,78 @@
---
description: Get Started with Docker Hub
keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, documentation, accounts, organizations, repositories, groups, teams
title: Get Started with Docker Hub
redirect_from:
- /docker-hub/overview/
title: Get Started with Docker Hub
- /apidocs/docker-cloud/
- /docker-cloud/migration/
- /docker-cloud/migration/cloud-to-swarm/
- /docker-cloud/migration/cloud-to-kube-aks/
- /docker-cloud/migration/cloud-to-kube-gke/
- /docker-cloud/migration/cloud-to-aws-ecs/
- /docker-cloud/migration/deregister-swarms/
- /docker-cloud/migration/kube-primer/
- /docker-cloud/cloud-swarm/
- /docker-cloud/cloud-swarm/using-swarm-mode/
- /docker-cloud/cloud-swarm/register-swarms/
- /docker-cloud/cloud-swarm/register-swarms/
- /docker-cloud/cloud-swarm/create-cloud-swarm-aws/
- /docker-cloud/cloud-swarm/create-cloud-swarm-azure/
- /docker-cloud/cloud-swarm/connect-to-swarm/
- /docker-cloud/cloud-swarm/link-aws-swarm/
- /docker-cloud/cloud-swarm/link-azure-swarm/
- /docker-cloud/cloud-swarm/ssh-key-setup/
- /docker-cloud/infrastructure/
- /docker-cloud/infrastructure/deployment-strategies/
- /docker-cloud/infrastructure/link-aws/
- /docker-cloud/infrastructure/link-do/
- /docker-cloud/infrastructure/link-azure/
- /docker-cloud/infrastructure/link-packet/
- /docker-cloud/infrastructure/link-softlayer/
- /docker-cloud/infrastructure/ssh-into-a-node/
- /docker-cloud/infrastructure/docker-upgrade/
- /docker-cloud/infrastructure/byoh/
- /docker-cloud/infrastructure/cloud-on-packet.net-faq/
- /docker-cloud/infrastructure/cloud-on-aws-faq/
- /docker-cloud/standard/
- /docker-cloud/getting-started/
- /docker-cloud/getting-started/intro_cloud/
- /docker-cloud/getting-started/connect-infra/
- /docker-cloud/getting-started/your_first_node/
- /docker-cloud/getting-started/your_first_service/
- /docker-cloud/getting-started/deploy-app/1_introduction/
- /docker-cloud/getting-started/deploy-app/2_set_up/
- /docker-cloud/getting-started/deploy-app/3_prepare_the_app/
- /docker-cloud/getting-started/deploy-app/4_push_to_cloud_registry/
- /docker-cloud/getting-started/deploy-app/5_deploy_the_app_as_a_service/
- /docker-cloud/getting-started/deploy-app/6_define_environment_variables/
- /docker-cloud/getting-started/deploy-app/7_scale_the_service/
- /docker-cloud/getting-started/deploy-app/8_view_logs/
- /docker-cloud/getting-started/deploy-app/9_load-balance_the_service/
- /docker-cloud/getting-started/deploy-app/10_provision_a_data_backend_for_your_service/
- /docker-cloud/getting-started/deploy-app/11_service_stacks/
- /docker-cloud/getting-started/deploy-app/12_data_management_with_volumes/
- /docker-cloud/apps/
- /docker-cloud/apps/deploy-to-cloud-btn/
- /docker-cloud/apps/auto-destroy/
- /docker-cloud/apps/autorestart/
- /docker-cloud/apps/auto-redeploy/
- /docker-cloud/apps/load-balance-hello-world/
- /docker-cloud/apps/deploy-tags/
- /docker-cloud/apps/stacks/
- /docker-cloud/apps/ports/
- /docker-cloud/apps/service-redeploy/
- /docker-cloud/apps/service-scaling/
- /docker-cloud/apps/api-roles/
- /docker-cloud/apps/service-links/
- /docker-cloud/apps/triggers/
- /docker-cloud/apps/volumes/
- /docker-cloud/apps/stack-yaml-reference/
- /docker-cloud/installing-cli/
- /docker-cloud/docker-errors-faq/
- /docker-cloud/release-notes/
- /docker-store/
---
[Docker Hub](https://hub.docker.com) is a service provided by Docker for finding and sharing container images with your team.

View File

@ -2,6 +2,8 @@
description: Guidelines for Official Images on Docker Hub
keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, official,image, documentation
title: Official Images on Docker Hub
redirect_from:
- /docker-hub/official_repos/
---
The Docker [Official Images](https://hub.docker.com/search?q=&type=image&image_filter=official) are a

View File

@ -2,6 +2,8 @@
description: Docker Hub Teams and Organizations
keywords: Docker, docker, registry, teams, organizations, plans, Dockerfile, Docker Hub, docs, documentation
title: Organizations and teams in Docker Hub
redirect_from:
- /docker-cloud/orgs/
---
Docker Hub [organizations](https://hub.docker.com/organizations/) let you create

View File

@ -2,6 +2,8 @@
description: Submit a product to be listed on Docker Hub
keywords: Docker, docker, hub, purchase images
title: Bring Your Own License (BYOL) products on Docker Hub
redirect_from:
- /docker-store/byol/
---
## What is Bring Your Own License (BYOL)?

View File

@ -2,6 +2,8 @@
description: Run certification tests against your images
keywords: Docker, docker, store, certified content, images
title: Certify Docker images
redirect_from:
- /docker-store/certify-images/
---
## Introduction

View File

@ -2,6 +2,9 @@
description: Run certification tests against your images
keywords: Docker, docker, hub, certified content, logging
title: Certify Docker logging plugins
redirect_from:
- /docker-store/certify-plugins-logging/
---
## Introduction

View File

@ -2,6 +2,8 @@
description: Docker Hub frequently asked questions
keywords: Docker, docker, store, purchase images
title: Docker Hub Customer FAQs
redirect_from:
- /docker-store/customer_faq/
---
## Customer FAQs

View File

@ -2,6 +2,8 @@
description: Submit a product for Docker Hub
keywords: Docker, docker, hub, purchase images
title: Publish content on Docker Hub
redirect_from:
- /docker-store/publish/
---
## Permitted content and support options

View File

@ -2,6 +2,9 @@
description: Docker Hub frequently asked questions
keywords: Docker, docker, hub, purchase images
title: Docker Hub Publisher FAQs
redirect_from:
- /docker-store/publisher_faq/
---
## Certification program

View File

@ -1,13 +1,15 @@
---
title: Docker Hub Publisher Image Trust Chain
keywords: trust, chain, store, security
redirect_from:
- /docker-store/trustchain/
---
## For consumers
Docker ensures that all content is securely received and verified from original
Docker can ensure that all content is securely received and verified from original
producers, and additionally audits images before adding them to the Docker
Store. Docker cryptographically signs the images upon completion of a
Hub. Docker cryptographically signs the images upon completion of a
satisfactory image check, so that you can verify and trust certified content
from the Docker Hub.

View File

@ -0,0 +1,50 @@
---
description: Integrate Docker Hub with Slack
keywords: Slack, integrate, notifications
redirect_from:
- /docker-cloud/tutorials/slack-integration/
- /docker-cloud/slack-integration/
title: Set up Docker Hub notifications in Slack
---
Docker Hub can integrate with your **Slack** team to provide notifications about builds.
## Set up a Slack integration
Before you begin, make sure that you are signed into the Slack team that you want to show notifications in.
1. Log in to the Docker account that owns the builds that you want to receive notifications about.
> **Note**: If you are setting up notifications for an organization, log in as a member of the organization's `Owners` team, then switch to the organization account to change the settings.
2. Click **Account Settings** in the left hand navigation, and scroll down to the **Notifications** section.
3. Click the plug icon next to **Slack**.
The Docker Hub page refreshes to show a Slack authorization screen.
4. On the page that appears, double check that you're signed in to the correct Slack team. (If necessary sign in to the correct one.)
5. Select the channel that should receive notifications.
6. Click **Authorize**.
Once you click **Authorize**, you should see a message in the Slack channel notifying you of the new integration.
![](images/slack-oauth-authorize.png)
Once configured, choose a notification level:
* **Off** Do not receive any notifications.
* **Only failures** Only receive notifications about failed builds.
* **Everything** Receive notifications for both failed and successful builds.
![](images/slack-notification-updates.png)
Enjoy your new Slack channel integration!
## Edit a Slack integration
* Click **Account Settings** in the lower left, scroll down to **Notifications**, and locate the **Slack** section. From here you can choose a new notification level, or remove the integration.
* From the Slack **Notifications** section you can also change the channel that the integration posts to. Click the reload icon (two arrows) next to the Slack integration to reopen the OAuth channel selector.
* Alternately, go to the <a href="https://slack.com/apps/manage" target="_blank">Slack App Management page</a> and search for "Docker Hub". Click the result to see all of the Docker Hub notification channels set for the Slack team.

View File

@ -2,6 +2,8 @@
description: Sign up for a Docker ID and log in
keywords: accounts, docker ID, billing, paid plans, support, Hub, Store, Forums, knowledge base, beta access
title: Docker ID accounts
redirect_from:
- /docker-cloud/dockerid/
---
Your free Docker ID grants you access to Docker Hub repositories, and some beta programs. All you need is an email address.

View File

@ -286,6 +286,8 @@ Redis service. Be sure to replace `username/repo:tag` with your image details.
![Visualizer with redis screenshot](images/visualizer-with-redis.png)
[On to Part 6 >>](part6.md){: class="button outline-btn"}
## Recap (optional)
Here's [a terminal recording of what was covered on this page](https://asciinema.org/a/113840):
@ -298,24 +300,3 @@ You learned that to add more services to your stack, you insert them in your
Compose file. Finally, you learned that by using a combination of placement
constraints and volumes you can create a permanent home for persisting data, so
that your app's data survives when the container is torn down and redeployed.
## Congratulations!
You've taken a full-stack, dev-to-deploy tour of the entire Docker platform.
There is much more to the Docker platform than what was covered here, but you
have a good idea of the basics of containers, images, services, swarms, stacks,
scaling, load-balancing, volumes, and placement constraints.
Want to go deeper? Here are some resources we recommend:
- [Deploy your app](/ee): Deploy your app in a production environment using Docker Enterprise
- [Samples](/samples/): Our samples include multiple examples of popular software
running in containers, and some good labs that teach best practices.
- [User Guide](/engine/userguide/): The user guide has several examples that
explain networking and storage in greater depth than was covered here.
- [Admin Guide](/engine/admin/): Covers how to manage a Dockerized production
environment.
- [Training](https://training.docker.com/): Official Docker courses that offer
in-person instruction and virtual classroom environments.
- [Blog](https://blog.docker.com): Covers what's going on with Docker lately.

View File

@ -32,7 +32,7 @@ Dockerized application.
## Choose an option
{% capture cloud %}
{% capture community %}
To set up and deploy:
@ -190,7 +190,7 @@ you choose, or even edit the Compose file itself.
Bringing your own server to Docker Enterprise and setting up Docker Datacenter
essentially involves two steps:
1. [Get Docker Enterprise for your server's OS from Docker Store](https://store.docker.com/search?offering=enterprise&type=edition){: onclick="ga('send', 'event', 'Get Started Referral', 'Enterprise', 'Get Docker EE for your OS');"}.
1. [Get Docker Enterprise for your server's OS from Docker Hub](https://hub.docker.com/search?offering=enterprise&type=edition){: onclick="ga('send', 'event', 'Get Started Referral', 'Enterprise', 'Get Docker EE for your OS');"}.
2. Follow the [instructions to install Docker Enterprise on your own host](/datacenter/install/linux/){: onclick="ga('send', 'event', 'Get Started Referral', 'Enterprise', 'BYOH setup guide');"}.
> **Note**: Running Windows containers? View our [Windows Server setup guide](/install/windows/docker-ee.md){: onclick="ga('send', 'event', 'Get Started Referral', 'Enterprise', 'Windows Server setup guide');"}.
@ -203,8 +203,8 @@ essentially involves two steps:
<li><a data-toggle="tab" href="#community">Docker Engine - Community</a></li>
</ul>
<div class="tab-content">
<div id="community" class="tab-pane fade in active" markdown="1">{{ community }}</div>
<div id="enterprise" class="tab-pane fade" markdown="1">{{ enterprise }}</div>
<div id="enterprise" class="tab-pane fade in active" markdown="1">{{ enterprise }}</div>
<div id="community" class="tab-pane fade" markdown="1">{{ community }}</div>
</div>
## Congratulations!