mirror of
https://github.com/docker/docs.git
synced 2026-03-27 06:18:55 +07:00
Merge pull request #844 from docker/beta-cleanup
Removed Beta disclaimer tags
This commit is contained in:
@@ -310,7 +310,6 @@ repository, doing it afterwards actually worsens the impact on the Git repo (but
|
||||
still optimizes the bandwidth during browsing).
|
||||
|
||||
## Beta content disclaimer
|
||||
|
||||
```bash
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Enable auto-deletion of image events within a repository for mainte
|
||||
keywords: registry, events, log, activity stream
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
## Overview
|
||||
|
||||
Docker Trusted Registry has a global setting for repository event auto-deletion. This allows event records to be removed as part of [garbage collection](../admin/configure/garbage-collection.md). DTR administrators can enable auto-deletion of repository events in DTR 2.6 based on specified conditions which are covered below.
|
||||
|
||||
@@ -5,10 +5,6 @@ description: Save disk space by configuring the garbage collection settings in
|
||||
keywords: registry, online garbage collection, gc, space, disk space
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
You can configure the Docker Trusted Registry (DTR) to automatically delete unused image
|
||||
layers, thus saving you disk space. This process is also known as garbage collection.
|
||||
|
||||
|
||||
@@ -6,10 +6,6 @@ redirect_from: /ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-batch-jobs/
|
||||
---
|
||||
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
## Overview
|
||||
|
||||
This covers troubleshooting batch jobs via the API and was introduced in DTR 2.2. Starting in DTR 2.6, admins have the ability to [audit jobs](audit-jobs-via-ui.md) using the web interface.
|
||||
|
||||
@@ -4,11 +4,6 @@ description: View a list of jobs happening within DTR and review the detailed lo
|
||||
keywords: dtr, troubleshoot, audit, job logs, jobs, ui
|
||||
---
|
||||
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
As of DTR 2.2, admins were able to [view and audit jobs within DTR](audit-jobs-via-api) using the API. DTR 2.6 enhances those capabilities by adding a **Job Logs** tab under **System** settings on the user interface. The tab displays a sortable and paginated list of jobs along with links to associated job logs.
|
||||
|
||||
## Prerequisite
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Enable auto-deletion of old or unnecessary job logs for maintenance
|
||||
keywords: dtr, jobs, log, job logs, system
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
## Overview
|
||||
|
||||
Docker Trusted Registry has a global setting for auto-deletion of job logs which allows them to be removed as part of [garbage collection](../configure/garbage-collection.md). DTR admins can enable auto-deletion of repository events in DTR 2.6 based on specified conditions which are covered below.
|
||||
|
||||
@@ -4,10 +4,6 @@ description: View your repository permissions.
|
||||
keywords: dtr, repository, permissions
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
The **Repository Info** tab includes the following details:
|
||||
* README (which you can [edit if you have admin rights to the repository](../../admin/manage-users/permission-levels/#team-permission-levels))
|
||||
* Docker Pull Command
|
||||
|
||||
@@ -4,10 +4,6 @@ description: View and audit your repository events.
|
||||
keywords: dtr, events, log, activity stream
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
## Overview
|
||||
|
||||
Starting in DTR 2.6, each repository page includes an **Activity** tab which displays a sortable and paginated list of the most recent events within the repository. This offers better visibility along with the ability to audit events. Event types listed will vary according to your [repository permission level](../../admin/manage-users/permission-levels/). Additionally, DTR admins can [enable auto-deletion of repository events](../../admin/configure/auto-delete-repo-events/) as part of maintenance and cleanup.
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Skip the management headache of deciding which tags to delete or pr
|
||||
keywords: registry, tag pruning, tag limit, repo management
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
## Overview
|
||||
|
||||
Tag pruning is the process of cleaning up unnecessary or unwanted repository tags. As of v2.6, you can configure the Docker Trusted Registry (DTR) to automatically perform tag pruning on repositories that you manage by:
|
||||
|
||||
@@ -6,10 +6,6 @@ redirect_from:
|
||||
- /engine/admin/prometheus/
|
||||
---
|
||||
|
||||
> Beta disclaimer
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
[Prometheus](https://prometheus.io/) is an open-source systems monitoring and
|
||||
alerting toolkit. You can configure Docker as a Prometheus target. This topic
|
||||
shows you how to configure Docker, set up Prometheus to run as a Docker
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Learn how to create audit logs of all activity in UCP
|
||||
keywords: logs, ucp, swarm, kubernetes, audits
|
||||
---
|
||||
|
||||
> Beta disclaimer
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
Audit logs are focused on external user/agent actions and security rather than understanding state or events of the system itself. They are a chronological record of security-relevant activities by individual users, administrators or software components that have affected the system.
|
||||
|
||||
Audit Logs capture all HTTP actions (GET, PUT, POST, PATCH, DELETE) to all UCP API, Swarm API and Kubernetes API endpoints that are invoked (except for the ignored list) and sent to Docker Engine via stdout. Creating audit logs is CLI driven and is an UCP component that integrates with Swarm, K8s, and UCP APIs.
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Learn how to configure user authentication with SAML 2.0
|
||||
keywords: SAML, ucp, authentication, SSO, Okta, ADFS
|
||||
---
|
||||
|
||||
> Beta disclaimer
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
SAML is commonly supported by enterprise authentication systems. SAML-based single sign-on (SSO) gives you access to UCP through a SAML 2.0-compliant identity provider.
|
||||
|
||||
SAML-based single sign-on (SSO) gives you access to UCP through a SAML 2.0-compliant identity provider. UCP supports SAML for authentication as a service provider integrated with your identity provider.
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Learn how to deploy an application package in UCP
|
||||
keywords: ucp, swarm, kubernetes, application, app package
|
||||
---
|
||||
|
||||
> Beta disclaimer
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
## Application packages
|
||||
|
||||
Docker Enterprise Edition 2.1 introduces application packages in Docker. With application packages, you can add metadata and settings to an existing Compose file. This gives operators more context about applications they deploy and manage.
|
||||
|
||||
@@ -4,10 +4,6 @@ description: Learn how to install a Container Networking Interface plugin on Doc
|
||||
keywords: ucp, cli, administration, kubectl, Kubernetes, cni, Container Networking Interface, flannel, weave, ipip, calico
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
For Docker Universal Control Plane, [Project Calico](https://docs.projectcalico.org/v3.0/introduction/)
|
||||
provides the secure networking functionality for the container communication with Kubernetes.
|
||||
|
||||
|
||||
@@ -4,10 +4,6 @@ keywords: Engine, CE, EE, node, activation, enterprise
|
||||
title: CE-EE Node Activate
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
The Docker Engine `18.09` release introduces a new feature called **CE-EE Node Activate**, which allows a user to perform an in-place seamless activation of the Enterprise engine feature set on an existing Community Edition (CE) node through the Docker command line.
|
||||
|
||||
CE-EE Node Activate will apply a license, and switch the Docker engine to the Enterprise engine binary.
|
||||
@@ -89,7 +85,7 @@ Login Succeeded
|
||||
```
|
||||
$ sudo docker engine activate --license ee-engine-license-1000-nodes.lic
|
||||
License: Quantity: 400 Nodes Expiration date: 2019-05-12 License is currently active
|
||||
18.09.0-beta: resolved
|
||||
18.09.0: resolved
|
||||
e3cba72cdf2e: done [==================================================>] 434B/434B
|
||||
3642e2b52398: done [==================================================>] 1.161kB/1.161kB
|
||||
eb6fe2abc4ad: done [==================================================>] 4.544MB/4.544MB
|
||||
|
||||
@@ -4,10 +4,6 @@ keywords: guide, swarm mode, node
|
||||
title: Join nodes to a swarm
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
When you first create a swarm, you place a single Docker Engine into
|
||||
swarm mode. To take full advantage of swarm mode you can add nodes to the swarm:
|
||||
|
||||
|
||||
@@ -9,10 +9,6 @@ redirect_from:
|
||||
title: Get Docker EE for Red Hat Enterprise Linux
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
{% assign linux-dist = "rhel" %}
|
||||
{% assign linux-dist-cap = "RHEL" %}
|
||||
{% assign linux-dist-url-slug = "rhel" %}
|
||||
|
||||
@@ -7,10 +7,6 @@ redirect_from:
|
||||
- /engine/installation/windows/docker-ee/
|
||||
---
|
||||
|
||||
> BETA DISCLAIMER
|
||||
>
|
||||
> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
|
||||
|
||||
{% capture filename %}{{ page.win_latest_build }}.zip{% endcapture %} {% capture download_url %}https://download.docker.com/components/engine/windows-server/{{ site.docker_ee_version }}/{{ filename }}{% endcapture %}
|
||||
|
||||
Docker Enterprise Edition for Windows Server (*Docker EE*) enables native Docker containers on Windows Server. Windows Server 2016 and later versions are supported. The Docker EE installation package includes everything you need to run Docker on Windows Server. This topic describes pre-install considerations, and how to download and install Docker EE.
|
||||
|
||||
Reference in New Issue
Block a user