mirror of https://github.com/docker/docs.git
Found more outdated callouts, fixed whitespacing
This commit is contained in:
Sarah Sanders
parent
be328b9958
commit
8b81c215db
|
|
@ -819,7 +819,8 @@ supported on Windows.
|
|||
|
||||
Get `stdout` and `stderr` logs from the container ``id``
|
||||
|
||||
> **Note**:
|
||||
> [!NOTE]:
|
||||
>
|
||||
> This endpoint works only for containers with the `json-file` or `journald` logging drivers.
|
||||
|
||||
**Example request**:
|
||||
|
|
@ -1486,9 +1487,9 @@ Get a tar archive of a resource in the filesystem of container `id`.
|
|||
indicates that only the contents of the **path** directory should be
|
||||
copied. A symlink is always resolved to its target.
|
||||
|
||||
> **Note**: It is not possible to copy certain system files such as resources
|
||||
> under `/proc`, `/sys`, `/dev`, and mounts created by the user in the
|
||||
> container.
|
||||
> [!NOTE]
|
||||
>
|
||||
> It is not possible to copy certain system files such as resources under `/proc`, `/sys`, `/dev`, and mounts created by the user in the container.
|
||||
|
||||
**Example request**:
|
||||
|
||||
|
|
@ -2151,7 +2152,8 @@ Remove the image `name` from the filesystem
|
|||
|
||||
Search for an image on [Docker Hub](https://hub.docker.com).
|
||||
|
||||
> **Note**:
|
||||
> [!NOTE]
|
||||
>
|
||||
> The response keys have changed from API v1.6 to reflect the JSON
|
||||
> sent by the registry server to the docker daemon's request.
|
||||
|
||||
|
|
@ -3921,7 +3923,9 @@ an image](#create-an-image) section for more details.
|
|||
|
||||
### 3.7 Nodes
|
||||
|
||||
**Note**: Node operations require the engine to be part of a swarm.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Node operations require the engine to be part of a swarm.
|
||||
|
||||
#### List nodes
|
||||
|
||||
|
|
@ -4471,7 +4475,9 @@ JSON Parameters:
|
|||
|
||||
### 3.9 Services
|
||||
|
||||
**Note**: Service operations require to first be part of a swarm.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Service operations require to first be part of a swarm.
|
||||
|
||||
#### List services
|
||||
|
||||
|
|
@ -5021,7 +5027,9 @@ image](#create-an-image) section for more details.
|
|||
|
||||
### 3.10 Tasks
|
||||
|
||||
**Note**: Task operations require the engine to be part of a swarm.
|
||||
> [!NOTE]
|
||||
>
|
||||
> Task operations require the engine to be part of a swarm.
|
||||
|
||||
#### List tasks
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ The following diagram shows the relationship between a registry, repositories, a
|
|||
+---------------------------------------+
|
||||
```
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> You can create one private repository and unlimited public repositories using the free version of Docker Hub. For more information, visit the [Docker Hub subscription page](https://www.docker.com/pricing/).
|
||||
|
||||
|
|
@ -112,7 +112,7 @@ Don't worry about the specifics of the Dockerfile, as you'll learn about that in
|
|||
docker build -t <YOUR_DOCKER_USERNAME>/docker-quickstart .
|
||||
```
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Make sure you include the dot (.) at the end of the `docker build` command. This tells Docker where to find the Dockerfile.
|
||||
|
||||
|
|
|
|||
|
|
@ -72,9 +72,9 @@ To remove a container, you first need to stop it. Once it has stopped, you can r
|
|||
$ docker rm <the-container-id>
|
||||
```
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
>You can stop and remove a container in a single command by adding the `force` flag to the `docker rm` command. For example: `docker rm -f <the-container-id>`
|
||||
> You can stop and remove a container in a single command by adding the `force` flag to the `docker rm` command. For example: `docker rm -f <the-container-id>`
|
||||
|
||||
{{< /tab >}}
|
||||
{{< tab name="Docker Desktop" >}}
|
||||
|
|
|
|||
|
|
@ -93,14 +93,14 @@ multiple Dockerfiles that can't be easily merged into one.
|
|||
|
||||
## Deduplicate context transfer
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> As of Buildx version 0.17.0 and later, Bake automatically deduplicates
|
||||
> As of Buildx version 0.17.0 and later, Bake automatically de-duplicates
|
||||
> context transfer for targets that share the same context. In addition to
|
||||
> Buildx version 0.17.0, the builder must be running BuildKit version 0.16.0 or
|
||||
> later, and the Dockerfile syntax must be `docker/dockerfile:1.10` or later.
|
||||
>
|
||||
> If you meet these requirements, you don't need to manually deduplicate
|
||||
> If you meet these requirements, you don't need to manually de-duplicate
|
||||
> context transfer as described in this section.
|
||||
>
|
||||
> - To check your Buildx version, run `docker buildx version`.
|
||||
|
|
|
|||
|
|
@ -19,13 +19,13 @@ Computing components of an application are defined as [services](/reference/comp
|
|||
|
||||
Services communicate with each other through [networks](/reference/compose-file/networks.md). In the Compose Specification, a network is a platform capability abstraction to establish an IP route between containers within services connected together.
|
||||
|
||||
Services store and share persistent data into [volumes](/reference/compose-file/volumes.md). The Specification describes such a persistent data as a high-level filesystem mount with global options.
|
||||
Services store and share persistent data into [volumes](/reference/compose-file/volumes.md). The Specification describes such a persistent data as a high-level filesystem mount with global options.
|
||||
|
||||
Some services require configuration data that is dependent on the runtime or platform. For this, the Specification defines a dedicated [configs](/reference/compose-file/configs.md) concept. From a service container point of view, configs are comparable to volumes, in that they are files mounted into the container. But the actual definition involves distinct platform resources and services, which are abstracted by this type.
|
||||
|
||||
A [secret](/reference/compose-file/secrets.md) is a specific flavor of configuration data for sensitive data that should not be exposed without security considerations. Secrets are made available to services as files mounted into their containers, but the platform-specific resources to provide sensitive data are specific enough to deserve a distinct concept and definition within the Compose specification.
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> With volumes, configs and secrets you can have a simple declaration at the top-level and then add more platform-specific information at the service level.
|
||||
|
||||
|
|
|
|||
|
|
@ -1450,7 +1450,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
### Beta 36 Release Notes (2017-01-12 1.13.0-rc6-beta36)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -1464,7 +1466,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
### Beta 35 Release Notes (2017-01-06 1.13.0-rc5-beta35)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -1475,7 +1479,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
### Beta 34.1 Release Notes (2016-12-22 1.13.0-rc4-beta34.1)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Hotfix**
|
||||
|
||||
|
|
@ -1487,7 +1493,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
### Beta 34 Release Notes (2016-12-20 1.13.0-rc4-beta34)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**New**
|
||||
|
||||
|
|
@ -1509,7 +1517,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
### Beta 33.1 Release Notes (2016-12-16 1.13.0-rc3-beta33.1)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Hotfix**
|
||||
|
||||
|
|
@ -1517,7 +1527,9 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
### Beta 33 Release Notes (2016-12-15 1.13.0-rc3-beta33)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**New**
|
||||
|
||||
|
|
@ -1926,7 +1938,7 @@ events or unexpected unmounts.
|
|||
|
||||
### Beta 18.1 Release Notes (2016-07-07 1.12.0-rc3-beta18.1)
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>
|
||||
> Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
|
||||
|
||||
|
|
|
|||
|
|
@ -1627,7 +1627,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
|
||||
### Beta 36 Release Notes (2017-01-12 1.13.0-rc6-beta36)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -1641,7 +1643,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
|
||||
### Beta 35 Release Notes (2017-01-06 1.13.0-rc5-beta35)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Upgrades**
|
||||
|
||||
|
|
@ -1670,7 +1674,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
|
||||
### Beta 33 Release Notes (2016-12-15 1.13.0-rc3-beta33)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**New**
|
||||
|
||||
|
|
@ -1687,7 +1693,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
|
||||
### Beta 32.1 Release Notes (2016-12-09 1.13.0-rc3-beta32.1)
|
||||
|
||||
>**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**Hotfixes**
|
||||
|
||||
|
|
@ -1717,9 +1725,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
|
|||
|
||||
### Beta 32 Release Notes (2016-12-07 1.13.0-rc3-beta32)
|
||||
|
||||
>**Important Note**:
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
|
||||
|
||||
**New**
|
||||
|
||||
|
|
|
|||
|
|
@ -10,8 +10,7 @@ aliases:
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
To automate building and testing of your images, you link to your hosted source
|
||||
code service to Docker Hub so that it can access your source code
|
||||
|
|
@ -38,7 +37,7 @@ If you are linking a source code provider to create autobuilds for a team, follo
|
|||
|
||||
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you are the owner of any GitHub organizations, you might see
|
||||
options to grant Docker Hub access to them from this screen. You can also
|
||||
|
|
@ -140,6 +139,7 @@ unlink it both from Docker Hub, and revoke authorization in your Bitbucket accou
|
|||
3. From the **Linked accounts** tab, select the **Plug** icon next to the source provider you want to remove.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> After unlinking the account on Docker Hub, you must also revoke the authorization on the Bitbucket end.
|
||||
|
||||
To revoke authorization in your Bitbucket account:
|
||||
|
|
|
|||
|
|
@ -6,8 +6,7 @@ keywords: autobuilds, automated, docker hub, registry
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
## Cancel or retry a build
|
||||
|
||||
|
|
@ -32,11 +31,9 @@ From either location, you can select a build job to view its build report. The
|
|||
build report shows information about the build job. This includes the source
|
||||
repository and branch, or tag, the build logs, the build duration, creation time and location, and the user account the build occurred in.
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> You can now view the progress of your builds every 30 seconds when you
|
||||
> refresh the **Builds** page. With the in-progress build logs, you can debug your
|
||||
> builds before they're finished.
|
||||
> You can now view the progress of your builds every 30 seconds when you refresh the **Builds** page. With the in-progress build logs, you can debug your builds before they're finished.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -213,7 +213,7 @@ docker-ratelimit-source
|
|||
|
||||
These headers are returned on both GET and HEAD requests.
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Using GET emulates a real pull and counts towards the limit. Using HEAD won't.
|
||||
> To check your limits, you need `curl`, `grep`, and `jq` installed.
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ Docker image locally.
|
|||
efa9baa size: 526
|
||||
```
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> You must be signed in to Docker Hub through Docker Desktop or the command line, and you must also name your images correctly, as per the above steps.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,10 +20,9 @@ The ZFS on Linux (ZoL) port is healthy and maturing. However, at this point in
|
|||
time it is not recommended to use the `zfs` Docker storage driver for production
|
||||
use unless you have substantial experience with ZFS on Linux.
|
||||
|
||||
> ***Note***: There is also a FUSE implementation of ZFS on the Linux platform.
|
||||
> This is not recommended. The native ZFS driver (ZoL) is more tested, more
|
||||
> performant, and is more widely used. The remainder of this document refers
|
||||
> to the native ZoL port.
|
||||
> [!NOTE]
|
||||
>
|
||||
> There is also a FUSE implementation of ZFS on the Linux platform. This is not recommended. The native ZFS driver (ZoL) is more tested, has better performance, and is more widely used. The remainder of this document refers to the native ZoL port.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
@ -38,8 +37,7 @@ use unless you have substantial experience with ZFS on Linux.
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> There is no need to use `MountFlags=slave` because `dockerd` and `containerd`
|
||||
> are in different mount namespaces.
|
||||
> There is no need to use `MountFlags=slave` because `dockerd` and `containerd` are in different mount namespaces.
|
||||
|
||||
## Configure Docker with the `zfs` storage driver
|
||||
|
||||
|
|
|
|||
|
|
@ -39,11 +39,9 @@ Amazon EC2 instances, or hosted in some other way. Check out
|
|||
One of these machines is a manager (called `manager1`) and two of them are
|
||||
workers (`worker1` and `worker2`).
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> You can follow many of the tutorial steps to test single-node swarm
|
||||
> as well, in which case you need only one host. Multi-node commands do not
|
||||
> work, but you can initialize a swarm, create services, and scale them.
|
||||
> You can follow many of the tutorial steps to test single-node swarm as well, in which case you need only one host. Multi-node commands do not work, but you can initialize a swarm, create services, and scale them.
|
||||
|
||||
#### Install Docker Engine on Linux machines
|
||||
|
||||
|
|
|
|||
|
|
@ -19,9 +19,9 @@ Docker Extensions is switched on by default. To change your settings:
|
|||
3. Next to **Enable Docker Extensions**, select or clear the checkbox to set your desired state.
|
||||
4. In the bottom-right corner, select **Apply & Restart**.
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you are an [organization owner](/manuals/admin/organization/manage-a-team.md#organization-owner), you can turn off extensions for your users. Open the `settings-store.json` file, and set `"extensionsEnabled"` to `false`.
|
||||
> If you are an [organization owner](/manuals/admin/organization/manage-a-team.md#organization-owner), you can turn off extensions for your users. Open the `settings-store.json` file, and set `"extensionsEnabled"` to `false`.
|
||||
> The `settings-store.json` file (or `settings.json` for Docker Desktop versions 4.34 and earlier) is located at:
|
||||
> - `~/Library/Group Containers/group.com.docker/settings-store.json` on Mac
|
||||
> - `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings-store.json` on Windows
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Desktop was configured to use Windows Subsystem for Linux (aka WSL).
|
|||
Starting with Docker Desktop 4.20, ECI is supported when Docker Desktop is
|
||||
configured to use either Hyper-V or WSL 2.
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Docker Desktop requires WSL 2 version 1.1.3.0 or later. To get the current
|
||||
> version of WSL on your host, type `wsl --version`. If the command fails or if
|
||||
|
|
|
|||
|
|
@ -9,9 +9,9 @@ aliases:
|
|||
weight: 10
|
||||
---
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
>Settings Management is available to Docker Business customers only.
|
||||
> Settings Management is available to Docker Business customers only.
|
||||
|
||||
Settings Management is a feature that helps admins to control certain Docker Desktop settings on client machines within their organization.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,13 +3,13 @@ description: How to configure Settings Management for Docker Desktop
|
|||
keywords: admin, controls, rootless, enhanced container isolation
|
||||
title: Configure Settings Management
|
||||
linkTitle: Configure
|
||||
aliases:
|
||||
aliases:
|
||||
- /desktop/hardened-desktop/settings-management/configure/
|
||||
---
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
>Settings Management is available to Docker Business customers only.
|
||||
> Settings Management is available to Docker Business customers only.
|
||||
|
||||
This page contains information for admins on how to configure Settings Management to specify and lock configuration parameters to create a standardized Docker Desktop environment across the organization.
|
||||
|
||||
|
|
@ -48,9 +48,9 @@ To set it up manually:
|
|||
|
||||
### Step two: Configure the settings you want to lock in
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
>Some of the configuration parameters only apply to Windows. This is highlighted in the table below.
|
||||
> Some of the configuration parameters only apply to Windows. This is highlighted in the table below.
|
||||
|
||||
The `admin-settings.json` file requires a nested list of configuration parameters, each of which must contain the `locked` parameter. You can add or remove configuration parameters as per your requirements.
|
||||
|
||||
|
|
@ -227,15 +227,15 @@ The following `admin-settings.json` code and table provides an example of the re
|
|||
|
||||
### Step three: Re-launch Docker Desktop
|
||||
|
||||
>**Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
>Administrators should test the changes made through the `admin-settings.json` file locally to see if the settings work as expected.
|
||||
> Administrators should test the changes made through the `admin-settings.json` file locally to see if the settings work as expected.
|
||||
|
||||
For settings to take effect:
|
||||
- On a new install, developers need to launch Docker Desktop and authenticate to their organization.
|
||||
- On an existing install, developers need to quit Docker Desktop through the Docker menu, and then relaunch Docker Desktop. If they are already signed in, they don't need to sign in again for the changes to take effect.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Selecting **Restart** from the Docker menu isn't enough as it only restarts some components of Docker Desktop.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ To audit your domains:
|
|||
|
||||
You can invite all the uncaptured users to your organization using the exported CSV file. For more details, see [Invite members](/admin/organization/members/). Optionally, enforce single sign-on or enable SCIM to add users to your organization automatically. For more details, see {{ $sso_link }} or {{ $scim_link }}.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Domain audit may identify accounts of users who are no longer a part of your organization. If you don't want to add a user to your organization and you don't want the user to appear in future domain audits, you must deactivate the account or update the associated email address.
|
||||
>
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@
|
|||
- **Docker Verified Publisher Images**: Images published by Docker partners that are part of the Verified Publisher program and are qualified to be included in the developer secure supply chain.
|
||||
- **Community images**: These images are disabled by default when Image Access Management is enabled because various users contribute them and they may pose security risks. This category includes Docker-Sponsored Open Source images.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Image Access Management is turned off by default. However, owners in your organization have access to all images regardless of the settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ To view the activity logs:
|
|||
1. Sign in to {{ $product_link }}.
|
||||
2. {{ $audit_navigation }}
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Docker retains the activity data for a period of three months.
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ To view the activity logs:
|
|||
|
||||
By default, all activities that occur are displayed on the **Activity** tab. Use the calendar option to select a date range and customize your results. After you have selected a date range, the activity logs of all the activities that occurred during that period are displayed.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> Activities created by the Docker Support team as part of resolving customer issues appear in the activity logs as **dockersupport**.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,6 +17,6 @@
|
|||
7. Select **Next** to confirm or change the default organization and team provisioning selections.
|
||||
8. Review the **Connection Summary** and select **Update connection**.
|
||||
|
||||
> [!Note]
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you want to re-add the domain, a new TXT record value is assigned. You must then complete the verification steps with the new TXT record value.
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ of members to your organization via CSV file, see the next section.
|
|||
5. Follow the on-screen instructions to invite members.
|
||||
Invite a maximum of 1000 members and separate multiple entries by comma, semicolon, or space.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> When you invite members, you assign them a role.
|
||||
> See [Roles and permissions](/security/for-admins/roles-and-permissions/)
|
||||
|
|
@ -98,7 +98,7 @@ To invite multiple members to an organization via a CSV file containing email ad
|
|||
7. Select **Browse files** and then select your CSV file, or drag and drop the CSV file into the **Select a CSV file to
|
||||
upload** box. You can only select one CSV file at a time.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> If the amount of email addresses in your CSV file exceeds the number of available seats in your organization, you
|
||||
> cannot continue to invite members. To invite members, you can purchase more seats, or remove some email addresses from
|
||||
|
|
@ -120,7 +120,7 @@ To invite multiple members to an organization via a CSV file containing email ad
|
|||
|
||||
9. Follow the on-screen instructions to invite members.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> When you invite members, you assign them a role.
|
||||
> See [Roles and permissions](/security/for-admins/roles-and-permissions/)
|
||||
|
|
@ -153,7 +153,7 @@ Organization owners can manage [roles](/security/for-admins/roles-and-permission
|
|||
within an organization. If an organization is part of a company,
|
||||
the company owner can also manage that organization's roles. If you have SSO enabled, you can use {{ $role_mapping_link }}.
|
||||
|
||||
> **Note**
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you're the only owner of an organization,
|
||||
> you need to assign a new owner before you can edit your role.
|
||||
|
|
|
|||
Loading…
Reference in New Issue