From 15e9e1e694ae8fd56c9e4bdd523909f72993876f Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Tue, 22 Aug 2023 09:42:25 +0200 Subject: [PATCH] hugo: run migration script Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- content/_index.md | 75 +- content/admin/_index.md | 28 +- content/admin/company/_index.md | 56 +- content/admin/company/organizations.md | 13 +- content/admin/company/owners.md | 7 +- content/admin/company/settings/domains.md | 2 +- .../admin/company/settings/group-mapping.md | 4 +- content/admin/company/settings/scim.md | 2 +- .../company/settings/sso-configuration.md | 2 +- .../admin/company/settings/sso-management.md | 7 +- content/admin/company/settings/sso.md | 4 +- content/admin/company/users.md | 4 +- content/admin/organization/_index.md | 66 +- content/admin/organization/activity-logs.md | 4 +- .../admin/organization/general-settings.md | 6 +- content/admin/organization/image-access.md | 4 +- content/admin/organization/members.md | 6 +- content/admin/organization/onboard.md | 4 +- content/admin/organization/registry-access.md | 4 +- .../organization/security-settings/domains.md | 4 +- .../security-settings/group-mapping.md | 4 +- .../organization/security-settings/scim.md | 2 +- .../security-settings/sso-configuration.md | 2 +- .../organization/security-settings/sso-faq.md | 4 +- .../security-settings/sso-management.md | 2 +- .../organization/security-settings/sso.md | 4 +- content/billing/_index.md | 2 +- content/billing/cycle.md | 2 +- content/billing/details.md | 2 +- content/billing/faqs.md | 4 +- content/billing/history.md | 2 +- content/billing/payment-method.md | 2 +- content/billing/scout-billing.md | 8 +- content/build/_index.md | 83 +- content/build/architecture.md | 8 +- content/build/attestations/_index.md | 13 +- content/build/attestations/sbom.md | 21 +- content/build/attestations/slsa-provenance.md | 10 +- content/build/bake/_index.md | 10 +- content/build/bake/build-contexts.md | 6 +- content/build/bake/compose-file.md | 8 +- content/build/bake/configuring-build.md | 8 +- content/build/bake/hcl-funcs.md | 10 +- content/build/bake/remote-definition.md | 4 +- content/build/builders/_index.md | 8 +- content/build/builders/manage.md | 6 +- content/build/building/base-images.md | 12 +- content/build/building/context.md | 4 +- content/build/building/env-vars.md | 12 +- content/build/building/multi-platform.md | 10 +- content/build/building/multi-stage.md | 10 +- content/build/building/opentelemetry.md | 6 +- content/build/building/packaging.md | 6 +- content/build/buildkit/_index.md | 12 +- content/build/buildkit/configure.md | 12 +- content/build/cache/_index.md | 27 +- content/build/cache/backends/_index.md | 16 +- content/build/cache/backends/azblob.md | 12 +- content/build/cache/backends/gha.md | 20 +- content/build/cache/backends/inline.md | 8 +- content/build/cache/backends/local.md | 12 +- content/build/cache/backends/registry.md | 8 +- content/build/cache/backends/s3.md | 12 +- content/build/cache/garbage-collection.md | 6 +- content/build/ci/_index.md | 18 +- content/build/ci/github-actions/_index.md | 30 +- content/build/ci/github-actions/cache.md | 33 +- .../ci/github-actions/configure-builder.md | 27 +- .../github-actions/copy-image-registries.md | 5 +- .../build/ci/github-actions/export-docker.md | 5 +- .../build/ci/github-actions/local-registry.md | 7 +- .../ci/github-actions/manage-tags-labels.md | 9 +- .../build/ci/github-actions/multi-platform.md | 13 +- .../build/ci/github-actions/named-contexts.md | 12 +- .../github-actions/push-multi-registries.md | 7 +- content/build/ci/github-actions/secrets.md | 14 +- .../ci/github-actions/share-image-jobs.md | 13 +- .../ci/github-actions/test-before-push.md | 6 +- .../github-actions/update-dockerhub-desc.md | 7 +- content/build/dockerfile/frontend.md | 18 +- content/build/dockerfile/release-notes.md | 52 +- content/build/drivers/_index.md | 12 +- content/build/drivers/docker-container.md | 18 +- content/build/drivers/docker.md | 10 +- content/build/drivers/kubernetes.md | 23 +- content/build/drivers/remote.md | 22 +- content/build/exporters/_index.md | 23 +- content/build/exporters/image-registry.md | 15 +- content/build/exporters/local-tar.md | 13 +- content/build/exporters/oci-docker.md | 17 +- content/build/guide/_index.md | 2 +- content/build/guide/build-args.md | 19 +- content/build/guide/export.md | 9 +- content/build/guide/intro.md | 8 +- content/build/guide/layers.md | 10 +- content/build/guide/mounts.md | 15 +- content/build/guide/multi-platform.md | 16 +- content/build/guide/multi-stage.md | 10 +- content/build/guide/next-steps.md | 4 +- content/build/guide/test.md | 6 +- content/build/hydrobuild.md | 4 +- content/build/release-notes.md | 198 ++--- content/cloud/aci-integration.md | 20 +- content/cloud/ecs-integration.md | 36 +- content/compose/_index.md | 76 +- content/compose/compose-file/_index.md | 90 +-- .../compose/compose-file/compose-file-v2.md | 55 +- .../compose/compose-file/compose-file-v3.md | 131 ++-- .../compose-file/compose-versioning.md | 16 +- .../compose/environment-variables/_index.md | 6 +- .../compose/environment-variables/env-file.md | 4 +- .../envvars-precedence.md | 9 +- .../compose/environment-variables/envvars.md | 6 +- .../set-environment-variables.md | 12 +- content/compose/faq.md | 23 +- content/compose/features-uses.md | 2 +- content/compose/file-watch.md | 8 +- content/compose/gettingstarted.md | 14 +- content/compose/gpu-support.md | 10 +- content/compose/history.md | 10 +- content/compose/install/_index.md | 18 +- content/compose/install/linux.md | 21 +- content/compose/install/standalone.md | 21 +- content/compose/install/uninstall.md | 7 +- content/compose/migrate.md | 29 +- .../compose/multiple-compose-files/_index.md | 8 +- .../compose/multiple-compose-files/extends.md | 11 +- .../compose/multiple-compose-files/include.md | 2 +- .../compose/multiple-compose-files/merge.md | 4 +- content/compose/networking.md | 7 +- content/compose/production.md | 5 +- content/compose/profiles.md | 7 +- content/compose/reference/_index.md | 13 +- content/compose/release-notes.md | 706 ++++++++---------- content/compose/samples-for-compose.md | 2 +- content/compose/startup-order.md | 6 +- content/compose/use-secrets.md | 2 +- content/config/containers/live-restore.md | 4 +- content/config/containers/logging/_index.md | 4 +- content/config/containers/logging/awslogs.md | 16 +- .../config/containers/logging/configure.md | 16 +- .../config/containers/logging/dual-logging.md | 8 +- content/config/containers/logging/etwlogs.md | 4 +- content/config/containers/logging/fluentd.md | 8 +- content/config/containers/logging/gcplogs.md | 10 +- content/config/containers/logging/gelf.md | 6 +- content/config/containers/logging/journald.md | 6 +- .../config/containers/logging/json-file.md | 7 +- content/config/containers/logging/local.md | 6 +- content/config/containers/logging/log_tags.md | 15 +- .../config/containers/logging/logentries.md | 4 +- content/config/containers/logging/plugins.md | 4 +- content/config/containers/logging/splunk.md | 12 +- content/config/containers/logging/syslog.md | 6 +- .../containers/multi-service_container.md | 6 +- .../config/containers/resource_constraints.md | 14 +- content/config/containers/runmetrics.md | 6 +- .../start-containers-automatically.md | 8 +- content/config/daemon/_index.md | 44 +- content/config/daemon/ipv6.md | 4 +- content/config/daemon/logs.md | 2 +- content/config/daemon/prometheus.md | 8 +- content/config/daemon/remote-access.md | 12 +- content/config/daemon/start.md | 2 +- content/config/daemon/systemd.md | 12 +- content/config/daemon/troubleshoot.md | 4 +- content/config/formatting.md | 49 +- content/config/labels-custom-metadata.md | 4 +- content/config/pruning.md | 8 +- content/contribute/checklist.md | 3 +- content/contribute/components/accordions.md | 2 +- content/contribute/components/badges.md | 4 +- content/contribute/components/buttons.md | 2 +- content/contribute/components/call-outs.md | 2 +- content/contribute/components/cards.md | 6 +- content/contribute/components/code-blocks.md | 2 +- content/contribute/components/images.md | 2 +- content/contribute/components/links.md | 2 +- content/contribute/components/lists.md | 2 +- content/contribute/components/tables.md | 2 +- content/contribute/components/tabs.md | 2 +- content/contribute/components/tooltips.md | 3 +- content/contribute/components/videos.md | 2 +- content/contribute/contribute-guide.md | 7 +- content/contribute/file-conventions.md | 2 +- content/contribute/overview.md | 50 +- content/contribute/style/grammar.md | 5 +- content/contribute/style/recommended-words.md | 2 +- content/contribute/style/terminology.md | 3 +- content/contribute/style/voice-tone.md | 4 +- content/contribute/ui.md | 2 +- content/desktop/_index.md | 73 +- content/desktop/allow-list.md | 2 +- content/desktop/backup-and-restore.md | 7 +- content/desktop/containerd/_index.md | 16 +- content/desktop/dev-environments/_index.md | 11 +- .../dev-environments/create-dev-env.md | 21 +- content/desktop/dev-environments/dev-cli.md | 5 +- content/desktop/dev-environments/set-up.md | 3 +- content/desktop/dev-environments/share.md | 5 +- content/desktop/enterprise/_index.md | 6 +- content/desktop/extensions-sdk/_index.md | 8 +- .../extensions-sdk/architecture/_index.md | 6 +- .../extensions-sdk/architecture/metadata.md | 2 +- .../extensions-sdk/architecture/security.md | 5 +- .../build/backend-extension-tutorial.md | 70 +- .../build/frontend-extension-tutorial.md | 47 +- .../build/minimal-frontend-extension.md | 10 +- .../desktop/extensions-sdk/design/_index.md | 12 +- .../design/design-guidelines.md | 12 +- .../design/design-principles.md | 2 +- .../design/mui-best-practices.md | 10 +- .../desktop/extensions-sdk/dev/api/backend.md | 2 +- .../dev/api/dashboard-routes-navigation.md | 2 +- .../extensions-sdk/dev/api/dashboard.md | 2 +- .../desktop/extensions-sdk/dev/api/docker.md | 8 +- .../extensions-sdk/dev/api/overview.md | 2 +- .../dev/api/reference/README.md | 2 +- .../dev/api/reference/interfaces/BackendV0.md | 2 +- .../dev/api/reference/interfaces/DesktopUI.md | 2 +- .../dev/api/reference/interfaces/Dialog.md | 2 +- .../dev/api/reference/interfaces/Docker.md | 2 +- .../api/reference/interfaces/DockerCommand.md | 2 +- .../interfaces/DockerDesktopClient.md | 2 +- .../dev/api/reference/interfaces/Exec.md | 2 +- .../api/reference/interfaces/ExecOptions.md | 2 +- .../api/reference/interfaces/ExecProcess.md | 2 +- .../api/reference/interfaces/ExecResult.md | 2 +- .../api/reference/interfaces/ExecResultV0.md | 2 +- .../reference/interfaces/ExecStreamOptions.md | 2 +- .../dev/api/reference/interfaces/Extension.md | 2 +- .../api/reference/interfaces/ExtensionCli.md | 2 +- .../api/reference/interfaces/ExtensionHost.md | 2 +- .../api/reference/interfaces/ExtensionVM.md | 2 +- .../dev/api/reference/interfaces/Host.md | 2 +- .../api/reference/interfaces/HttpService.md | 2 +- .../reference/interfaces/NavigationIntents.md | 2 +- .../reference/interfaces/OpenDialogResult.md | 2 +- .../api/reference/interfaces/RawExecResult.md | 2 +- .../api/reference/interfaces/RequestConfig.md | 2 +- .../reference/interfaces/RequestConfigV0.md | 2 +- .../api/reference/interfaces/ServiceError.md | 2 +- .../api/reference/interfaces/SpawnOptions.md | 2 +- .../dev/api/reference/interfaces/Toast.md | 2 +- .../dev/continuous-integration.md | 6 +- .../desktop/extensions-sdk/dev/test-debug.md | 8 +- content/desktop/extensions-sdk/dev/usage.md | 4 +- .../extensions-sdk/extensions/DISTRIBUTION.md | 6 +- .../extensions-sdk/extensions/_index.md | 5 +- .../extensions-sdk/extensions/labels.md | 8 +- .../extensions-sdk/extensions/multi-arch.md | 4 +- .../extensions-sdk/extensions/publish.md | 12 +- .../extensions-sdk/extensions/share.md | 2 +- .../extensions-sdk/extensions/validate.md | 5 +- .../guides/invoke-host-binaries.md | 17 +- .../extensions-sdk/guides/kubernetes.md | 12 +- .../extensions-sdk/guides/oauth2-flow.md | 10 +- .../guides/use-docker-socket-from-backend.md | 2 +- content/desktop/extensions-sdk/process.md | 10 +- content/desktop/extensions-sdk/quickstart.md | 12 +- content/desktop/extensions/_index.md | 6 +- content/desktop/extensions/marketplace.md | 2 +- content/desktop/extensions/non-marketplace.md | 6 +- .../desktop/extensions/settings-feedback.md | 2 +- content/desktop/faqs/general.md | 20 +- content/desktop/faqs/linuxfaqs.md | 12 +- content/desktop/faqs/macfaqs.md | 16 +- content/desktop/faqs/releases.md | 3 +- content/desktop/faqs/windowsfaqs.md | 24 +- content/desktop/feedback.md | 21 +- content/desktop/get-started.md | 12 +- content/desktop/hardened-desktop/_index.md | 7 +- .../enhanced-container-isolation/_index.md | 13 +- .../enhanced-container-isolation/faq.md | 4 +- .../features-benefits.md | 7 +- .../how-eci-works.md | 4 +- .../limitations.md | 2 +- .../image-access-management.md | 2 +- .../registry-access-management.md | 7 +- .../settings-management/_index.md | 6 +- .../settings-management/configure.md | 4 +- content/desktop/install/archlinux.md | 16 +- content/desktop/install/debian.md | 15 +- content/desktop/install/fedora.md | 15 +- content/desktop/install/linux-install.md | 32 +- content/desktop/install/mac-install.md | 25 +- content/desktop/install/ubuntu.md | 18 +- content/desktop/install/windows-install.md | 33 +- content/desktop/kubernetes.md | 10 +- .../desktop/mac/permission-requirements.md | 9 +- content/desktop/networking.md | 5 +- content/desktop/previous-versions/2.x-mac.md | 88 ++- .../desktop/previous-versions/2.x-windows.md | 82 +- content/desktop/previous-versions/3.x-mac.md | 104 ++- .../desktop/previous-versions/3.x-windows.md | 78 +- .../desktop/previous-versions/archive-mac.md | 116 ++- .../previous-versions/archive-windows.md | 96 ++- .../previous-versions/edge-releases-mac.md | 258 ++++--- .../edge-releases-windows.md | 248 +++--- content/desktop/release-notes.md | 258 ++++--- content/desktop/settings/linux.md | 19 +- content/desktop/settings/mac.md | 29 +- content/desktop/settings/windows.md | 26 +- content/desktop/support.md | 4 +- content/desktop/troubleshoot/known-issues.md | 18 +- content/desktop/troubleshoot/overview.md | 29 +- content/desktop/troubleshoot/topics.md | 38 +- content/desktop/troubleshoot/workarounds.md | 2 +- content/desktop/uninstall.md | 8 +- content/desktop/use-desktop/_index.md | 13 +- content/desktop/use-desktop/builds.md | 5 +- content/desktop/use-desktop/container.md | 4 +- content/desktop/use-desktop/images.md | 3 +- content/desktop/use-desktop/pause.md | 4 +- content/desktop/vm-vdi.md | 8 +- content/desktop/wasm/_index.md | 8 +- .../windows/permission-requirements.md | 4 +- content/desktop/wsl/_index.md | 16 +- content/desktop/wsl/best-practices.md | 4 +- content/desktop/wsl/use-wsl.md | 8 +- content/develop/_index.md | 22 +- content/develop/dev-best-practices.md | 4 +- .../dockerfile_best-practices.md | 10 +- content/develop/remote-development.md | 18 +- content/develop/security-best-practices.md | 8 +- content/docker-hub/2fa/_index.md | 5 +- content/docker-hub/2fa/disable-2fa.md | 9 +- content/docker-hub/2fa/new-recovery-code.md | 5 +- content/docker-hub/2fa/recover-hub-account.md | 10 +- content/docker-hub/_index.md | 59 +- content/docker-hub/access-tokens.md | 11 +- content/docker-hub/admin-overview.md | 50 +- content/docker-hub/api/deprecated.md | 4 +- content/docker-hub/api/dvp.md | 2 +- content/docker-hub/api/latest.md | 2 +- content/docker-hub/audit-log.md | 2 +- content/docker-hub/builds/_index.md | 6 +- content/docker-hub/builds/advanced.md | 12 +- .../docker-hub/builds/automated-testing.md | 8 +- content/docker-hub/builds/how-builds-work.md | 7 +- content/docker-hub/builds/link-source.md | 12 +- content/docker-hub/builds/manage-builds.md | 1 + content/docker-hub/company-faqs.md | 3 +- content/docker-hub/company-owner.md | 8 +- content/docker-hub/configure-sign-in.md | 4 +- content/docker-hub/convert-account.md | 6 +- content/docker-hub/creating-companies.md | 5 +- content/docker-hub/deactivate-account.md | 6 +- content/docker-hub/domain-audit.md | 2 +- content/docker-hub/download-rate-limit.md | 36 +- content/docker-hub/dsos-program.md | 10 +- content/docker-hub/dvp-program.md | 45 +- content/docker-hub/general-faqs.md | 5 +- content/docker-hub/group-mapping.md | 2 +- content/docker-hub/image-access-management.md | 2 +- content/docker-hub/image-management.md | 4 +- content/docker-hub/insights-analytics.md | 26 +- content/docker-hub/manage-a-team.md | 13 +- content/docker-hub/members.md | 6 +- content/docker-hub/new-company.md | 5 +- content/docker-hub/oci-artifacts.md | 7 +- content/docker-hub/official_images.md | 19 +- content/docker-hub/onboard.md | 4 +- content/docker-hub/organization-faqs.md | 3 +- content/docker-hub/orgs.md | 21 +- content/docker-hub/publish/_index.md | 52 +- .../docker-hub/publish/insights-analytics.md | 26 +- .../docker-hub/publish/repository-logos.md | 2 +- content/docker-hub/quickstart.md | 11 +- .../docker-hub/registry-access-management.md | 2 +- content/docker-hub/release-notes.md | 13 +- content/docker-hub/repos/_index.md | 15 +- content/docker-hub/repos/access/_index.md | 5 +- content/docker-hub/repos/create.md | 5 +- content/docker-hub/roles-and-permissions.md | 5 +- content/docker-hub/scim.md | 4 +- content/docker-hub/service-accounts.md | 5 +- content/docker-hub/slack_integration.md | 8 +- content/docker-hub/vulnerability-scanning.md | 15 +- content/docker-hub/webhooks.md | 2 +- content/docker-id/_index.md | 12 +- content/engine/_index.md | 88 ++- content/engine/alternative-runtimes.md | 23 +- content/engine/api/_index.md | 10 +- content/engine/api/sdk/_index.md | 18 +- content/engine/api/sdk/examples.md | 44 +- content/engine/api/v1.25.md | 6 +- content/engine/api/v1.26.md | 6 +- content/engine/api/v1.27.md | 6 +- content/engine/api/v1.28.md | 6 +- content/engine/api/v1.29.md | 2 +- content/engine/api/v1.30.md | 2 +- content/engine/api/v1.31.md | 2 +- content/engine/api/v1.32.md | 2 +- content/engine/api/v1.33.md | 2 +- content/engine/api/v1.34.md | 2 +- content/engine/api/v1.35.md | 2 +- content/engine/api/v1.36.md | 2 +- content/engine/api/v1.37.md | 2 +- content/engine/api/v1.38.md | 2 +- content/engine/api/v1.39.md | 2 +- content/engine/api/v1.40.md | 2 +- content/engine/api/v1.41.md | 2 +- content/engine/api/v1.42.md | 2 +- content/engine/api/v1.43.md | 2 +- content/engine/breaking_changes.md | 6 +- .../engine/context/working-with-contexts.md | 3 +- content/engine/faq.md | 28 +- content/engine/install/_index.md | 42 +- content/engine/install/binaries.md | 13 +- content/engine/install/centos.md | 28 +- content/engine/install/debian.md | 30 +- content/engine/install/fedora.md | 23 +- content/engine/install/linux-postinstall.md | 19 +- content/engine/install/raspberry-pi-os.md | 27 +- content/engine/install/rhel.md | 23 +- content/engine/install/sles.md | 23 +- content/engine/install/troubleshoot.md | 8 +- content/engine/install/ubuntu.md | 45 +- content/engine/migration.md | 2 +- .../engine/reference/commandline/README.md | 6 +- .../engine/reference/commandline/attach.md | 10 +- content/engine/reference/commandline/build.md | 9 +- .../engine/reference/commandline/builder.md | 6 +- .../reference/commandline/builder_build.md | 6 +- .../reference/commandline/builder_prune.md | 6 +- .../engine/reference/commandline/buildx.md | 5 +- .../reference/commandline/buildx_bake.md | 5 +- .../reference/commandline/buildx_build.md | 5 +- .../reference/commandline/buildx_create.md | 5 +- .../commandline/buildx_debug-shell.md | 5 +- .../engine/reference/commandline/buildx_du.md | 5 +- .../commandline/buildx_imagetools.md | 5 +- .../commandline/buildx_imagetools_create.md | 5 +- .../commandline/buildx_imagetools_inspect.md | 5 +- .../reference/commandline/buildx_inspect.md | 5 +- .../engine/reference/commandline/buildx_ls.md | 5 +- .../reference/commandline/buildx_prune.md | 5 +- .../engine/reference/commandline/buildx_rm.md | 5 +- .../reference/commandline/buildx_stop.md | 5 +- .../reference/commandline/buildx_use.md | 5 +- .../reference/commandline/buildx_version.md | 5 +- .../reference/commandline/checkpoint.md | 9 +- .../commandline/checkpoint_create.md | 9 +- .../reference/commandline/checkpoint_ls.md | 9 +- .../reference/commandline/checkpoint_rm.md | 9 +- .../engine/reference/commandline/commit.md | 9 +- .../engine/reference/commandline/compose.md | 7 +- .../reference/commandline/compose_build.md | 7 +- .../reference/commandline/compose_config.md | 11 +- .../reference/commandline/compose_cp.md | 5 +- .../reference/commandline/compose_create.md | 7 +- .../reference/commandline/compose_down.md | 7 +- .../reference/commandline/compose_events.md | 7 +- .../reference/commandline/compose_exec.md | 7 +- .../reference/commandline/compose_images.md | 7 +- .../reference/commandline/compose_kill.md | 7 +- .../reference/commandline/compose_logs.md | 7 +- .../reference/commandline/compose_ls.md | 5 +- .../reference/commandline/compose_pause.md | 7 +- .../reference/commandline/compose_port.md | 7 +- .../reference/commandline/compose_ps.md | 7 +- .../reference/commandline/compose_pull.md | 7 +- .../reference/commandline/compose_push.md | 7 +- .../reference/commandline/compose_restart.md | 7 +- .../reference/commandline/compose_rm.md | 7 +- .../reference/commandline/compose_run.md | 7 +- .../reference/commandline/compose_start.md | 7 +- .../reference/commandline/compose_stop.md | 7 +- .../reference/commandline/compose_top.md | 7 +- .../reference/commandline/compose_unpause.md | 7 +- .../reference/commandline/compose_up.md | 7 +- .../reference/commandline/compose_version.md | 5 +- .../engine/reference/commandline/config.md | 10 +- .../reference/commandline/config_create.md | 10 +- .../reference/commandline/config_inspect.md | 10 +- .../engine/reference/commandline/config_ls.md | 10 +- .../engine/reference/commandline/config_rm.md | 10 +- .../engine/reference/commandline/container.md | 10 +- .../reference/commandline/container_attach.md | 10 +- .../reference/commandline/container_commit.md | 10 +- .../reference/commandline/container_cp.md | 10 +- .../reference/commandline/container_create.md | 10 +- .../reference/commandline/container_diff.md | 10 +- .../reference/commandline/container_exec.md | 10 +- .../reference/commandline/container_export.md | 10 +- .../commandline/container_inspect.md | 10 +- .../reference/commandline/container_kill.md | 10 +- .../reference/commandline/container_logs.md | 10 +- .../reference/commandline/container_ls.md | 10 +- .../reference/commandline/container_pause.md | 10 +- .../reference/commandline/container_port.md | 10 +- .../reference/commandline/container_prune.md | 10 +- .../reference/commandline/container_rename.md | 10 +- .../commandline/container_restart.md | 10 +- .../reference/commandline/container_rm.md | 10 +- .../reference/commandline/container_run.md | 10 +- .../reference/commandline/container_start.md | 10 +- .../reference/commandline/container_stats.md | 10 +- .../reference/commandline/container_stop.md | 10 +- .../reference/commandline/container_top.md | 10 +- .../commandline/container_unpause.md | 10 +- .../reference/commandline/container_update.md | 10 +- .../reference/commandline/container_wait.md | 10 +- .../engine/reference/commandline/context.md | 6 +- .../reference/commandline/context_create.md | 6 +- .../reference/commandline/context_export.md | 6 +- .../reference/commandline/context_import.md | 6 +- .../reference/commandline/context_inspect.md | 6 +- .../reference/commandline/context_ls.md | 6 +- .../reference/commandline/context_rm.md | 6 +- .../reference/commandline/context_show.md | 6 +- .../reference/commandline/context_update.md | 6 +- .../reference/commandline/context_use.md | 6 +- content/engine/reference/commandline/cp.md | 9 +- .../engine/reference/commandline/create.md | 9 +- content/engine/reference/commandline/diff.md | 9 +- .../engine/reference/commandline/docker.md | 28 +- .../engine/reference/commandline/events.md | 9 +- content/engine/reference/commandline/exec.md | 9 +- .../engine/reference/commandline/export.md | 9 +- .../engine/reference/commandline/history.md | 9 +- content/engine/reference/commandline/image.md | 10 +- .../reference/commandline/image_build.md | 10 +- .../reference/commandline/image_history.md | 10 +- .../reference/commandline/image_import.md | 10 +- .../reference/commandline/image_inspect.md | 10 +- .../reference/commandline/image_load.md | 10 +- .../engine/reference/commandline/image_ls.md | 10 +- .../reference/commandline/image_prune.md | 10 +- .../reference/commandline/image_pull.md | 10 +- .../reference/commandline/image_push.md | 10 +- .../engine/reference/commandline/image_rm.md | 10 +- .../reference/commandline/image_save.md | 10 +- .../engine/reference/commandline/image_tag.md | 10 +- .../engine/reference/commandline/images.md | 9 +- .../engine/reference/commandline/import.md | 9 +- content/engine/reference/commandline/info.md | 10 +- content/engine/reference/commandline/init.md | 6 +- .../engine/reference/commandline/inspect.md | 9 +- content/engine/reference/commandline/kill.md | 9 +- content/engine/reference/commandline/load.md | 9 +- content/engine/reference/commandline/login.md | 9 +- .../engine/reference/commandline/logout.md | 9 +- content/engine/reference/commandline/logs.md | 9 +- .../engine/reference/commandline/manifest.md | 10 +- .../commandline/manifest_annotate.md | 10 +- .../reference/commandline/manifest_create.md | 10 +- .../reference/commandline/manifest_inspect.md | 10 +- .../reference/commandline/manifest_push.md | 10 +- .../reference/commandline/manifest_rm.md | 6 +- .../engine/reference/commandline/network.md | 9 +- .../reference/commandline/network_connect.md | 9 +- .../reference/commandline/network_create.md | 9 +- .../commandline/network_disconnect.md | 9 +- .../reference/commandline/network_inspect.md | 9 +- .../reference/commandline/network_ls.md | 9 +- .../reference/commandline/network_prune.md | 9 +- .../reference/commandline/network_rm.md | 9 +- content/engine/reference/commandline/node.md | 9 +- .../reference/commandline/node_demote.md | 9 +- .../reference/commandline/node_inspect.md | 9 +- .../engine/reference/commandline/node_ls.md | 9 +- .../reference/commandline/node_promote.md | 9 +- .../engine/reference/commandline/node_ps.md | 9 +- .../engine/reference/commandline/node_rm.md | 9 +- .../reference/commandline/node_update.md | 9 +- content/engine/reference/commandline/pause.md | 9 +- .../engine/reference/commandline/plugin.md | 9 +- .../reference/commandline/plugin_create.md | 9 +- .../reference/commandline/plugin_disable.md | 9 +- .../reference/commandline/plugin_enable.md | 9 +- .../reference/commandline/plugin_inspect.md | 9 +- .../reference/commandline/plugin_install.md | 9 +- .../engine/reference/commandline/plugin_ls.md | 9 +- .../reference/commandline/plugin_push.md | 9 +- .../engine/reference/commandline/plugin_rm.md | 9 +- .../reference/commandline/plugin_set.md | 9 +- .../reference/commandline/plugin_upgrade.md | 9 +- content/engine/reference/commandline/port.md | 9 +- content/engine/reference/commandline/ps.md | 9 +- content/engine/reference/commandline/pull.md | 9 +- content/engine/reference/commandline/push.md | 9 +- .../engine/reference/commandline/rename.md | 9 +- .../engine/reference/commandline/restart.md | 9 +- content/engine/reference/commandline/rm.md | 9 +- content/engine/reference/commandline/rmi.md | 9 +- content/engine/reference/commandline/run.md | 16 +- content/engine/reference/commandline/save.md | 9 +- content/engine/reference/commandline/scout.md | 6 +- .../reference/commandline/scout_compare.md | 6 +- .../reference/commandline/scout_cves.md | 6 +- .../commandline/scout_entitlement.md | 6 +- .../reference/commandline/scout_quickview.md | 6 +- .../commandline/scout_recommendations.md | 6 +- .../reference/commandline/scout_repo.md | 6 +- .../commandline/scout_repo_disable.md | 6 +- .../commandline/scout_repo_enable.md | 6 +- .../reference/commandline/scout_repo_list.md | 6 +- .../reference/commandline/scout_sbom.md | 6 +- .../reference/commandline/scout_stream.md | 6 +- .../reference/commandline/scout_version.md | 6 +- .../engine/reference/commandline/search.md | 9 +- .../engine/reference/commandline/secret.md | 9 +- .../reference/commandline/secret_create.md | 9 +- .../reference/commandline/secret_inspect.md | 9 +- .../engine/reference/commandline/secret_ls.md | 9 +- .../engine/reference/commandline/secret_rm.md | 9 +- .../engine/reference/commandline/service.md | 10 +- .../reference/commandline/service_create.md | 9 +- .../reference/commandline/service_inspect.md | 9 +- .../reference/commandline/service_logs.md | 10 +- .../reference/commandline/service_ls.md | 9 +- .../reference/commandline/service_ps.md | 10 +- .../reference/commandline/service_rm.md | 10 +- .../reference/commandline/service_rollback.md | 10 +- .../reference/commandline/service_scale.md | 10 +- .../reference/commandline/service_update.md | 10 +- content/engine/reference/commandline/stack.md | 10 +- .../reference/commandline/stack_config.md | 6 +- .../reference/commandline/stack_deploy.md | 16 +- .../engine/reference/commandline/stack_ls.md | 10 +- .../engine/reference/commandline/stack_ps.md | 14 +- .../engine/reference/commandline/stack_rm.md | 10 +- .../reference/commandline/stack_services.md | 10 +- content/engine/reference/commandline/start.md | 10 +- content/engine/reference/commandline/stats.md | 10 +- content/engine/reference/commandline/stop.md | 10 +- content/engine/reference/commandline/swarm.md | 10 +- .../engine/reference/commandline/swarm_ca.md | 10 +- .../reference/commandline/swarm_init.md | 10 +- .../reference/commandline/swarm_join-token.md | 14 +- .../reference/commandline/swarm_join.md | 10 +- .../reference/commandline/swarm_leave.md | 10 +- .../reference/commandline/swarm_unlock-key.md | 10 +- .../reference/commandline/swarm_unlock.md | 10 +- .../reference/commandline/swarm_update.md | 10 +- .../engine/reference/commandline/system.md | 10 +- .../engine/reference/commandline/system_df.md | 10 +- .../reference/commandline/system_events.md | 10 +- .../reference/commandline/system_info.md | 10 +- .../reference/commandline/system_prune.md | 10 +- content/engine/reference/commandline/tag.md | 10 +- content/engine/reference/commandline/top.md | 10 +- content/engine/reference/commandline/trust.md | 10 +- .../reference/commandline/trust_inspect.md | 10 +- .../engine/reference/commandline/trust_key.md | 10 +- .../commandline/trust_key_generate.md | 10 +- .../reference/commandline/trust_key_load.md | 10 +- .../reference/commandline/trust_revoke.md | 10 +- .../reference/commandline/trust_sign.md | 10 +- .../reference/commandline/trust_signer.md | 10 +- .../reference/commandline/trust_signer_add.md | 10 +- .../commandline/trust_signer_remove.md | 10 +- .../engine/reference/commandline/unpause.md | 10 +- .../engine/reference/commandline/update.md | 10 +- .../engine/reference/commandline/version.md | 10 +- .../engine/reference/commandline/volume.md | 10 +- .../reference/commandline/volume_create.md | 10 +- .../reference/commandline/volume_inspect.md | 10 +- .../engine/reference/commandline/volume_ls.md | 10 +- .../reference/commandline/volume_prune.md | 10 +- .../engine/reference/commandline/volume_rm.md | 10 +- .../reference/commandline/volume_update.md | 6 +- content/engine/reference/commandline/wait.md | 10 +- content/engine/release-notes/17.03.md | 3 +- content/engine/release-notes/17.04.md | 2 +- content/engine/release-notes/17.05.md | 2 +- content/engine/release-notes/17.06.md | 2 +- content/engine/release-notes/17.07.md | 2 +- content/engine/release-notes/17.09.md | 6 +- content/engine/release-notes/17.10.md | 4 +- content/engine/release-notes/17.11.md | 4 +- content/engine/release-notes/17.12.md | 2 +- content/engine/release-notes/18.01.md | 3 +- content/engine/release-notes/18.02.md | 3 +- content/engine/release-notes/18.03.md | 1 - content/engine/release-notes/18.04.md | 3 +- content/engine/release-notes/18.05.md | 2 +- content/engine/release-notes/18.06.md | 2 +- content/engine/release-notes/18.09.md | 2 +- content/engine/release-notes/19.03.md | 2 +- content/engine/release-notes/20.10.md | 191 ++--- content/engine/release-notes/23.0.md | 21 +- content/engine/release-notes/24.0.md | 27 +- .../engine/release-notes/prior-releases.md | 22 +- content/engine/sbom/_index.md | 6 +- content/engine/security/_index.md | 6 +- content/engine/security/antivirus.md | 2 +- content/engine/security/apparmor.md | 2 +- content/engine/security/certificates.md | 9 +- content/engine/security/https/README.md | 2 +- content/engine/security/protect-access.md | 10 +- content/engine/security/rootless.md | 4 +- content/engine/security/seccomp.md | 2 +- content/engine/security/trust/_index.md | 8 +- .../engine/security/trust/deploying_notary.md | 4 +- .../engine/security/trust/trust_automation.md | 4 +- .../engine/security/trust/trust_delegation.md | 8 +- .../engine/security/trust/trust_key_mng.md | 10 +- .../engine/security/trust/trust_sandbox.md | 4 +- content/engine/security/userns-remap.md | 6 +- content/engine/swarm/_index.md | 8 +- content/engine/swarm/admin_guide.md | 14 +- content/engine/swarm/configs.md | 4 +- .../swarm/how-swarm-mode-works/nodes.md | 6 +- .../engine/swarm/how-swarm-mode-works/pki.md | 2 +- .../swarm/how-swarm-mode-works/services.md | 2 +- .../how-swarm-mode-works/swarm-task-states.md | 4 +- content/engine/swarm/ingress.md | 6 +- content/engine/swarm/join-nodes.md | 2 +- content/engine/swarm/key-concepts.md | 2 +- content/engine/swarm/manage-nodes.md | 2 +- content/engine/swarm/networking.md | 2 +- content/engine/swarm/raft.md | 2 +- content/engine/swarm/secrets.md | 5 +- content/engine/swarm/services.md | 12 +- content/engine/swarm/stack-deploy.md | 4 +- content/engine/swarm/swarm-mode.md | 2 +- content/engine/swarm/swarm-tutorial/_index.md | 2 +- .../engine/swarm/swarm-tutorial/add-nodes.md | 2 +- .../swarm/swarm-tutorial/create-swarm.md | 2 +- .../swarm/swarm-tutorial/delete-service.md | 2 +- .../swarm/swarm-tutorial/deploy-service.md | 2 +- .../engine/swarm/swarm-tutorial/drain-node.md | 4 +- .../swarm/swarm-tutorial/inspect-service.md | 2 +- .../swarm/swarm-tutorial/rolling-update.md | 2 +- .../swarm/swarm-tutorial/scale-service.md | 2 +- content/engine/swarm/swarm_manager_locking.md | 2 +- content/engine/tutorials/_index.md | 9 +- .../engine/tutorials/networkingcontainers.md | 18 +- content/faq/_index.md | 38 +- content/get-docker.md | 10 +- content/get-started/02_our_app.md | 25 +- content/get-started/03_updating_app.md | 9 +- content/get-started/04_sharing_app.md | 26 +- content/get-started/05_persisting_data.md | 13 +- content/get-started/06_bind_mounts.md | 18 +- content/get-started/07_multi_container.md | 13 +- content/get-started/08_using_compose.md | 11 +- content/get-started/09_image_best.md | 9 +- content/get-started/11_what_next.md | 12 +- content/get-started/_index.md | 12 +- content/get-started/hands-on-overview.md | 26 +- content/get-started/kube-deploy.md | 4 +- content/get-started/orchestration.md | 4 +- content/get-started/overview.md | 13 +- content/get-started/publish-your-own-image.md | 6 +- content/get-started/resources.md | 61 +- content/get-started/run-docker-hub-images.md | 12 +- content/get-started/run-your-own-container.md | 10 +- content/get-started/swarm-deploy.md | 10 +- content/get-started/what-is-a-container.md | 12 +- content/glossary.md | 11 +- content/includes/aci-ecs-eol.md | 2 +- content/includes/admin-company-overview.md | 2 +- content/includes/admin-early-access.md | 2 +- content/includes/admin-org-overview.md | 2 +- content/includes/api-version-matrix.md | 2 +- content/includes/beta.md | 4 +- content/includes/build-feature-state.md | 2 +- content/includes/buildx-v0.10-disclaimer.md | 8 +- content/includes/compose-eol.md | 2 +- content/includes/configure-registry-json.md | 4 +- .../includes/content/compose-extfields-sub.md | 8 +- content/includes/content/compose-matrix.md | 2 +- content/includes/content/compose-var-sub.md | 4 +- content/includes/deploy.md | 2 +- content/includes/desktop-builders-setting.md | 2 +- content/includes/desktop-experimental.md | 2 +- content/includes/desktop-license-update.md | 2 +- content/includes/desktop-linux-launch.md | 2 +- content/includes/dev-envs-changing.md | 2 +- content/includes/dockerfile-labs-channel.md | 2 +- content/includes/experimental.md | 2 +- content/includes/gha-tutorial.md | 25 +- content/includes/github_issue.md | 2 +- content/includes/index.md | 3 - content/includes/install-script.md | 7 +- content/includes/registry.md | 4 +- content/includes/root-errors.md | 2 +- content/includes/scout-early-access.md | 4 +- content/includes/swarm-compose-compat.md | 2 +- content/includes/swarm-mode.md | 2 +- content/language/_index.md | 3 +- content/language/dotnet/_index.md | 2 +- content/language/dotnet/build-images.md | 10 +- content/language/dotnet/configure-ci-cd.md | 8 +- content/language/dotnet/deploy.md | 6 +- content/language/dotnet/develop.md | 6 +- content/language/dotnet/run-containers.md | 6 +- content/language/dotnet/run-tests.md | 6 +- content/language/golang/_index.md | 10 +- content/language/golang/build-images.md | 28 +- content/language/golang/configure-ci-cd.md | 13 +- content/language/golang/deploy.md | 6 +- content/language/golang/develop.md | 20 +- content/language/golang/run-containers.md | 8 +- content/language/golang/run-tests.md | 12 +- content/language/java/_index.md | 2 +- content/language/java/build-images.md | 10 +- content/language/java/configure-ci-cd.md | 8 +- content/language/java/deploy.md | 6 +- content/language/java/develop.md | 8 +- content/language/java/run-containers.md | 6 +- content/language/java/run-tests.md | 6 +- content/language/nodejs/_index.md | 2 +- content/language/nodejs/build-images.md | 15 +- content/language/nodejs/configure-ci-cd.md | 8 +- content/language/nodejs/deploy.md | 6 +- content/language/nodejs/develop.md | 14 +- content/language/nodejs/run-containers.md | 8 +- content/language/nodejs/run-tests.md | 6 +- content/language/python/_index.md | 2 +- content/language/python/build-images.md | 8 +- content/language/python/configure-ci-cd.md | 6 +- content/language/python/deploy.md | 4 +- content/language/python/develop.md | 4 +- content/language/python/run-containers.md | 4 +- content/language/rust/_index.md | 2 +- content/language/rust/build-images.md | 2 +- content/language/rust/configure-ci-cd.md | 6 +- content/language/rust/deploy.md | 4 +- content/language/rust/develop.md | 2 +- content/language/rust/run-containers.md | 4 +- content/network/_index.md | 24 +- content/network/drivers/_index.md | 2 +- content/network/drivers/bridge.md | 18 +- content/network/drivers/host.md | 6 +- content/network/drivers/ipvlan.md | 9 +- content/network/drivers/macvlan.md | 10 +- content/network/drivers/none.md | 6 +- content/network/drivers/overlay.md | 14 +- content/network/links.md | 17 +- content/network/network-tutorial-host.md | 3 +- content/network/network-tutorial-macvlan.md | 6 +- content/network/network-tutorial-overlay.md | 7 +- .../network/network-tutorial-standalone.md | 3 +- content/network/packet-filtering-firewalls.md | 12 +- content/network/proxy.md | 7 +- content/reference.md | 144 ++-- content/registry/_index.md | 10 +- content/registry/compatibility.md | 5 +- content/registry/deploying.md | 10 +- content/registry/deprecated.md | 2 +- content/registry/garbage-collection.md | 4 +- content/registry/glossary.md | 2 +- content/registry/help.md | 5 +- content/registry/insecure.md | 12 +- content/registry/introduction.md | 4 +- content/registry/migration.md | 2 +- content/registry/notifications.md | 7 +- content/registry/recipes/_index.md | 4 +- content/registry/recipes/apache.md | 7 +- content/registry/recipes/mirror.md | 11 +- content/registry/recipes/nginx.md | 9 +- content/registry/recipes/osx-setup-guide.md | 7 +- content/registry/storage-drivers/_index.md | 11 +- content/registry/storage-drivers/azure.md | 4 +- .../registry/storage-drivers/filesystem.md | 4 +- content/registry/storage-drivers/gcs.md | 5 +- content/registry/storage-drivers/inmemory.md | 4 +- content/registry/storage-drivers/oss.md | 4 +- content/registry/storage-drivers/s3.md | 4 +- content/registry/storage-drivers/swift.md | 4 +- content/release-lifecycle.md | 9 +- content/release-notes.md | 32 +- content/samples/_index.md | 7 +- content/samples/django.md | 4 +- content/samples/dotnet.md | 8 +- content/samples/java.md | 1 - content/samples/javascript.md | 1 - content/samples/mariadb.md | 1 - content/samples/minecraft.md | 1 - content/samples/mongodb.md | 1 - content/samples/ms-sql.md | 2 - content/samples/mysql.md | 1 - content/samples/nextcloud.md | 1 - content/samples/nginx.md | 1 - content/samples/nodejs.md | 1 - content/samples/php.md | 1 - content/samples/pi-hole.md | 1 - content/samples/plex.md | 1 - content/samples/portainer.md | 1 - content/samples/postgres.md | 7 +- content/samples/prometheus.md | 1 - content/samples/python.md | 1 - content/samples/rails.md | 1 - content/samples/react.md | 1 - content/samples/redis.md | 1 - content/samples/ruby.md | 1 - content/samples/rust.md | 1 - content/samples/spark.md | 1 - content/samples/spring.md | 1 - content/samples/traefik.md | 1 - content/samples/typescript.md | 1 - content/samples/vuejs.md | 1 - content/samples/wireguard.md | 1 - content/samples/wordpress.md | 7 +- content/scout/_index.md | 32 +- content/scout/advanced-image-analysis.md | 7 +- content/scout/advisory-db-sources.md | 7 +- content/scout/artifactory.md | 25 +- content/scout/dashboard.md | 13 +- content/scout/data-handling.md | 4 +- content/scout/image-details-view.md | 16 +- content/scout/integrations/_index.md | 4 +- content/scout/integrations/ci/_index.md | 11 +- content/scout/integrations/ci/azure.md | 5 +- content/scout/integrations/ci/circle-ci.md | 5 +- content/scout/integrations/ci/gha.md | 20 +- content/scout/integrations/ci/gitlab.md | 8 +- content/scout/integrations/ci/jenkins.md | 4 +- .../scout/integrations/environment/_index.md | 10 +- .../integrations/registry/artifactory.md | 25 +- content/scout/quickstart.md | 24 +- content/scout/web-app.md | 13 +- content/security.md | 29 +- content/single-sign-on/_index.md | 2 +- content/single-sign-on/configure/_index.md | 6 +- content/single-sign-on/domain-faqs.md | 3 +- content/single-sign-on/faqs.md | 3 +- content/single-sign-on/idp-faqs.md | 2 +- content/single-sign-on/manage/_index.md | 5 +- content/single-sign-on/saml-faqs.md | 2 +- content/single-sign-on/users-faqs.md | 3 +- content/storage/_index.md | 6 +- content/storage/bind-mounts.md | 10 +- content/storage/containerd.md | 6 +- content/storage/storagedriver/_index.md | 22 +- content/storage/storagedriver/aufs-driver.md | 9 +- content/storage/storagedriver/btrfs-driver.md | 4 +- .../storagedriver/device-mapper-driver.md | 6 +- .../storage/storagedriver/overlayfs-driver.md | 4 +- .../storagedriver/select-storage-driver.md | 10 +- content/storage/storagedriver/vfs-driver.md | 7 +- content/storage/storagedriver/zfs-driver.md | 5 +- content/storage/tmpfs.md | 4 +- .../storage/troubleshooting_volume_errors.md | 4 +- content/storage/volumes.md | 22 +- content/subscription/_index.md | 32 +- content/subscription/add-seats.md | 8 +- content/subscription/desktop-license.md | 6 +- content/subscription/details.md | 14 +- content/subscription/downgrade.md | 10 +- content/subscription/faq.md | 10 +- content/subscription/remove-seats.md | 8 +- content/subscription/scout-details.md | 6 +- content/subscription/upgrade.md | 8 +- content/support.md | 18 +- 950 files changed, 5772 insertions(+), 5726 deletions(-) diff --git a/content/_index.md b/content/_index.md index bcc3c7a096..2e42059811 100644 --- a/content/_index.md +++ b/content/_index.md @@ -3,40 +3,41 @@ title: Home description: Home page for Docker's documentation keywords: Docker, documentation, manual, guide, reference, api, samples grid: - - title: Get started - image: - dark: /assets/images/rocket-dark.svg - light: /assets/images/rocket.svg - link: /get-started/ - description: Learn Docker basics and the benefits of containerizing your applications. - - title: Download and install - image: - dark: /assets/images/download-docker-dark.svg - light: /assets/images/download-docker.svg - link: /get-docker/ - description: Download and install Docker on your machine in a few easy steps. - - title: Guides - image: - dark: /assets/images/guides-dark.svg - light: /assets/images/guides.svg - link: /get-started/overview/ - description: Learn how to set up your Docker environment and start containerizing your applications. - - title: Language-specific guides - image: - dark: /assets/images/language-guides-dark.svg - light: /assets/images/language-guides.svg - link: /language/ - description: Learn how to use Docker with your favorite programming language. - - title: Manuals - image: - dark: /assets/images/manuals-dark.svg - light: /assets/images/manuals.svg - link: /desktop/ - description: Browse the manuals and learn how to use Docker products. - - title: Reference - image: - dark: /assets/images/reference-dark.svg - light: /assets/images/reference.svg - link: /reference/ - description: Browse the CLI and API reference documentation. ---- +- title: Get started + image: + dark: /assets/images/rocket-dark.svg + light: /assets/images/rocket.svg + link: /get-started/ + description: Learn Docker basics and the benefits of containerizing your applications. +- title: Download and install + image: + dark: /assets/images/download-docker-dark.svg + light: /assets/images/download-docker.svg + link: /get-docker/ + description: Download and install Docker on your machine in a few easy steps. +- title: Guides + image: + dark: /assets/images/guides-dark.svg + light: /assets/images/guides.svg + link: /get-started/overview/ + description: Learn how to set up your Docker environment and start containerizing + your applications. +- title: Language-specific guides + image: + dark: /assets/images/language-guides-dark.svg + light: /assets/images/language-guides.svg + link: /language/ + description: Learn how to use Docker with your favorite programming language. +- title: Manuals + image: + dark: /assets/images/manuals-dark.svg + light: /assets/images/manuals.svg + link: /desktop/ + description: Browse the manuals and learn how to use Docker products. +- title: Reference + image: + dark: /assets/images/reference-dark.svg + light: /assets/images/reference.svg + link: /reference/ + description: Browse the CLI and API reference documentation. +--- \ No newline at end of file diff --git a/content/admin/_index.md b/content/admin/_index.md index d45c6d1337..f2587d0473 100644 --- a/content/admin/_index.md +++ b/content/admin/_index.md @@ -1,22 +1,24 @@ --- -description: Docker Admin provides administrators with centralized observability, access management, and controls for their company and organizations. +description: Docker Admin provides administrators with centralized observability, + access management, and controls for their company and organizations. keywords: admin, administration, company, organization title: Docker Admin overview grid: - - title: Company administration - description: Explore how to manage a company in Docker Admin. - icon: lan - link: /admin/company/ - - title: Organization administration - description: Learn about organization administration in Docker Admin. - icon: contact_page - link: /admin/organization/ +- title: Company administration + description: Explore how to manage a company in Docker Admin. + icon: lan + link: /admin/company/ +- title: Organization administration + description: Learn about organization administration in Docker Admin. + icon: contact_page + link: /admin/organization/ --- -{% include admin-early-access.md %} -The [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"} console provides administrators with centralized observability, access management, and controls for their company and organizations. To provide these features, Docker uses the following hierarchy and roles. +{{< include "admin-early-access.md" >}} -![Docker hierarchy](./images/docker-hierarchy-company.svg){: width="800px" } +The [Docker Admin](https://admin.docker.com) console provides administrators with centralized observability, access management, and controls for their company and organizations. To provide these features, Docker uses the following hierarchy and roles. + +![Docker hierarchy](./images/docker-hierarchy-company.svg) - Company: A company simplifies the management of Docker organizations and settings. Creating a company is optional and only available to Docker Business subscribers. - Company owner: A company can have multiple owners. Company owners have company-wide observability and can manage company-wide settings that apply to all associated organizations. In addition, company owners have the same access as organization owners for all associated organizations. @@ -25,4 +27,4 @@ The [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" cl - Team: A team is a group of Docker members that belong to an organization. Organization and company owners can group members into additional teams to configure repository permissions on a per-team basis. - Member: A member is a Docker user that's a member of at least one team in an organization. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/admin/company/_index.md b/content/admin/company/_index.md index 79b85eabfb..834ac0c8c2 100644 --- a/content/admin/company/_index.md +++ b/content/admin/company/_index.md @@ -3,39 +3,41 @@ description: Learn about companies. keywords: company, multiple organizations, manage companies title: Overview grid: - - title: Manage organizations - description: Learn how to add and manage organizations as well as seats within your company. - icon: note_add - link: /admin/company/organizations/ - - title: Manage users - description: Explore how to manage users in all organizations. - icon: contact_page - link: /admin/company/users/ - - title: Manage company owners - description: Find out more about company owners and how to manage them. - icon: group_add - link: /admin/company/owners/ - - title: Configure Single Sign-On - description: Discover how to configure SSO for your entire company. - icon: key - link: /admin/company/settings/sso/ - - title: Set up SCIM - description: Set up SCIM to automatically provision and deprovision users in your company. - icon: checklist - link: /admin/company/settings/scim/ - - title: Domain management - description: Add and verify your domains. - icon: security - link: /admin/company/settings/domains/ +- title: Manage organizations + description: Learn how to add and manage organizations as well as seats within your + company. + icon: note_add + link: /admin/company/organizations/ +- title: Manage users + description: Explore how to manage users in all organizations. + icon: contact_page + link: /admin/company/users/ +- title: Manage company owners + description: Find out more about company owners and how to manage them. + icon: group_add + link: /admin/company/owners/ +- title: Configure Single Sign-On + description: Discover how to configure SSO for your entire company. + icon: key + link: /admin/company/settings/sso/ +- title: Set up SCIM + description: Set up SCIM to automatically provision and deprovision users in your + company. + icon: checklist + link: /admin/company/settings/scim/ +- title: Domain management + description: Add and verify your domains. + icon: security + link: /admin/company/settings/domains/ --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-company-overview.md %} +{{< include "admin-company-overview.md" >}} To create a company, see [Create a company](../organization/general-settings.md#create-a-company). Learn how to administer a company using Docker Admin in the following sections. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/admin/company/organizations.md b/content/admin/company/organizations.md index 1c6d4f63d6..871792acfb 100644 --- a/content/admin/company/organizations.md +++ b/content/admin/company/organizations.md @@ -3,11 +3,12 @@ description: Manage organizations for a company in Docker Admin. keywords: company, multiple organizations, manage organizations title: Manage organizations --- -{% include admin-early-access.md %} + +{{< include "admin-early-access.md" >}} ## View all organizations -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your company in the drop-down menu. 3. Under **Organizations**, select **Overview**. @@ -15,7 +16,7 @@ title: Manage organizations When you have a [self-serve](../../subscription/details.md#self-serve) subscription that has no pending subscription changes, you can add seats using the following steps. -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your company in the drop-down menu. 3. Under **Organizations**, select **Overview**. 4. Select the action icon in the organization's card, and then select **Get more seats**. @@ -25,7 +26,7 @@ When you have a [self-serve](../../subscription/details.md#self-serve) subscript There is no limit to the number of organizations you can have under a company layer. All organizations must have a Business subscription. -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your company in the drop-down menu. 3. Select **Add organization**. 4. Choose the organization you want to add from the drop-down menu. @@ -33,8 +34,8 @@ There is no limit to the number of organizations you can have under a company la ## Manage an organization -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your company in the drop-down menu. 3. Select the organization that you want to manage. -For more details about managing an organization, see [Organization administration](../organization/index.md). +For more details about managing an organization, see [Organization administration](../organization/index.md). \ No newline at end of file diff --git a/content/admin/company/owners.md b/content/admin/company/owners.md index a4dbc1c488..eea6c18df4 100644 --- a/content/admin/company/owners.md +++ b/content/admin/company/owners.md @@ -3,13 +3,14 @@ description: Learn about company owners. keywords: company, owners title: Manage company owners --- -{% include admin-early-access.md %} + +{{< include "admin-early-access.md" >}} As a company owner, you can configure [Single Sign-on (SSO)](./settings/sso.md) and [System for Cross-domain Identity Management (SCIM)](./settings/scim.md) for all organizations under the company. ## Add a company owner -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your company in the drop-down menu. 3. Select **Company Owners**. 4. Select **Add Owner**. @@ -18,7 +19,7 @@ As a company owner, you can configure [Single Sign-on (SSO)](./settings/sso.md) ## Remove a company owner -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your company in the drop-down menu. 3. Select **Company Owners**. 4. Select the **Action** icon in the row of the company owner that your want to remove. diff --git a/content/admin/company/settings/domains.md b/content/admin/company/settings/domains.md index 07c123d265..97ccca98e3 100644 --- a/content/admin/company/settings/domains.md +++ b/content/admin/company/settings/domains.md @@ -4,7 +4,7 @@ keywords: domains, SCIM, SSO, Docker Admin title: Domain management --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Use domain management to manage your domains for Single Sign-On and SCIM. diff --git a/content/admin/company/settings/group-mapping.md b/content/admin/company/settings/group-mapping.md index 13251a19ac..d87ce553c1 100644 --- a/content/admin/company/settings/group-mapping.md +++ b/content/admin/company/settings/group-mapping.md @@ -4,6 +4,6 @@ keywords: Group Mapping, SCIM, Docker Admin title: Group Mapping --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-group-mapping.md product="admin" layer="company" %} \ No newline at end of file +{{% admin-group-mapping product="admin" layer="company" %}} \ No newline at end of file diff --git a/content/admin/company/settings/scim.md b/content/admin/company/settings/scim.md index d827e1eec3..53fb617f94 100644 --- a/content/admin/company/settings/scim.md +++ b/content/admin/company/settings/scim.md @@ -4,7 +4,7 @@ keywords: SCIM, SSO title: SCIM --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Follow the steps on this page to manage SCIM for your company. To manage SCIM for an organization, see [SCIM for an organization](/admin/organization/security-settings/scim/). diff --git a/content/admin/company/settings/sso-configuration.md b/content/admin/company/settings/sso-configuration.md index f7332affcd..18c8983a4d 100644 --- a/content/admin/company/settings/sso-configuration.md +++ b/content/admin/company/settings/sso-configuration.md @@ -4,7 +4,7 @@ keywords: configure, sso, docker admin title: Configure Single Sign-On for a company --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Follow the steps on this page to configure SSO for your company. To configure SSO for an organization, see [Configure SSO for an organization](/admin/organization/security-settings/sso-configuration/). diff --git a/content/admin/company/settings/sso-management.md b/content/admin/company/settings/sso-management.md index 65d84b5d17..cc71f18fa0 100644 --- a/content/admin/company/settings/sso-management.md +++ b/content/admin/company/settings/sso-management.md @@ -4,13 +4,12 @@ keywords: manage, single sign-on, SSO, sign-on title: Manage Single Sign-On for a company --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Follow the steps on this page to manage SSO for your company. To manage SSO for an organization, see [Manage SSO for an organization](/admin/organization/security-settings/sso-management/). ## Manage organizations -{% include admin-sso-management-orgs.md product="admin" %} - -{% include admin-sso-management.md product="admin" layer="company"%} +{{% admin-sso-management-orgs product="admin" %}} +{% include admin-sso-management.md product="admin" layer="company"%} \ No newline at end of file diff --git a/content/admin/company/settings/sso.md b/content/admin/company/settings/sso.md index 36ed9304dd..b34fb60f23 100644 --- a/content/admin/company/settings/sso.md +++ b/content/admin/company/settings/sso.md @@ -4,6 +4,6 @@ keywords: Single Sign-on, SSO, sign-on title: Single Sign-On overview --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-sso.md product="admin" layer="company" %} \ No newline at end of file +{{% admin-sso product="admin" layer="company" %}} \ No newline at end of file diff --git a/content/admin/company/users.md b/content/admin/company/users.md index f59d3e1aee..ba5e7b3423 100644 --- a/content/admin/company/users.md +++ b/content/admin/company/users.md @@ -4,9 +4,9 @@ keywords: company, company users, users, admin, docker admin title: Manage company users --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-users.md product="admin" layer="company" %} +{{% admin-users product="admin" layer="company" %}} ## Manage members on a team diff --git a/content/admin/organization/_index.md b/content/admin/organization/_index.md index 4c13df3951..e9aab0b2de 100644 --- a/content/admin/organization/_index.md +++ b/content/admin/organization/_index.md @@ -3,44 +3,44 @@ description: Learn about organizations. keywords: organizations, admin, overview title: Organization administration overview grid: - - title: Manage members - description: Explore how to manage members. - icon: contact_page - link: /admin/organization/members/ - - title: Activity logs - description: Learn how to audit the activities of your members. - icon: feed - link: /admin/organization/activity-logs/ - - title: Image Access Management - description: Control which types of images your developers can pull. - icon: dynamic_feed - link: /admin/organization/image-access/ - - title: Registry Access Management - description: Define which registries your developers can access. - icon: all_inbox - link: /admin/organization/registry-access/ - - title: General settings - description: Configure general information or create a company. - icon: settings_suggest - link: /admin/organization/general-settings/ - - title: SSO & SCIM - description: > - Set up [Single Sign-On](/admin/organization/security-settings/sso/) and - [SCIM](/admin/organization/security-settings/scim/) for your organization. - icon: key - - title: Domain management - description: Add, verify, and audit your domains. - link: /admin/organization/security-settings/domains/ - icon: security +- title: Manage members + description: Explore how to manage members. + icon: contact_page + link: /admin/organization/members/ +- title: Activity logs + description: Learn how to audit the activities of your members. + icon: feed + link: /admin/organization/activity-logs/ +- title: Image Access Management + description: Control which types of images your developers can pull. + icon: dynamic_feed + link: /admin/organization/image-access/ +- title: Registry Access Management + description: Define which registries your developers can access. + icon: all_inbox + link: /admin/organization/registry-access/ +- title: General settings + description: Configure general information or create a company. + icon: settings_suggest + link: /admin/organization/general-settings/ +- title: SSO & SCIM + description: 'Set up [Single Sign-On](/admin/organization/security-settings/sso/) + and [SCIM](/admin/organization/security-settings/scim/) for your organization. + + ' + icon: key +- title: Domain management + description: Add, verify, and audit your domains. + link: /admin/organization/security-settings/domains/ + icon: security --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-org-overview.md %} +{{< include "admin-org-overview.md" >}} To create an organization, see [Create your organization](../../docker-hub/orgs.md). Learn how to administer an organization using Docker Admin in the following sections. -{{< grid >}} - +{{< grid >}} \ No newline at end of file diff --git a/content/admin/organization/activity-logs.md b/content/admin/organization/activity-logs.md index 8529070cbc..29588b75eb 100644 --- a/content/admin/organization/activity-logs.md +++ b/content/admin/organization/activity-logs.md @@ -4,6 +4,6 @@ keywords: team, organization, activity, log, audit, activities title: Activity logs --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-org-audit-log.md product="admin" %} \ No newline at end of file +{{% admin-org-audit-log product="admin" %}} \ No newline at end of file diff --git a/content/admin/organization/general-settings.md b/content/admin/organization/general-settings.md index 832ab14356..7923da0879 100644 --- a/content/admin/organization/general-settings.md +++ b/content/admin/organization/general-settings.md @@ -4,7 +4,7 @@ keywords: organization, settings title: General settings --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} ## Configure general information @@ -19,7 +19,7 @@ This information includes: To edit this information: -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your organization in the drop-down menu. 3. Under **Organization Settings**, select **General**. 4. Specify the organization information and select **Save**. @@ -28,7 +28,7 @@ To edit this information: To create a new company: -1. Sign in to [Docker Admin](https://admin.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Admin](https://admin.docker.com). 2. In the left navigation, select your organization in the drop-down menu. 3. Under **Organization Settings**, select **General**. 4. In the **Organization management** section, select **Create a company**. diff --git a/content/admin/organization/image-access.md b/content/admin/organization/image-access.md index 206e5a80ac..13f9290d11 100644 --- a/content/admin/organization/image-access.md +++ b/content/admin/organization/image-access.md @@ -4,6 +4,6 @@ keywords: image, access, management title: Image Access Management --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-image-access.md product="admin" %} \ No newline at end of file +{{% admin-image-access product="admin" %}} \ No newline at end of file diff --git a/content/admin/organization/members.md b/content/admin/organization/members.md index 586e9fb5ef..73d2316243 100644 --- a/content/admin/organization/members.md +++ b/content/admin/organization/members.md @@ -4,10 +4,10 @@ keywords: members, teams, organizations title: Manage members --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-users.md product="admin" %} +{{% admin-users product="admin" %}} ## Manage members on a team -Use Docker Hub to add a member to a team or remove a member from a team. For more details, see [Manage members in Docker Hub](../../docker-hub/members.md). +Use Docker Hub to add a member to a team or remove a member from a team. For more details, see [Manage members in Docker Hub](../../docker-hub/members.md). \ No newline at end of file diff --git a/content/admin/organization/onboard.md b/content/admin/organization/onboard.md index 8bc1836503..e5bc10b523 100644 --- a/content/admin/organization/onboard.md +++ b/content/admin/organization/onboard.md @@ -6,6 +6,6 @@ toc_min: 1 toc_max: 2 --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-org-onboarding.md product="admin" %} \ No newline at end of file +{{% admin-org-onboarding product="admin" %}} \ No newline at end of file diff --git a/content/admin/organization/registry-access.md b/content/admin/organization/registry-access.md index 64a20ed376..ec80dc99fe 100644 --- a/content/admin/organization/registry-access.md +++ b/content/admin/organization/registry-access.md @@ -4,6 +4,6 @@ keywords: registry, access, management title: Registry Access Management --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-registry-access.md product="admin" %} \ No newline at end of file +{{% admin-registry-access product="admin" %}} \ No newline at end of file diff --git a/content/admin/organization/security-settings/domains.md b/content/admin/organization/security-settings/domains.md index 21d13407d1..51f16ed1bc 100644 --- a/content/admin/organization/security-settings/domains.md +++ b/content/admin/organization/security-settings/domains.md @@ -4,7 +4,7 @@ keywords: domains, SCIM, SSO, Docker Admin, domain audit title: Domain management --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Use domain management to manage your domains for Single Sign-On and SCIM, as well as audit your domains for uncaptured users. @@ -14,4 +14,4 @@ Use domain management to manage your domains for Single Sign-On and SCIM, as wel ## Domain audit -{% include admin-domain-audit.md product="admin" %} +{{% admin-domain-audit product="admin" %}} \ No newline at end of file diff --git a/content/admin/organization/security-settings/group-mapping.md b/content/admin/organization/security-settings/group-mapping.md index 1dbd7f5b73..aab60b50df 100644 --- a/content/admin/organization/security-settings/group-mapping.md +++ b/content/admin/organization/security-settings/group-mapping.md @@ -4,6 +4,6 @@ keywords: Group Mapping, SCIM, Docker Admin title: Group Mapping --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-group-mapping.md product="admin" layer="organization" %} +{{% admin-group-mapping product="admin" layer="organization" %}} \ No newline at end of file diff --git a/content/admin/organization/security-settings/scim.md b/content/admin/organization/security-settings/scim.md index 54530818d5..705811568b 100644 --- a/content/admin/organization/security-settings/scim.md +++ b/content/admin/organization/security-settings/scim.md @@ -4,7 +4,7 @@ keywords: SCIM, SSO title: SCIM --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Follow the steps on this page to manage SCIM for your organization. To manage SCIM for a company, see [SCIM for a company](/admin/company/settings/scim/). diff --git a/content/admin/organization/security-settings/sso-configuration.md b/content/admin/organization/security-settings/sso-configuration.md index 0173d3b156..bcd6b58bbc 100644 --- a/content/admin/organization/security-settings/sso-configuration.md +++ b/content/admin/organization/security-settings/sso-configuration.md @@ -4,7 +4,7 @@ keywords: configure, sso, docker admin title: Configure Single Sign-On for an organization --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Follow the steps on this page to configure SSO for your organization. To configure SSO for a company, see [Configure SSO for a company](/admin/company/settings/sso-configuration/). diff --git a/content/admin/organization/security-settings/sso-faq.md b/content/admin/organization/security-settings/sso-faq.md index 8943fa6f13..4a936db0e2 100644 --- a/content/admin/organization/security-settings/sso-faq.md +++ b/content/admin/organization/security-settings/sso-faq.md @@ -5,6 +5,6 @@ title: Single Sign-On FAQs toc_max: 2 --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-sso-faq.md %} \ No newline at end of file +{{< include "admin-sso-faq.md" >}} \ No newline at end of file diff --git a/content/admin/organization/security-settings/sso-management.md b/content/admin/organization/security-settings/sso-management.md index d1cc2dfc9c..d11503baaa 100644 --- a/content/admin/organization/security-settings/sso-management.md +++ b/content/admin/organization/security-settings/sso-management.md @@ -4,7 +4,7 @@ keywords: manage, single sign-on, SSO, sign-on title: Manage Single Sign-On for an organization --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} Follow the steps on this page to manage SSO for an organization. To manage SSO for a company, see [Manage SSO for a company](/admin/company/settings/sso-management/). diff --git a/content/admin/organization/security-settings/sso.md b/content/admin/organization/security-settings/sso.md index 7efbfc32fb..91899470e1 100644 --- a/content/admin/organization/security-settings/sso.md +++ b/content/admin/organization/security-settings/sso.md @@ -4,6 +4,6 @@ keywords: Single sign-on, SSO, sign-on title: Single Sign-On overview --- -{% include admin-early-access.md %} +{{< include "admin-early-access.md" >}} -{% include admin-sso.md product="admin" layer="organization" %} +{{% admin-sso product="admin" layer="organization" %}} \ No newline at end of file diff --git a/content/billing/_index.md b/content/billing/_index.md index 7211db39fb..1b48ca4d99 100644 --- a/content/billing/_index.md +++ b/content/billing/_index.md @@ -19,4 +19,4 @@ grid: Use the resources in this section to manage your billing and payment settings for your Pro, Team, or Business subscription. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/billing/cycle.md b/content/billing/cycle.md index 8d219bc799..52a455a8af 100644 --- a/content/billing/cycle.md +++ b/content/billing/cycle.md @@ -30,4 +30,4 @@ When you change the billing cycle's duration: 1. In Docker Hub, select **Organizations**. 2. Select the organization that you want to change the payment method for. 3. In the bottom-right of the **Plan** tab, select **Switch to annual billing**. -4. Review the information displayed on the **Change to an Annual subscription** page and select **Accept Terms and Purchase** to confirm. +4. Review the information displayed on the **Change to an Annual subscription** page and select **Accept Terms and Purchase** to confirm. \ No newline at end of file diff --git a/content/billing/details.md b/content/billing/details.md index 61622409c0..2e3095e7fc 100644 --- a/content/billing/details.md +++ b/content/billing/details.md @@ -26,4 +26,4 @@ The billing information provided appears on all your billing invoices. The email 2. Select the organization that you want to change the payment method for. 3. Select the **Billing** tab and then **Payment Methods**. 4. In the **Billing Information** section, enter your updated billing details. -5. Select **Update**. +5. Select **Update**. \ No newline at end of file diff --git a/content/billing/faqs.md b/content/billing/faqs.md index f82d2ab06f..2e349a1611 100644 --- a/content/billing/faqs.md +++ b/content/billing/faqs.md @@ -43,7 +43,7 @@ Docker Hub sends the following billing-related emails: ### Does Docker offer academic pricing? -Contact the [Docker Sales Team](https://www.docker.com/company/contact){:target="blank" rel="noopener" class=""}. +Contact the [Docker Sales Team](https://www.docker.com/company/contact). ### Do I need to do anything at the end of my subscription term? @@ -88,4 +88,4 @@ For organizations: 1. In Docker Hub, select **Organization**, your organization, and then **Billing**. 2. Select the **Payment Methods** tab, then update the email field in the **Billing Information** section. -3. Select **Update**. +3. Select **Update**. \ No newline at end of file diff --git a/content/billing/history.md b/content/billing/history.md index bb1f852a4f..874e7a0ce3 100644 --- a/content/billing/history.md +++ b/content/billing/history.md @@ -32,4 +32,4 @@ From here you can choose to: From here you can choose to: - Download an invoice. -- Update an invoice with recently [updated billing information](details.md) by selecting the menu icon and then **Update Invoice**. \ No newline at end of file +- Update an invoice with recently [updated billing information](details.md) by selecting the menu icon and then **Update Invoice**. \ No newline at end of file diff --git a/content/billing/payment-method.md b/content/billing/payment-method.md index 22d806f69c..e8fc11afdc 100644 --- a/content/billing/payment-method.md +++ b/content/billing/payment-method.md @@ -34,4 +34,4 @@ You can add a payment method or update your account's existing payment method at 4. In the **Payment Information** section, enter the new payment method. The screen refreshes and displays your new payment information alongside your existing information. 5. Select **Make Default** to ensure that your new payment method applies to all purchases and subscriptions. -6. Optional. Remove your existing payment method by selecting the **X** icon. +6. Optional. Remove your existing payment method by selecting the **X** icon. \ No newline at end of file diff --git a/content/billing/scout-billing.md b/content/billing/scout-billing.md index 34828442c1..fd076f6483 100644 --- a/content/billing/scout-billing.md +++ b/content/billing/scout-billing.md @@ -4,11 +4,11 @@ description: Learn how to buy Docker Scout and manage your subscription keywords: payments, billing, subscription, scout --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Docker Scout lets users secure their software supply chain and continuously observe and improve their security posture. Docker Scout is free for up to 3 repositories. You can buy Docker Scout Team or Docker Scout Business to turn on Docker Scout for additional repositories. See [Docker Scout subscription and features](../subscription/scout-details.md) to select the plan that works for you. -In this section, learn how to buy Docker Scout Team in Docker Hub for your personal account or for an organization. To buy Docker Scout Business, [contact sales](https://www.docker.com/products/docker-scout/){: target="_blank" rel="noopener" class="_"}. +In this section, learn how to buy Docker Scout Team in Docker Hub for your personal account or for an organization. To buy Docker Scout Business, [contact sales](https://www.docker.com/products/docker-scout/). ## Personal account @@ -36,7 +36,7 @@ Once your purchase is complete, you receive a confirmation email and a copy of y >**Note** > - > If you're an organization with multiple teams, a Docker Scout Business plan may be better. [Contact sales](https://www.docker.com/products/docker-scout/){: target="_blank" rel="noopener" class="_"} to learn more. + > If you're an organization with multiple teams, a Docker Scout Business plan may be better. [Contact sales](https://www.docker.com/products/docker-scout/) to learn more. 7. This redirects you to the payment processing page. Enter your email if this field isn't pre-populated. Then, enter your payment information. 8. Update the quantity of repositories you want to use with Docker Scout. See [Docker Scout subscriptions](../subscription/scout-details.md) to learn more about the number of repositories available for each plan. @@ -50,4 +50,4 @@ Once your purchase is complete, you receive a confirmation email and a copy of y To access your subscription details, go to the **Billing** section for your personal account or organization that's subscribed. In the **Docker Scout Team** section, select **Change plan**. Here you can find your renewal date, invoice history, or cancel your plan. -Renewals charge to the original credit card used to buy Docker Scout Team. +Renewals charge to the original credit card used to buy Docker Scout Team. \ No newline at end of file diff --git a/content/build/_index.md b/content/build/_index.md index 880ee2a5d0..1d9e9371e1 100644 --- a/content/build/_index.md +++ b/content/build/_index.md @@ -2,50 +2,45 @@ title: Overview of Docker Build description: Introduction and overview of Docker Build keywords: build, buildx, buildkit -redirect_from: - - /buildx/working-with-buildx/ - - /develop/develop-images/build_enhancements/ grid: - - title: "Packaging your software" - description: - "Build and package your application to run it anywhere: locally or in the - cloud." - icon: "inventory_2" - link: "/build/building/packaging" - - title: "Multi-stage builds" - description: "Keep your images small and secure with minimal dependencies." - icon: "stairs" - link: "/build/building/multi-stage" - - title: "Multi-platform images" - description: - "Build, push, pull, and run images seamlessly on different computer - architectures." - icon: "home_storage" - link: "/build/building/multi-platform/" - - title: "Architecture" - description: "Learn about the Docker Build components." - icon: "explore" - description: "Explore BuildKit, the open source build engine." - icon: "construction" - link: "/build/buildkit/" - - title: "Build drivers" - description: "Configure where and how you run your builds." - icon: "engineering" - link: "/build/drivers/" - - title: "Exporters" - description: "Export any artifact you like, not just Docker images." - icon: "output" - link: "/build/exporters" - - title: "Build caching" - description: - "Avoid unnecessary repetitions of costly operations, such as package - installs." - icon: "cycle" - link: "/build/cache" - - title: "Bake" - description: "Orchestrate your builds with Bake." - icon: "cake" - link: "/build/bake" +- title: Packaging your software + description: 'Build and package your application to run it anywhere: locally or + in the cloud.' + icon: inventory_2 + link: /build/building/packaging +- title: Multi-stage builds + description: Keep your images small and secure with minimal dependencies. + icon: stairs + link: /build/building/multi-stage +- title: Multi-platform images + description: Build, push, pull, and run images seamlessly on different computer + architectures. + icon: home_storage + link: /build/building/multi-platform/ +- title: Architecture + description: Explore BuildKit, the open source build engine. + icon: construction + link: /build/buildkit/ +- title: Build drivers + description: Configure where and how you run your builds. + icon: engineering + link: /build/drivers/ +- title: Exporters + description: Export any artifact you like, not just Docker images. + icon: output + link: /build/exporters +- title: Build caching + description: Avoid unnecessary repetitions of costly operations, such as package + installs. + icon: cycle + link: /build/cache +- title: Bake + description: Orchestrate your builds with Bake. + icon: cake + link: /build/bake +aliases: +- /buildx/working-with-buildx/ +- /develop/develop-images/build_enhancements/ --- Docker Build is one of Docker Engine's most used features. Whenever you are @@ -58,4 +53,4 @@ packaging your code. It's a whole ecosystem of tools and features that support not only common workflow tasks but also provides support for more complex and advanced scenarios. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/build/architecture.md b/content/build/architecture.md index 4ec77f0eff..fb11f527f9 100644 --- a/content/build/architecture.md +++ b/content/build/architecture.md @@ -2,8 +2,8 @@ title: Docker Build architecture description: Learn about Docker Build and its components. keywords: build, buildkit, buildx, architecture -redirect_from: - - /build/install-buildx/ +aliases: +- /build/install-buildx/ --- Docker Build implements a client-server architecture, where: @@ -37,7 +37,7 @@ package. Buildx is included in the Docker Engine installation instructions, see You can also build the CLI plugin from source, or grab a binary from the GitHub repository and install it manually. See -[docker/buildx README](https://github.com/docker/buildx#manual-download){: target="blank" rel="noopener"} +[docker/buildx README](https://github.com/docker/buildx#manual-download) for more information ## Builders @@ -90,4 +90,4 @@ For more information about BuildKit, see [BuildKit](buildkit/index.md). The following diagram shows an example build sequence involving Buildx and BuildKit. -![Buildx and BuildKit sequence diagram](./images/build-execution.png) +![Buildx and BuildKit sequence diagram](./images/build-execution.png) \ No newline at end of file diff --git a/content/build/attestations/_index.md b/content/build/attestations/_index.md index 0404e2d07b..595a39839b 100644 --- a/content/build/attestations/_index.md +++ b/content/build/attestations/_index.md @@ -1,9 +1,10 @@ --- title: Build attestations keywords: build, attestations, sbom, provenance -description: > - Introduction to SBOM and provenance attestations with Docker Build; what they - are and why they exist +description: 'Introduction to SBOM and provenance attestations with Docker Build; + what they are and why they exist + + ' --- {% include build-feature-state.md buildkit_v=">=0.11" buildx_v=">=0.10" %} @@ -66,9 +67,9 @@ index in a manifest for the final image. BuildKit produces attestations in the -[in-toto format](https://github.com/in-toto/attestation){: target="blank" rel="noopener" class="\_" }, +[in-toto format](https://github.com/in-toto/attestation), as defined by the -[in-toto framework](https://in-toto.io/){: target="blank" rel="noopener" class="\_" }, +[in-toto framework](https://in-toto.io/), a standard supported by the Linux Foundation. Attestations attach to images as a manifest in the image index. The data records @@ -155,4 +156,4 @@ To deep-dive into the specifics about how attestations are stored, see Learn more about the available attestation types and how to use them: - [Provenance](slsa-provenance.md) -- [SBOM](sbom.md) +- [SBOM](sbom.md) \ No newline at end of file diff --git a/content/build/attestations/sbom.md b/content/build/attestations/sbom.md index f28d3fa8fc..86990bd5bc 100644 --- a/content/build/attestations/sbom.md +++ b/content/build/attestations/sbom.md @@ -23,8 +23,7 @@ final image. The SBOMs generated by BuildKit follow the SPDX standard. SBOMs attach to the final image as a JSON-encoded SPDX document, using the format defined by the -[in-toto SPDX predicate](https://github.com/in-toto/attestation/blob/main/spec/predicates/spdx.md){: -target="blank" rel="noopener" }. +[in-toto SPDX predicate](https://github.com/in-toto/attestation/blob/main/spec/predicates/spdx.md). ## Create SBOM attestations @@ -138,7 +137,7 @@ Only stages that are built will be scanned. Stages that aren't dependencies of the target stage won't be built, or scanned. The following Dockerfile example uses multi-stage builds to build a static website with -[Hugo](https://gohugo.io/){: target="blank" rel="noopener" class="_"}. +[Hugo](https://gohugo.io/). ```dockerfile # syntax=docker/dockerfile:1 @@ -177,7 +176,7 @@ Using the `--format` option, you can specify a template for the output. All SBOM-related data is available under the `.SBOM` attribute. For example, to get the raw contents of an SBOM in SPDX format: -{% raw %} + ```console $ docker buildx imagetools inspect /: \ --format "{{ json .SBOM.SPDX }}" @@ -186,13 +185,13 @@ $ docker buildx imagetools inspect /: \ ... } ``` -{% endraw %} + You can also construct more complex expressions using the full functionality of Go templates. For example, you can list all the installed packages and their version identifiers: -{% raw %} + ```console $ docker buildx imagetools inspect /: \ --format "{{ range .SBOM.SPDX.packages }}{{ .name }}@{{ .versionInfo }}{{ println }}{{ end }}" @@ -202,19 +201,19 @@ base-files@11ubuntu5.6 base-passwd@3.5.47 ... ``` -{% endraw %} + ## SBOM generator BuildKit generates the SBOM using a scanner plugin. By default, it uses is the -[BuildKit Syft scanner](https://github.com/docker/buildkit-syft-scanner){: target="blank" rel="noopener" } +[BuildKit Syft scanner](https://github.com/docker/buildkit-syft-scanner) plugin. This plugin is built on top of -[Anchore's Syft](https://github.com/anchore/syft){: target="blank" rel="noopener" }, +[Anchore's Syft](https://github.com/anchore/syft), an open source tool for generating an SBOM. You can select a different plugin to use with the `generator` option, specifying an image that implements the -[BuildKit SBOM scanner protocol](https://github.com/moby/buildkit/blob/master/docs/attestations/sbom-protocol.md){: target="blank" rel="noopener" }. +[BuildKit SBOM scanner protocol](https://github.com/moby/buildkit/blob/master/docs/attestations/sbom-protocol.md). ```console $ docker buildx build --attest type=sbom,generator= . @@ -323,4 +322,4 @@ The following JSON example shows what an SBOM attestation might look like. "spdxVersion": "SPDX-2.2" } } -``` +``` \ No newline at end of file diff --git a/content/build/attestations/slsa-provenance.md b/content/build/attestations/slsa-provenance.md index ea76c2f4fe..f46e413a32 100644 --- a/content/build/attestations/slsa-provenance.md +++ b/content/build/attestations/slsa-provenance.md @@ -151,7 +151,7 @@ Using the `--format` option, you can specify a template for the output. All provenance-related data is available under the `.Provenance` attribute. For example, to get the raw contents of the Provenance in the SLSA format: -{% raw %} + ```console $ docker buildx imagetools inspect /: \ --format "{{ json .Provenance.SLSA }}" @@ -160,13 +160,13 @@ $ docker buildx imagetools inspect /: \ ... } ``` -{% endraw %} + You can also construct more complex expressions using the full functionality of Go templates. For example, for provenance generated with `mode=max`, you can extract the full source code of the Dockerfile used to build the image: -{% raw %} + ```console $ docker buildx imagetools inspect /: \ --format '{{ range (index .Provenance.SLSA.metadata "https://mobyproject.org/buildkit@v1#metadata").source.infos }}{{ if eq .filename "Dockerfile" }}{{ .data }}{{ end }}{{ end }}' | base64 -d @@ -174,7 +174,7 @@ FROM ubuntu:20.04 RUN apt-get update ... ``` -{% endraw %} + ## Provenance attestation example @@ -349,4 +349,4 @@ attestation with `mode=max` looks like: } } } -``` +``` \ No newline at end of file diff --git a/content/build/bake/_index.md b/content/build/bake/_index.md index 1e0011d6f7..da4e56bb8b 100644 --- a/content/build/bake/_index.md +++ b/content/build/bake/_index.md @@ -1,21 +1,21 @@ --- title: High-level builds with Bake keywords: build, buildx, bake, buildkit, hcl, json, compose -redirect_from: +aliases: - /build/customize/bake/ --- > This command is experimental. > -> The design of bake is in early stages, and we are looking for [feedback from users](https://github.com/docker/buildx/issues){:target="blank" rel="noopener" class=""}. -{: .experimental } +> The design of bake is in early stages, and we are looking for [feedback from users](https://github.com/docker/buildx/issues). +{ .experimental } Buildx also aims to provide support for high-level build concepts that go beyond invoking a single build command. We want to support building all the images in your application together and let the users define project specific reusable build flows that can then be easily invoked by anyone. -[BuildKit](https://github.com/moby/buildkit){:target="blank" rel="noopener" class=""} +[BuildKit](https://github.com/moby/buildkit) efficiently handles multiple concurrent build requests and de-duplicating work. The build commands can be combined with general-purpose command runners (for example, `make`). However, these tools generally invoke builds in sequence @@ -38,4 +38,4 @@ and also allows better code reuse, different target groups and extended features * [Configuring builds](configuring-build.md) * [User defined HCL functions](hcl-funcs.md) * [Defining additional build contexts and linking targets](build-contexts.md) -* [Building from Compose file](compose-file.md) +* [Building from Compose file](compose-file.md) \ No newline at end of file diff --git a/content/build/bake/build-contexts.md b/content/build/bake/build-contexts.md index 10b2a5ef07..e6a8aaf895 100644 --- a/content/build/bake/build-contexts.md +++ b/content/build/bake/build-contexts.md @@ -1,7 +1,7 @@ --- -title: "Defining additional build contexts and linking targets" +title: Defining additional build contexts and linking targets keywords: build, buildx, bake, buildkit, hcl -redirect_from: +aliases: - /build/customize/bake/build-contexts/ --- @@ -76,4 +76,4 @@ target "app" { Please note that in most cases you should just use a single multi-stage Dockerfile with multiple targets for similar behavior. This case is recommended -when you have multiple Dockerfiles that can't be easily merged into one. +when you have multiple Dockerfiles that can't be easily merged into one. \ No newline at end of file diff --git a/content/build/bake/compose-file.md b/content/build/bake/compose-file.md index 03b915e122..5e92a03f4d 100644 --- a/content/build/bake/compose-file.md +++ b/content/build/bake/compose-file.md @@ -1,7 +1,7 @@ --- -title: "Building from Compose file" +title: Building from Compose file keywords: build, buildx, bake, buildkit, compose -redirect_from: +aliases: - /build/customize/bake/compose-file/ --- @@ -97,7 +97,7 @@ $ docker buildx bake --print The compose format has some limitations compared to the HCL format: * Specifying variables or global scope attributes is not yet supported -* `inherits` service field is not supported, but you can use [YAML anchors](../../compose/compose-file/10-fragments.md){:target="blank" rel="noopener" class=""} +* `inherits` service field is not supported, but you can use [YAML anchors](../../compose/compose-file/10-fragments.md) to reference other services like the example above ## `.env` file @@ -275,4 +275,4 @@ Complete list of valid fields for `x-bake`: * `pull` * `secret` * `ssh` -* `tags` +* `tags` \ No newline at end of file diff --git a/content/build/bake/configuring-build.md b/content/build/bake/configuring-build.md index ced5ee3597..be38abf77d 100644 --- a/content/build/bake/configuring-build.md +++ b/content/build/bake/configuring-build.md @@ -1,7 +1,7 @@ --- -title: "Configuring builds" +title: Configuring builds keywords: build, buildx, bake, buildkit, hcl, json -redirect_from: +aliases: - /build/customize/bake/configuring-build/ --- @@ -189,7 +189,7 @@ $ docker buildx bake --set app.args.mybuildarg=bar --set app.platform=linux/arm6 } ``` -Pattern matching syntax defined in [https://golang.org/pkg/path/#Match](https://golang.org/pkg/path/#Match){:target="blank" rel="noopener" class=""} +Pattern matching syntax defined in [https://golang.org/pkg/path/#Match](https://golang.org/pkg/path/#Match) is also supported: ```console @@ -274,4 +274,4 @@ $ docker buildx bake -f docker-bake1.hcl -f docker-bake2.hcl --print app } } } -``` +``` \ No newline at end of file diff --git a/content/build/bake/hcl-funcs.md b/content/build/bake/hcl-funcs.md index 1822481453..9f671e7a98 100644 --- a/content/build/bake/hcl-funcs.md +++ b/content/build/bake/hcl-funcs.md @@ -1,7 +1,7 @@ --- -title: "User defined HCL functions" +title: User defined HCL functions keywords: build, buildx, bake, buildkit, hcl -redirect_from: +aliases: - /build/customize/bake/hcl-funcs/ --- @@ -100,7 +100,7 @@ $ TAG=$(git rev-parse --short HEAD) docker buildx bake --print webapp ## Using the `add` function -You can use [`go-cty` stdlib functions](https://github.com/zclconf/go-cty/tree/main/cty/function/stdlib){:target="blank" rel="noopener" class=""}. +You can use [`go-cty` stdlib functions](https://github.com/zclconf/go-cty/tree/main/cty/function/stdlib). Here we are using the `add` function. ```hcl @@ -147,7 +147,7 @@ $ docker buildx bake --print webapp ## Defining an `increment` function -It also supports [user defined functions](https://github.com/hashicorp/hcl/tree/main/ext/userfunc){:target="blank" rel="noopener" class=""}. +It also supports [user defined functions](https://github.com/hashicorp/hcl/tree/main/ext/userfunc). The following example defines a simple an `increment` function. ```hcl @@ -336,4 +336,4 @@ $ docker buildx bake --print app } } } -``` +``` \ No newline at end of file diff --git a/content/build/bake/remote-definition.md b/content/build/bake/remote-definition.md index 6cd5be926f..c35dccf962 100644 --- a/content/build/bake/remote-definition.md +++ b/content/build/bake/remote-definition.md @@ -45,7 +45,7 @@ $ docker buildx bake "https://github.com/docker/cli.git#v20.10.11" --print ``` As you can see the context is fixed to `https://github.com/docker/cli.git` even if -[no context is actually defined](https://github.com/docker/cli/blob/2776a6d694f988c0c1df61cad4bfac0f54e481c8/docker-bake.hcl#L17-L26){:target="blank" rel="noopener" class=""} +[no context is actually defined](https://github.com/docker/cli/blob/2776a6d694f988c0c1df61cad4bfac0f54e481c8/docker-bake.hcl#L17-L26) in the definition. If you want to access the main context for bake command from a bake file @@ -133,4 +133,4 @@ $ docker buildx bake "https://github.com/tonistiigi/buildx.git#remote-test" "htt #8 0.136 drwxrwxrwx 10 root root 4096 Jul 27 18:31 vendor #8 0.136 -rwxrwxrwx 1 root root 9620 Jul 27 18:31 vendor.conf #8 0.136 /bin/sh: stop: not found -``` +``` \ No newline at end of file diff --git a/content/build/builders/_index.md b/content/build/builders/_index.md index e3de06960d..10c2163f7b 100644 --- a/content/build/builders/_index.md +++ b/content/build/builders/_index.md @@ -1,7 +1,7 @@ --- -title: "Builders" +title: Builders keywords: build, buildx, builders, buildkit, drivers, backend -description: +description: null --- A builder is a BuildKit daemon that you can use to run your builds. BuildKit @@ -16,7 +16,7 @@ running remotely. You interact with builders using the Docker CLI. > The [Docker Desktop Builds view](../../desktop/use-desktop/builds.md) > is a [Beta](../../release-lifecycle.md#beta) feature that lets you > view and manage builders using Docker Desktop. -{: .experimental } +{ .experimental } ## Default builder @@ -76,4 +76,4 @@ selected when you invoke builds. - For information about how to interact with and manage builders, see [Manage builders](./manage.md) - To learn about different types of builders, - see [Build drivers](../drivers/index.md) + see [Build drivers](../drivers/index.md) \ No newline at end of file diff --git a/content/build/builders/manage.md b/content/build/builders/manage.md index 00ee48b995..dece019f8a 100644 --- a/content/build/builders/manage.md +++ b/content/build/builders/manage.md @@ -1,7 +1,7 @@ --- -title: "Manage builders" +title: Manage builders keywords: build, buildx, builders, buildkit, drivers, backend -description: +description: null --- You can create, inspect, and manage builders using `docker buildx` commands, @@ -105,4 +105,4 @@ you can inspect builders in Docker Desktop settings. See: - [Change settings, Windows](../../desktop/settings/windows.md#builders) - [Change settings, Mac](../../desktop/settings/mac.md#builders) -- [Change settings, Linux](../../desktop/settings/linux.md#builders) +- [Change settings, Linux](../../desktop/settings/linux.md#builders) \ No newline at end of file diff --git a/content/build/building/base-images.md b/content/build/building/base-images.md index 3bf58dfe93..4bfb6b783d 100644 --- a/content/build/building/base-images.md +++ b/content/build/building/base-images.md @@ -2,7 +2,7 @@ title: Create a base image description: How to create base images keywords: images, base image, examples -redirect_from: +aliases: - /articles/baseimages/ - /engine/articles/baseimages/ - /engine/userguide/eng-image/baseimages/ @@ -30,7 +30,7 @@ ones. In general, start with a working machine that is running the distribution you'd like to package as a parent image, though that is -not required for some tools like Debian's [Debootstrap](https://wiki.debian.org/Debootstrap){:target="blank" rel="noopener" class=""}, +not required for some tools like Debian's [Debootstrap](https://wiki.debian.org/Debootstrap), which you can also use to build Ubuntu images. It can be as simple as this to create an Ubuntu parent image: @@ -48,7 +48,7 @@ It can be as simple as this to create an Ubuntu parent image: DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" There are more example scripts for creating parent images in -[the Docker GitHub repository](https://github.com/docker/docker/blob/master/contrib){:target="blank" rel="noopener" class=""}. +[the Docker GitHub repository](https://github.com/docker/docker/blob/master/contrib). ## Create a simple parent image using scratch @@ -70,7 +70,7 @@ CMD ["/hello"] ``` Assuming you built the "hello" executable example by using the source code at -[https://github.com/docker-library/hello-world](https://github.com/docker-library/hello-world){:target="blank" rel="noopener" class=""}, +[https://github.com/docker-library/hello-world](https://github.com/docker-library/hello-world), and you compiled it with the `-static` flag, you can build this Docker image using this `docker build` command: @@ -100,7 +100,7 @@ $ docker run --rm hello ``` This example creates the hello-world image used in the tutorials. -If you want to test it out, you can clone [the image repo](https://github.com/docker-library/hello-world){:target="blank" rel="noopener" class=""}. +If you want to test it out, you can clone [the image repo](https://github.com/docker-library/hello-world). ## More resources @@ -109,4 +109,4 @@ There are lots of resources available to help you write your `Dockerfile`. * There's a [complete guide to all the instructions](../../engine/reference/builder.md) available for use in a `Dockerfile` in the reference section. * To help you write a clear, readable, maintainable `Dockerfile`, we've also written a [Dockerfile best practices guide](../../develop/develop-images/dockerfile_best-practices.md). -* If your goal is to create a new Docker Official Image, read [Docker Official Images](../../docker-hub/official_images.md). +* If your goal is to create a new Docker Official Image, read [Docker Official Images](../../docker-hub/official_images.md). \ No newline at end of file diff --git a/content/build/building/context.md b/content/build/building/context.md index 23b74c2853..a710e3c3f3 100644 --- a/content/build/building/context.md +++ b/content/build/building/context.md @@ -356,7 +356,7 @@ ERROR: failed to solve: failed to compute cache key: failed to calculate checksu The following example builds an image using a `Dockerfile` that is passed through standard input using -[shell heredocs](https://en.wikipedia.org/wiki/Here_document){: target="_blank" rel="noopener"}: +[shell heredocs](https://en.wikipedia.org/wiki/Here_document): ```bash docker build -t myimage:latest - < We recommend using `docker/dockerfile:1`, which always points to the latest > release of the version 1 syntax. BuildKit automatically checks for updates of > the syntax before building, making sure you are using the most current version. -{: .tip } +{ .tip } ### Base image @@ -273,4 +273,4 @@ If you are interested in examples in other languages, such as Go, check out our [language-specific guides](../../language/index.md) in the Guides section. For more information about building, including advanced use cases and patterns, -refer to the [Build with Docker](../guide/index.md) guide. +refer to the [Build with Docker](../guide/index.md) guide. \ No newline at end of file diff --git a/content/build/buildkit/_index.md b/content/build/buildkit/_index.md index 9d484c72a6..c70f709597 100644 --- a/content/build/buildkit/_index.md +++ b/content/build/buildkit/_index.md @@ -6,7 +6,7 @@ keywords: build, buildkit ## Overview -[BuildKit](https://github.com/moby/buildkit){:target="blank" rel="noopener" class=""} +[BuildKit](https://github.com/moby/buildkit) is an improved backend to replace the legacy builder. BuildKit is the default builder for users on Docker Desktop, and Docker Engine as of version 23.0. @@ -36,8 +36,7 @@ files to be read or uploaded before the work can begin. ## LLB At the core of BuildKit is a -[Low-Level Build (LLB)](https://github.com/moby/buildkit#exploring-llb){:target="blank" -rel="noopener" class=""} definition format. LLB is an intermediate binary format +[Low-Level Build (LLB)](https://github.com/moby/buildkit#exploring-llb) definition format. LLB is an intermediate binary format that allows developers to extend BuildKit. LLB defines a content-addressable dependency graph that can be used to put together very complex build definitions. It also supports features not exposed in Dockerfiles, like direct @@ -54,8 +53,7 @@ more precise, and portable. The build cache can even be exported to a registry, where it can be pulled on-demand by subsequent invocations on any host. LLB can be generated directly using a -[golang client package](https://pkg.go.dev/github.com/moby/buildkit/client/llb){:target="blank" -rel="noopener" class=""} that allows defining the relationships between your +[golang client package](https://pkg.go.dev/github.com/moby/buildkit/client/llb) that allows defining the relationships between your build operations using Go language primitives. This gives you full power to run anything you can imagine, but will probably not be how most people will define their builds. Instead, most users would use a frontend component, or LLB nested @@ -112,5 +110,5 @@ daemon. > > BuildKit only supports building Linux containers. Windows support is tracked > in -> [`moby/buildkit#616`](https://github.com/moby/buildkit/issues/616){:target="blank" rel="noopener" class=""} -{: .warning} +> [`moby/buildkit#616`](https://github.com/moby/buildkit/issues/616) +{ .warning } \ No newline at end of file diff --git a/content/build/buildkit/configure.md b/content/build/buildkit/configure.md index 99d1e24d4f..98532a2ead 100644 --- a/content/build/buildkit/configure.md +++ b/content/build/buildkit/configure.md @@ -136,19 +136,19 @@ $ docker buildx build --push --tag myregistry.com/myimage:latest . ## CNI networking CNI networking for builders can be useful for dealing with network port -contention during concurrent builds. CNI is [not yet](https://github.com/moby/buildkit/issues/28){:target="blank" rel="noopener" class=""} +contention during concurrent builds. CNI is [not yet](https://github.com/moby/buildkit/issues/28) available in the default BuildKit image. But you can create your own image that includes CNI support. The following Dockerfile example shows a custom BuildKit image with CNI support. -It uses the [CNI config for integration tests](https://github.com/moby/buildkit/blob/master//hack/fixtures/cni.json){:target="blank" rel="noopener" class=""} +It uses the [CNI config for integration tests](https://github.com/moby/buildkit/blob/master//hack/fixtures/cni.json) in BuildKit as an example. Feel free to include your own CNI configuration. -{% raw %} + ```dockerfile # syntax=docker/dockerfile:1 -ARG BUILDKIT_VERSION=v{{ site.buildkit_version }} +ARG BUILDKIT_VERSION=v{{% param "buildkit_version" %}} ARG CNI_VERSION=v1.0.1 FROM --platform=$BUILDPLATFORM alpine AS cni-plugins @@ -165,7 +165,7 @@ RUN apk add --no-cache iptables COPY --from=cni-plugins /opt/cni/bin /opt/cni/bin ADD https://raw.githubusercontent.com/moby/buildkit/${BUILDKIT_VERSION}/hack/fixtures/cni.json /etc/buildkit/cni.json ``` -{% endraw %} + Now you can build this image, and create a builder instance from it using [the `--driver-opt image` option](../../engine/reference/commandline/buildx_create.md#driver-opt): @@ -211,4 +211,4 @@ requests. This connection limit prevents your build from getting stuck while pulling images. The dedicated metadata connection helps reduce the overall build time. -More information: [moby/buildkit#2259](https://github.com/moby/buildkit/pull/2259){:target="blank" rel="noopener" class=""} +More information: [moby/buildkit#2259](https://github.com/moby/buildkit/pull/2259) \ No newline at end of file diff --git a/content/build/cache/_index.md b/content/build/cache/_index.md index 4fe1cb80e7..9c29e15a57 100644 --- a/content/build/cache/_index.md +++ b/content/build/cache/_index.md @@ -1,11 +1,12 @@ --- title: Optimizing builds with cache management description: Improve your build speeds by taking advantage of the builtin cache -keywords: > - build, buildx, buildkit, dockerfile, image layers, build instructions, build - context -redirect_from: - - /build/building/cache/ +keywords: 'build, buildx, buildkit, dockerfile, image layers, build instructions, + build context + + ' +aliases: +- /build/building/cache/ --- You will likely find yourself rebuilding the same Docker image over and over @@ -37,7 +38,7 @@ Each instruction in this Dockerfile translates (roughly) to a layer in your final image. You can think of image layers as a stack, with each layer adding more content on top of the layers that came before it: -![Image layer diagram](../images/cache-stack.png){:.invertible} +![Image layer diagram](../images/cache-stack.png) Whenever a layer changes, that layer will need to be re-built. For example, suppose you make a change to your program in the `main.c` file. After this @@ -49,7 +50,7 @@ If a layer changes, all other layers that come after it are also affected. When the layer with the `COPY` command gets invalidated, all layers that follow will need to run again, too: -![Image layer diagram, showing cache invalidation](../images/cache-stack-invalidated.png){:.invertible} +![Image layer diagram, showing cache invalidation](../images/cache-stack-invalidated.png) And that's the Docker build cache in a nutshell. Once a layer changes, then all downstream layers need to be rebuilt as well. Even if they wouldn't build @@ -199,12 +200,12 @@ layers to a minimum. #### Use an appropriate base image -Docker provides over 170 pre-built [official images](https://hub.docker.com/search?q=&image_filter=official){:target="blank" rel="noopener" class=""} +Docker provides over 170 pre-built [official images](https://hub.docker.com/search?q=&image_filter=official) for almost every common development scenario. For example, if you're building a -Java web server, use a dedicated image such as [`eclipse-temurin`](https://hub.docker.com/_/eclipse-temurin/){:target="blank" rel="noopener" class=""}. +Java web server, use a dedicated image such as [`eclipse-temurin`](https://hub.docker.com/_/eclipse-temurin/). Even when there's not an official image for what you might want, Docker provides -images from [verified publishers](https://hub.docker.com/search?q=&image_filter=store){:target="blank" rel="noopener" class=""} -and [open source partners](https://hub.docker.com/search?q=&image_filter=open_source){:target="blank" rel="noopener" class=""} +images from [verified publishers](https://hub.docker.com/search?q=&image_filter=store) +and [open source partners](https://hub.docker.com/search?q=&image_filter=open_source) that can help you on your way. The Docker community often produces third-party images to use as well. @@ -273,7 +274,7 @@ RUN echo "the first command" && \ ``` Another shell feature that allows you to simplify and concatenate commands in a -neat way are [`heredocs`](https://en.wikipedia.org/wiki/Here_document){:target="blank" rel="noopener" class=""}. +neat way are [`heredocs`](https://en.wikipedia.org/wiki/Here_document). It enables you to create multi-line scripts with good readability: ```dockerfile @@ -292,4 +293,4 @@ of continuing.) For more information on using cache to do efficient builds, see: - [Garbage collection](garbage-collection.md) -- [Cache storage backends](./backends/index.md) +- [Cache storage backends](./backends/index.md) \ No newline at end of file diff --git a/content/build/cache/backends/_index.md b/content/build/cache/backends/_index.md index cf7f727d2f..d5303315a2 100644 --- a/content/build/cache/backends/_index.md +++ b/content/build/cache/backends/_index.md @@ -1,8 +1,8 @@ --- -title: "Cache storage backends" +title: Cache storage backends keywords: build, buildx, cache, backend, gha, azblob, s3, registry, local -redirect_from: - - /build/building/cache/backends/ +aliases: +- /build/building/cache/backends/ --- To ensure fast builds, BuildKit automatically caches the build result in its own @@ -40,13 +40,13 @@ Buildx supports the following cache storage backends: - `local`: writes the build cache to a local directory on the filesystem. - `gha`: uploads the build cache to - [GitHub Actions cache](https://docs.github.com/en/rest/actions/cache){:target="blank" rel="noopener" class=""} (beta). + [GitHub Actions cache](https://docs.github.com/en/rest/actions/cache) (beta). - `s3`: uploads the build cache to an - [AWS S3 bucket](https://aws.amazon.com/s3/){:target="blank" rel="noopener" class=""} (unreleased). + [AWS S3 bucket](https://aws.amazon.com/s3/) (unreleased). - `azblob`: uploads the build cache to - [Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/blobs/){:target="blank" rel="noopener" class=""} + [Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/blobs/) (unreleased). ## Command syntax @@ -78,7 +78,7 @@ $ docker buildx build --push -t / \ ## Multiple caches BuildKit currently only supports -[a single cache exporter](https://github.com/moby/buildkit/pull/3024){:target="blank" rel="noopener" class=""}. But you +[a single cache exporter](https://github.com/moby/buildkit/pull/3024). But you can import from as many remote caches as you like. For example, a common pattern is to use the cache of both the current branch and the main branch. The following example shows importing cache from multiple locations using the @@ -162,4 +162,4 @@ $ docker buildx build --push -t / \ ``` This property is only meaningful with the `--cache-to` flag. When fetching -cache, BuildKit will auto-detect the correct media types to use. +cache, BuildKit will auto-detect the correct media types to use. \ No newline at end of file diff --git a/content/build/cache/backends/azblob.md b/content/build/cache/backends/azblob.md index f80a69bf27..3f77f0feb1 100644 --- a/content/build/cache/backends/azblob.md +++ b/content/build/cache/backends/azblob.md @@ -1,8 +1,8 @@ --- -title: "Azure Blob Storage cache" +title: Azure Blob Storage cache keywords: build, buildx, cache, backend, azblob, azure -redirect_from: - - /build/building/cache/backends/azblob/ +aliases: +- /build/building/cache/backends/azblob/ --- > **Warning** @@ -11,7 +11,7 @@ redirect_from: > `moby/buildkit:master` image in your Buildx driver. The `azblob` cache store uploads your resulting build cache to -[Azure's blob storage service](https://azure.microsoft.com/en-us/services/storage/blobs/){:target="blank" rel="noopener" class=""}. +[Azure's blob storage service](https://azure.microsoft.com/en-us/services/storage/blobs/). > **Note** > @@ -50,7 +50,7 @@ The following table describes the available CSV parameters that you can pass to The `secret_access_key`, if left unspecified, is read from environment variables on the BuildKit server following the scheme for the -[Azure Go SDK](https://docs.microsoft.com/en-us/azure/developer/go/azure-sdk-authentication){:target="blank" rel="noopener" class=""}. +[Azure Go SDK](https://docs.microsoft.com/en-us/azure/developer/go/azure-sdk-authentication). The environment variables are read from the server, not the Buildx client. ## Further reading @@ -58,4 +58,4 @@ The environment variables are read from the server, not the Buildx client. For an introduction to caching see [Optimizing builds with cache](../index.md). For more information on the `azblob` cache backend, see the -[BuildKit README](https://github.com/moby/buildkit#azure-blob-storage-cache-experimental){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit#azure-blob-storage-cache-experimental). \ No newline at end of file diff --git a/content/build/cache/backends/gha.md b/content/build/cache/backends/gha.md index 9cdc377450..481fe3217b 100644 --- a/content/build/cache/backends/gha.md +++ b/content/build/cache/backends/gha.md @@ -1,8 +1,8 @@ --- -title: "GitHub Actions cache" +title: GitHub Actions cache keywords: build, buildx, cache, backend, gha, github, actions -redirect_from: - - /build/building/cache/backends/gha/ +aliases: +- /build/building/cache/backends/gha/ --- > **Warning** @@ -12,10 +12,10 @@ redirect_from: > unstable and may change in future releases. The GitHub Actions cache utilizes the -[GitHub-provided Action's cache](https://github.com/actions/cache){:target="blank" rel="noopener" class=""} available +[GitHub-provided Action's cache](https://github.com/actions/cache) available from within your CI execution environment. This is the recommended cache to use inside your GitHub action pipelines, as long as your use case falls within the -[size and usage limits set by GitHub](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy){:target="blank" rel="noopener" class=""}. +[size and usage limits set by GitHub](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy). > **Note** > @@ -57,7 +57,7 @@ If the `url` or `token` parameters are left unspecified, the `gha` cache backend will fall back to using environment variables. If you invoke the `docker buildx` command manually from an inline step, then the variables must be manually exposed (using -[`crazy-max/ghaction-github-runtime`](https://github.com/crazy-max/ghaction-github-runtime){:target="blank" rel="noopener" class=""}, +[`crazy-max/ghaction-github-runtime`](https://github.com/crazy-max/ghaction-github-runtime), for example). ## Scope @@ -81,14 +81,14 @@ $ docker buildx build --push -t / \ --cache-from type=gha,url=...,token=...,scope=$GITHUB_REF_NAME-image2 . ``` -GitHub's [cache access restrictions](https://docs.github.com/en/actions/advanced-guides/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache){:target="blank" rel="noopener" class=""}, +GitHub's [cache access restrictions](https://docs.github.com/en/actions/advanced-guides/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache), still apply. Only the cache for the current branch, the base branch and the default branch is accessible by a workflow. ### Using `docker/build-push-action` When using the -[`docker/build-push-action`](https://github.com/docker/build-push-action){:target="blank" rel="noopener" class=""}, the +[`docker/build-push-action`](https://github.com/docker/build-push-action), the `url` and `token` parameters are automatically populated. No need to manually specify them, or include any additional workarounds. @@ -110,7 +110,7 @@ For example: For an introduction to caching see [Optimizing builds with cache](../index.md). For more information on the `gha` cache backend, see the -[BuildKit README](https://github.com/moby/buildkit#github-actions-cache-experimental){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit#github-actions-cache-experimental). For more information about using GitHub Actions with Docker, see -[Introduction to GitHub Actions](../../ci/github-actions/index.md) +[Introduction to GitHub Actions](../../ci/github-actions/index.md) \ No newline at end of file diff --git a/content/build/cache/backends/inline.md b/content/build/cache/backends/inline.md index 99c766879a..0a55243c21 100644 --- a/content/build/cache/backends/inline.md +++ b/content/build/cache/backends/inline.md @@ -1,8 +1,8 @@ --- -title: "Inline cache" +title: Inline cache keywords: build, buildx, cache, backend, inline -redirect_from: - - /build/building/cache/backends/inline/ +aliases: +- /build/building/cache/backends/inline/ --- The `inline` cache storage backend is the simplest way to get an external cache @@ -56,4 +56,4 @@ $ docker buildx build --push -t / \ For an introduction to caching see [Optimizing builds with cache](../index.md). For more information on the `inline` cache backend, see the -[BuildKit README](https://github.com/moby/buildkit#inline-push-image-and-cache-together){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit#inline-push-image-and-cache-together). \ No newline at end of file diff --git a/content/build/cache/backends/local.md b/content/build/cache/backends/local.md index 1690b606aa..278a20e029 100644 --- a/content/build/cache/backends/local.md +++ b/content/build/cache/backends/local.md @@ -1,13 +1,13 @@ --- -title: "Local cache" +title: Local cache keywords: build, buildx, cache, backend, local -redirect_from: - - /build/building/cache/backends/local/ +aliases: +- /build/building/cache/backends/local/ --- The `local` cache store is a simple cache option that stores your cache as files in a directory on your filesystem, using an -[OCI image layout](https://github.com/opencontainers/image-spec/blob/main/image-layout.md){:target="blank" rel="noopener" class=""} +[OCI image layout](https://github.com/opencontainers/image-spec/blob/main/image-layout.md) for the underlying directory structure. Local cache is a good choice if you're just testing, or if you want the flexibility to self-manage a shared storage solution. @@ -76,7 +76,7 @@ Like other cache types, local cache gets replaced on export, by replacing the contents of the `index.json` file. However, previous caches will still be available in the `blobs` directory. These old caches are addressable by digest, and kept indefinitely. Therefore, the size of the local cache will continue to -grow (see [`moby/buildkit#1896`](https://github.com/moby/buildkit/issues/1896){:target="blank" rel="noopener" class=""} +grow (see [`moby/buildkit#1896`](https://github.com/moby/buildkit/issues/1896) for more information). When importing cache using `--cache-to`, you can specify the `digest` parameter @@ -93,4 +93,4 @@ $ docker buildx build --push -t / \ For an introduction to caching see [Optimizing builds with cache](../index.md). For more information on the `local` cache backend, see the -[BuildKit README](https://github.com/moby/buildkit#local-directory-1){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit#local-directory-1). \ No newline at end of file diff --git a/content/build/cache/backends/registry.md b/content/build/cache/backends/registry.md index ff9e006383..93f2943e9e 100644 --- a/content/build/cache/backends/registry.md +++ b/content/build/cache/backends/registry.md @@ -1,8 +1,8 @@ --- -title: "Registry cache" +title: Registry cache keywords: build, buildx, cache, backend, registry -redirect_from: - - /build/building/cache/backends/registry/ +aliases: +- /build/building/cache/backends/registry/ --- The `registry` cache storage can be thought of as an extension to the `inline` @@ -72,4 +72,4 @@ fail, but the build will continue. For an introduction to caching see [Optimizing builds with cache](../index.md). For more information on the `registry` cache backend, see the -[BuildKit README](https://github.com/moby/buildkit#registry-push-image-and-cache-separately){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit#registry-push-image-and-cache-separately). \ No newline at end of file diff --git a/content/build/cache/backends/s3.md b/content/build/cache/backends/s3.md index 5d6ba4ae93..a647ba8fe7 100644 --- a/content/build/cache/backends/s3.md +++ b/content/build/cache/backends/s3.md @@ -1,8 +1,8 @@ --- -title: "Amazon S3 cache" +title: Amazon S3 cache keywords: build, buildx, cache, backend, s3 -redirect_from: - - /build/building/cache/backends/s3/ +aliases: +- /build/building/cache/backends/s3/ --- > **Warning** @@ -11,7 +11,7 @@ redirect_from: > `moby/buildkit:master` image in your Buildx driver. The `s3` cache storage uploads your resulting build cache to -[Amazon S3 file storage service](https://aws.amazon.com/s3/){:target="blank" rel="noopener" class=""}, +[Amazon S3 file storage service](https://aws.amazon.com/s3/), into a specified bucket. > **Note** @@ -54,7 +54,7 @@ The following table describes the available CSV parameters that you can pass to `access_key_id`, `secret_access_key`, and `session_token`, if left unspecified, are read from environment variables on the BuildKit server following the scheme -for the [AWS Go SDK](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html){:target="blank" rel="noopener" class=""}. +for the [AWS Go SDK](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html). The environment variables are read from the server, not the Buildx client. @@ -64,4 +64,4 @@ The environment variables are read from the server, not the Buildx client. For an introduction to caching see [Optimizing builds with cache](../index.md). For more information on the `s3` cache backend, see the -[BuildKit README](https://github.com/moby/buildkit#s3-cache-experimental){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit#s3-cache-experimental). \ No newline at end of file diff --git a/content/build/cache/garbage-collection.md b/content/build/cache/garbage-collection.md index 9ce560209a..8f24516006 100644 --- a/content/build/cache/garbage-collection.md +++ b/content/build/cache/garbage-collection.md @@ -1,8 +1,8 @@ --- title: Garbage collection keywords: build, buildx, buildkit, garbage collection, prune -redirect_from: - - /build/building/cache/garbage-collection/ +aliases: +- /build/building/cache/garbage-collection/ --- While [`docker builder prune`](../../engine/reference/commandline/builder_prune.md) @@ -89,4 +89,4 @@ GC Policy rule#3: > **Note** > > "Keep bytes" defaults to 10% of the size of the disk. If the disk size cannot -> be determined, it defaults to 2GB. +> be determined, it defaults to 2GB. \ No newline at end of file diff --git a/content/build/ci/_index.md b/content/build/ci/_index.md index bf2f3ffea5..84e6a736c0 100644 --- a/content/build/ci/_index.md +++ b/content/build/ci/_index.md @@ -1,9 +1,9 @@ --- description: Overview of using Docker for continuous integration keywords: ci, build -redirect_from: - - /ci-cd/best-practices/ title: Continuous integration with Docker +aliases: +- /ci-cd/best-practices/ --- Continuous Integration (CI) is the part of the development process where you're @@ -11,7 +11,7 @@ looking to get your code changes merged with the main branch of the project. At this point, development teams run tests and builds to vet that the code changes don't cause any unwanted or unexpected behaviors. -![Git branches about to get merged](./images/continuous-integration.svg){: .invertible } +![Git branches about to get merged](./images/continuous-integration.svg) There are several uses for Docker at this stage of development, even if you don't end up packaging your application as a container image. @@ -36,10 +36,10 @@ image, just like you would for any other containerized application. The following links provide instructions for how you can get started using Docker for building your applications in CI: -- [GitHub Actions](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action){:target="blank" rel="noopener" class=""} -- [GitLab](https://docs.gitlab.com/runner/executors/docker.html){:target="blank" rel="noopener" class=""} -- [Circle CI](https://circleci.com/docs/using-docker/){:target="blank" rel="noopener" class=""} -- [Render](https://render.com/docs/docker){:target="blank" rel="noopener" class=""} +- [GitHub Actions](https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action) +- [GitLab](https://docs.gitlab.com/runner/executors/docker.html) +- [Circle CI](https://circleci.com/docs/using-docker/) +- [Render](https://render.com/docs/docker) ### Docker in Docker @@ -47,7 +47,7 @@ You can also use a Dockerized build environment to build container images using Docker. That is, your build environment runs inside a container which itself is equipped to run Docker builds. This method is referred to as "Docker in Docker". -Docker provides an official [Docker image](https://hub.docker.com/_/docker){:target="blank" rel="noopener" class=""} +Docker provides an official [Docker image](https://hub.docker.com/_/docker) that you can use for this purpose. ## What's next @@ -55,4 +55,4 @@ that you can use for this purpose. Docker maintains a set of official GitHub Actions that you can use to build, annotate, and push container images on the GitHub Actions platform. See [Introduction to GitHub Actions](./github-actions/index.md) to learn more and -get started. +get started. \ No newline at end of file diff --git a/content/build/ci/github-actions/_index.md b/content/build/ci/github-actions/_index.md index 53de23ec69..ce72ea9c41 100644 --- a/content/build/ci/github-actions/_index.md +++ b/content/build/ci/github-actions/_index.md @@ -1,11 +1,13 @@ --- title: Introduction to GitHub Actions -description: > - Docker maintains a set of official GitHub Actions for building Docker images. +description: 'Docker maintains a set of official GitHub Actions for building Docker + images. + + ' keywords: ci, github actions, gha, build, introduction, tutorial -redirect_from: - - /ci-cd/github-actions/ - - /build/ci/github-actions/examples/ +aliases: +- /ci-cd/github-actions/ +- /build/ci/github-actions/examples/ --- GitHub Actions is a popular CI/CD platform for automating your build, test, and @@ -15,20 +17,20 @@ components for building, annotating, and pushing images. The following GitHub Actions are available: -- [Build and push Docker images](https://github.com/marketplace/actions/build-and-push-docker-images){:target="blank" rel="noopener" class=""}: +- [Build and push Docker images](https://github.com/marketplace/actions/build-and-push-docker-images): build and push Docker images with BuildKit. -- [Docker Login](https://github.com/marketplace/actions/docker-login){:target="blank" rel="noopener" class=""}: +- [Docker Login](https://github.com/marketplace/actions/docker-login): sign in to a Docker registry. -- [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){:target="blank" rel="noopener" class=""}: +- [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx): initiates a BuildKit builder. -- [Docker Metadata action](https://github.com/marketplace/actions/docker-metadata-action){:target="blank" rel="noopener" class=""}: +- [Docker Metadata action](https://github.com/marketplace/actions/docker-metadata-action): extracts metadata from Git reference and GitHub events. -- [Docker Setup QEMU](https://github.com/marketplace/actions/docker-setup-qemu){:target="blank" rel="noopener" class=""}: +- [Docker Setup QEMU](https://github.com/marketplace/actions/docker-setup-qemu): installs [QEMU](https://github.com/qemu/qemu) static binaries for multi-arch builds. -- [Docker Buildx Bake](https://github.com/marketplace/actions/docker-buildx-bake){:target="blank" rel="noopener" class=""}: +- [Docker Buildx Bake](https://github.com/marketplace/actions/docker-buildx-bake): enables using high-level builds with [Bake](../../bake/index.md). -- [Docker Scout](https://github.com/docker/scout-action){:target="blank" rel="noopener" class=""}: +- [Docker Scout](https://github.com/docker/scout-action): analyze Docker images for security vulnerabilities. Using Docker's actions provides an easy-to-use interface, while still allowing @@ -56,7 +58,7 @@ refer to the following sections: ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Next steps @@ -66,4 +68,4 @@ using the official Docker actions, to build and push an image to Docker Hub. There are many more things you can do to customize your workflow to better suit your needs. To learn more about some of the more advanced use cases, take a look at the advanced examples, such as [building multi-platform images](multi-platform.md), -or [using cache storage backends](cache.md) and also how to [configure your builder](configure-builder.md). +or [using cache storage backends](cache.md) and also how to [configure your builder](configure-builder.md). \ No newline at end of file diff --git a/content/build/ci/github-actions/cache.md b/content/build/ci/github-actions/cache.md index dcf17903bc..e9794806a3 100644 --- a/content/build/ci/github-actions/cache.md +++ b/content/build/ci/github-actions/cache.md @@ -18,7 +18,7 @@ However, note that the `inline` cache exporter only supports `min` cache mode. To use `max` cache mode, push the image and the cache separately using the registry cache exporter with the `cache-to` option, as shown in the [registry cache example](#registry-cache). -{% raw %} + ```yaml name: ci @@ -53,14 +53,14 @@ jobs: cache-from: type=registry,ref=user/app:latest cache-to: type=inline ``` -{% endraw %} + ## Registry cache You can import/export cache from a cache manifest or (special) image configuration on the registry with the [registry cache exporter](../../cache/backends/registry.md). -{% raw %} + ```yaml name: ci @@ -95,7 +95,7 @@ jobs: cache-from: type=registry,ref=user/app:buildcache cache-to: type=registry,ref=user/app:buildcache,mode=max ``` -{% endraw %} + ## GitHub cache @@ -103,9 +103,9 @@ jobs: > Experimental > -> This cache exporter is experimental. Please provide feedback on [BuildKit repository](https://github.com/moby/buildkit){:target="blank" rel="noopener" class=""} +> This cache exporter is experimental. Please provide feedback on [BuildKit repository](https://github.com/moby/buildkit) > if you experience any issues. -{: .experimental } +{ .experimental } The [GitHub Actions cache exporter](../../cache/backends/gha.md) backend uses the [GitHub Cache API](https://github.com/tonistiigi/go-actions-cache/blob/master/api.md) @@ -114,7 +114,7 @@ backend in a GitHub Action workflow, as the `url` (`$ACTIONS_CACHE_URL`) and `token` (`$ACTIONS_RUNTIME_TOKEN`) attributes only get populated in a workflow context. -{% raw %} + ```yaml name: ci @@ -149,7 +149,7 @@ jobs: cache-from: type=gha cache-to: type=gha,mode=max ``` -{% endraw %} + ### Cache mounts @@ -165,7 +165,7 @@ cache mount data with your Docker build steps. The following example shows how to use this workaround with a Go project. -{% raw %} + ```yaml name: ci on: push @@ -223,7 +223,7 @@ jobs: with: cache-source: go-build-cache ``` -{% endraw %} + For more information about this workaround, refer to the [GitHub repository](https://github.com/overmindtech/buildkit-cache-dance). @@ -232,16 +232,16 @@ For more information about this workaround, refer to the > **Warning** > -> At the moment, old cache entries aren't deleted, so the cache size [keeps growing](https://github.com/docker/build-push-action/issues/252){:target="blank" rel="noopener" class=""}. -> The following example uses the `Move cache` step as a workaround (see [`moby/buildkit#1896`](https://github.com/moby/buildkit/issues/1896){:target="blank" rel="noopener" class=""} +> At the moment, old cache entries aren't deleted, so the cache size [keeps growing](https://github.com/docker/build-push-action/issues/252). +> The following example uses the `Move cache` step as a workaround (see [`moby/buildkit#1896`](https://github.com/moby/buildkit/issues/1896) > for more info). -{: .warning } +{ .warning } -You can also leverage [GitHub cache](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows){:target="blank" rel="noopener" class=""} +You can also leverage [GitHub cache](https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows) using the [actions/cache](https://github.com/actions/cache) and [local cache exporter](../../cache/backends/local.md) with this action: -{% raw %} + ```yaml name: ci @@ -291,5 +291,4 @@ jobs: run: | rm -rf /tmp/.buildx-cache mv /tmp/.buildx-cache-new /tmp/.buildx-cache -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/configure-builder.md b/content/build/ci/github-actions/configure-builder.md index bcff323e5f..f2981a7778 100644 --- a/content/build/ci/github-actions/configure-builder.md +++ b/content/build/ci/github-actions/configure-builder.md @@ -5,13 +5,13 @@ keywords: ci, github actions, gha, buildkit, buildx --- This page contains instructions on configuring your BuildKit instances when -using our [Setup Buildx Action](https://github.com/docker/setup-buildx-action){:target="blank" rel="noopener" class=""}. +using our [Setup Buildx Action](https://github.com/docker/setup-buildx-action). ## Version pinning -By default, the action will attempt to use the latest version of [Buildx](https://github.com/docker/buildx){:target="blank" rel="noopener" class=""} +By default, the action will attempt to use the latest version of [Buildx](https://github.com/docker/buildx) available on the GitHub Runner (the build client) and the latest release of -[BuildKit](https://github.com/moby/buildkit){:target="blank" rel="noopener" class=""} (the build server). +[BuildKit](https://github.com/moby/buildkit) (the build server). To pin to a specific version of Buildx, use the `version` input. For example, to pin to Buildx v0.10.0: @@ -36,8 +36,8 @@ To pin to a specific version of BuildKit, use the `image` option in the ## BuildKit container logs To display BuildKit container logs when using the `docker-container` driver, -you must either [enable step debug logging](https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging){:target="blank" rel="noopener" class=""}, -or set the `--debug` buildkitd flag in the [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){:target="blank" rel="noopener" class=""} action: +you must either [enable step debug logging](https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging), +or set the `--debug` buildkitd flag in the [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx) action: ```yaml name: ci @@ -162,7 +162,7 @@ fields: Here is an example using remote nodes with the [`remote` driver](../../drivers/remote.md) and [TLS authentication](#tls-authentication): -{% raw %} + ```yaml name: ci @@ -195,7 +195,7 @@ jobs: BUILDER_NODE_2_AUTH_TLS_CERT: ${{ secrets.LINUXONE_CERT }} BUILDER_NODE_2_AUTH_TLS_KEY: ${{ secrets.LINUXONE_KEY }} ``` -{% endraw %} + ## Authentication for remote builders @@ -207,7 +207,7 @@ using SSH or TLS. To be able to connect to an SSH endpoint using the [`docker-container` driver](../../drivers/docker-container.md), you have to set up the SSH private key and configuration on the GitHub Runner: -{% raw %} + ```yaml name: ci @@ -231,7 +231,7 @@ jobs: with: endpoint: ssh://me@graviton2 ``` -{% endraw %} + ### TLS authentication @@ -246,7 +246,7 @@ certificates for the `tcp://`: The `` placeholder is the position of the node in the list of nodes. -{% raw %} + ```yaml name: ci @@ -268,7 +268,7 @@ jobs: BUILDER_NODE_0_AUTH_TLS_CERT: ${{ secrets.GRAVITON2_CERT }} BUILDER_NODE_0_AUTH_TLS_KEY: ${{ secrets.GRAVITON2_KEY }} ``` -{% endraw %} + ## Standalone mode @@ -315,7 +315,7 @@ hardware. For more information about remote builder, see [`remote` driver](../../drivers/remote.md) and the [append builder nodes example](#append-additional-nodes-to-the-builder). -{% raw %} + ```yaml name: ci @@ -357,5 +357,4 @@ jobs: builder: ${{ steps.builder2.outputs.name }} context: . target: mytarget2 -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/copy-image-registries.md b/content/build/ci/github-actions/copy-image-registries.md index 723a5c45a7..cc0719eee6 100644 --- a/content/build/ci/github-actions/copy-image-registries.md +++ b/content/build/ci/github-actions/copy-image-registries.md @@ -6,7 +6,7 @@ keywords: ci, github actions, gha, buildkit, buildx, registry [Multi-platform images](../../building/multi-platform.md) built using Buildx can be copied from one registry to another using the [`buildx imagetools create` command](../../../engine/reference/commandline/buildx_imagetools_create.md): -{% raw %} + ```yaml name: ci @@ -58,5 +58,4 @@ jobs: --tag ghcr.io/user/app:latest \ --tag ghcr.io/user/app:1.0.0 \ user/app:latest -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/export-docker.md b/content/build/ci/github-actions/export-docker.md index 96390db5be..92313b4247 100644 --- a/content/build/ci/github-actions/export-docker.md +++ b/content/build/ci/github-actions/export-docker.md @@ -6,7 +6,7 @@ keywords: ci, github actions, gha, buildkit, buildx, docker You may want your build result to be available in the Docker client through `docker images` to be able to use it in another step of your workflow: -{% raw %} + ```yaml name: ci @@ -36,5 +36,4 @@ jobs: name: Inspect run: | docker image inspect myimage:latest -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/local-registry.md b/content/build/ci/github-actions/local-registry.md index 53ee634b1a..8927e2e479 100644 --- a/content/build/ci/github-actions/local-registry.md +++ b/content/build/ci/github-actions/local-registry.md @@ -3,10 +3,10 @@ title: Local registry with GitHub Actions keywords: ci, github actions, gha, buildkit, buildx, registry --- -For testing purposes you may need to create a [local registry](https://hub.docker.com/_/registry){:target="blank" rel="noopener" class=""} +For testing purposes you may need to create a [local registry](https://hub.docker.com/_/registry) to push images into: -{% raw %} + ```yaml name: ci @@ -46,5 +46,4 @@ jobs: name: Inspect run: | docker buildx imagetools inspect localhost:5000/name/app:latest -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/manage-tags-labels.md b/content/build/ci/github-actions/manage-tags-labels.md index b3180d5a25..90c0715f8c 100644 --- a/content/build/ci/github-actions/manage-tags-labels.md +++ b/content/build/ci/github-actions/manage-tags-labels.md @@ -3,12 +3,12 @@ title: Manage tags and labels with GitHub Actions keywords: ci, github actions, gha, buildkit, buildx, tags, labels --- -If you want an "automatic" tag management and [OCI Image Format Specification](https://github.com/opencontainers/image-spec/blob/master/annotations.md){:target="blank" rel="noopener" class=""} +If you want an "automatic" tag management and [OCI Image Format Specification](https://github.com/opencontainers/image-spec/blob/master/annotations.md) for labels, you can do it in a dedicated setup step. The following workflow -will use the [Docker Metadata Action](https://github.com/docker/metadata-action){:target="blank" rel="noopener" class=""} +will use the [Docker Metadata Action](https://github.com/docker/metadata-action) to handle tags and labels based on GitHub Actions events and Git metadata: -{% raw %} + ```yaml name: ci @@ -78,5 +78,4 @@ jobs: push: ${{ github.event_name != 'pull_request' }} tags: ${{ steps.meta.outputs.tags }} labels: ${{ steps.meta.outputs.labels }} -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/multi-platform.md b/content/build/ci/github-actions/multi-platform.md index 626223b889..e0aabdedbc 100644 --- a/content/build/ci/github-actions/multi-platform.md +++ b/content/build/ci/github-actions/multi-platform.md @@ -8,12 +8,12 @@ the `platforms` option, as shown in the following example: > **Note** > -> - For a list of available platforms, see the [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){:target="blank" rel="noopener" class=""} +> - For a list of available platforms, see the [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx) > action. -> - If you want support for more platforms, you can use QEMU with the [Docker Setup QEMU](https://github.com/docker/setup-qemu-action){:target="blank" rel="noopener" class=""} +> - If you want support for more platforms, you can use QEMU with the [Docker Setup QEMU](https://github.com/docker/setup-qemu-action) > action. -{% raw %} + ```yaml name: ci @@ -50,7 +50,7 @@ jobs: push: true tags: user/app:latest ``` -{% endraw %} + ## Distribute build across multiple runners @@ -68,7 +68,7 @@ create a manifest list and push it to Docker Hub. This example also uses the [`metadata` action](https://github.com/docker/metadata-action) to set tags and labels. -{% raw %} + ```yaml name: ci @@ -173,5 +173,4 @@ jobs: name: Inspect image run: | docker buildx imagetools inspect ${{ env.REGISTRY_IMAGE }}:${{ steps.meta.outputs.version }} -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/named-contexts.md b/content/build/ci/github-actions/named-contexts.md index 5364d44f75..1ec0bec019 100644 --- a/content/build/ci/github-actions/named-contexts.md +++ b/content/build/ci/github-actions/named-contexts.md @@ -20,7 +20,7 @@ FROM alpine RUN echo "Hello World" ``` -{% raw %} + ```yaml name: ci @@ -48,11 +48,11 @@ jobs: alpine=docker-image://alpine:3.16 tags: myimage:latest ``` -{% endraw %} + ## Use image in subsequent steps -By default, the [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){:target="blank" rel="noopener" class=""} +By default, the [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx) action uses `docker-container` as a build driver, so built Docker images aren't loaded automatically. @@ -64,7 +64,7 @@ FROM alpine RUN echo "Hello World" ``` -{% raw %} + ```yaml name: ci @@ -102,7 +102,7 @@ jobs: alpine=docker-image://my-base-image:latest tags: myimage:latest ``` -{% endraw %} + ## Using with a container builder @@ -163,4 +163,4 @@ jobs: build-contexts: | alpine=docker-image://localhost:5000/my-base-image:latest tags: myimage:latest -``` +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/push-multi-registries.md b/content/build/ci/github-actions/push-multi-registries.md index 6d8b0caffe..de0d68cc77 100644 --- a/content/build/ci/github-actions/push-multi-registries.md +++ b/content/build/ci/github-actions/push-multi-registries.md @@ -3,10 +3,10 @@ title: Push to multi-registries with GitHub Actions keywords: ci, github actions, gha, buildkit, buildx, registry --- -The following workflow will connect you to Docker Hub and [GitHub Container Registry](https://github.com/docker/login-action#github-container-registry){:target="blank" rel="noopener" class=""} +The following workflow will connect you to Docker Hub and [GitHub Container Registry](https://github.com/docker/login-action#github-container-registry) and push the image to both registries: -{% raw %} + ```yaml name: ci @@ -53,5 +53,4 @@ jobs: user/app:1.0.0 ghcr.io/user/app:latest ghcr.io/user/app:1.0.0 -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/secrets.md b/content/build/ci/github-actions/secrets.md index f21293303b..242cefa1ec 100644 --- a/content/build/ci/github-actions/secrets.md +++ b/content/build/ci/github-actions/secrets.md @@ -3,7 +3,7 @@ title: Using secrets with GitHub Actions keywords: ci, github actions, gha, buildkit, buildx, secret --- -In the following example uses and exposes the [`GITHUB_TOKEN` secret](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret){:target="blank" rel="noopener" class=""} +In the following example uses and exposes the [`GITHUB_TOKEN` secret](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret) as provided by GitHub in your workflow. First, create a `Dockerfile` that uses the secret: @@ -18,7 +18,7 @@ RUN --mount=type=secret,id=github_token \ In this example, the secret name is `github_token`. The following workflow exposes this secret using the `secrets` input: -{% raw %} + ```yaml name: ci @@ -51,7 +51,7 @@ jobs: "github_token=${{ secrets.GITHUB_TOKEN }}" ``` -{% endraw %} + > **Note** > @@ -62,11 +62,11 @@ jobs: > "MY_SECRET=./secret.txt" > ``` -If you're using [GitHub secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets){:target="blank" rel="noopener" class=""} +If you're using [GitHub secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) and need to handle multi-line value, you will need to place the key-value pair between quotes: -{% raw %} + ```yaml secrets: | "MYSECRET=${{ secrets.GPG_KEY }}" @@ -81,7 +81,7 @@ secrets: | ccc" "JSON_SECRET={""key1"":""value1"",""key2"":""value2""}" ``` -{% endraw %} + | Key | Value | |------------------|-------------------------------------| @@ -94,4 +94,4 @@ secrets: | > **Note** > -> Double escapes are needed for quote signs. +> Double escapes are needed for quote signs. \ No newline at end of file diff --git a/content/build/ci/github-actions/share-image-jobs.md b/content/build/ci/github-actions/share-image-jobs.md index 0fb15d0b49..a6523f8ee8 100644 --- a/content/build/ci/github-actions/share-image-jobs.md +++ b/content/build/ci/github-actions/share-image-jobs.md @@ -4,13 +4,13 @@ keywords: ci, github actions, gha, buildkit, buildx --- As each job is isolated in its own runner, you can't use your built image -between jobs, except if you're using [self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners){:target="blank" rel="noopener" class=""} -However, you can [pass data between jobs](https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts#passing-data-between-jobs-in-a-workflow){:target="blank" rel="noopener" class=""} -in a workflow using the [actions/upload-artifact](https://github.com/actions/upload-artifact){:target="blank" rel="noopener" class=""} -and [actions/download-artifact](https://github.com/actions/download-artifact){:target="blank" rel="noopener" class=""} +between jobs, except if you're using [self-hosted runners](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners) +However, you can [pass data between jobs](https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts#passing-data-between-jobs-in-a-workflow) +in a workflow using the [actions/upload-artifact](https://github.com/actions/upload-artifact) +and [actions/download-artifact](https://github.com/actions/download-artifact) actions: -{% raw %} + ```yaml name: ci @@ -58,5 +58,4 @@ jobs: run: | docker load --input /tmp/myimage.tar docker image ls -a -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/ci/github-actions/test-before-push.md b/content/build/ci/github-actions/test-before-push.md index a50f03757e..4052b7b1da 100644 --- a/content/build/ci/github-actions/test-before-push.md +++ b/content/build/ci/github-actions/test-before-push.md @@ -12,7 +12,7 @@ The following workflow implements several steps to achieve this: 2. Test your image 3. Multi-platform build and push the image -{% raw %} + ```yaml name: ci @@ -64,11 +64,11 @@ jobs: push: true tags: ${{ env.LATEST_TAG }} ``` -{% endraw %} + > **Note** > > This workflow doesn't actually build the `linux/amd64` image twice. The image > is built once, and the following steps uses the internal cache for from the > first `Build and push` step. The second `Build and push` step only builds -> `linux/arm64`. +> `linux/arm64`. \ No newline at end of file diff --git a/content/build/ci/github-actions/update-dockerhub-desc.md b/content/build/ci/github-actions/update-dockerhub-desc.md index bac9449578..001d7bf652 100644 --- a/content/build/ci/github-actions/update-dockerhub-desc.md +++ b/content/build/ci/github-actions/update-dockerhub-desc.md @@ -4,10 +4,10 @@ keywords: ci, github actions, gha, buildkit, buildx, docker hub --- You can update the Docker Hub repository description using a third party action -called [Docker Hub Description](https://github.com/peter-evans/dockerhub-description){:target="blank" rel="noopener" class=""} +called [Docker Hub Description](https://github.com/peter-evans/dockerhub-description) with this action: -{% raw %} + ```yaml name: ci @@ -49,5 +49,4 @@ jobs: username: ${{ secrets.DOCKERHUB_USERNAME }} password: ${{ secrets.DOCKERHUB_TOKEN }} repository: user/app -``` -{% endraw %} +``` \ No newline at end of file diff --git a/content/build/dockerfile/frontend.md b/content/build/dockerfile/frontend.md index 6b9e5e74e3..fed9b7cf35 100644 --- a/content/build/dockerfile/frontend.md +++ b/content/build/dockerfile/frontend.md @@ -1,8 +1,8 @@ --- title: Custom Dockerfile syntax keywords: build, buildkit, dockerfile, frontend -redirect_from: - - /build/buildkit/dockerfile-frontend/ +aliases: +- /build/buildkit/dockerfile-frontend/ --- ## Dockerfile frontend @@ -35,7 +35,7 @@ Custom Dockerfile implementations allow you to: - Make sure all users are using the same implementation to build your Dockerfile - Use the latest features without updating the Docker daemon - Try out new features or third-party features before they are integrated in the Docker daemon -- Use [alternative build definitions, or create your own](https://github.com/moby/buildkit#exploring-llb){:target="blank" rel="noopener" class=""} +- Use [alternative build definitions, or create your own](https://github.com/moby/buildkit#exploring-llb) > **Note** > @@ -52,7 +52,7 @@ channels where new images are released: `stable` and `labs`. ### Stable channel -The `stable` channel follows [semantic versioning](https://semver.org){:target="blank" rel="noopener" class=""}. +The `stable` channel follows [semantic versioning](https://semver.org). For example: - `docker/dockerfile:1` - kept updated with the latest `1.x.x` minor _and_ patch @@ -90,14 +90,14 @@ suffix, for example: Choose a channel that best fits your needs. If you want to benefit from new features, use the `labs` channel. Images in the `labs` channel contain all the features in the `stable` channel, plus early access features. -Stable features in the `labs` channel follow [semantic versioning](https://semver.org){:target="blank" rel="noopener" class=""}, +Stable features in the `labs` channel follow [semantic versioning](https://semver.org), but early access features don't, and newer releases may not be backwards compatible. Pin the version to avoid having to deal with breaking changes. ## Other resources For documentation on "labs" features, master builds, and nightly feature -releases, refer to the description in [the BuildKit source repository on GitHub](https://github.com/moby/buildkit/blob/master/README.md){:target="blank" rel="noopener" class=""}. -For a full list of available images, visit the [`docker/dockerfile` repository on Docker Hub](https://hub.docker.com/r/docker/dockerfile){:target="blank" rel="noopener" class=""}, -and the [`docker/dockerfile-upstream` repository on Docker Hub](https://hub.docker.com/r/docker/dockerfile-upstream){:target="blank" rel="noopener" class=""} -for development builds. +releases, refer to the description in [the BuildKit source repository on GitHub](https://github.com/moby/buildkit/blob/master/README.md). +For a full list of available images, visit the [`docker/dockerfile` repository on Docker Hub](https://hub.docker.com/r/docker/dockerfile), +and the [`docker/dockerfile-upstream` repository on Docker Hub](https://hub.docker.com/r/docker/dockerfile-upstream) +for development builds. \ No newline at end of file diff --git a/content/build/dockerfile/release-notes.md b/content/build/dockerfile/release-notes.md index 7cb49b9b44..4b2c7d724c 100644 --- a/content/build/dockerfile/release-notes.md +++ b/content/build/dockerfile/release-notes.md @@ -12,7 +12,7 @@ For usage, see the [Dockerfile frontend syntax](frontend.md) page. ## 1.6.0 -{% include release-date.html date="2023-06-13" %} +{{< release-date date="2023-06-13" >}} ### New @@ -36,7 +36,7 @@ The following features have graduated from the labs channel to stable: ## 1.5.2 -{% include release-date.html date="2023-02-14" %} +{{< release-date date="2023-02-14" >}} ### Bug fixes and enhancements @@ -46,7 +46,7 @@ The following features have graduated from the labs channel to stable: ## 1.5.1 -{% include release-date.html date="2023-01-18" %} +{{< release-date date="2023-01-18" >}} ### Bug fixes and enhancements @@ -54,9 +54,9 @@ The following features have graduated from the labs channel to stable: ## 1.5.0 (labs) -{% include release-date.html date="2023-01-10" %} +{{< release-date date="2023-01-10" >}} -{% include dockerfile-labs-channel.md %} +{{< include "dockerfile-labs-channel.md" >}} ### New @@ -65,7 +65,7 @@ The following features have graduated from the labs channel to stable: ## 1.5.0 -{% include release-date.html date="2023-01-10" %} +{{< release-date date="2023-01-10" >}} ### New @@ -86,7 +86,7 @@ The following features have graduated from the labs channel to stable: ## 1.4.3 -{% include release-date.html date="2022-08-23" %} +{{< release-date date="2022-08-23" >}} ### Bug fixes and enhancements @@ -97,7 +97,7 @@ The following features have graduated from the labs channel to stable: ## 1.4.2 -{% include release-date.html date="2022-05-06" %} +{{< release-date date="2022-05-06" >}} ### Bug fixes and enhancements @@ -106,7 +106,7 @@ The following features have graduated from the labs channel to stable: ## 1.4.1 -{% include release-date.html date="2022-04-08" %} +{{< release-date date="2022-04-08" >}} ### Bug fixes and enhancements @@ -115,7 +115,7 @@ The following features have graduated from the labs channel to stable: ## 1.4.0 -{% include release-date.html date="2022-03-09" %} +{{< release-date date="2022-03-09" >}} ### New @@ -140,7 +140,7 @@ The following features have graduated from the labs channel to stable: ## 1.3.1 -{% include release-date.html date="2021-10-04" %} +{{< release-date date="2021-10-04" >}} ### Bug fixes and enhancements @@ -148,9 +148,9 @@ The following features have graduated from the labs channel to stable: ## 1.3.0 (labs) -{% include release-date.html date="2021-07-16" %} +{{< release-date date="2021-07-16" >}} -{% include dockerfile-labs-channel.md %} +{{< include "dockerfile-labs-channel.md" >}} ### New @@ -159,7 +159,7 @@ The following features have graduated from the labs channel to stable: ## 1.3.0 -{% include release-date.html date="2021-07-16" %} +{{< release-date date="2021-07-16" >}} ### New @@ -179,9 +179,9 @@ The following features have graduated from the labs channel to stable: ## 1.2.1 (labs) -{% include release-date.html date="2020-12-12" %} +{{< release-date date="2020-12-12" >}} -{% include dockerfile-labs-channel.md %} +{{< include "dockerfile-labs-channel.md" >}} ### Bug fixes and enhancements @@ -191,7 +191,7 @@ The following features have graduated from the labs channel to stable: ## 1.2.1 -{% include release-date.html date="2020-12-12" %} +{{< release-date date="2020-12-12" >}} ### Bug fixes and enhancements @@ -200,9 +200,9 @@ The following features have graduated from the labs channel to stable: ## 1.2.0 (labs) -{% include release-date.html date="2020-12-03" %} +{{< release-date date="2020-12-03" >}} -{% include dockerfile-labs-channel.md %} +{{< include "dockerfile-labs-channel.md" >}} ### Bug fixes and enhancements @@ -210,7 +210,7 @@ The following features have graduated from the labs channel to stable: ## 1.2.0 -{% include release-date.html date="2020-12-03" %} +{{< release-date date="2020-12-03" >}} ### New @@ -229,7 +229,7 @@ The following features have graduated from the labs channel to stable: ## 1.1.7 -{% include release-date.html date="2020-04-18" %} +{{< release-date date="2020-04-18" >}} ### Bug fixes and enhancements @@ -237,9 +237,9 @@ The following features have graduated from the labs channel to stable: ## 1.1.2 (experimental) -{% include release-date.html date="2019-07-31" %} +{{< release-date date="2019-07-31" >}} -{% include dockerfile-labs-channel.md %} +{{< include "dockerfile-labs-channel.md" >}} ### Bug fixes and enhancements @@ -251,7 +251,7 @@ The following features have graduated from the labs channel to stable: ## 1.1.2 -{% include release-date.html date="2019-07-31" %} +{{< release-date date="2019-07-31" >}} ### Bug fixes and enhancements @@ -261,7 +261,7 @@ The following features have graduated from the labs channel to stable: ## 1.1.0 -{% include release-date.html date="2019-04-27" %} +{{< release-date date="2019-04-27" >}} ### New @@ -275,4 +275,4 @@ The following features have graduated from the labs channel to stable: first look for a file `.dockerignore` and if it is not found `.dockerignore` file will be looked up from the root of the build context. This allows projects with multiple Dockerfiles to use different - `.dockerignore` definitions + `.dockerignore` definitions \ No newline at end of file diff --git a/content/build/drivers/_index.md b/content/build/drivers/_index.md index 52b0e278ff..2cd6d5c423 100644 --- a/content/build/drivers/_index.md +++ b/content/build/drivers/_index.md @@ -1,10 +1,10 @@ --- -title: "Drivers overview" +title: Drivers overview keywords: build, buildx, driver, builder, docker-container, kubernetes, remote -redirect_from: - - /build/buildx/drivers/ - - /build/building/drivers/ - - /build/buildx/multiple-builders/ +aliases: +- /build/buildx/drivers/ +- /build/building/drivers/ +- /build/buildx/multiple-builders/ --- Buildx drivers are configurations for how and where the BuildKit backend runs. @@ -39,4 +39,4 @@ use them: - [Docker driver](./docker.md) - [Docker container driver](./docker-container.md) - [Kubernetes driver](./kubernetes.md) -- [Remote driver](./remote.md) +- [Remote driver](./remote.md) \ No newline at end of file diff --git a/content/build/drivers/docker-container.md b/content/build/drivers/docker-container.md index aacf564eaa..287fb5e7a7 100644 --- a/content/build/drivers/docker-container.md +++ b/content/build/drivers/docker-container.md @@ -1,9 +1,9 @@ --- -title: "Docker container driver" +title: Docker container driver keywords: build, buildx, driver, builder, docker-container -redirect_from: - - /build/buildx/drivers/docker-container/ - - /build/building/drivers/docker-container/ +aliases: +- /build/buildx/drivers/docker-container/ +- /build/building/drivers/docker-container/ --- The buildx Docker container driver allows creation of a managed and customizable @@ -42,7 +42,7 @@ pass to `--driver-opt`: ## Usage When you run a build, Buildx pulls the specified `image` (by default, -[`moby/buildkit`](https://hub.docker.com/r/moby/buildkit)){:target="blank" rel="noopener" class=""}. +[`moby/buildkit`](https://hub.docker.com/r/moby/buildkit)). When the container has started, Buildx submits the build submitted to the containerized build server. @@ -120,7 +120,7 @@ container ## QEMU -The `docker-container` driver supports using [QEMU](https://www.qemu.org/){:target="blank" rel="noopener" class=""} +The `docker-container` driver supports using [QEMU](https://www.qemu.org/) (user mode) to build non-native platforms. Use the `--platform` flag to specify which architectures that you want to build for. @@ -171,14 +171,14 @@ $ docker buildx inspect --bootstrap [Inspect the builder container](../../engine/reference/commandline/inspect.md) and see what network is being used: -{% raw %} + ```console $ docker inspect buildx_buildkit_mybuilder0 --format={{.NetworkSettings.Networks}} map[foonet:0xc00018c0c0] ``` -{% endraw %} + ## Further reading For more information on the Docker container driver, see the -[buildx reference](../../engine/reference/commandline/buildx_create.md#driver). +[buildx reference](../../engine/reference/commandline/buildx_create.md#driver). \ No newline at end of file diff --git a/content/build/drivers/docker.md b/content/build/drivers/docker.md index 8f719b09a2..b332386e0e 100644 --- a/content/build/drivers/docker.md +++ b/content/build/drivers/docker.md @@ -1,9 +1,9 @@ --- -title: "Docker driver" +title: Docker driver keywords: build, buildx, driver, builder, docker -redirect_from: - - /build/buildx/drivers/docker/ - - /build/building/drivers/docker/ +aliases: +- /build/buildx/drivers/docker/ +- /build/building/drivers/docker/ --- The Buildx Docker driver is the default driver. It uses the BuildKit server @@ -33,4 +33,4 @@ If you need additional configuration and flexibility, consider using the ## Further reading For more information on the Docker driver, see the -[buildx reference](../../engine/reference/commandline/buildx_create.md#driver). +[buildx reference](../../engine/reference/commandline/buildx_create.md#driver). \ No newline at end of file diff --git a/content/build/drivers/kubernetes.md b/content/build/drivers/kubernetes.md index aee832868c..581436cd23 100644 --- a/content/build/drivers/kubernetes.md +++ b/content/build/drivers/kubernetes.md @@ -1,9 +1,9 @@ --- -title: "Kubernetes driver" +title: Kubernetes driver keywords: build, buildx, driver, builder, kubernetes -redirect_from: - - /build/buildx/drivers/kubernetes/ - - /build/building/drivers/kubernetes/ +aliases: +- /build/buildx/drivers/kubernetes/ +- /build/building/drivers/kubernetes/ --- The Buildx Kubernetes driver allows connecting your local development or CI @@ -64,7 +64,7 @@ is configurable using the following driver options: These options allow requesting and limiting the resources available to each BuildKit pod according to the official Kubernetes documentation - [here](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/){:target="blank" rel="noopener" class=""}. + [here](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/). For example, to create 4 replica BuildKit pods: @@ -135,7 +135,7 @@ leveraging the native architecture of nodes. ### QEMU Like the `docker-container` driver, the Kubernetes driver also supports using -[QEMU](https://www.qemu.org/){:target="blank" rel="noopener" class=""} (user +[QEMU](https://www.qemu.org/) (user mode) to build images for non-native platforms. Include the `--platform` flag and specify which platforms you want to output to. @@ -232,8 +232,7 @@ that you want to support. The Kubernetes driver supports rootless mode. For more information on how rootless mode works, and it's requirements, see -[here](https://github.com/moby/buildkit/blob/master/docs/rootless.md){:target="blank" -rel="noopener" class=""}. +[here](https://github.com/moby/buildkit/blob/master/docs/rootless.md). To turn it on in your cluster, you can use the `rootless=true` driver option: @@ -262,12 +261,10 @@ Prerequisites: - You have an existing Kubernetes cluster. If you don't already have one, you can follow along by installing - [minikube](https://minikube.sigs.k8s.io/docs/){:target="blank" rel="noopener" - class=""}. + [minikube](https://minikube.sigs.k8s.io/docs/). - The cluster you want to connect to is accessible via the `kubectl` command, with the `KUBECONFIG` environment variable - [set appropriately](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable){:target="blank" - rel="noopener" class=""} if necessary. + [set appropriately](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable) if necessary. 1. Create a `buildkit` namespace. @@ -334,4 +331,4 @@ That's it! You've now built an image from a Kubernetes pod, using Buildx! ## Further reading For more information on the Kubernetes driver, see the -[buildx reference](../../engine/reference/commandline/buildx_create.md#driver). +[buildx reference](../../engine/reference/commandline/buildx_create.md#driver). \ No newline at end of file diff --git a/content/build/drivers/remote.md b/content/build/drivers/remote.md index 47777f429b..da5e84892c 100644 --- a/content/build/drivers/remote.md +++ b/content/build/drivers/remote.md @@ -1,9 +1,9 @@ --- -title: "Remote driver" +title: Remote driver keywords: build, buildx, driver, builder, remote -redirect_from: - - /build/buildx/drivers/remote/ - - /build/building/drivers/remote/ +aliases: +- /build/buildx/drivers/remote/ +- /build/building/drivers/remote/ --- The Buildx remote driver allows for more complex custom build workloads, @@ -35,7 +35,7 @@ pass to `--driver-opt`: This guide shows you how to create a setup with a BuildKit daemon listening on a Unix socket, and have Buildx connect through it. -1. Ensure that [BuildKit](https://github.com/moby/buildkit){:target="blank" rel="noopener" class=""} +1. Ensure that [BuildKit](https://github.com/moby/buildkit) is installed. For example, you can launch an instance of buildkitd with: @@ -44,8 +44,8 @@ Unix socket, and have Buildx connect through it. $ sudo ./buildkitd --group $(id -gn) --addr unix://$HOME/buildkitd.sock ``` - Alternatively, [see here](https://github.com/moby/buildkit/blob/master/docs/rootless.md){:target="blank" rel="noopener" class=""} - for running buildkitd in rootless mode or [here](https://github.com/moby/buildkit/tree/master/examples/systemd){:target="blank" rel="noopener" class=""} + Alternatively, [see here](https://github.com/moby/buildkit/blob/master/docs/rootless.md) + for running buildkitd in rootless mode or [here](https://github.com/moby/buildkit/tree/master/examples/systemd) for examples of running it as a systemd service. 2. Check that you have a Unix socket that you can connect to. @@ -97,7 +97,7 @@ but this is for illustration purposes.) 1. Generate certificates for BuildKit. - You can use the [create-certs.sh](https://github.com/moby/buildkit/blob/master/examples/kubernetes/create-certs.sh){:target="blank" rel="noopener" class=""} + You can use the [create-certs.sh](https://github.com/moby/buildkit/blob/master/examples/kubernetes/create-certs.sh) script as a starting point. Note that while it's possible to expose BuildKit over TCP without using TLS, it's not recommended. Doing so allows arbitrary access to BuildKit without credentials. @@ -150,10 +150,10 @@ pods, the Buildx builder will need to be recreated from within each pod or copied between them. 1. Create a Kubernetes deployment of `buildkitd`, as per the instructions - [here](https://github.com/moby/buildkit/tree/master/examples/kubernetes){:target="blank" rel="noopener" class=""}. + [here](https://github.com/moby/buildkit/tree/master/examples/kubernetes). Following the guide, create certificates for the BuildKit daemon and client - using [create-certs.sh](https://github.com/moby/buildkit/blob/master/examples/kubernetes/create-certs.sh){:target="blank" rel="noopener" class=""}, + using [create-certs.sh](https://github.com/moby/buildkit/blob/master/examples/kubernetes/create-certs.sh), and create a deployment of BuildKit pods with a service that connects to them. @@ -192,4 +192,4 @@ $ docker buildx create \ --name remote-container \ --driver remote \ kube-pod://buildkitd-XXXXXXXXXX-xxxxx -``` +``` \ No newline at end of file diff --git a/content/build/exporters/_index.md b/content/build/exporters/_index.md index 141c28ccb8..c3dcf7883b 100644 --- a/content/build/exporters/_index.md +++ b/content/build/exporters/_index.md @@ -1,10 +1,11 @@ --- -title: "Exporters overview" -keywords: > - build, buildx, buildkit, exporter, image, registry, local, tar, oci, docker, +title: Exporters overview +keywords: 'build, buildx, buildkit, exporter, image, registry, local, tar, oci, docker, cacheonly -redirect_from: - - /build/building/exporters/ + + ' +aliases: +- /build/building/exporters/ --- Exporters save your build results to a specified output type. You specify the @@ -18,10 +19,10 @@ Buildx supports the following exporters: - `local`: exports the build root filesystem into a local directory. - `tar`: packs the build root filesystem into a local tarball. - `oci`: exports the build result to the local filesystem in the - [OCI image layout](https://github.com/opencontainers/image-spec/blob/v1.0.1/image-layout.md){:target="blank" rel="noopener" class="_"} + [OCI image layout](https://github.com/opencontainers/image-spec/blob/v1.0.1/image-layout.md) format. - `docker`: exports the build result to the local filesystem in the - [Docker Image Specification v1.2.0](https://github.com/moby/moby/blob/v24.0.0/image/spec/v1.2.md){:target="blank" rel="noopener" class="_"} + [Docker Image Specification v1.2.0](https://github.com/moby/moby/blob/v24.0.0/image/spec/v1.2.md) format. - `cacheonly`: doesn't export a build output, but runs the build and creates a cache. @@ -184,7 +185,7 @@ WARNING: No output specified with docker-container driver. ## Multiple exporters You can only specify a single exporter for any given build (see -[this pull request](https://github.com/moby/buildkit/pull/2760) for details){:target="blank" rel="noopener" class="_"}. +[this pull request](https://github.com/moby/buildkit/pull/2760) for details). But you can perform multiple builds one after another to export the same content twice. BuildKit caches the build, so unless any of the layers change, all successive builds following the first are instant. @@ -242,8 +243,8 @@ the previous compression algorithm. > **Note** > -> The `gzip` and `estargz` compression methods use the [`compress/gzip` package](https://pkg.go.dev/compress/gzip){: target="blank" rel="noopener" class="_" }, -> while `zstd` uses the [`github.com/klauspost/compress/zstd` package](https://github.com/klauspost/compress/tree/master/zstd){: target="blank" rel="noopener" class="_" }. +> The `gzip` and `estargz` compression methods use the [`compress/gzip` package](https://pkg.go.dev/compress/gzip), +> while `zstd` uses the [`github.com/klauspost/compress/zstd` package](https://github.com/klauspost/compress/tree/master/zstd). ### OCI media types @@ -266,4 +267,4 @@ them: - [Image and registry exporters](image-registry.md) - [OCI and Docker exporters](oci-docker.md). -- [Local and tar exporters](local-tar.md) +- [Local and tar exporters](local-tar.md) \ No newline at end of file diff --git a/content/build/exporters/image-registry.md b/content/build/exporters/image-registry.md index 1a43c8d447..9fbcc2959f 100644 --- a/content/build/exporters/image-registry.md +++ b/content/build/exporters/image-registry.md @@ -1,9 +1,10 @@ --- -title: "Image and registry exporters" -keywords: > - build, buildx, buildkit, exporter, image, registry -redirect_from: - - /build/building/exporters/image-registry/ +title: Image and registry exporters +keywords: 'build, buildx, buildkit, exporter, image, registry + + ' +aliases: +- /build/building/exporters/image-registry/ --- The `image` exporter outputs the build result into a container image format. The @@ -57,9 +58,9 @@ $ docker buildx build \ ``` For more information about annotations, see -[BuildKit documentation](https://github.com/moby/buildkit/blob/master/docs/annotations.md){:target="blank" rel="noopener" class=""}. +[BuildKit documentation](https://github.com/moby/buildkit/blob/master/docs/annotations.md). ## Further reading For more information on the `image` or `registry` exporters, see the -[BuildKit README](https://github.com/moby/buildkit/blob/master/README.md#imageregistry){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit/blob/master/README.md#imageregistry). \ No newline at end of file diff --git a/content/build/exporters/local-tar.md b/content/build/exporters/local-tar.md index 1eff481483..1cd411e7a8 100644 --- a/content/build/exporters/local-tar.md +++ b/content/build/exporters/local-tar.md @@ -1,9 +1,10 @@ --- -title: "Local and tar exporters" -keywords: > - build, buildx, buildkit, exporter, local, tar -redirect_from: - - /build/building/exporters/local-tar/ +title: Local and tar exporters +keywords: 'build, buildx, buildkit, exporter, local, tar + + ' +aliases: +- /build/building/exporters/local-tar/ --- The `local` and `tar` exporters output the root filesystem of the build result @@ -34,4 +35,4 @@ The following table describes the available parameters: ## Further reading For more information on the `local` or `tar` exporters, see the -[BuildKit README](https://github.com/moby/buildkit/blob/master/README.md#local-directory){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit/blob/master/README.md#local-directory). \ No newline at end of file diff --git a/content/build/exporters/oci-docker.md b/content/build/exporters/oci-docker.md index 90b2e38cb4..027f0916e0 100644 --- a/content/build/exporters/oci-docker.md +++ b/content/build/exporters/oci-docker.md @@ -1,13 +1,14 @@ --- -title: "OCI and Docker exporters" -keywords: > - build, buildx, buildkit, exporter, oci, docker -redirect_from: - - /build/building/exporters/local-tar/ +title: OCI and Docker exporters +keywords: 'build, buildx, buildkit, exporter, oci, docker + + ' +aliases: +- /build/building/exporters/local-tar/ --- The `oci` exporter outputs the build result into an -[OCI image layout](https://github.com/opencontainers/image-spec/blob/main/image-layout.md){:target="blank" rel="noopener" class=""} +[OCI image layout](https://github.com/opencontainers/image-spec/blob/main/image-layout.md) tarball. The `docker` exporter behaves the same way, except it exports a Docker image layout instead. @@ -56,9 +57,9 @@ $ docker buildx build \ ``` For more information about annotations, see -[BuildKit documentation](https://github.com/moby/buildkit/blob/master/docs/annotations.md){:target="blank" rel="noopener" class=""}. +[BuildKit documentation](https://github.com/moby/buildkit/blob/master/docs/annotations.md). ## Further reading For more information on the `oci` or `docker` exporters, see the -[BuildKit README](https://github.com/moby/buildkit/blob/master/README.md#docker-tarball){:target="blank" rel="noopener" class=""}. +[BuildKit README](https://github.com/moby/buildkit/blob/master/README.md#docker-tarball). \ No newline at end of file diff --git a/content/build/guide/_index.md b/content/build/guide/_index.md index f93d910ac2..7cc2e9aca6 100644 --- a/content/build/guide/_index.md +++ b/content/build/guide/_index.md @@ -31,4 +31,4 @@ workflows. You don't need to complete this entire guide from start to finish. Follow the sections that seem relevant to you, and save the advanced sections at the end for later, when you need them. -[Get started](intro.md){: .button .primary-btn } +{{< button text="Get started" url="intro.md" >}} \ No newline at end of file diff --git a/content/build/guide/build-args.md b/content/build/guide/build-args.md index 284362f3fd..11eee58002 100644 --- a/content/build/guide/build-args.md +++ b/content/build/guide/build-args.md @@ -1,8 +1,9 @@ --- title: Build arguments description: Introduction to configurable builds, using build args -keywords: > - build, buildkit, buildx, guide, tutorial, build arguments, arg +keywords: 'build, buildkit, buildx, guide, tutorial, build arguments, arg + + ' --- {% include_relative nav.html selected="5" %} @@ -14,7 +15,7 @@ uses as a fallback. ## Change runtime versions A practical use case for build arguments is to specify runtime versions for -build stages. Your image uses the `golang:{{site.example_go_version}}-alpine` +build stages. Your image uses the `golang:{{% param "example_go_version" %}}-alpine` image as a base image. But what if someone wanted to use a different version of Go for building the application? They could update the version number inside the Dockerfile, but @@ -23,8 +24,8 @@ has to be. Build arguments make life easier: ```diff # syntax=docker/dockerfile:1 -- FROM golang:{{site.example_go_version}}-alpine AS base -+ ARG GO_VERSION={{site.example_go_version}} +- FROM golang:{{% param "example_go_version" %}}-alpine AS base ++ ARG GO_VERSION={{% param "example_go_version" %}} + FROM golang:${GO_VERSION}-alpine AS base WORKDIR /src RUN --mount=type=cache,target=/go/pkg/mod/ \ @@ -52,9 +53,9 @@ has to be. Build arguments make life easier: ``` The `ARG` keyword is interpolated in the image name in the `FROM` instruction. -The default value of the `GO_VERSION` build argument is set to `{{site.example_go_version}}`. +The default value of the `GO_VERSION` build argument is set to `{{% param "example_go_version" %}}`. If the build doesn't receive a `GO_VERSION` build argument, the `FROM` instruction -resolves to `golang:{{site.example_go_version}}-alpine`. +resolves to `golang:{{% param "example_go_version" %}}-alpine`. Try setting a different version of Go to use for building, using the `--build-arg` flag for the build command: @@ -97,7 +98,7 @@ a variable in the code. ```diff # syntax=docker/dockerfile:1 - ARG GO_VERSION={{site.example_go_version}} + ARG GO_VERSION={{% param "example_go_version" %}} FROM golang:${GO_VERSION}-alpine AS base WORKDIR /src RUN --mount=type=cache,target=/go/pkg/mod/ \ @@ -153,4 +154,4 @@ Related information: The next section of this guide shows how you can use Docker builds to create not only container images, but executable binaries as well. -[Export binaries](export.md){: .button .primary-btn } +{{< button text="Export binaries" url="export.md" >}} \ No newline at end of file diff --git a/content/build/guide/export.md b/content/build/guide/export.md index fa2839befd..7a86925dae 100644 --- a/content/build/guide/export.md +++ b/content/build/guide/export.md @@ -1,8 +1,9 @@ --- title: Export binaries description: Using Docker builds to create and export executable binaries -keywords: > - build, buildkit, buildx, guide, tutorial, build arguments, arg +keywords: 'build, buildkit, buildx, guide, tutorial, build arguments, arg + + ' --- {% include_relative nav.html selected="6" %} @@ -50,7 +51,7 @@ stage: ```diff # syntax=docker/dockerfile:1 - ARG GO_VERSION={{site.example_go_version}} + ARG GO_VERSION={{% param "example_go_version" %}} FROM golang:${GO_VERSION}-alpine AS base WORKDIR /src RUN --mount=type=cache,target=/go/pkg/mod/ \ @@ -114,4 +115,4 @@ Related information: The next topic of this guide is testing: how you can use Docker to run application tests. -[Test](test.md){: .button .primary-btn } +{{< button text="Test" url="test.md" >}} \ No newline at end of file diff --git a/content/build/guide/intro.md b/content/build/guide/intro.md index c3eb0a135e..425d144ba7 100644 --- a/content/build/guide/intro.md +++ b/content/build/guide/intro.md @@ -55,7 +55,7 @@ Here's the Dockerfile used as the starting point for this guide: ```dockerfile # syntax=docker/dockerfile:1 -FROM golang:{{site.example_go_version}}-alpine +FROM golang:{{% param "example_go_version" %}}-alpine WORKDIR /src COPY . . RUN go mod download @@ -74,9 +74,9 @@ Here’s what this Dockerfile does: the `dockerfile:1` syntax which is best practice: it ensures that you have access to the latest Docker build features. -2. `FROM golang:{{site.example_go_version}}-alpine` +2. `FROM golang:{{% param "example_go_version" %}}-alpine` - The `FROM` instruction uses version `{{site.example_go_version}}-alpine` of the `golang` official image. + The `FROM` instruction uses version `{{% param "example_go_version" %}}-alpine` of the `golang` official image. 3. `WORKDIR /src` @@ -169,4 +169,4 @@ Related information: The next section explores how you can use layer cache to improve build speed. -[Layers](layers.md){: .button .primary-btn } +{{< button text="Layers" url="layers.md" >}} \ No newline at end of file diff --git a/content/build/guide/layers.md b/content/build/guide/layers.md index 56602433cf..d0ee913b07 100644 --- a/content/build/guide/layers.md +++ b/content/build/guide/layers.md @@ -11,7 +11,7 @@ of ordered build instructions. Each instruction in a Dockerfile roughly translat to an image layer. The following diagram illustrates how a Dockerfile translates into a stack of layers in a container image. -![From Dockerfile to layers](./images/layers.png){:.invertible} +![From Dockerfile to layers](./images/layers.png) ## Cached layers @@ -25,7 +25,7 @@ following step (`RUN go mod download`). If you were to change any of the project files, then that would invalidate the cache for the `COPY` layer. It also invalidates the cache for all of the layers that follow. -![Layer cache is bust](./images/cache-bust.png){:.invertible} +![Layer cache is bust](./images/cache-bust.png) Because of the current order of the Dockerfile instructions, the builder must download the Go modules again, despite none of the packages having changed since @@ -47,7 +47,7 @@ For Go to know which dependencies to download, you need to copy the `go.mod` and ```diff # syntax=docker/dockerfile:1 - FROM golang:{{site.example_go_version}}-alpine + FROM golang:{{% param "example_go_version" %}}-alpine WORKDIR /src - COPY . . + COPY go.mod go.sum . @@ -63,7 +63,7 @@ builder to download the dependencies each time. The `COPY . .` instruction appears after the package management instructions, so the builder can reuse the `RUN go mod download` layer. -![Reordered](./images/reordered-layers.png){:.invertible} +![Reordered](./images/reordered-layers.png) ## Summary @@ -80,4 +80,4 @@ Related information: The next section shows how you can make the build run faster, and make the resulting output smaller, using multi-stage builds. -[Multi-stage](multi-stage.md){: .button .primary-btn } +{{< button text="Multi-stage" url="multi-stage.md" >}} \ No newline at end of file diff --git a/content/build/guide/mounts.md b/content/build/guide/mounts.md index 433192dda0..044c133a6a 100644 --- a/content/build/guide/mounts.md +++ b/content/build/guide/mounts.md @@ -1,8 +1,9 @@ --- title: Mounts description: Introduction to cache mounts and bind mounts in builds -keywords: > - build, buildkit, buildx, guide, tutorial, mounts, cache mounts, bind mounts +keywords: 'build, buildkit, buildx, guide, tutorial, mounts, cache mounts, bind mounts + + ' --- {% include_relative nav.html selected="4" %} @@ -36,7 +37,7 @@ mount the `/go/pkg/mod` directory as a cache mount: ```diff # syntax=docker/dockerfile:1 - FROM golang:{{site.example_go_version}}-alpine AS base + FROM golang:{{% param "example_go_version" %}}-alpine AS base WORKDIR /src COPY go.mod go.sum . - RUN go mod download @@ -117,7 +118,7 @@ Update the version of the `chi` package that the server component of the application uses: ```console -$ docker run -v $PWD:$PWD -w $PWD golang:{{site.example_go_version}}-alpine \ +$ docker run -v $PWD:$PWD -w $PWD golang:{{% param "example_go_version" %}}-alpine \ go get github.com/go-chi/chi/v5@v5.0.8 ``` @@ -151,7 +152,7 @@ the need for the additional `COPY` instruction (and layer) entirely. ```diff # syntax=docker/dockerfile:1 - FROM golang:{{site.example_go_version}}-alpine AS base + FROM golang:{{% param "example_go_version" %}}-alpine AS base WORKDIR /src - COPY go.mod go.sum . RUN --mount=type=cache,target=/go/pkg/mod/ \ @@ -183,7 +184,7 @@ Similarly, you can use the same technique to remove the need for the second ```diff # syntax=docker/dockerfile:1 - FROM golang:{{site.example_go_version}}-alpine AS base + FROM golang:{{% param "example_go_version" %}}-alpine AS base WORKDIR /src RUN --mount=type=cache,target=/go/pkg/mod/ \ --mount=type=bind,source=go.sum,target=go.sum \ @@ -225,4 +226,4 @@ Related information: The next section of this guide is an introduction to making your builds configurable, using build arguments. -[Build arguments](build-args.md){: .button .primary-btn } +{{< button text="Build arguments" url="build-args.md" >}} \ No newline at end of file diff --git a/content/build/guide/multi-platform.md b/content/build/guide/multi-platform.md index 97cc877ab0..0f345f6ee5 100644 --- a/content/build/guide/multi-platform.md +++ b/content/build/guide/multi-platform.md @@ -1,9 +1,7 @@ --- title: Multi-platform description: Building for multiple operating systems and architectures -keywords: >- - build, buildkit, buildx, guide, tutorial, multi-platform, emulation, - cross-compilation +keywords: build, buildkit, buildx, guide, tutorial, multi-platform, emulation, cross-compilation --- {% include_relative nav.html selected="8" %} @@ -112,7 +110,7 @@ When you build using a builder that supports multi-platform builds, the builder runs all of the build steps under emulation for each platform that you specify. Effectively forking the build into two concurrent processes. -![Build pipelines using emulation](./images/emulation.png){:.invertible} +![Build pipelines using emulation](./images/emulation.png) There are, however, a few downsides to running multi-platform builds using emulation: @@ -157,7 +155,7 @@ the pre-defined platform arguments are forked automatically for each platform. This is in contrast to builds running under emulation, where the entire build pipeline runs per platform. -![Build pipelines using cross-compilation](./images/cross-compilation.png){:.invertible} +![Build pipelines using cross-compilation](./images/cross-compilation.png) ### Update the Dockerfile @@ -175,8 +173,8 @@ follows: ```diff # syntax=docker/dockerfile:1 - ARG GO_VERSION={{site.example_go_version}} - ARG GOLANGCI_LINT_VERSION={{site.example_golangci_lint_version}} + ARG GO_VERSION={{% param "example_go_version" %}} + ARG GOLANGCI_LINT_VERSION={{% param "example_golangci_lint_version" %}} - FROM golang:${GO_VERSION}-alpine AS base + FROM --platform=$BUILDPLATFORM golang:${GO_VERSION}-alpine AS base WORKDIR /src @@ -262,7 +260,7 @@ Related information: - [`docker buildx create` CLI reference](../../engine/reference/commandline/buildx_create.md) You may also want to consider checking out -[xx - Dockerfile cross-compilation helpers](https://github.com/tonistiigi/xx){: target="_blank" rel="noopener" }. +[xx - Dockerfile cross-compilation helpers](https://github.com/tonistiigi/xx). `xx` is a Docker image containing utility scripts that make cross-compiling with Docker builds easier. ## Next steps @@ -270,4 +268,4 @@ You may also want to consider checking out This section is the final part of the Build with Docker guide. The following page contains some pointers for where to go next. -[Next steps](next-steps.md){: .button .primary-btn } +{{< button text="Next steps" url="next-steps.md" >}} \ No newline at end of file diff --git a/content/build/guide/multi-stage.md b/content/build/guide/multi-stage.md index e7d7dd8030..e829892fee 100644 --- a/content/build/guide/multi-stage.md +++ b/content/build/guide/multi-stage.md @@ -41,7 +41,7 @@ built in the previous stage are copied over to the filesystem of the new stage. ```diff # syntax=docker/dockerfile:1 - FROM golang:{{site.example_go_version}}-alpine + FROM golang:{{% param "example_go_version" %}}-alpine WORKDIR /src COPY go.mod go.sum . RUN go mod download @@ -90,8 +90,8 @@ to the final `scratch` image. ```diff # syntax=docker/dockerfile:1 -- FROM golang:{{site.example_go_version}}-alpine -+ FROM golang:{{site.example_go_version}}-alpine AS base +- FROM golang:{{% param "example_go_version" %}}-alpine ++ FROM golang:{{% param "example_go_version" %}}-alpine AS base WORKDIR /src COPY go.mod go.sum . RUN go mod download @@ -129,7 +129,7 @@ unnamed `FROM scratch` stage with two separate stages named `client` and ```diff # syntax=docker/dockerfile:1 - FROM golang:{{site.example_go_version}}-alpine AS base + FROM golang:{{% param "example_go_version" %}}-alpine AS base WORKDIR /src COPY go.mod go.sum . RUN go mod download @@ -190,4 +190,4 @@ Related information: The next section describes how you can use file mounts to further improve build speeds. -[Mounts](mounts.md){: .button .primary-btn } +{{< button text="Mounts" url="mounts.md" >}} \ No newline at end of file diff --git a/content/build/guide/next-steps.md b/content/build/guide/next-steps.md index 782396b879..a31a9b9d43 100644 --- a/content/build/guide/next-steps.md +++ b/content/build/guide/next-steps.md @@ -30,5 +30,5 @@ If you don't see the feedback widget, try turning off your content filtering extension or ad blocker, if you use one. You can also submit an issue on -[the docs GitHub repository](https://github.com/docker/docs/issues/new){: target="_blank" rel="noopener" }, -if you prefer. +[the docs GitHub repository](https://github.com/docker/docs/issues/new), +if you prefer. \ No newline at end of file diff --git a/content/build/guide/test.md b/content/build/guide/test.md index 36439a97b2..44a56d5ab4 100644 --- a/content/build/guide/test.md +++ b/content/build/guide/test.md @@ -40,8 +40,8 @@ Now you can add this as a step to the Dockerfile. ```diff # syntax=docker/dockerfile:1 - ARG GO_VERSION={{site.example_go_version}} -+ ARG GOLANGCI_LINT_VERSION={{site.example_golangci_lint_version}} + ARG GO_VERSION={{% param "example_go_version" %}} ++ ARG GOLANGCI_LINT_VERSION={{% param "example_golangci_lint_version" %}} FROM golang:${GO_VERSION}-alpine AS base WORKDIR /src RUN --mount=type=cache,target=/go/pkg/mod/ \ @@ -114,4 +114,4 @@ This section has shown an example on how you can use Docker builds to run tests The next topic in this guide is multi-platform builds, using emulation and cross-compilation. -[Multi-platform](multi-platform.md){: .button .primary-btn } +{{< button text="Multi-platform" url="multi-platform.md" >}} \ No newline at end of file diff --git a/content/build/hydrobuild.md b/content/build/hydrobuild.md index 0e3ac3b2f8..01bb6305f2 100644 --- a/content/build/hydrobuild.md +++ b/content/build/hydrobuild.md @@ -11,7 +11,7 @@ sitemap: false > > If you want to get involved in testing Hydrobuild, you can > [sign up for the early access program](https://www.docker.com/build-early-access-program/?utm_source=docs). -{: .restricted } +{ .restricted } Hydrobuild is a service that lets you build your container images faster, both locally and in CI. Builds run on cloud infrastructure optimally dimensioned for @@ -378,4 +378,4 @@ No. Your interface to Hydrobuild is Buildx, and you can use the existing For more information, refer to: - [docker buildx build --secret](../engine/reference/commandline/buildx_build.md#secret) -- [docker buildx build --ssh](../engine/reference/commandline/buildx_build.md#ssh) +- [docker buildx build --ssh](../engine/reference/commandline/buildx_build.md#ssh) \ No newline at end of file diff --git a/content/build/release-notes.md b/content/build/release-notes.md index 516b78a8e2..d57eb3a7d0 100644 --- a/content/build/release-notes.md +++ b/content/build/release-notes.md @@ -6,124 +6,124 @@ toc_max: 2 --- This page contains information about the new features, improvements, and bug -fixes in [Docker Buildx](https://github.com/docker/buildx){:target="blank" rel="noopener" class=""}. +fixes in [Docker Buildx](https://github.com/docker/buildx). ## 0.11.2 -{% include release-date.html date="2023-07-18" %} +{{< release-date date="2023-07-18" >}} The full release note for this release is available -[on GitHub](https://github.com/docker/buildx/releases/tag/v0.11.2){:target="blank" rel="noopener"}. +[on GitHub](https://github.com/docker/buildx/releases/tag/v0.11.2). ### Bug fixes and enhancements - Fix a regression that caused buildx to not read the `KUBECONFIG` path from the instance store. - [docker/buildx#1941](https://github.com/docker/buildx/pull/1941){:target="blank" rel="noopener"} + [docker/buildx#1941](https://github.com/docker/buildx/pull/1941) - Fix a regression with result handle builds showing up in the build history incorrectly. - [docker/buildx#1954](https://github.com/docker/buildx/pull/1954){:target="blank" rel="noopener"} + [docker/buildx#1954](https://github.com/docker/buildx/pull/1954) ## 0.11.1 -{% include release-date.html date="2023-07-05" %} +{{< release-date date="2023-07-05" >}} The full release note for this release is available -[on GitHub](https://github.com/docker/buildx/releases/tag/v0.11.1){:target="blank" rel="noopener"}. +[on GitHub](https://github.com/docker/buildx/releases/tag/v0.11.1). ### Bug fixes and enhancements - Fix a regression for bake where services in profiles would not be loaded. - [docker/buildx#1903](https://github.com/docker/buildx/pull/1903){:target="blank" rel="noopener"} + [docker/buildx#1903](https://github.com/docker/buildx/pull/1903) - Fix a regression where `--cgroup-parent` option had no effect during build. - [docker/buildx#1913](https://github.com/docker/buildx/pull/1913){:target="blank" rel="noopener"} + [docker/buildx#1913](https://github.com/docker/buildx/pull/1913) - Fix a regression where valid docker contexts could fail buildx builder name - validation. [docker/buildx#1879](https://github.com/docker/buildx/pull/1879){:target="blank" rel="noopener"} + validation. [docker/buildx#1879](https://github.com/docker/buildx/pull/1879) - Fix a possible panic when terminal is resized during the build. - [docker/buildx#1929](https://github.com/docker/buildx/pull/1929){:target="blank" rel="noopener"} + [docker/buildx#1929](https://github.com/docker/buildx/pull/1929) ## 0.11.0 -{% include release-date.html date="2023-06-13" %} +{{< release-date date="2023-06-13" >}} The full release note for this release is available -[on GitHub](https://github.com/docker/buildx/releases/tag/v0.11.0){:target="blank" rel="noopener"}. +[on GitHub](https://github.com/docker/buildx/releases/tag/v0.11.0). ### New - Bake now supports [matrix builds](../build/bake/reference.md#targetmatrix). The new matrix field on `target` lets you create multiple similar targets to - remove duplication in bake files. [docker/buildx#1690](https://github.com/docker/buildx/pull/1690){:target="blank" rel="noopener"} + remove duplication in bake files. [docker/buildx#1690](https://github.com/docker/buildx/pull/1690) - New experimental `--detach` flag for running builds in detached mode. - [docker/buildx#1296](https://github.com/docker/buildx/pull/1296){:target="blank" rel="noopener"}, - [docker/buildx#1620](https://github.com/docker/buildx/pull/1620){:target="blank" rel="noopener"}, - [docker/buildx#1614](https://github.com/docker/buildx/pull/1614){:target="blank" rel="noopener"}, - [docker/buildx#1737](https://github.com/docker/buildx/pull/1737){:target="blank" rel="noopener"}, - [docker/buildx#1755](https://github.com/docker/buildx/pull/1755){:target="blank" rel="noopener"} -- New experimental [debug monitor mode](https://github.com/docker/buildx/blob/v0.11.0-rc1/docs/guides/debugging.md){:target="blank" rel="noopener"} + [docker/buildx#1296](https://github.com/docker/buildx/pull/1296), + [docker/buildx#1620](https://github.com/docker/buildx/pull/1620), + [docker/buildx#1614](https://github.com/docker/buildx/pull/1614), + [docker/buildx#1737](https://github.com/docker/buildx/pull/1737), + [docker/buildx#1755](https://github.com/docker/buildx/pull/1755) +- New experimental [debug monitor mode](https://github.com/docker/buildx/blob/v0.11.0-rc1/docs/guides/debugging.md) that lets you start a debug session in your builds. - [docker/buildx#1626](https://github.com/docker/buildx/pull/1626){:target="blank" rel="noopener"}, - [docker/buildx#1640](https://github.com/docker/buildx/pull/1640){:target="blank" rel="noopener"} + [docker/buildx#1626](https://github.com/docker/buildx/pull/1626), + [docker/buildx#1640](https://github.com/docker/buildx/pull/1640) - New [`EXPERIMENTAL_BUILDKIT_SOURCE_POLICY` environment variable](./building/env-vars.md#experimental_buildkit_source_policy) for applying a BuildKit source policy file. - [docker/buildx#1628](https://github.com/docker/buildx/pull/1628){:target="blank" rel="noopener"} + [docker/buildx#1628](https://github.com/docker/buildx/pull/1628) ### Bug fixes and enhancements - `--load` now supports loading multi-platform images when the containerd image store is enabled. - [docker/buildx#1813](https://github.com/docker/buildx/pull/1813){:target="blank" rel="noopener"} + [docker/buildx#1813](https://github.com/docker/buildx/pull/1813) - Build progress output now displays the name of the builder being used. - [docker/buildx#1177](https://github.com/docker/buildx/pull/1177){:target="blank" rel="noopener"} + [docker/buildx#1177](https://github.com/docker/buildx/pull/1177) - Bake now supports detecting `compose.{yml,yaml}` files. - [docker/buildx#1752](https://github.com/docker/buildx/pull/1752){:target="blank" rel="noopener"} + [docker/buildx#1752](https://github.com/docker/buildx/pull/1752) - Bake now supports new compose build keys `dockerfile_inline` and `additional_contexts`. - [docker/buildx#1784](https://github.com/docker/buildx/pull/1784){:target="blank" rel="noopener"} + [docker/buildx#1784](https://github.com/docker/buildx/pull/1784) - Bake now supports replace HCL function. - [docker/buildx#1720](https://github.com/docker/buildx/pull/1720){:target="blank" rel="noopener"} + [docker/buildx#1720](https://github.com/docker/buildx/pull/1720) - Bake now allows merging multiple similar attestation parameters into a single parameter to allow overriding with a single global value. - [docker/buildx#1699](https://github.com/docker/buildx/pull/1699){:target="blank" rel="noopener"} + [docker/buildx#1699](https://github.com/docker/buildx/pull/1699) - Initial support for shell completion. - [docker/buildx#1727](https://github.com/docker/buildx/pull/1727){:target="blank" rel="noopener"} + [docker/buildx#1727](https://github.com/docker/buildx/pull/1727) - BuildKit versions now correctly display in `buildx ls` and `buildx inspect` for builders using the `docker` driver. - [docker/buildx#1552](https://github.com/docker/buildx/pull/1552){:target="blank" rel="noopener"} + [docker/buildx#1552](https://github.com/docker/buildx/pull/1552) - Display additional builder node details in buildx inspect view. - [docker/buildx#1440](https://github.com/docker/buildx/pull/1440){:target="blank" rel="noopener"}, - [docker/buildx#1854](https://github.com/docker/buildx/pull/1874){:target="blank" rel="noopener"} + [docker/buildx#1440](https://github.com/docker/buildx/pull/1440), + [docker/buildx#1854](https://github.com/docker/buildx/pull/1874) - Builders using the `remote` driver allow using TLS without proving its own key/cert (if BuildKit remote is configured to support it) - [docker/buildx#1693](https://github.com/docker/buildx/pull/1693){:target="blank" rel="noopener"} + [docker/buildx#1693](https://github.com/docker/buildx/pull/1693) - Builders using the `kubernetes` driver support a new `serviceaccount` option, which sets the `serviceAccountName` of the Kubernetes pod. - [docker/buildx#1597](https://github.com/docker/buildx/pull/1597){:target="blank" rel="noopener"} + [docker/buildx#1597](https://github.com/docker/buildx/pull/1597) - Builders using the `kubernetes` driver support the `proxy-url` option in the kubeconfig file. - [docker/buildx#1780](https://github.com/docker/buildx/pull/1780){:target="blank" rel="noopener"} + [docker/buildx#1780](https://github.com/docker/buildx/pull/1780) - Builders using the `kubernetes` are now automatically assigned a node name if no name is explicitly provided. - [docker/buildx#1673](https://github.com/docker/buildx/pull/1673){:target="blank" rel="noopener"} + [docker/buildx#1673](https://github.com/docker/buildx/pull/1673) - Fix invalid path when writing certificates for `docker-container` driver on Windows. - [docker/buildx#1831](https://github.com/docker/buildx/pull/1831){:target="blank" rel="noopener"} + [docker/buildx#1831](https://github.com/docker/buildx/pull/1831) - Fix bake failure when remote bake file is accessed using SSH. - [docker/buildx#1711](https://github.com/docker/buildx/pull/1711){:target="blank" rel="noopener"}, - [docker/buildx#1734](https://github.com/docker/buildx/pull/1734){:target="blank" rel="noopener"} + [docker/buildx#1711](https://github.com/docker/buildx/pull/1711), + [docker/buildx#1734](https://github.com/docker/buildx/pull/1734) - Fix bake failure when remote bake context is incorrectly resolved. - [docker/buildx#1783](https://github.com/docker/buildx/pull/1783){:target="blank" rel="noopener"} + [docker/buildx#1783](https://github.com/docker/buildx/pull/1783) - Fix path resolution of `BAKE_CMD_CONTEXT` and `cwd://` paths in bake contexts. - [docker/buildx#1840](https://github.com/docker/buildx/pull/1840){:target="blank" rel="noopener"} + [docker/buildx#1840](https://github.com/docker/buildx/pull/1840) - Fix mixed OCI and Docker media types when creating images using `buildx imagetools create`. - [docker/buildx#1797](https://github.com/docker/buildx/pull/1797){:target="blank" rel="noopener"} + [docker/buildx#1797](https://github.com/docker/buildx/pull/1797) - Fix mismatched image id between `--iidfile` and `-q`. - [docker/buildx#1844](https://github.com/docker/buildx/pull/1844){:target="blank" rel="noopener"} + [docker/buildx#1844](https://github.com/docker/buildx/pull/1844) - Fix AWS authentication when mixing static creds and IAM profiles. - [docker/buildx#1816](https://github.com/docker/buildx/pull/1816){:target="blank" rel="noopener"} + [docker/buildx#1816](https://github.com/docker/buildx/pull/1816) ## 0.10.4 -{% include release-date.html date="2023-03-06" %} +{{< release-date date="2023-03-06" >}} -{% include buildx-v0.10-disclaimer.md %} +{{< include "buildx-v0.10-disclaimer.md" >}} ### Bug fixes and enhancements @@ -133,9 +133,9 @@ The full release note for this release is available ## 0.10.3 -{% include release-date.html date="2023-02-16" %} +{{< release-date date="2023-02-16" >}} -{% include buildx-v0.10-disclaimer.md %} +{{< include "buildx-v0.10-disclaimer.md" >}} ### Bug fixes and enhancements @@ -147,9 +147,9 @@ The full release note for this release is available ## 0.10.2 -{% include release-date.html date="2023-01-30" %} +{{< release-date date="2023-01-30" >}} -{% include buildx-v0.10-disclaimer.md %} +{{< include "buildx-v0.10-disclaimer.md" >}} ### Bug fixes and enhancements @@ -161,9 +161,9 @@ The full release note for this release is available ## 0.10.1 -{% include release-date.html date="2023-01-27" %} +{{< release-date date="2023-01-27" >}} -{% include buildx-v0.10-disclaimer.md %} +{{< include "buildx-v0.10-disclaimer.md" >}} ### Bug fixes and enhancements @@ -178,9 +178,9 @@ The full release note for this release is available ## 0.10.0 -{% include release-date.html date="2023-01-10" %} +{{< release-date date="2023-01-10" >}} -{% include buildx-v0.10-disclaimer.md %} +{{< include "buildx-v0.10-disclaimer.md" >}} ### New @@ -208,7 +208,7 @@ The full release note for this release is available where you can reuse the values from other target definitions. {% include github_issue.md repo="docker/buildx" number="1434" %} * Buildx will now automatically forward `SOURCE_DATE_EPOCH` environment variable if it is defined in your environment. This feature is meant to be used with - updated [reproducible builds](https://github.com/moby/buildkit/blob/master/docs/build-repro.md){:target="blank" rel="noopener" class=""} + updated [reproducible builds](https://github.com/moby/buildkit/blob/master/docs/build-repro.md) support in BuildKit v0.11.0+. {% include github_issue.md repo="docker/buildx" number="1482" %} * Buildx now remembers the last activity for a builder for better organization of builder instances. {% include github_issue.md repo="docker/buildx" number="1439" %} @@ -246,7 +246,7 @@ The full release note for this release is available ## 0.9.1 -{% include release-date.html date="2022-08-18" %} +{{< release-date date="2022-08-18" >}} ### Bug fixes and enhancements @@ -254,11 +254,11 @@ The full release note for this release is available * Fixed a regression when building Compose files that contain services without a build block {% include github_issue.md repo="docker/buildx" number="1277" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.9.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.9.1). ## 0.9.0 -{% include release-date.html date="2022-08-17" %} +{{< release-date date="2022-08-17" >}} ### New @@ -349,11 +349,11 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Fix image tools commands not handling `--builder` flag correctly {% include github_issue.md repo="docker/buildx" number="1067" %} * Fix using custom image together with rootless option {% include github_issue.md repo="docker/buildx" number="1063" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.9.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.9.0). ## 0.8.2 -{% include release-date.html date="2022-04-04" %} +{{< release-date date="2022-04-04" >}} ### Updates * Update Compose spec used by `buildx bake` to v1.2.1 to fix parsing ports definition {% include github_issue.md repo="docker/buildx" number="1033" %} @@ -362,22 +362,22 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Fix possible crash on handling progress streams from BuildKit v0.10 {% include github_issue.md repo="docker/buildx" number="1042" %} * Fix parsing groups in `buildx bake` when already loaded by a parent group {% include github_issue.md repo="docker/buildx" number="1021" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.8.2){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.8.2). ## 0.8.1 -{% include release-date.html date="2022-03-21" %} +{{< release-date date="2022-03-21" >}} ### Bug fixes and enhancements * Fix possible panic on handling build context scanning errors {% include github_issue.md repo="docker/buildx" number="1005" %} * Allow `.` on Compose target names in `buildx bake` for backward compatibility {% include github_issue.md repo="docker/buildx" number="1018" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.8.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.8.1). ## 0.8.0 -{% include release-date.html date="2022-03-09" %} +{{< release-date date="2022-03-09" >}} ### New @@ -423,22 +423,22 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Fix printing default group on Bake files {% include github_issue.md repo="docker/buildx" number="884" %} * Fix `UsernsMode` when using rootless container {% include github_issue.md repo="docker/buildx" number="887" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.8.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.8.0). ## 0.7.1 -{% include release-date.html date="2021-08-25" %} +{{< release-date date="2021-08-25" >}} ### Fixes * Fix issue with matching exclude rules in `.dockerignore` {% include github_issue.md repo="docker/buildx" number="858" %} * Fix `bake --print` JSON output for current group {% include github_issue.md repo="docker/buildx" number="857" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.7.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.7.1). ## 0.7.0 -{% include release-date.html date="2021-11-10" %} +{{< release-date date="2021-11-10" >}} ### New features @@ -479,23 +479,23 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Unsupported build flags now show a warning {% include github_issue.md repo="docker/buildx" number="810" %} * Fix reporting error details in some OpenTelemetry traces {% include github_issue.md repo="docker/buildx" number="812" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.7.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.7.0). ## 0.6.3 -{% include release-date.html date="2021-08-30" %} +{{< release-date date="2021-08-30" >}} ### Fixes * Fix BuildKit state volume location for Windows clients {% include github_issue.md repo="docker/buildx" number="751" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.3){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.3). ## 0.6.2 -{% include release-date.html date="2021-08-21" %} +{{< release-date date="2021-08-21" >}} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.2){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.2). ### Fixes @@ -503,7 +503,7 @@ For more details, see the complete release notes in the [Buildx GitHub repositor ## 0.6.1 -{% include release-date.html date="2021-07-30" %} +{{< release-date date="2021-07-30" >}} ### Enhancements @@ -514,11 +514,11 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Duplicate progress env var {% include github_issue.md repo="docker/buildx" number="693" %} * Should ignore nil client {% include github_issue.md repo="docker/buildx" number="686" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.1). ## 0.6.0 -{% include release-date.html date="2021-07-16" %} +{{< release-date date="2021-07-16" >}} ### New features @@ -539,7 +539,7 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Bake allows variables across multiple files {% include github_issue.md repo="docker/buildx" number="538" %} * New quiet mode has been added to progress printer {% include github_issue.md repo="docker/buildx" number="558" %} * `kubernetes` driver now supports defining resources/limits {% include github_issue.md repo="docker/buildx" number="618" %} -* Buildx binaries can now be accessed through [buildx-bin](https://hub.docker.com/r/docker/buildx-bin){:target="blank" rel="noopener" class=""} +* Buildx binaries can now be accessed through [buildx-bin](https://hub.docker.com/r/docker/buildx-bin) Docker image {% include github_issue.md repo="docker/buildx" number="656" %} ### Enhancements @@ -563,22 +563,22 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * `imagetools create` command now correctly merges JSON descriptor with old one {% include github_issue.md repo="docker/buildx" number="592" %} * Fix building with `--network=none` not requiring extra security entitlements {% include github_issue.md repo="docker/buildx" number="531" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.6.0). ## 0.5.1 -{% include release-date.html date="2020-12-15" %} +{{< release-date date="2020-12-15" >}} ### Fixes * Fix regression on setting `--platform` on `buildx create` outside `kubernetes` driver {% include github_issue.md repo="docker/buildx" number="475" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.5.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.5.1). ## 0.5.0 -{% include release-date.html date="2020-12-15" %} +{{< release-date date="2020-12-15" >}} ### New features @@ -615,11 +615,11 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Handle lowercase Dockerfile name as a fallback for backward compatibility {% include github_issue.md repo="docker/buildx" number="444" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.5.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.5.0). ## 0.4.2 -{% include release-date.html date="2020-08-22" %} +{{< release-date date="2020-08-22" >}} ### New features @@ -636,22 +636,22 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Ensure `--builder` is wired from root options {% include github_issue.md repo="docker/buildx" number="321" %} * Remove warning for multi-platform iidfile {% include github_issue.md repo="docker/buildx" number="351" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.4.2){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.4.2). ## 0.4.1 -{% include release-date.html date="2020-05-01" %} +{{< release-date date="2020-05-01" >}} ### Fixes * Fix regression on flag parsing {% include github_issue.md repo="docker/buildx" number="268" %} * Fix using pull and no-cache keys in HCL targets {% include github_issue.md repo="docker/buildx" number="268" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.4.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.4.1). ## 0.4.0 -{% include release-date.html date="2020-04-30" %} +{{< release-date date="2020-04-30" >}} ### New features @@ -667,11 +667,11 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Bake now supports wildcard overrides for multiple targets {% include github_issue.md repo="docker/buildx" number="164" %} * Container driver allows setting environment variables via `driver-opt` {% include github_issue.md repo="docker/buildx" number="170" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.4.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.4.0). ## 0.3.1 -{% include release-date.html date="2019-09-27" %} +{{< release-date date="2019-09-27" >}} ### Enhancements @@ -683,11 +683,11 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Running Bake with multiple Compose files now merges targets correctly {% include github_issue.md repo="docker/buildx" number="134" %} * Fix bug when building a Dockerfile from stdin (`build -f -`) {% include github_issue.md repo="docker/buildx" number="153" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.3.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.3.1). ## 0.3.0 -{% include release-date.html date="2019-08-02" %} +{{< release-date date="2019-08-02" >}} ### New features @@ -705,21 +705,21 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Fix bug where `--build-arg foo` would not read `foo` from environment {% include github_issue.md repo="docker/buildx" number="116" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.3.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.3.0). ## 0.2.2 -{% include release-date.html date="2019-05-30" %} +{{< release-date date="2019-05-30" >}} ### Enhancements * Change Compose file handling to require valid service specifications {% include github_issue.md repo="docker/buildx" number="87" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.2.2){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.2.2). ## 0.2.1 -{% include release-date.html date="2019-05-25" %} +{{< release-date date="2019-05-25" >}} ### New features @@ -735,14 +735,14 @@ For more details, see the complete release notes in the [Buildx GitHub repositor * Fix parsing target from compose files {% include github_issue.md repo="docker/buildx" number="53" %} -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.2.1){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.2.1). ## 0.2.0 -{% include release-date.html date="2019-04-25" %} +{{< release-date date="2019-04-25" >}} ### New features * First release -For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.2.0){:target="blank" rel="noopener" class=""}. +For more details, see the complete release notes in the [Buildx GitHub repository](https://github.com/docker/buildx/releases/tag/v0.2.0). \ No newline at end of file diff --git a/content/cloud/aci-integration.md b/content/cloud/aci-integration.md index 17dbbf5303..d5a520bf8e 100644 --- a/content/cloud/aci-integration.md +++ b/content/cloud/aci-integration.md @@ -1,13 +1,15 @@ --- title: Deploying Docker containers on Azure description: Deploying Docker containers on Azure -keywords: Docker, Azure, Integration, ACI, context, Compose, cli, deploy, containers, cloud -redirect_from: - - /engine/context/aci-integration/ +keywords: Docker, Azure, Integration, ACI, context, Compose, cli, deploy, containers, + cloud toc_min: 1 toc_max: 2 +aliases: +- /engine/context/aci-integration/ --- -{% include aci-ecs-eol.md %} + +{{< include "aci-ecs-eol.md" >}} ## Overview @@ -32,7 +34,7 @@ To deploy Docker containers on Azure, you must meet the following requirements: Alternatively, install the [Docker Compose CLI for Linux](#install-the-docker-compose-cli-on-linux). -2. Ensure you have an Azure subscription. You can get started with an [Azure free account](https://aka.ms/AA8r2pj){: target="_blank" rel="noopener" class="_"}. +2. Ensure you have an Azure subscription. You can get started with an [Azure free account](https://aka.ms/AA8r2pj). ## Run Docker containers on ACI @@ -50,8 +52,8 @@ $ docker login azure ``` This opens your web browser and prompts you to enter your Azure login credentials. -If the Docker CLI cannot open a browser, it will fall back to the [Azure device code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code){:target="_blank" rel="noopener" class="_"} and lets you connect manually. -Note that the [Azure command line](https://docs.microsoft.com/en-us/cli/azure/){:target="_blank" rel="noopener" class="_"} login is separated from the Docker CLI Azure login. +If the Docker CLI cannot open a browser, it will fall back to the [Azure device code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code) and lets you connect manually. +Note that the [Azure command line](https://docs.microsoft.com/en-us/cli/azure/) login is separated from the Docker CLI Azure login. Alternatively, you can log in without interaction (typically in scripts or continuous integration scenarios), using an Azure Service @@ -391,7 +393,7 @@ $ curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/inst ### Manual install You can download the Docker ACI Integration CLI from the -[latest release](https://github.com/docker/compose-cli/releases/latest){: target="_blank" rel="noopener" class="_"} page. +[latest release](https://github.com/docker/compose-cli/releases/latest) page. You will then need to make it executable: @@ -469,4 +471,4 @@ $ sudo rm /usr/local/bin/docker /usr/local/bin/com.docker.cli ## Feedback -Thank you for trying out Docker Azure Integration. Your feedback is very important to us. Let us know your feedback by creating an issue in the [compose-cli](https://github.com/docker/compose-cli){: target="_blank" rel="noopener" class="_"} GitHub repository. +Thank you for trying out Docker Azure Integration. Your feedback is very important to us. Let us know your feedback by creating an issue in the [compose-cli](https://github.com/docker/compose-cli) GitHub repository. \ No newline at end of file diff --git a/content/cloud/ecs-integration.md b/content/cloud/ecs-integration.md index 49cf89da43..d2e8e2f147 100644 --- a/content/cloud/ecs-integration.md +++ b/content/cloud/ecs-integration.md @@ -1,13 +1,15 @@ --- title: Deploying Docker containers on ECS description: Deploying Docker containers on ECS -keywords: Docker, AWS, ECS, Integration, context, Compose, cli, deploy, containers, cloud -redirect_from: - - /engine/context/ecs-integration/ +keywords: Docker, AWS, ECS, Integration, context, Compose, cli, deploy, containers, + cloud toc_min: 1 toc_max: 2 +aliases: +- /engine/context/ecs-integration/ --- -{% include aci-ecs-eol.md %} + +{{< include "aci-ecs-eol.md" >}} ## Overview @@ -102,7 +104,7 @@ Run the `docker context create ecs myecscontext` command to create an Amazon ECS context named `myecscontext`. If you have already installed and configured the AWS CLI, the setup command lets you select an existing AWS profile to connect to Amazon. Otherwise, you can create a new profile by passing an -[AWS access key ID and a secret access key](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys){: target="_blank" rel="noopener" class="_"}. +[AWS access key ID and a secret access key](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys). Finally, you can configure your ECS context to retrieve AWS credentials by `AWS_*` environment variables, which is a common way to integrate with third-party tools and single-sign-on providers. @@ -139,9 +141,9 @@ stop a full Compose application. You can also specify a name for the Compose application using the `--project-name` flag during deployment. If no name is specified, a name will be derived from the working directory. -Docker ECS integration converts the Compose application model into a set of AWS resources, described as a [CloudFormation](https://aws.amazon.com/cloudformation/){: target="_blank" rel="noopener" class="_"} template. The actual mapping is described in [technical documentation](https://github.com/docker/compose-cli/blob/main/docs/ecs-architecture.md){: target="_blank" rel="noopener" class="_"}. +Docker ECS integration converts the Compose application model into a set of AWS resources, described as a [CloudFormation](https://aws.amazon.com/cloudformation/) template. The actual mapping is described in [technical documentation](https://github.com/docker/compose-cli/blob/main/docs/ecs-architecture.md). You can review the generated template using `docker compose convert` command, and follow CloudFormation applying this model within -[AWS web console](https://console.aws.amazon.com/cloudformation/home){: target="_blank" rel="noopener" class="_"} when you run `docker compose up`, in addition to CloudFormation events being displayed +[AWS web console](https://console.aws.amazon.com/cloudformation/home) when you run `docker compose up`, in addition to CloudFormation events being displayed in your terminal. - You can view services created for the Compose application on Amazon ECS and @@ -203,11 +205,11 @@ default behavior is to keep logs forever. You can also pass `awslogs` parameters to your container as standard -Compose file `logging.driver_opts` elements. See [AWS documentation](https://docs.amazonaws.cn/en_us/AmazonECS/latest/developerguide/using_awslogs.html){:target="_blank" rel="noopener" class="_"} for details on available log driver options. +Compose file `logging.driver_opts` elements. See [AWS documentation](https://docs.amazonaws.cn/en_us/AmazonECS/latest/developerguide/using_awslogs.html) for details on available log driver options. ## Private Docker images -The Docker Compose CLI automatically configures authorization so you can pull private images from the Amazon ECR registry on the same AWS account. To pull private images from another registry, including Docker Hub, you’ll have to create a Username + Password (or a Username + Token) secret on the [AWS Secrets Manager service](https://docs.aws.amazon.com/secretsmanager/){: target="_blank" rel="noopener" class="_"}. +The Docker Compose CLI automatically configures authorization so you can pull private images from the Amazon ECR registry on the same AWS account. To pull private images from another registry, including Docker Hub, you’ll have to create a Username + Password (or a Username + Token) secret on the [AWS Secrets Manager service](https://docs.aws.amazon.com/secretsmanager/). For your convenience, the Docker Compose CLI offers the `docker secret` command, so you can manage secrets created on AWS SMS without having to install the AWS CLI. @@ -248,7 +250,7 @@ Service-to-service communication is implemented transparently by default, so you ### Service names -Services are registered automatically by the Docker Compose CLI on [AWS Cloud Map](https://docs.aws.amazon.com/cloud-map/latest/dg/what-is-cloud-map.html){: target="_blank" rel="noopener" class="_"} during application deployment. They are declared as fully qualified domain names of the form: `..local`. +Services are registered automatically by the Docker Compose CLI on [AWS Cloud Map](https://docs.aws.amazon.com/cloud-map/latest/dg/what-is-cloud-map.html) during application deployment. They are declared as fully qualified domain names of the form: `..local`. Services can retrieve their dependencies using Compose service names (as they do when deploying locally with docker-compose), or optionally use the fully qualified names. @@ -261,11 +263,11 @@ Services can retrieve their dependencies using Compose service names (as they do Services get concurrently scheduled on ECS when a Compose file is deployed. AWS Cloud Map introduces an initial delay for DNS service to be able to resolve your services domain names. Your code needs to support this delay by waiting for dependent services to be ready, or by adding a wait-script as the entrypoint to your Docker image, as documented in [Control startup order](../compose/startup-order.md). Note that this need to wait for dependent services in your Compose application also exists when deploying locally with docker-compose, but the delay is typically shorter. Issues might become more visible when deploying to ECS if services do not wait for their dependencies to be available. -Alternatively, you can use the [depends_on](https://github.com/compose-spec/compose-spec/blob/master/spec.md#depends_on){: target="_blank" rel="noopener" class="_"} feature of the Compose file format. By doing this, dependent service will be created first, and application deployment will wait for it to be up and running before starting the creation of the dependent services. +Alternatively, you can use the [depends_on](https://github.com/compose-spec/compose-spec/blob/master/spec.md#depends_on) feature of the Compose file format. By doing this, dependent service will be created first, and application deployment will wait for it to be up and running before starting the creation of the dependent services. ### Service isolation -Service isolation is implemented by the [Security Groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html){: target="_blank" rel="noopener" class="_"} rules, allowing services sharing a common Compose file “network” to communicate together using their Compose service names. +Service isolation is implemented by the [Security Groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html) rules, allowing services sharing a common Compose file “network” to communicate together using their Compose service names. ## Volumes @@ -443,7 +445,7 @@ services: ## Tuning the CloudFormation template -The Docker Compose CLI relies on [Amazon CloudFormation](https://docs.aws.amazon.com/cloudformation/){: target="_blank" rel="noopener" class="_"} to manage the application deployment. To get more control on the created resources, you can use `docker compose convert` to generate a CloudFormation stack file from your Compose file. This allows you to inspect resources it defines, or customize the template for your needs, and then apply the template to AWS using the AWS CLI, or the AWS web console. +The Docker Compose CLI relies on [Amazon CloudFormation](https://docs.aws.amazon.com/cloudformation/) to manage the application deployment. To get more control on the created resources, you can use `docker compose convert` to generate a CloudFormation stack file from your Compose file. This allows you to inspect resources it defines, or customize the template for your needs, and then apply the template to AWS using the AWS CLI, or the AWS web console. Once you have identified the changes required to your CloudFormation template, you can include _overlays_ in your Compose file that will be automatically applied on `compose up`. An _overlay_ is a yaml object that uses the same CloudFormation template data structure as the one generated by ECS integration, but only contains attributes to @@ -456,7 +458,7 @@ their own URL-based HealthCheck mechanism so traffic gets routed. As the Compose abstraction (yet), the default one is applied, which queries your service under `/` expecting HTTP status code `200`. -You can tweak this behavior using a cloudformation overlay by following the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-targetgroup.html){:target="_blank" rel="noopener" class="_"} for +You can tweak this behavior using a cloudformation overlay by following the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-targetgroup.html) for configuration reference: ```yaml @@ -511,7 +513,7 @@ services: - "80:80" ``` -If your AWS account does not have [permissions](https://github.com/docker/ecs-plugin/blob/master/docs/requirements.md#permissions){: target="_blank" rel="noopener" class="_"} to create such resources, or if you want to manage these yourself, you can use the following custom Compose extensions: +If your AWS account does not have [permissions](https://github.com/docker/ecs-plugin/blob/master/docs/requirements.md#permissions) to create such resources, or if you want to manage these yourself, you can use the following custom Compose extensions: - Use `x-aws-cluster` as a top-level element in your Compose file to set the ID of an ECS cluster when deploying a Compose application. Otherwise, a @@ -618,8 +620,8 @@ $ curl -L https://raw.githubusercontent.com/docker/compose-cli/main/scripts/inst **What does the error `this tool requires the "new ARN resource ID format"` mean?** -This error message means that your account requires the new ARN resource ID format for ECS. To learn more, see [Migrating your Amazon ECS deployment to the new ARN and resource ID format](https://aws.amazon.com/blogs/compute/migrating-your-amazon-ecs-deployment-to-the-new-arn-and-resource-id-format-2/){: target="_blank" rel="noopener" class="_"}. +This error message means that your account requires the new ARN resource ID format for ECS. To learn more, see [Migrating your Amazon ECS deployment to the new ARN and resource ID format](https://aws.amazon.com/blogs/compute/migrating-your-amazon-ecs-deployment-to-the-new-arn-and-resource-id-format-2/). ## Feedback -Thank you for trying out the Docker Compose CLI. Your feedback is very important to us. Let us know your feedback by creating an issue in the [Compose CLI](https://github.com/docker/compose-cli){: target="_blank" rel="noopener" class="_"} GitHub repository. +Thank you for trying out the Docker Compose CLI. Your feedback is very important to us. Let us know your feedback by creating an issue in the [Compose CLI](https://github.com/docker/compose-cli) GitHub repository. \ No newline at end of file diff --git a/content/compose/_index.md b/content/compose/_index.md index 51ee880776..61ba1c6b9b 100644 --- a/content/compose/_index.md +++ b/content/compose/_index.md @@ -1,42 +1,46 @@ --- -description: Learn how to use Docker Compose to define and run multi-container applications with this detailed introduction to the tool. -keywords: docker compose, docker-compose, docker compose command, docker compose files, docker compose documentation, using docker compose, compose container, docker compose service +description: Learn how to use Docker Compose to define and run multi-container applications + with this detailed introduction to the tool. +keywords: docker compose, docker-compose, docker compose command, docker compose files, + docker compose documentation, using docker compose, compose container, docker compose + service title: Docker Compose overview -redirect_from: - - /compose/cli-command/ - - /compose/networking/swarm/ - - /compose/overview/ - - /compose/swarm/ - - /compose/completion/ grid: - - title: "Install Compose" - description: "Follow the instructions on how to install Docker Compose." - icon: "download" - link: "/compose/install" - - title: "Try Compose" - description: "Learn the key concepts of Docker Compose whilst building a simple Python web application." - icon: "explore" - link: "/compose/gettingstarted" - - title: "View the release notes" - description: "Find out about the latest enhancements and bug fixes." - icon: "note_add" - link: "/compose/release-notes" - - title: "Understand key features of Compose" - description: "Understand its key features and explore common use cases." - icon: "help" - link: "/compose/features-uses/" - - title: "Explore the Compose file reference" - description: - "Find information on defining services, networks, and volumes for a Docker application." - icon: "all_inbox" - link: "/compose/compose-file" - - title: "Browse common FAQs" - description: - "Explore general FAQs and find out how to give feedback." - icon: "sms" - link: "/compose/faq" +- title: Install Compose + description: Follow the instructions on how to install Docker Compose. + icon: download + link: /compose/install +- title: Try Compose + description: Learn the key concepts of Docker Compose whilst building a simple Python + web application. + icon: explore + link: /compose/gettingstarted +- title: View the release notes + description: Find out about the latest enhancements and bug fixes. + icon: note_add + link: /compose/release-notes +- title: Understand key features of Compose + description: Understand its key features and explore common use cases. + icon: help + link: /compose/features-uses/ +- title: Explore the Compose file reference + description: Find information on defining services, networks, and volumes for a + Docker application. + icon: all_inbox + link: /compose/compose-file +- title: Browse common FAQs + description: Explore general FAQs and find out how to give feedback. + icon: sms + link: /compose/faq +aliases: +- /compose/cli-command/ +- /compose/networking/swarm/ +- /compose/overview/ +- /compose/swarm/ +- /compose/completion/ --- -{% include compose-eol.md %} + +{{< include "compose-eol.md" >}} Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application's services. @@ -58,4 +62,4 @@ The key features of Compose that make it effective are: * [Only recreate containers that have changed](features-uses.md#only-recreate-containers-that-have-changed) * [Support variables and moving a composition between environments](features-uses.md#supports-variables-and-moving-a-composition-between-environments) -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/compose/compose-file/_index.md b/content/compose/compose-file/_index.md index 18e9f37c0a..b45fdb40b5 100644 --- a/content/compose/compose-file/_index.md +++ b/content/compose/compose-file/_index.md @@ -1,54 +1,58 @@ --- -description: Find the latest recommended version of the Docker Compose file format for defining multi-container applications. -keywords: docker compose file, docker compose yml, docker compose reference, docker compose cmd, docker compose user, docker compose image, yaml spec, docker compose syntax, yaml specification, docker compose specification -redirect_from: -- /compose/yaml/ -- /compose/compose-file/compose-file-v1/ +description: Find the latest recommended version of the Docker Compose file format + for defining multi-container applications. +keywords: docker compose file, docker compose yml, docker compose reference, docker + compose cmd, docker compose user, docker compose image, yaml spec, docker compose + syntax, yaml specification, docker compose specification title: Overview toc_max: 4 toc_min: 1 grid: - - title: Status of the Specification - description: Read about the status of the specification. - icon: select_check_box - link: /compose/compose-file/01-status/ - - title: The Compose application model - description: Learn about the Compose application model. - icon: storage - link: /compose/compose-file/02-model/ - - title: The Compose file - description: Understand the Compose file. - icon: web_stories - link: /compose/compose-file/03-compose-file/ - - title: Version and name top-level element - description: Understand version and name attributes for Compose. - icon: feed - link: /compose/compose-file/04-version-and-name/ - - title: Services top-level element - description: Explore all services attributes for Compose. - icon: construction - link: /compose/compose-file/05-services/ - - title: Networks top-level element - description: Find all networks attributes for Compose. - icon: lan - link: /compose/compose-file/06-networks/ - - title: Volumes top-level element - description: Explore all volumes attributes for Compose. - icon: database - link: /compose/compose-file/07-volumes/ - - title: Configs top-level element - description: Find out about configs in Compose. - icon: settings_suggest - link: /compose/compose-file/08-configs/ - - title: Secrets top-level element - description: Learn about secrets in Compose. - icon: lock - link: /compose/compose-file/09-secrets/ +- title: Status of the Specification + description: Read about the status of the specification. + icon: select_check_box + link: /compose/compose-file/01-status/ +- title: The Compose application model + description: Learn about the Compose application model. + icon: storage + link: /compose/compose-file/02-model/ +- title: The Compose file + description: Understand the Compose file. + icon: web_stories + link: /compose/compose-file/03-compose-file/ +- title: Version and name top-level element + description: Understand version and name attributes for Compose. + icon: feed + link: /compose/compose-file/04-version-and-name/ +- title: Services top-level element + description: Explore all services attributes for Compose. + icon: construction + link: /compose/compose-file/05-services/ +- title: Networks top-level element + description: Find all networks attributes for Compose. + icon: lan + link: /compose/compose-file/06-networks/ +- title: Volumes top-level element + description: Explore all volumes attributes for Compose. + icon: database + link: /compose/compose-file/07-volumes/ +- title: Configs top-level element + description: Find out about configs in Compose. + icon: settings_suggest + link: /compose/compose-file/08-configs/ +- title: Secrets top-level element + description: Learn about secrets in Compose. + icon: lock + link: /compose/compose-file/09-secrets/ +aliases: +- /compose/yaml/ +- /compose/compose-file/compose-file-v1/ --- + >**New to Compose?** > > Find more information about the [key features and use cases of Docker Compose](../features-uses.md) or [try the get started guide](../gettingstarted.md). -{: .tip} +{ .tip } The [Compose Specification](https://github.com/compose-spec/compose-spec/blob/master/spec.md) is the latest and recommended version of the Compose file format. It helps you define a [Compose file](03-compose-file.md) which is used to configure your Docker application’s services, networks, volumes, and more. @@ -63,4 +67,4 @@ Legacy versions 2.x and 3.x of the Compose file format were merged into the Comp Use the following links to navigate key sections of the Compose Specification. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/compose/compose-file/compose-file-v2.md b/content/compose/compose-file/compose-file-v2.md index f68a05615b..ba75110461 100644 --- a/content/compose/compose-file/compose-file-v2.md +++ b/content/compose/compose-file/compose-file-v2.md @@ -5,7 +5,8 @@ title: Compose file version 2 reference toc_max: 4 toc_min: 1 --- -{% include compose-eol.md %} + +{{< include "compose-eol.md" >}} ## Reference and guidelines @@ -17,7 +18,7 @@ There are several versions of the Compose file format – 1, 2, 2.x, and 3.x. Th table below is a quick look. For full details on what each version includes and how to upgrade, see **[About versions and upgrading](compose-versioning.md)**. -{% include content/compose-matrix.md %} +{{< include "content/compose-matrix.md" >}} ## Service configuration reference @@ -50,7 +51,7 @@ definition in version 2. A set of configuration options to set block IO limits for this service. - version: "{{ site.compose_file_v2 }}" + version: "{{% param "compose_file_v2" %}}" services: foo: image: busybox @@ -112,7 +113,7 @@ Configuration options that are applied at build time. context: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: webapp: build: ./dir @@ -122,7 +123,7 @@ Or, as an object with the path specified under [context](#context) and optionally [Dockerfile](#dockerfile) and [args](#args): ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: webapp: build: @@ -474,7 +475,7 @@ behaviors: Simple example: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: web: build: . @@ -503,7 +504,7 @@ the healthcheck) before starting. Example: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: web: build: . @@ -783,7 +784,7 @@ details. A full example: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: myservice: image: alpine @@ -880,7 +881,7 @@ Run an init inside the container that forwards signals and reaps processes. Set this option to `true` to enable this feature for the service. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: web: image: alpine:latest @@ -1068,7 +1069,7 @@ the hostname `db` or `database` on the `new` network, and at `db` or `mysql` on the `legacy` network. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: web: @@ -1109,7 +1110,7 @@ The corresponding network configuration in the An example: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: app: @@ -1145,7 +1146,7 @@ managed by docker (IPAM driver). Example usage: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: app: image: busybox @@ -1170,7 +1171,7 @@ as it has the highest priority. It then connects to `app_net_3`, then `app_net_2`, which uses the default priority value of `0`. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: app: image: busybox @@ -1466,7 +1467,7 @@ expressed in the short form. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: web: image: nginx:alpine @@ -1551,7 +1552,7 @@ restart: "on-failure" restart: "unless-stopped" ``` -{: id="cpu-and-other-resources"} +{ #cpu-and-other-resources } ### cpu_count, cpu_percent, cpu\_shares, cpu\_period, cpu\_quota, cpus, cpuset, domainname, hostname, ipc, mac\_address, mem\_limit, memswap\_limit, mem\_swappiness, mem\_reservation, oom_kill_disable, oom_score_adj, privileged, read\_only, shm\_size, stdin\_open, tty, user, working\_dir @@ -1645,7 +1646,7 @@ shared with another service as a volume so that it can be periodically backed up: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: db: @@ -1707,7 +1708,7 @@ In the example below, instead of attempting to create a volume called called `data` and mount it into the `db` service's containers. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: db: @@ -1733,7 +1734,7 @@ volumes: > Deprecated in [version 2.1](compose-versioning.md#version-21) file format. > > external.name was deprecated in version 2.1 file format use `name` instead. -{: .important } +{ .important } ### labels @@ -1769,7 +1770,7 @@ volumes that contain special characters. The name is used as is and will **not** be scoped with the stack name. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" volumes: data: name: my-app-data @@ -1778,7 +1779,7 @@ volumes: It can also be used in conjunction with the `external` property: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" volumes: data: external: true @@ -1910,7 +1911,7 @@ looks for an existing network simply called `outside` and connect the `proxy` service's containers to it. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" services: proxy: @@ -1932,7 +1933,7 @@ You can also specify the name of the network separately from the name used to refer to it within the Compose file: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" networks: outside: external: @@ -1951,7 +1952,7 @@ networks which contain special characters. The name is used as is and will **not** be scoped with the stack name. ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" networks: network1: name: my-app-net @@ -1960,7 +1961,7 @@ networks: It can also be used in conjunction with the `external` property: ```yaml -version: "{{ site.compose_file_v2 }}" +version: "{{% param "compose_file_v2" %}}" networks: network1: external: true @@ -1969,13 +1970,13 @@ networks: ## Variable substitution -{% include content/compose-var-sub.md %} +{{< include "content/compose-var-sub.md" >}} ## Extension fields > Added in [version 2.1](compose-versioning.md#version-21) file format. -{% include content/compose-extfields-sub.md %} +{{< include "content/compose-extfields-sub.md" >}} ## Compose documentation @@ -1983,4 +1984,4 @@ networks: - [Installing Compose](../install/index.md) - [Compose file versions and upgrading](compose-versioning.md) - [Sample apps with Compose](../samples-for-compose.md) -- [Command line reference](../reference/index.md) +- [Command line reference](../reference/index.md) \ No newline at end of file diff --git a/content/compose/compose-file/compose-file-v3.md b/content/compose/compose-file/compose-file-v3.md index 0e53e9a022..662de4ae72 100644 --- a/content/compose/compose-file/compose-file-v3.md +++ b/content/compose/compose-file/compose-file-v3.md @@ -1,11 +1,14 @@ --- -description: Find a quick reference for Docker Compose version 3, including Docker Engine compatibility, memory limitations, and more. -keywords: docker compose ports, docker compose version 3, docker-compose memory limit version 3, docker compose 3 memory limit +description: Find a quick reference for Docker Compose version 3, including Docker + Engine compatibility, memory limitations, and more. +keywords: docker compose ports, docker compose version 3, docker-compose memory limit + version 3, docker compose 3 memory limit title: Compose file version 3 reference toc_max: 4 toc_min: 1 --- -{% include compose-eol.md %} + +{{< include "compose-eol.md" >}} ## Reference and guidelines @@ -17,7 +20,7 @@ There are several versions of the Compose file format – 1, 2, 2.x, and 3.x. Th table below is a quick look. For full details on what each version includes and how to upgrade, see **[About versions and upgrading](compose-versioning.md)**. -{% include content/compose-matrix.md %} +{{< include "content/compose-matrix.md" >}} ## Compose file structure and examples @@ -31,7 +34,7 @@ topic on [Deploying an app to a Swarm](https://github.com/docker/labs/blob/maste 

-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
 
   redis:
@@ -173,7 +176,7 @@ Configuration options that are applied at build time.
 context:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   webapp:
     build: ./dir
@@ -183,7 +186,7 @@ Or, as an object with the path specified under [context](#context) and
 optionally [Dockerfile](#dockerfile) and [args](#args):
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   webapp:
     build:
@@ -208,7 +211,7 @@ This results in an image named `webapp` and tagged `tag`, built from `./dir`.
 > The `build` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
 > The `docker stack` command does not build images before deploying.
-{: .important }
+{ .important }
 
 #### context
 
@@ -419,7 +422,7 @@ cap_drop:
 >
 > The `cap_add` and `cap_drop` options are ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
-{: .important }
+{ .important }
 
 ### cgroup_parent
 
@@ -433,7 +436,7 @@ cgroup_parent: m-executor-abcd
 >
 > The `cgroup_parent` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
-{: .important }
+{ .important }
 
 ### command
 
@@ -482,7 +485,7 @@ the stack deployment fails with a `config not found` error.
 > compose file format.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:latest
@@ -515,7 +518,7 @@ the service's task containers.
   because they are mounted in a temporary filesystem, so if you set the writable
   bit, it is ignored. The executable bit can be set. If you aren't familiar with
   UNIX file permission modes, you may find this
-  [permissions calculator](http://permissions-calculator.org/){: target="_blank" rel="noopener" class="_" }
+  [permissions calculator](http://permissions-calculator.org/)
   useful.
 
 The following example sets the name of `my_config` to `redis_config` within the
@@ -524,7 +527,7 @@ to `103`. The `redis` service does not have access to the `my_other_config`
 config.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:latest
@@ -562,7 +565,7 @@ an error.
 >
 > The `container_name` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
-{: .important }
+{ .important }
 
 ### credential_spec
 
@@ -604,7 +607,7 @@ When configuring a gMSA credential spec for a service, you only need
 to specify a credential spec with `config`, as shown in the following example:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   myservice:
     image: myimage:latest
@@ -632,7 +635,7 @@ behaviors:
 Simple example:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     build: .
@@ -665,7 +668,7 @@ sub-options only takes effect when deploying to a [swarm](../../engine/swarm/ind
 ignored by `docker-compose up` and `docker-compose run`, except for `resources`.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:alpine
@@ -703,7 +706,7 @@ in cases where you want to use your own load balancer, or for Hybrid
 Windows and Linux applications.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 
 services:
   wordpress:
@@ -751,7 +754,7 @@ Specify labels for the service. These labels are *only* set on the service,
 and *not* on any containers for the service.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     image: web
@@ -763,7 +766,7 @@ services:
 To set labels on containers instead, use the `labels` key outside of `deploy`:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     image: web
@@ -780,7 +783,7 @@ in the [swarm](../../engine/swarm/index.md) topics.)
 
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   worker:
     image: dockersamples/examplevotingapp_worker
@@ -797,7 +800,7 @@ documentation for a full description of the syntax and available types of
 and [specifying the maximum replicas per node](../../engine/reference/commandline/service_create.md#replicas-max-per-node)
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   db:
     image: postgres
@@ -821,7 +824,7 @@ When there are more tasks requested than running nodes, an error
 `no suitable node (max replicas per node limit exceed)` is raised.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   worker:
     image: dockersamples/examplevotingapp_worker
@@ -841,7 +844,7 @@ If the service is `replicated` (which is the default), specify the number of
 containers that should be running at any given time.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   worker:
     image: dockersamples/examplevotingapp_worker
@@ -873,7 +876,7 @@ In this general example, the `redis` service is constrained to use no more than
 and has `20M` of memory and `0.25` CPU time reserved (as always available to it).
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:alpine
@@ -897,8 +900,8 @@ services or containers in a swarm.
 on non swarm deployments, use
 [Compose file format version 2 CPU, memory, and other resource options](compose-file-v2.md#cpu-and-other-resources).
 If you have further questions, refer to the discussion on the GitHub
-issue [docker/compose/4513](https://github.com/docker/compose/issues/4513){: target="_blank" rel="noopener" class="_"}.
-{: .important}
+issue [docker/compose/4513](https://github.com/docker/compose/issues/4513).
+{ .important }
 
 ##### Out Of Memory Exceptions (OOME)
 
@@ -927,7 +930,7 @@ Configures if and how to restart containers when they exit. Replaces
   decide immediately).
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:alpine
@@ -972,7 +975,7 @@ updates.
 > file format.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   vote:
     image: dockersamples/examplevotingapp_vote:before
@@ -1024,7 +1027,7 @@ devices:
 >
 > The `devices` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
-{: .important }
+{ .important }
 
 ### dns
 
@@ -1224,7 +1227,7 @@ external_links:
 >
 > The `external_links` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
-{: .important }
+{ .important }
 
 ### extra_hosts
 
@@ -1326,7 +1329,7 @@ Run an init inside the container that forwards signals and reaps processes.
 Set this option to `true` to enable this feature for the service.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     image: alpine:latest
@@ -1379,7 +1382,7 @@ labels:
 > `--link` is sharing environmental variables between containers. However, you
 > can use other mechanisms such as volumes to share environment variables between
 > containers in a more controlled way.
-{:.warning}
+{ .warning }
 
 Link to containers in another service. Either specify both the service name and
 a link alias (`"SERVICE:ALIAS"`), or just the service name.
@@ -1412,7 +1415,7 @@ Links also express dependency between services in the same way as
 >
 > The `links` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md)
-{: .important }
+{ .important }
 
 ### logging
 
@@ -1473,7 +1476,7 @@ files are removed to allow storage of new logs.
 Here is an example `docker-compose.yml` file that limits logging storage:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   some-service:
     image: some-service
@@ -1518,7 +1521,7 @@ network_mode: "container:[container name/id]"
 > * This option is ignored when
 >   [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md).
 > * `network_mode: "host"` cannot be mixed with [links](#links).
-{: .important }
+{ .important }
 
 ### networks
 
@@ -1566,7 +1569,7 @@ the hostname `db` or `database` on the `new` network, and at `db` or `mysql` on
 the `legacy` network.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 
 services:
   web:
@@ -1619,7 +1622,7 @@ Then, reload the docker daemon and edit docker-compose.yml to contain the follow
 An example:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 
 services:
   app:
@@ -1747,7 +1750,7 @@ container is stopped (manually or otherwise).
 >
 > The `restart` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md).
-{: .important }
+{ .important }
 
 ### secrets
 
@@ -1759,7 +1762,7 @@ configuration. Two different syntax variants are supported.
 > The secret must already exist or be
 > [defined in the top-level `secrets` configuration](#secrets-configuration-reference)
 > of the compose file, or stack deployment fails.
-{: .important }
+{ .important }
 
 For more information on secrets, see [secrets](../../engine/swarm/secrets.md).
 
@@ -1779,7 +1782,7 @@ command or by another stack deployment. If the external secret does not exist,
 the stack deployment fails with a `secret not found` error.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:latest
@@ -1813,7 +1816,7 @@ the service's task containers.
   in a temporary filesystem, so if you set the writable bit, it is ignored. The
   executable bit can be set. If you aren't familiar with UNIX file permission
   modes, you may find this
-  [permissions calculator](http://permissions-calculator.org/){: target="_blank" rel="noopener" class="_" }
+  [permissions calculator](http://permissions-calculator.org/)
   useful.
 
 The following example sets name of the `my_secret` to `redis_secret` within the
@@ -1822,7 +1825,7 @@ to `103`. The `redis` service does not have access to the `my_other_secret`
 secret.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   redis:
     image: redis:latest
@@ -1858,7 +1861,7 @@ security_opt:
 >
 > The `security_opt` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md).
-{: .important }
+{ .important }
 
 ### stop_grace_period
 
@@ -1974,7 +1977,7 @@ more information.
 >
 > The `userns_mode` option is ignored when
 > [deploying a stack in swarm mode](../../engine/reference/commandline/stack_deploy.md).
-{: .important }
+{ .important }
 
 ### volumes
 
@@ -2002,7 +2005,7 @@ for mounting a named volume. Named volumes must be listed under the top-level
 `volumes` key, as shown.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     image: nginx:alpine
@@ -2084,7 +2087,7 @@ expressed in the short form.
   - `size`: the size for the tmpfs mount in bytes
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     image: nginx:alpine
@@ -2139,7 +2142,7 @@ as a named volume to persist the data on the swarm, _and_ is constrained to run
 only on `manager` nodes. Here is the relevant snip-it from that file:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   db:
     image: postgres:9.4
@@ -2221,7 +2224,7 @@ shared with another service as a volume so that it can be periodically backed
 up:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 
 services:
   db:
@@ -2283,7 +2286,7 @@ In the example below, instead of attempting to create a volume called
 called `data` and mount it into the `db` service's containers.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 
 services:
   db:
@@ -2299,7 +2302,7 @@ volumes:
 > Deprecated in [version 3.4](compose-versioning.md#version-34) file format.
 >
 > external.name was deprecated in version 3.4 file format use `name` instead.
-{: .important }
+{ .important }
 
 You can also specify the name of the volume separately from the name used to
 refer to it within the Compose file:
@@ -2319,7 +2322,7 @@ volumes:
 > automatically created when it is defined by a service. As service tasks are
 > scheduled on new nodes, [swarmkit](https://github.com/docker/swarmkit/blob/master/README.md)
 > creates the volume on the local node. To learn more, see [moby/moby#29976](https://github.com/moby/moby/issues/29976).
-{: .important }
+{ .important }
 
 ### labels
 
@@ -2353,7 +2356,7 @@ volumes that contain special characters. The name is used as is
 and will **not** be scoped with the stack name.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 volumes:
   data:
     name: my-app-data
@@ -2362,7 +2365,7 @@ volumes:
 It can also be used in conjunction with the `external` property:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 volumes:
   data:
     external: true
@@ -2428,7 +2431,7 @@ Docker has already created automatically) and an alias that Compose can use
 network using the alias.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 services:
   web:
     networks:
@@ -2501,7 +2504,7 @@ Enable IPv6 networking on this network.
 >
 > `enable_ipv6` requires you to use a version 2 Compose file, as this directive
 > is not yet supported in Swarm mode.
-{: .warning }
+{ .warning }
 
 ### ipam
 
@@ -2572,7 +2575,7 @@ looks for an existing network simply called `outside` and connect the `proxy`
 service's containers to it.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 
 services:
   proxy:
@@ -2593,13 +2596,13 @@ networks:
 > Deprecated in [version 3.5](compose-versioning.md#version-35) file format.
 >
 > external.name was deprecated in version 3.5 file format use `name` instead.
-{: .important }
+{ .important }
 
 You can also specify the name of the network separately from the name used to
 refer to it within the Compose file:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 networks:
   outside:
     external:
@@ -2615,7 +2618,7 @@ networks which contain special characters. The name is used as is
 and will **not** be scoped with the stack name.
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 networks:
   network1:
     name: my-app-net
@@ -2624,7 +2627,7 @@ networks:
 It can also be used in conjunction with the `external` property:
 
 ```yaml
-version: "{{ site.compose_file_v3 }}"
+version: "{{% param "compose_file_v3" %}}"
 networks:
   network1:
     external: true
@@ -2749,13 +2752,13 @@ stack.
 
 ## Variable substitution
 
-{% include content/compose-var-sub.md %}
+{{< include "content/compose-var-sub.md" >}}
 
 ## Extension fields
 
 > Added in [version 3.4](compose-versioning.md#version-34) file format.
 
-{% include content/compose-extfields-sub.md %}
+{{< include "content/compose-extfields-sub.md" >}}
 
 ## Compose documentation
 
@@ -2763,4 +2766,4 @@ stack.
 - [Installing Compose](../install/index.md)
 - [Compose file versions and upgrading](compose-versioning.md)
 - [Sample apps with Compose](../samples-for-compose.md)
-- [Command line reference](../reference/index.md)
+- [Command line reference](../reference/index.md)
\ No newline at end of file
diff --git a/content/compose/compose-file/compose-versioning.md b/content/compose/compose-file/compose-versioning.md
index d2724350e6..106414b094 100644
--- a/content/compose/compose-file/compose-versioning.md
+++ b/content/compose/compose-file/compose-versioning.md
@@ -13,7 +13,7 @@ title: Compose file versions and upgrading
 >Make sure you switch to [Compose V2](/compose/compose-file/) with the `docker compose` CLI plugin or by activating the **Use Docker Compose V2** setting in Docker Desktop.
 >
 > For more information, see the [History of Compose](/compose/history/). 
-{: .warning}
+{ .warning }
 
 The Compose file is a [YAML](https://yaml.org) file defining services,
 networks, and volumes for a Docker application.
@@ -31,7 +31,7 @@ compatibility, and [how to upgrade](#upgrading).
 
 ## Compatibility matrix
 
-{% include content/compose-matrix.md %}
+{{< include "content/compose-matrix.md" >}}
 
 > Looking for more detail on Docker and Compose compatibility?
 >
@@ -41,7 +41,7 @@ Compose release is compatible, refer to the [Compose release
 notes](https://github.com/docker/compose/releases/). Each set of release notes
 gives details on which versions of Docker Engine are supported, along
 with compatible Compose file format versions. (See also, the discussion in
-[issue #3404]({{ site.repo }}/issues/3404).)
+[issue #3404]({{% param "repo" %}}/issues/3404).)
 
 
 For details on versions and how to upgrade, see
@@ -118,7 +118,7 @@ discoverable at a hostname that's the same as the service name. This means
 
 Simple example:
 
-    version: "{{ site.compose_file_v2 }}"
+    version: "{{% param "compose_file_v2" %}}"
     services:
       web:
         build: .
@@ -131,7 +131,7 @@ Simple example:
 
 A more extended example, defining volumes and networks:
 
-    version: "{{ site.compose_file_v2 }}"
+    version: "{{% param "compose_file_v2" %}}"
     services:
       web:
         build: .
@@ -164,7 +164,7 @@ Several other options were added to support networking, such as:
 * The [`depends_on`](compose-file-v2.md#depends_on) option can be used in place of links to indicate dependencies
 between services and startup order.
 
-      version: "{{ site.compose_file_v2 }}"
+      version: "{{% param "compose_file_v2" %}}"
       services:
         web:
           build: .
@@ -515,7 +515,7 @@ It's more complicated if you're using particular configuration features:
     named volume called `data`, you must declare a `data` volume in your
     top-level `volumes` section. The whole file might look like this:
 
-        version: "{{ site.compose_file_v2 }}"
+        version: "{{% param "compose_file_v2" %}}"
         services:
           db:
             image: postgres
@@ -530,4 +530,4 @@ It's more complicated if you're using particular configuration features:
 
         volumes:
           data:
-            external: true
+            external: true
\ No newline at end of file
diff --git a/content/compose/environment-variables/_index.md b/content/compose/environment-variables/_index.md
index 8f1a92629e..0398761b66 100644
--- a/content/compose/environment-variables/_index.md
+++ b/content/compose/environment-variables/_index.md
@@ -1,9 +1,11 @@
 ---
 title: Overview
-description: Explainer on the ways to set, use and manage environment variables in Compose
+description: Explainer on the ways to set, use and manage environment variables in
+  Compose
 keywords: compose, orchestration, environment, env file
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 Environment variables can help you define various configuration values. They also keep your app flexible and organized. 
 
diff --git a/content/compose/environment-variables/env-file.md b/content/compose/environment-variables/env-file.md
index 0ed5a6f5f0..ef9d8e325c 100644
--- a/content/compose/environment-variables/env-file.md
+++ b/content/compose/environment-variables/env-file.md
@@ -2,7 +2,7 @@
 description: Understand the accepted syntax for declaring environment variables.
 keywords: fig, composition, compose, docker, orchestration, environment, env file
 title: Use an environment file in Docker Compose
-redirect_from:
+aliases:
 - /compose/env-file/
 ---
 
@@ -54,4 +54,4 @@ For braced expressions, the following formats are supported:
 ## Precedence
 
 Environment variables from an environment file have lower precedence than those passed via the command-line or via the `environment` attribute in the `compose.yml` file.
-For more information, see [Environment variables precedence](envvars-precedence.md).
+For more information, see [Environment variables precedence](envvars-precedence.md).
\ No newline at end of file
diff --git a/content/compose/environment-variables/envvars-precedence.md b/content/compose/environment-variables/envvars-precedence.md
index a10f684800..6fba7b3229 100644
--- a/content/compose/environment-variables/envvars-precedence.md
+++ b/content/compose/environment-variables/envvars-precedence.md
@@ -1,8 +1,9 @@
 ---
 title: Environment variables precedence in Docker Compose
-description: Scenario overview illustrating how environment variables are resolved in Compose
+description: Scenario overview illustrating how environment variables are resolved
+  in Compose
 keywords: compose, environment, env file
-redirect_from:
+aliases:
 - /compose/envvars-precedence/
 ---
 
@@ -52,7 +53,7 @@ $ docker compose exec api node
 > Executing a command within the container that unconditionally sets a variable value overrules any setting in your `compose.yml` file.
 >
 > For example, in a NodeJS project, if you have a `package.json` entry for `scripts.start`, such as `NODE_ENV=test` `node server.js`, any value set for `NODE_ENV` in your Compose file, is ignored when running `npm run start` within the container.
-{: .important}
+{ .important }
 
 ## Advanced example 
 
@@ -81,4 +82,4 @@ Each row represents a combination of contexts where `TAG` is set, substituted, o
 | 10 |`TAG=1.8`      |   -                                |  `TAG=1.6`                      |  `TAG=1.5`   |  `TAG=1.4`              |  `TAG=1.3`        ||**`TAG=1.8`**  |
 | 11 |`TAG=1.8`      |  `TAG=1.7`                         |  `TAG=1.6`                      |  `TAG=1.5`   |  `TAG=1.4`              |  `TAG=1.3`        ||**`TAG=1.8`**  |
 | 12 |   -           |   -                                |`TAG=1.6`                        |  `TAG=1.5`   |  `TAG=1.4`              |   -               ||**`TAG=1.6`**  |
-| 13 |   -           |`TAG=1.7`                           |   -                             |  `TAG=1.5`   |  `TAG=1.4`              |   -               ||**`TAG=1.7`**  |
+| 13 |   -           |`TAG=1.7`                           |   -                             |  `TAG=1.5`   |  `TAG=1.4`              |   -               ||**`TAG=1.7`**  |
\ No newline at end of file
diff --git a/content/compose/environment-variables/envvars.md b/content/compose/environment-variables/envvars.md
index e36401da3d..bae1e6ca79 100644
--- a/content/compose/environment-variables/envvars.md
+++ b/content/compose/environment-variables/envvars.md
@@ -2,7 +2,7 @@
 description: Compose pre-defined environment variables
 keywords: fig, composition, compose, docker, orchestration, cli, reference
 title: Change pre-defined environment variables in Docker Compose
-redirect_from:
+aliases:
 - /compose/reference/envvars/
 ---
 
@@ -148,10 +148,10 @@ For more information, see [Migrate to Compose V2](../migrate.md).
 
 - `COMPOSE_API_VERSION`
     By default the API version is negotiated with the server. Use `DOCKER_API_VERSION`.  
-    See the [Docker CLI environment variable reference](../../../engine/reference/commandline/cli/#environment-variables){:target="_blank" rel="noopener" class="_"} page.
+    See the [Docker CLI environment variable reference](../../../engine/reference/commandline/cli/#environment-variables) page.
 - `COMPOSE_HTTP_TIMEOUT`
 - `COMPOSE_TLS_VERSION`
 - `COMPOSE_FORCE_WINDOWS_HOST`
 - `COMPOSE_INTERACTIVE_NO_CLI`
 - `COMPOSE_DOCKER_CLI_BUILD`
-    Use `DOCKER_BUILDKIT` to select between BuildKit and the classic builder. If `DOCKER_BUILDKIT=0` then `docker compose build` uses the classic builder to build images.
+    Use `DOCKER_BUILDKIT` to select between BuildKit and the classic builder. If `DOCKER_BUILDKIT=0` then `docker compose build` uses the classic builder to build images.
\ No newline at end of file
diff --git a/content/compose/environment-variables/set-environment-variables.md b/content/compose/environment-variables/set-environment-variables.md
index f29e578c8b..45bd80dbe3 100644
--- a/content/compose/environment-variables/set-environment-variables.md
+++ b/content/compose/environment-variables/set-environment-variables.md
@@ -2,7 +2,7 @@
 title: Ways to set environment variables in Compose
 description: How to set, use and manage environment variables in Compose
 keywords: compose, orchestration, environment, env file
-redirect_from:
+aliases:
 - /compose/env/
 - /compose/link-env-deprecated/
 ---
@@ -12,7 +12,7 @@ Environment variables are dealt with by either the Compose file or the CLI. Both
 >**Tip**
 >
 > Don't use environment variables to pass sensitive information, such as passwords, in to your containers. Use [secrets](../use-secrets.md) instead.
-{: .tip}
+{ .tip }
 
 ## Compose file
 
@@ -56,7 +56,7 @@ For more information on formatting an environment file, see [Use an environment
 > Substitution from `.env` files is a Docker Compose CLI feature.
 >
 > It is not supported by Swarm when running `docker stack deploy`.
-{: .important}
+{ .important }
 
 ### Use the `environment` attribute
 
@@ -123,7 +123,7 @@ If an environment variable is not set, Compose substitutes with an empty string.
 > **Important**
 >
 > Values set in the shell environment override those set in the `.env` file, the `environment` attribute, and the `env_file` attribute. For more information, see [Environment variable precedence](envvars-precedence.md).
-{: .important}
+{ .important }
 
 ## CLI
 
@@ -181,7 +181,7 @@ ERROR: Couldn't find env file: /home/user/./doesnotexist/.env.dev
 > **Important**
 >
 > Values set in the shell environment override those set when using the `--env-file` argument in the CLI. For more information, see [Environment variable precedence](envvars-precedence.md)
-{: .important}
+{ .important }
 
 ### Set environment variables with `docker compose run --env`
 
@@ -199,4 +199,4 @@ $ docker compose run -e DEBUG web python console.py
 ```
 
 The value of the `DEBUG` variable in the container is taken from the value for
-the same variable in the shell in which Compose is run.
+the same variable in the shell in which Compose is run.
\ No newline at end of file
diff --git a/content/compose/faq.md b/content/compose/faq.md
index 15f84c519c..d348bdabbe 100644
--- a/content/compose/faq.md
+++ b/content/compose/faq.md
@@ -3,7 +3,8 @@ description: Frequently asked questions for Docker Compose
 keywords: documentation, docs,  docker, compose, faq
 title: Compose FAQs
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 ### How do I get help?
 
@@ -11,16 +12,16 @@ Docker Compose is under active development. If you need help, would like to
 contribute, or simply want to talk about the project with like-minded
 individuals, we have a number of open channels for communication.
 
-* To report bugs or file feature requests, use the [issue tracker on Github](https://github.com/docker/compose/issues){: target="blank" rel="noopener" class="_" }.
+* To report bugs or file feature requests, use the [issue tracker on Github](https://github.com/docker/compose/issues).
 
 * To talk about the project with people in real time, join the
-  `#docker-compose` channel on the [Docker Community Slack](https://dockr.ly/slack){: target="blank" rel="noopener" class="_" }.
+  `#docker-compose` channel on the [Docker Community Slack](https://dockr.ly/slack).
 
-* To contribute code submit a [pull request on Github](https://github.com/docker/compose/pulls){: target="blank" rel="noopener" class="_" }.
+* To contribute code submit a [pull request on Github](https://github.com/docker/compose/pulls).
 
 ### Where can I find example Compose files?
 
-There are [many examples of Compose files on GitHub](https://github.com/docker/awesome-compose){: target="blank" rel="noopener" class="_" }.
+There are [many examples of Compose files on GitHub](https://github.com/docker/awesome-compose).
 
 ### What's the difference between `up`, `run`, and `start`?
 
@@ -51,7 +52,7 @@ are waiting for this timeout, it means that your containers aren't shutting down
 when they receive the `SIGTERM` signal.
 
 There has already been a lot written about this problem of
-[processes handling signals](https://medium.com/@gchudnov/trapping-signals-in-docker-containers-7a57fdda7d86){: target="blank" rel="noopener" class="_" }
+[processes handling signals](https://medium.com/@gchudnov/trapping-signals-in-docker-containers-7a57fdda7d86)
 in containers.
 
 To fix this problem, try the following:
@@ -77,9 +78,9 @@ services:
 ```
 
 * If you can't modify the application, wrap the application in a lightweight init
-system (like [s6](https://skarnet.org/software/s6/){: target="blank" rel="noopener" class="_" }) or a signal proxy (like
-[dumb-init](https://github.com/Yelp/dumb-init){: target="blank" rel="noopener" class="_" } or
-[tini](https://github.com/krallin/tini){: target="blank" rel="noopener" class="_" }).  Either of these wrappers takes care of
+system (like [s6](https://skarnet.org/software/s6/)) or a signal proxy (like
+[dumb-init](https://github.com/Yelp/dumb-init) or
+[tini](https://github.com/krallin/tini)).  Either of these wrappers takes care of
 handling `SIGTERM` properly.
 
 ### Can I control service startup order?
@@ -95,7 +96,7 @@ or the [`COMPOSE_PROJECT_NAME` environment variable](environment-variables/envva
 
 ### Can I use JSON instead of YAML for my Compose file?
 
-Yes. [YAML is a superset of JSON](https://stackoverflow.com/a/1729545/444646){: target="blank" rel="noopener" class="_" } so
+Yes. [YAML is a superset of JSON](https://stackoverflow.com/a/1729545/444646) so
 any JSON file should be valid YAML. To use a JSON file with Compose,
 specify the filename to use, for example:
 
@@ -117,4 +118,4 @@ supports hot code reloading or live-reload.
 There may be cases where you want to use both. You can have the image
 include the code using a `COPY`, and use a `volume` in your Compose file to
 include the code from the host during development. The volume overrides
-the directory contents of the image.
+the directory contents of the image.
\ No newline at end of file
diff --git a/content/compose/features-uses.md b/content/compose/features-uses.md
index ecd1877a1f..48e3313ba6 100644
--- a/content/compose/features-uses.md
+++ b/content/compose/features-uses.md
@@ -123,4 +123,4 @@ Compose has traditionally been focused on development and testing workflows,
 but with each release we're making progress on more production-oriented features.
 
 For details on using production-oriented features, see
-[Compose in production](production.md).
+[Compose in production](production.md).
\ No newline at end of file
diff --git a/content/compose/file-watch.md b/content/compose/file-watch.md
index ca74011d84..1178274283 100644
--- a/content/compose/file-watch.md
+++ b/content/compose/file-watch.md
@@ -1,6 +1,6 @@
 ---
 description: Use File watch to automatically update running services as you work
-keywords: compose, file watch, experimental 
+keywords: compose, file watch, experimental
 title: Automatically update services with file watch in Docker Compose
 ---
 
@@ -66,7 +66,7 @@ image rebuild (e.g. `package.json`).
 > Optimize your `Dockerfile` for speedy
 incremental rebuilds with [image layer caching](/build/cache)
 and [multi-stage builds](/build/building/multi-stage/).
-{: .tip}
+{ .tip }
 
 ### `path` and `target`
 
@@ -134,8 +134,8 @@ This pattern can be followed for many languages and frameworks, such as Python w
 >
 > Looking for a sample project to test things out? Check
 out [`dockersamples/avatars`](https://github.com/dockersamples/avatars) for a demonstration of Compose `watch`.
-{: .tip}
+{ .tip }
 
 ## Feedback
 
-We are actively looking for feedback on this feature. Give feedback or report any bugs you may find in the [Compose Specification repository](https://github.com/compose-spec/compose-spec/pull/253).
+We are actively looking for feedback on this feature. Give feedback or report any bugs you may find in the [Compose Specification repository](https://github.com/compose-spec/compose-spec/pull/253).
\ No newline at end of file
diff --git a/content/compose/gettingstarted.md b/content/compose/gettingstarted.md
index c5e9778eb3..c7913a4098 100644
--- a/content/compose/gettingstarted.md
+++ b/content/compose/gettingstarted.md
@@ -1,6 +1,10 @@
 ---
-description: Check out this tutorial on how to use Docker Compose from defining application dependencies to experimenting with commands.   
-keywords: docker compose example, docker compose tutorial, how to use docker compose, running docker compose, how to run docker compose, docker compose build image, docker compose command example, run docker compose file, how to create a docker compose file, run a docker compose file
+description: Check out this tutorial on how to use Docker Compose from defining application
+  dependencies to experimenting with commands.
+keywords: docker compose example, docker compose tutorial, how to use docker compose,
+  running docker compose, how to run docker compose, docker compose build image, docker
+  compose command example, run docker compose file, how to create a docker compose
+  file, run a docker compose file
 title: Try Docker Compose
 ---
 
@@ -111,7 +115,7 @@ This tells Docker to:
 >Important
 >
 >Check that the `Dockerfile` has no file extension like `.txt`. Some editors may append this file extension automatically which results in an error when you run the application.
-{: .important}
+{ .important }
 
 For more information on how to write Dockerfiles, see the
 [Docker user guide](../develop/index.md)
@@ -277,7 +281,7 @@ and the general examples on how to
 ticket](https://www.virtualbox.org/ticket/14920). Newer Windows systems meet the
 requirements for [Docker Desktop for Windows](../desktop/install/windows-install.md) and do not
 need VirtualBox.
-{: .important}
+{ .important }
 
 ## Step 7: Update the application
 
@@ -347,4 +351,4 @@ $ docker compose down --volumes
 - Try the [Sample apps with Compose](https://github.com/docker/awesome-compose)
 - [Explore the full list of Compose commands](reference/index.md)
 - [Explore the Compose file reference](compose-file/index.md)
-- To learn more about volumes and bind mounts, see [Manage data in Docker](../storage/index.md)
+- To learn more about volumes and bind mounts, see [Manage data in Docker](../storage/index.md)
\ No newline at end of file
diff --git a/content/compose/gpu-support.md b/content/compose/gpu-support.md
index 0d1b04cbd2..9a6f469c24 100644
--- a/content/compose/gpu-support.md
+++ b/content/compose/gpu-support.md
@@ -4,14 +4,14 @@ keywords: documentation, docs, docker, compose, GPU access, NVIDIA, samples
 title: Turn on GPU access with Docker Compose
 ---
 
-Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](../config/containers/resource_constraints.md#gpu){: target="_blank" rel="noopener" class="_" } if you haven't already done so.
+Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](../config/containers/resource_constraints.md#gpu) if you haven't already done so.
 
 The examples in the following sections focus specifically on providing service containers access to GPU devices with Docker Compose. 
-You can use either `docker-compose` or `docker compose` commands. For more information, see [Migrate to Compose V2](migrate.md){: target="_blank" rel="noopener" class="_" }.
+You can use either `docker-compose` or `docker compose` commands. For more information, see [Migrate to Compose V2](migrate.md).
 
 ## Enabling GPU access to service containers
 
-GPUs are referenced in a `compose.yml` file using the [device](compose-file/deploy.md#devices){:target="_blank" rel="noopener" class="_"} attribute from the Compose Deploy specification, within your services that need them. 
+GPUs are referenced in a `compose.yml` file using the [device](compose-file/deploy.md#devices) attribute from the Compose Deploy specification, within your services that need them. 
 
 This provides more granular control over a GPU reservation as custom values can be set for the following device properties: 
 
@@ -27,7 +27,7 @@ This provides more granular control over a GPU reservation as custom values can
 > You must set the `capabilities` field. Otherwise, it returns an error on service deployment.
 >
 > `count` and `device_ids` are mutually exclusive. You must only define one field at a time.
-{: .important}
+{ .important }
 
 For more information on these properties, see the `deploy` section in the [Compose Specification](compose-file/deploy.md#devices).
 
@@ -125,4 +125,4 @@ services:
             device_ids: ['0', '3']
             capabilities: [gpu]
 
-```
+```
\ No newline at end of file
diff --git a/content/compose/history.md b/content/compose/history.md
index 7e25d7a0f6..a38cf2400d 100644
--- a/content/compose/history.md
+++ b/content/compose/history.md
@@ -3,12 +3,12 @@ title: History of Docker Compose
 description: History of Compose V1 and Compose YAML schema versioning
 keywords: compose, compose yaml, swarm, migration, compatibility
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 This page provides a brief history of the major versions and file format revisions of Docker Compose.
 
-The currently supported version of Compose is V2, which uses YAML files as defined by the [Compose specification](https://github.com/compose-spec/compose-spec){:
-target="_blank" rel="noopener" class="_"}.
+The currently supported version of Compose is V2, which uses YAML files as defined by the [Compose specification](https://github.com/compose-spec/compose-spec).
 
 For users supporting projects originally targeting older versions of Compose, this can serve as a guide to understanding compatibility and the evolution of changes.
 
@@ -34,7 +34,7 @@ Its usage is historical and files written in this format don't run with Compose
 
 Compose file format 2.x and 3.x were very similar to each other, but the latter introduced many new options targeted at Swarm deployments.
 
-To address confusion around Compose CLI versioning, Compose file format versioning, and feature parity depending on whether Swarm mode was in use, file format 2.x and 3.x were merged into the [Compose Specification](https://github.com/compose-spec/compose-spec){:target="_blank" rel="noopener" class="_"}.
+To address confusion around Compose CLI versioning, Compose file format versioning, and feature parity depending on whether Swarm mode was in use, file format 2.x and 3.x were merged into the [Compose Specification](https://github.com/compose-spec/compose-spec).
 Unlike the prior file formats, the Compose Specification is rolling and eliminates the `version` field in YAML.
 
 Compose V2 uses the Compose Specification for project definition.
@@ -42,4 +42,4 @@ The `version` field should be omitted and is ignored if present.
 
 To make migration easier, Compose V2 has backwards compatibility for certain elements that have been deprecated or changed between Compose file format 2.x/3.x and the Compose Specification.
 In these cases, a warning is logged when running Compose V2 commands, and you should update your YAML accordingly.
-Future versions of Compose may return an error in these cases.
+Future versions of Compose may return an error in these cases.
\ No newline at end of file
diff --git a/content/compose/install/_index.md b/content/compose/install/_index.md
index 0301e85b5b..452cf5115d 100644
--- a/content/compose/install/_index.md
+++ b/content/compose/install/_index.md
@@ -1,14 +1,18 @@
 ---
-description: Learn how to install Docker Compose. Compose is available natively on Docker Desktop, as a Docker Engine plugin, and as a standalone tool. 
-keywords: install docker compose, docker compose install, install docker compose ubuntu, installing docker compose, docker compose download, docker compose not found, docker compose windows, how to install docker compose
+description: Learn how to install Docker Compose. Compose is available natively on
+  Docker Desktop, as a Docker Engine plugin, and as a standalone tool.
+keywords: install docker compose, docker compose install, install docker compose ubuntu,
+  installing docker compose, docker compose download, docker compose not found, docker
+  compose windows, how to install docker compose
 title: Overview of installing Docker Compose
 toc_max: 3
-redirect_from:
+aliases:
 - /compose/compose-desktop/
 - /compose/install/other/
 - /compose/install/compose-desktop/
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 This page contains summary information about the available options for installing Docker Compose.
 
@@ -24,7 +28,7 @@ Docker Desktop is available on:
 - [Mac](../../desktop/install/mac-install.md)
 - [Windows](../../desktop/install/windows-install.md)
 
-If you have already installed Docker Desktop, you can check which version of Compose you have by selecting **About Docker Desktop** from the Docker menu ![whale menu](../../desktop/images/whale-x.svg){: .inline}.
+If you have already installed Docker Desktop, you can check which version of Compose you have by selecting **About Docker Desktop** from the Docker menu {{< inline-image src="../../desktop/images/whale-x.svg" alt="whale menu" >}}.
 
 ### Scenario two: Install the Compose plugin
 
@@ -35,7 +39,7 @@ If you already have Docker Engine and Docker CLI installed, you can install the
 > **Important**
 >
 >This is only available on Linux
-{: .important}
+{ .important }
 
 ### Scenario three: Install the Compose standalone 
 
@@ -44,4 +48,4 @@ You can [install the Compose standalone](standalone.md) on Linux or on Windows S
 > **Warning**
 >
 >This install scenario is not recommended and is only supported for backward compatibility purposes.
-{: .warning}
+{ .warning }
\ No newline at end of file
diff --git a/content/compose/install/linux.md b/content/compose/install/linux.md
index 7f1f7e8039..ee9896da5f 100644
--- a/content/compose/install/linux.md
+++ b/content/compose/install/linux.md
@@ -1,13 +1,18 @@
 ---
-description: Download and install Docker Compose on Linux with this step-by-step handbook. This plugin can be installed manually or by using a repository.
-keywords: install docker compose linux, docker compose linux, docker compose plugin, docker-compose-plugin, linux install docker compose, install docker-compose linux, linux install docker-compose, linux docker compose, docker compose v2 linux, install docker compose on linux
+description: Download and install Docker Compose on Linux with this step-by-step handbook.
+  This plugin can be installed manually or by using a repository.
+keywords: install docker compose linux, docker compose linux, docker compose plugin,
+  docker-compose-plugin, linux install docker compose, install docker-compose linux,
+  linux install docker-compose, linux docker compose, docker compose v2 linux, install
+  docker compose on linux
 toc_max: 3
 title: Install the Compose plugin
-redirect_from:
+aliases:
 - /compose/compose-plugin/
 - /compose/compose-linux/
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 On this page you can find instructions on how to install the Compose plugin on Linux from the command line.
 
@@ -83,14 +88,14 @@ To update the Compose plugin, run the following commands:
     ```console
     $ DOCKER_CONFIG=${DOCKER_CONFIG:-$HOME/.docker}
     $ mkdir -p $DOCKER_CONFIG/cli-plugins
-    $ curl -SL https://github.com/docker/compose/releases/download/{{site.compose_version}}/docker-compose-linux-x86_64 -o $DOCKER_CONFIG/cli-plugins/docker-compose
+    $ curl -SL https://github.com/docker/compose/releases/download/{{% param "compose_version" %}}/docker-compose-linux-x86_64 -o $DOCKER_CONFIG/cli-plugins/docker-compose
     ```
 
     This command downloads the latest release of Docker Compose (from the Compose releases repository) and installs Compose for the active user under `$HOME` directory.
 
     To install:
     * Docker Compose for _all users_ on your system, replace `~/.docker/cli-plugins` with `/usr/local/lib/docker/cli-plugins`.
-    * A different version of Compose, substitute `{{site.compose_version}}` with the version of Compose you want to use.
+    * A different version of Compose, substitute `{{% param "compose_version" %}}` with the version of Compose you want to use.
     - For a different architecture, substitute `x86_64` with the [architecture you want](https://github.com/docker/compose/releases).   
 
 
@@ -109,5 +114,5 @@ To update the Compose plugin, run the following commands:
 
     ```console
     $ docker compose version
-    Docker Compose version {{site.compose_version}}
-    ```
+    Docker Compose version {{% param "compose_version" %}}
+    ```
\ No newline at end of file
diff --git a/content/compose/install/standalone.md b/content/compose/install/standalone.md
index cc056f3169..5c5c5db613 100644
--- a/content/compose/install/standalone.md
+++ b/content/compose/install/standalone.md
@@ -3,10 +3,11 @@ title: Install Compose standalone
 description: How to install Docker Compose - Other Scenarios
 keywords: compose, orchestration, install, installation, docker, documentation
 toc_max: 3
-redirect_from:
-  - /compose/install/other
+aliases:
+- /compose/install/other
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 On this page you can find instructions on how to install Compose standalone on Linux or Windows Server, from the command line.
 
@@ -18,7 +19,7 @@ On this page you can find instructions on how to install Compose standalone on L
 
 1. To download and install Compose standalone, run:
   ```console
-  $ curl -SL https://github.com/docker/compose/releases/download/{{site.compose_version}}/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose
+  $ curl -SL https://github.com/docker/compose/releases/download/{{% param "compose_version" %}}/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose
   ```
 2. Apply executable permissions to the standalone binary in the target path for the installation.
 3. Test and execute compose commands using `docker-compose`.
@@ -31,7 +32,7 @@ On this page you can find instructions on how to install Compose standalone on L
    > ```console
    > $ sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose
    > ```
-   {: .tip}
+   { .tip }
 
 ### On Windows Server
 
@@ -46,10 +47,10 @@ on Microsoft Windows Server and want to install Docker Compose.
     ```powershell
     [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
     ```
-3. Run the following command to download the latest release of Compose ({{site.compose_version}}):
+3. Run the following command to download the latest release of Compose ({{% param "compose_version" %}}):
 
     ```powershell
-     Start-BitsTransfer -Source "https://github.com/docker/compose/releases/download/{{site.compose_version}}/docker-compose-windows-x86_64.exe" -Destination $Env:ProgramFiles\Docker\docker-compose.exe
+     Start-BitsTransfer -Source "https://github.com/docker/compose/releases/download/{{% param "compose_version" %}}/docker-compose-windows-x86_64.exe" -Destination $Env:ProgramFiles\Docker\docker-compose.exe
     ```
 
     > **Note**
@@ -58,12 +59,12 @@ on Microsoft Windows Server and want to install Docker Compose.
      Because this directory is registered in the system `PATH`, you can run the `docker-compose --version` 
      command on the subsequent step with no additional configuration.
 
-    > To install a different version of Compose, substitute `{{site.compose_version}}`
+    > To install a different version of Compose, substitute `{{% param "compose_version" %}}`
     > with the version of Compose you want to use.
 
 4.  Test the installation.
 
     ```console
     $ docker-compose.exe version
-    Docker Compose version {{site.compose_version}}
-    ```
+    Docker Compose version {{% param "compose_version" %}}
+    ```
\ No newline at end of file
diff --git a/content/compose/install/uninstall.md b/content/compose/install/uninstall.md
index 684273d7ad..c629237248 100644
--- a/content/compose/install/uninstall.md
+++ b/content/compose/install/uninstall.md
@@ -51,14 +51,13 @@ Or, if you have installed Compose for all users, run:
 > If you get a **Permission denied** error using either of the above
 > methods, you do not have the permissions allowing you to remove
 > `docker-compose`. To force the removal, prepend `sudo` to either of the above instructions and run it again.
-{: .tip}
+{ .tip }
 
 ### Inspect the location of the Compose CLI plugin
 
 To check where Compose is installed, use:
 
-{% raw %}
+
 ```console
 $ docker info --format '{{range .ClientInfo.Plugins}}{{if eq .Name "compose"}}{{.Path}}{{end}}{{end}}'
-```
-{% endraw %}
+```
\ No newline at end of file
diff --git a/content/compose/migrate.md b/content/compose/migrate.md
index 7f6e40cb64..9218a20fda 100644
--- a/content/compose/migrate.md
+++ b/content/compose/migrate.md
@@ -2,9 +2,9 @@
 title: Migrate to Compose V2
 description: How to migrate from Compose V1 to V2
 keywords: compose, upgrade, migration, v1, v2
-redirect_from:
-  - /compose/compose-v2/
-  - /compose/cli-command-compatibility/
+aliases:
+- /compose/compose-v2/
+- /compose/cli-command-compatibility/
 ---
 
 From July 2023 Compose V1 stopped receiving updates. It’s also no longer available in new releases of Docker Desktop.
@@ -36,7 +36,7 @@ For example, `docker --log-level=debug --tls compose up` enables debug logging f
 > **Tip**
 >
 > Update scripts to use Compose V2 by replacing the hyphen (`-`) with a space, using `docker compose` instead of `docker-compose`.
-{: .tip}
+{ .tip }
 
 ### Service container names
 
@@ -54,7 +54,7 @@ For example, running the Compose command `-p myproject up --scale=1 svc` results
 >
 >In Compose V2, the global `--compatibility` flag or `COMPOSE_COMPATIBILITY` environment variable preserves the Compose V1 behavior to use underscores (`_`) as the word separator.
 As this option must be specified for every Compose V2 command run, it's recommended that you only use this as a temporary measure while transitioning to Compose V2.
-{: .tip}
+{ .tip }
 
 ### Command-line flags and subcommands
 
@@ -94,7 +94,7 @@ verify that values appear as expected.
 >
 > Maintaining backwards compatibility with Compose V1 is typically achievable by ensuring that literal values (no
 interpolation) are single-quoted and values that should have interpolation applied are double-quoted.
-{: .tip}
+{ .tip }
 
 ## What does this mean for my projects that use Compose V1?
 
@@ -117,11 +117,9 @@ Note that even if `--compatibility` flag is used to preserve the V1 naming style
 
 ### Using Compose V2 with Docker-in-Docker
 
-Compose V2 is now included in the [Docker official image on Docker Hub](https://hub.docker.com/_/docker){:
-target="_blank" rel="noopener" class="_"}.
+Compose V2 is now included in the [Docker official image on Docker Hub](https://hub.docker.com/_/docker).
 
-Additionally, a new [docker/compose-bin image on Docker Hub](https://hub.docker.com/r/docker/compose-bin){:
-target="_blank" rel="noopener" class="_"} packages the latest version of Compose V2 for use in multi-stage builds.
+Additionally, a new [docker/compose-bin image on Docker Hub](https://hub.docker.com/r/docker/compose-bin) packages the latest version of Compose V2 for use in multi-stage builds.
 
 ## Can I still use Compose V1 if I want to?
 
@@ -130,12 +128,9 @@ Yes. You can still download and install Compose V1 packages, but you won't get s
 >**Warning**
 >
 > The final Compose V1 release, version 1.29.2, was May 10, 2021. These packages haven't received any security updates since then. Use at your own risk. 
-{: .warning}
+{ .warning }
 
 ## Additional Resources
-- [docker-compose V1 on PyPI](https://pypi.org/project/docker-compose/1.29.2/){:
-  target="_blank" rel="noopener" class="_"}
-- [docker/compose V1 on Docker Hub](https://hub.docker.com/r/docker/compose){:
-  target="_blank" rel="noopener" class="_"}
-- [docker-compose V1 source on GitHub](https://github.com/docker/compose/releases/tag/1.29.2){:
-  target="_blank" rel="noopener" class="_"}
+- [docker-compose V1 on PyPI](https://pypi.org/project/docker-compose/1.29.2/)
+- [docker/compose V1 on Docker Hub](https://hub.docker.com/r/docker/compose)
+- [docker-compose V1 source on GitHub](https://github.com/docker/compose/releases/tag/1.29.2)
\ No newline at end of file
diff --git a/content/compose/multiple-compose-files/_index.md b/content/compose/multiple-compose-files/_index.md
index f888a1e068..880f786c15 100644
--- a/content/compose/multiple-compose-files/_index.md
+++ b/content/compose/multiple-compose-files/_index.md
@@ -1,9 +1,11 @@
 ---
-description: General overview for the different ways you can work with multiple compose files in Docker Compose
+description: General overview for the different ways you can work with multiple compose
+  files in Docker Compose
 keywords: compose, compose file, merge, extends, include, docker compose
 title: Overview
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 This section contains information on the three key ways you can use multiple Compose files in your Compose application. 
 
@@ -15,4 +17,4 @@ Docker Compose provides three ways to manage this complexity when working with m
 
 - [Extend a Compose file](extends.md) by referring to another Compose file and selecting the bits you want to use in your own application, with the ability to override some attributes.
 - [Merge a set of Compose files](merge.md) together to create a composite Compose file.
-- [Include other Compose files](include.md) directly in to your Compose file. 
+- [Include other Compose files](include.md) directly in to your Compose file.
\ No newline at end of file
diff --git a/content/compose/multiple-compose-files/extends.md b/content/compose/multiple-compose-files/extends.md
index 0218b8b44f..8445802db2 100644
--- a/content/compose/multiple-compose-files/extends.md
+++ b/content/compose/multiple-compose-files/extends.md
@@ -1,9 +1,10 @@
 ---
-description: How to use Docker Compose's extends keyword to share configuration between files and projects
+description: How to use Docker Compose's extends keyword to share configuration between
+  files and projects
 keywords: fig, composition, compose, docker, orchestration, documentation, docs
 title: Extend your Compose file
-redirect_from:
- - /compose/extends/
+aliases:
+- /compose/extends/
 ---
 
 Docker Compose's [`extends` attribute](../compose-file/05-services.md#extends) lets you share common configurations
@@ -22,7 +23,7 @@ Compose files. Extend files can contain small fragments of configuration.
 Tracking which fragment of a service is relative to which path is difficult and
 confusing, so to keep paths easier to understand, all paths must be defined
 relative to the base file.
-{: .important}
+{ .important }
 
 ## How it works
 
@@ -190,4 +191,4 @@ break anything.
 
 ## Reference information
 
-- [`extends`](../compose-file/05-services.md#extends)
+- [`extends`](../compose-file/05-services.md#extends)
\ No newline at end of file
diff --git a/content/compose/multiple-compose-files/include.md b/content/compose/multiple-compose-files/include.md
index 5fae797854..b49223d776 100644
--- a/content/compose/multiple-compose-files/include.md
+++ b/content/compose/multiple-compose-files/include.md
@@ -38,4 +38,4 @@ This means the team managing `serviceB` can refactor its own database component
 
 ## Reference information
 
-[`include` top-level element](../compose-file/14-include.md)
+[`include` top-level element](../compose-file/14-include.md)
\ No newline at end of file
diff --git a/content/compose/multiple-compose-files/merge.md b/content/compose/multiple-compose-files/merge.md
index d07f3dc482..cd1f7d40a6 100644
--- a/content/compose/multiple-compose-files/merge.md
+++ b/content/compose/multiple-compose-files/merge.md
@@ -31,7 +31,7 @@ Compose files. Override files can contain small fragments of configuration.
 Tracking which fragment of a service is relative to which path is difficult and
 confusing, so to keep paths easier to understand, all paths must be defined
 relative to the base file.
-{: .important}
+{ .important }
 
 ## Merging rules
 
@@ -275,4 +275,4 @@ With such a constraint, code organization in a monorepo can become hard as a nat
 
 ## Reference information
 
-- [Merge rules](../compose-file/13-merge.md)
+- [Merge rules](../compose-file/13-merge.md)
\ No newline at end of file
diff --git a/content/compose/networking.md b/content/compose/networking.md
index 4711f0ce24..6262ca0e13 100644
--- a/content/compose/networking.md
+++ b/content/compose/networking.md
@@ -3,7 +3,8 @@ description: How Docker Compose sets up networking between containers
 keywords: documentation, docs, docker, compose, orchestration, containers, networking
 title: Networking in Compose
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 By default Compose sets up a single
 [network](../engine/reference/commandline/network_create.md) for your app. Each
@@ -64,7 +65,7 @@ If any containers have connections open to the old container, they are closed. I
 > **Tip**
 >
 > Reference containers by name, not IP, whenever possible. Otherwise you’ll need to constantly update the IP address you use.
-{: .tip }
+{ .tip }
 
 ## Link containers
 
@@ -181,4 +182,4 @@ Instead of attempting to create a network called `[projectname]_default`, Compos
 For full details of the network configuration options available, see the following references:
 
 - [Top-level `networks` element](compose-file/06-networks.md)
-- [Service-level `networks` attribute](compose-file/05-services.md#networks)
+- [Service-level `networks` attribute](compose-file/05-services.md#networks)
\ No newline at end of file
diff --git a/content/compose/production.md b/content/compose/production.md
index 51879e360e..564cc24a43 100644
--- a/content/compose/production.md
+++ b/content/compose/production.md
@@ -3,7 +3,8 @@ description: Guide to using Docker Compose in production
 keywords: compose, orchestration, containers, production
 title: Use Compose in production
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 When you define your app with Compose in development, you can use this
 definition to run your application in different environments such as CI,
@@ -62,4 +63,4 @@ You can use Compose to deploy an app to a remote Docker host by setting the
 appropriately. See also [Compose CLI environment variables](environment-variables/envvars.md).
 
 Once you've set up your environment variables, all the normal `docker compose`
-commands work with no further configuration.
+commands work with no further configuration.
\ No newline at end of file
diff --git a/content/compose/profiles.md b/content/compose/profiles.md
index 14a64ebd3f..ec1a7c4f1b 100644
--- a/content/compose/profiles.md
+++ b/content/compose/profiles.md
@@ -3,7 +3,8 @@ title: Using profiles with Compose
 desription: How to use profiles with Docker Compose
 keywords: cli, compose, profile, profiles reference
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 Profiles help you adjust the Compose application model for various uses and
 environments by selectively starting services.
@@ -54,7 +55,7 @@ Valid profiles names follow the regex format of `[a-zA-Z0-9][a-zA-Z0-9_.-]+`.
 >
 > The core services of your application shouldn't be assigned `profiles` so
 > they are always enabled and automatically started.
-{: .tip}
+{ .tip }
 
 ## Start specific profiles
 
@@ -179,4 +180,4 @@ $ COMPOSE_PROFILES=dev docker compose up phpmyadmin
 
 ## Reference information
 
-[`profiles`](compose-file/05-services.md#profiles)
+[`profiles`](compose-file/05-services.md#profiles)
\ No newline at end of file
diff --git a/content/compose/reference/_index.md b/content/compose/reference/_index.md
index a1cc9dc1df..8b3f444713 100644
--- a/content/compose/reference/_index.md
+++ b/content/compose/reference/_index.md
@@ -1,11 +1,12 @@
 ---
 description: Overview of the Docker Compose CLI
 keywords: fig, composition, compose, docker, orchestration, cli, reference, docker-compose
-redirect_from:
-- /compose/reference/overview/
 title: Overview of docker compose CLI
+aliases:
+- /compose/reference/overview/
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 This page provides the usage information for the `docker compose` Command.
 
@@ -18,9 +19,9 @@ This page provides the usage information for the `docker compose` Command.
 > to support most of the previous `docker-compose` features and flags. You can
 > run Compose V2 by replacing the hyphen (`-`) with a space, using `docker compose`,
 > instead of `docker-compose`.
-{: .important}
+{ .important }
 
-For more information about Docker Compose V2 GA, see the blog post [Announcing Compose V2 General Availability](https://www.docker.com/blog/announcing-compose-v2-general-availability/){: target="_blank" rel="noopener" class="_"}.
+For more information about Docker Compose V2 GA, see the blog post [Announcing Compose V2 General Availability](https://www.docker.com/blog/announcing-compose-v2-general-availability/).
 
 ## Command options overview and help
 
@@ -212,4 +213,4 @@ Also, you can set some of these variables in an [environment file](../environmen
 ## Where to go next
 
 * [CLI environment variables](../environment-variables/envvars.md)
-* [Declare default environment variables in file](../environment-variables/env-file.md)
+* [Declare default environment variables in file](../environment-variables/env-file.md)
\ No newline at end of file
diff --git a/content/compose/release-notes.md b/content/compose/release-notes.md
index 6dd0c77bd2..507154c4e7 100644
--- a/content/compose/release-notes.md
+++ b/content/compose/release-notes.md
@@ -3,15 +3,16 @@ title: Docker Compose release notes
 description: Release notes for Docker Compose
 keywords: release notes, compose
 toc_max: 2
-redirect_from:
-  - /release-notes/docker-compose/
+aliases:
+- /release-notes/docker-compose/
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 For more detailed information, see the [release notes in the Compose repo](https://github.com/docker/compose/releases/).
 
 ## 2.20.3
-{% include release-date.html date="2023-07-19" %}
+{{< release-date date="2023-07-19" >}}
 
 ### Update
 - Dependencies upgrade: bump golang to 1.21.0
@@ -26,7 +27,7 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Removed unnecessary warning when an option dependency exists successfully.
 
 ## 2.20.2
-{% include release-date.html date="2023-07-19" %}
+{{< release-date date="2023-07-19" >}}
 
 ### Bug fixes and enhancements
 - Added support for the `depends_on.required` attribute.
@@ -35,7 +36,7 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Fixed a bug resolving build context path for services using `extends.file`.
 
 ## 2.20.1
-{% include release-date.html date="2023-07-18" %}
+{{< release-date date="2023-07-18" >}}
 
 ### Update
 - Dependencies upgrade: bump golang to 1.20.6
@@ -44,7 +45,7 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Dependencies upgrade: bump docker-cli to v24.0.5-dev
 
 ## 2.20.0
-{% include release-date.html date="2023-07-11" %}
+{{< release-date date="2023-07-11" >}}
 
 ### Update
 - Dependencies upgrade: bump docker/cli-docs-tools to v0.6.0
@@ -65,7 +66,7 @@ For more detailed information, see the [release notes in the Compose repo](https
 * Improved some test speeds.
 
 ## 2.19.1
-{% include release-date.html date="2023-06-29" %}
+{{< release-date date="2023-06-29" >}}
 
 ### Update
 - Dependencies upgrade: bump compose-go to v1.15.1
@@ -76,7 +77,7 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Compose now warns if using a bind mount in a service `watch` configuration.
 
 ## 2.19.0
-{% include release-date.html date="2023-06-21" %}
+{{< release-date date="2023-06-21" >}}
 
 ### Update
 - Dependencies upgrade: bump compose-go to v1.15.0
@@ -114,13 +115,13 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Added more ignore rules to dependabot.
 
 ## 2.18.1
-{% include release-date.html date="2023-05-17" %}
+{{< release-date date="2023-05-17" >}}
 
 ### Bug fixes and enhancements
 - Fixed "Image not found" errors when building images
 
 ## 2.18.0
-{% include release-date.html date="2023-05-16" %}
+{{< release-date date="2023-05-16" >}}
 
 ### Update
 - Dependencies upgrade: bump compose-go to v1.13.5
@@ -149,32 +150,28 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Compose now reports that the external network is not found when Swarm is disabled
 
 ## 2.17.2
-{% include release-date.html date="2023-03-26" %}
+{{< release-date date="2023-03-26" >}}
 
 ### Update
 - Dependencies upgrade: bump compose-go to v1.13.2
 
 ### Bug fixes and enhancements
-- Fixed invalid project name error for directories with uppercase characters or `.` in the name. Fixed [compose#10405](https://github.com/docker/compose/issues/10405){:
-  target="_blank" rel="noopener" class="_"}
+- Fixed invalid project name error for directories with uppercase characters or `.` in the name. Fixed [compose#10405](https://github.com/docker/compose/issues/10405)
 
 ## 2.17.1
-{% include release-date.html date="2023-03-24" %}
+{{< release-date date="2023-03-24" >}}
 ### Update
 - Dependencies upgrade: bump buildkit to v0.11.5
 - Dependencies upgrade: bump compose-go to v1.13.1
 - Dependencies upgrade: bump golang to 1.20.2
 
 ### Bug fixes and enhancements
-- Fixed panic on `alpha watch` command. Pull Request [compose#10393](https://github.com/docker/compose/pull/10393){:
-  target="_blank" rel="noopener" class="_"}
-- Prevented conflicts for services named `extensions`. Fixed [compose-go#247](https://github.com/compose-spec/compose-go/issues/247){:
-  target="_blank" rel="noopener" class="_"}
-- Compose now validates project names more consistently. Fixed [compose-go#363](https://github.com/compose-spec/compose-go/issues/363){:
-  target="_blank" rel="noopener" class="_"}
+- Fixed panic on `alpha watch` command. Pull Request [compose#10393](https://github.com/docker/compose/pull/10393)
+- Prevented conflicts for services named `extensions`. Fixed [compose-go#247](https://github.com/compose-spec/compose-go/issues/247)
+- Compose now validates project names more consistently. Fixed [compose-go#363](https://github.com/compose-spec/compose-go/issues/363)
 
 ## 2.17.0
-{% include release-date.html date="2023-03-23" %}
+{{< release-date date="2023-03-23" >}}
 ### Upgrade notes
 - Project name validation is more strictly enforced. Project names can only include letters, numbers, `_`, `-` and must be lowercase and start with a letter or number.
 - Boolean fields in YAML must be either `true` or `false`. Deprecated YAML 1.1 values such as "on" or "no" are not supported.
@@ -187,65 +184,36 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Dependencies upgrade: bump compose-go to v1.13.0
 
 ### Bug fixes and enhancements
-* Introduced `--wait-timeout` on `up` command. Fixed [compose#10269](https://github.com/docker/compose/issues/10269){:
-  target="_blank" rel="noopener" class="_"}
-* Made `compose service --hash` output sort by service name. Pull Request [compose#10278](https://github.com/docker/compose/pull/10278){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now renders a compact TUI progress report to monitor layers download. Pull Request [compose#10281](https://github.com/docker/compose/pull/10281){:
-  target="_blank" rel="noopener" class="_"}
-* Introduced `restart` for `depends_on`. Fixed [compose#10284](https://github.com/docker/compose/issues/10284){:
-  target="_blank" rel="noopener" class="_"}
-* Added support of `NO_COLOR` env var. Fixed [compose#10340](https://github.com/docker/compose/issues/10340){:
-  target="_blank" rel="noopener" class="_"}
-* Progress writer now uses `dockercli.Err` stream. Fixed [compose#10366](https://github.com/docker/compose/issues/10366){:
-  target="_blank" rel="noopener" class="_"}
-* Added support for `additional_contexts` in the `build` service configuration. Fixed [compose#9461](https://github.com/docker/compose/issues/9461){:
-  target="_blank" rel="noopener" class="_"} [compose#9961](https://github.com/docker/compose/issues/9961){:
-  target="_blank" rel="noopener" class="_"}
-* Added file delete/rename handling in `watch` mode. Pull Request [compose#10386](https://github.com/docker/compose/pull/10386){:
-  target="_blank" rel="noopener" class="_"}
-* Introduced an `ignore` attribute in `watch` mode. Pull Request [compose#10385](https://github.com/docker/compose/pull/10385){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now uses progress writer to show copies status. Pull Request [compose#10387](https://github.com/docker/compose/pull/10387){:
-  target="_blank" rel="noopener" class="_"}
-* Updated reference documentation for `-p`/`--project-name` flag. Fixed [docs#16915](https://github.com/docker/docs/pull/16915){:
-  target="_blank" rel="noopener" class="_"}, [compose-spec#311](https://github.com/compose-spec/compose-spec/issues/311){:
-  target="_blank" rel="noopener" class="_"}
-* Introduced a `replace` label to track the relationship between old and new containers of a service. Fixed [compose#9600](https://github.com/docker/compose/issues/9600){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed a bug that meant dependent services were not restarted after a service was restarted. Fixed [compose#10263](https://github.com/docker/compose/issues/10263){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now ignores services without a build section in `watch` mode. Fixed [compose#10270](https://github.com/docker/compose/issues/10270){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now applies config options for pseudo-subcommands. Fixed [compose#10286](https://github.com/docker/compose/issues/10286){:
-  target="_blank" rel="noopener" class="_"}
-* Compose manages only containers with config_hash labels (i.e, created by compose). Fixed [compose#10317](https://github.com/docker/compose/issues/10317){:
-  target="_blank" rel="noopener" class="_"}
-* Compose triggers an error if the project name is empty after normalization. Fixed [compose#10313](https://github.com/docker/compose/issues/10313){:
-  target="_blank" rel="noopener" class="_"}
-* Compose restarts only needed services by checking `depends_on` relations. Fixed [compose#10337](https://github.com/docker/compose/issues/10337){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed a display issue on small terminals. Fixed [compose#10322](https://github.com/docker/compose/issues/10322){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed an issue with building the built images IDs collection. Pull Request [compose#10372](https://github.com/docker/compose/issues/10372){:
-  target="_blank" rel="noopener" class="_"}
-* Use configured name separator to define oneoff container name. Fixed [compose#10354](https://github.com/docker/compose/issues/10354){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed concurrent map read/write issue when recreating containers. Fixed [compose#10319](https://github.com/docker/compose/issues/10319){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `stop` and `rm` commands. Pull Request [compose#10257](https://github.com/docker/compose/issues/10257){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `pull` command. Pull Request [compose#10341](https://github.com/docker/compose/issues/10341){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `push` command. Pull Request [compose#10355](https://github.com/docker/compose/issues/10355){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `exec` command. Pull Request [compose#10252](https://github.com/docker/compose/issues/10252){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `restart` command. Pull Request [compose#10339](https://github.com/docker/compose/issues/10339){:
-  target="_blank" rel="noopener" class="_"}
+* Introduced `--wait-timeout` on `up` command. Fixed [compose#10269](https://github.com/docker/compose/issues/10269)
+* Made `compose service --hash` output sort by service name. Pull Request [compose#10278](https://github.com/docker/compose/pull/10278)
+* Compose now renders a compact TUI progress report to monitor layers download. Pull Request [compose#10281](https://github.com/docker/compose/pull/10281)
+* Introduced `restart` for `depends_on`. Fixed [compose#10284](https://github.com/docker/compose/issues/10284)
+* Added support of `NO_COLOR` env var. Fixed [compose#10340](https://github.com/docker/compose/issues/10340)
+* Progress writer now uses `dockercli.Err` stream. Fixed [compose#10366](https://github.com/docker/compose/issues/10366)
+* Added support for `additional_contexts` in the `build` service configuration. Fixed [compose#9461](https://github.com/docker/compose/issues/9461) [compose#9961](https://github.com/docker/compose/issues/9961)
+* Added file delete/rename handling in `watch` mode. Pull Request [compose#10386](https://github.com/docker/compose/pull/10386)
+* Introduced an `ignore` attribute in `watch` mode. Pull Request [compose#10385](https://github.com/docker/compose/pull/10385)
+* Compose now uses progress writer to show copies status. Pull Request [compose#10387](https://github.com/docker/compose/pull/10387)
+* Updated reference documentation for `-p`/`--project-name` flag. Fixed [docs#16915](https://github.com/docker/docs/pull/16915), [compose-spec#311](https://github.com/compose-spec/compose-spec/issues/311)
+* Introduced a `replace` label to track the relationship between old and new containers of a service. Fixed [compose#9600](https://github.com/docker/compose/issues/9600)
+* Fixed a bug that meant dependent services were not restarted after a service was restarted. Fixed [compose#10263](https://github.com/docker/compose/issues/10263)
+* Compose now ignores services without a build section in `watch` mode. Fixed [compose#10270](https://github.com/docker/compose/issues/10270)
+* Compose now applies config options for pseudo-subcommands. Fixed [compose#10286](https://github.com/docker/compose/issues/10286)
+* Compose manages only containers with config_hash labels (i.e, created by compose). Fixed [compose#10317](https://github.com/docker/compose/issues/10317)
+* Compose triggers an error if the project name is empty after normalization. Fixed [compose#10313](https://github.com/docker/compose/issues/10313)
+* Compose restarts only needed services by checking `depends_on` relations. Fixed [compose#10337](https://github.com/docker/compose/issues/10337)
+* Fixed a display issue on small terminals. Fixed [compose#10322](https://github.com/docker/compose/issues/10322)
+* Fixed an issue with building the built images IDs collection. Pull Request [compose#10372](https://github.com/docker/compose/issues/10372)
+* Use configured name separator to define oneoff container name. Fixed [compose#10354](https://github.com/docker/compose/issues/10354)
+* Fixed concurrent map read/write issue when recreating containers. Fixed [compose#10319](https://github.com/docker/compose/issues/10319)
+* Compose now supports Dry Run mode for `stop` and `rm` commands. Pull Request [compose#10257](https://github.com/docker/compose/issues/10257)
+* Compose now supports Dry Run mode for `pull` command. Pull Request [compose#10341](https://github.com/docker/compose/issues/10341)
+* Compose now supports Dry Run mode for `push` command. Pull Request [compose#10355](https://github.com/docker/compose/issues/10355)
+* Compose now supports Dry Run mode for `exec` command. Pull Request [compose#10252](https://github.com/docker/compose/issues/10252)
+* Compose now supports Dry Run mode for `restart` command. Pull Request [compose#10339](https://github.com/docker/compose/issues/10339)
 
 ## 2.16.0
-{% include release-date.html date="2023-02-08" %}
+{{< release-date date="2023-02-08" >}}
 ### Update
 - Dependencies upgrade: bump docker to v23.0.0
 - Dependencies upgrade: bump docker-cli to v23.0.0
@@ -255,282 +223,214 @@ For more detailed information, see the [release notes in the Compose repo](https
 - Dependencies upgrade: bump golang to 1.20
 
 ### Bug fixes and enhancements
-* Introduced `--remove-orphans` for the `compose create` command. Fixed [compose#9718](https://github.com/docker/compose/issues/9718){:
-  target="_blank" rel="noopener" class="_"}
-* Shortened the TTY output when the terminal is too small. Fixed [compose#9962](https://github.com/docker/compose/issues/9962){:
-  target="_blank" rel="noopener" class="_"}
-* Added `remove-orphans` functionality to run. Fixed [compose#9718](https://github.com/docker/compose/issues/9718#issuecomment-1209448445){:
-  target="_blank" rel="noopener" class="_"}
-* Introduced the experimental `watch` command. Pull Request [compose#10163](https://github.com/docker/compose/pull/10163){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now allows TTY to be allocated with `-t`. Fixed [compose#10161](https://github.com/docker/compose/issues/10161){:
-  target="_blank" rel="noopener" class="_"}
-* Introduced the experimental `dry-run` command. Pull Request [compose#10173](https://github.com/docker/compose/issues/10173){:
-  target="_blank" rel="noopener" class="_"}
-* Updated the documentation to explain ways to configure parallelism. Pull Request [compose#10198](https://github.com/docker/compose/issues/10198){:
-  target="_blank" rel="noopener" class="_"}
-* Aligned the `logs` command with docker CLI by aliasing `-n` for `--tail`. Fixed [compose#10199](https://github.com/docker/compose/issues/10199){:
-  target="_blank" rel="noopener" class="_"}
-* Added support for `docker compose build --push`. Pull Request [compose#10148](https://github.com/docker/compose/issues/10148){:
-  target="_blank" rel="noopener" class="_"}
-* Added `--scale` to the `compose create` command. Fixed [compose#10208](https://github.com/docker/compose/issues/10208){:
-  target="_blank" rel="noopener" class="_"}
-* Renamed `convert` to `config` to align with the Compose V1 UX. Pull Request [compose#10214](https://github.com/docker/compose/issues/10214){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now passes the proxy config as build args. Fixed [compose#8797](https://github.com/docker/compose/issues/8797){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed parsing issue in `compose up` by ignoring containers not created by Compose. Fixed [compose#10162](https://github.com/docker/compose/issues/10162#issuecomment-1384989985){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed the goroutine leak in log formatter initialization. Fixed [compose#10157](https://github.com/docker/compose/issues/10157){:
-    target="_blank" rel="noopener" class="_"}
-* Fixed an issue where compose logs don't exit when all running containers have been stopped. Pull Request [compose#10181](https://github.com/docker/compose/issues/10181){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed the documentation to reflect `docker compose ps` being aligned with `docker ps`. Pull Request [compose#10195](https://github.com/docker/compose/issues/10195){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed an issue where the remote Buildx driver was not found. Fixed [compose#9893](https://github.com/docker/compose/issues/9893){:
-  target="_blank" rel="noopener" class="_"}
-* Improved logging when recreating a service container. Pull request [compose#10236](https://github.com/docker/compose/issues/10236){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed an issue so Compose now only waits for containers concerned by the wait condition. Fixed [compose#10200](https://github.com/docker/compose/issues/10200){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now prevents assignment to entry in nil map. Fixed [compose#10244](https://github.com/docker/compose/issues/10244){:
-  target="_blank" rel="noopener" class="_"}
-* Added a dedicated GitHub Action workflow for Cucumber tests. Pull Request [compose#10165](https://github.com/docker/compose/issues/10165){:
-  target="_blank" rel="noopener" class="_"}
-* Cleaned the TUI lines when switching in compact log mode. Fixed [compose#10201](https://github.com/docker/compose/issues/10201){:
-  target="_blank" rel="noopener" class="_"}
-* Added Tilt watcher to detect code changes in watch mode. Pull Request [compose#10218](https://github.com/docker/compose/issues/10218){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `kill` command. Fixed [compose#10210](https://github.com/docker/compose/issues/10210){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `pause` command.Fixed [compose#10217](https://github.com/docker/compose/issues/10217){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now supports Dry Run mode for `cp` command.Fixed [compose#10235](https://github.com/docker/compose/issues/10235){:
-  target="_blank" rel="noopener" class="_"}
+* Introduced `--remove-orphans` for the `compose create` command. Fixed [compose#9718](https://github.com/docker/compose/issues/9718)
+* Shortened the TTY output when the terminal is too small. Fixed [compose#9962](https://github.com/docker/compose/issues/9962)
+* Added `remove-orphans` functionality to run. Fixed [compose#9718](https://github.com/docker/compose/issues/9718#issuecomment-1209448445)
+* Introduced the experimental `watch` command. Pull Request [compose#10163](https://github.com/docker/compose/pull/10163)
+* Compose now allows TTY to be allocated with `-t`. Fixed [compose#10161](https://github.com/docker/compose/issues/10161)
+* Introduced the experimental `dry-run` command. Pull Request [compose#10173](https://github.com/docker/compose/issues/10173)
+* Updated the documentation to explain ways to configure parallelism. Pull Request [compose#10198](https://github.com/docker/compose/issues/10198)
+* Aligned the `logs` command with docker CLI by aliasing `-n` for `--tail`. Fixed [compose#10199](https://github.com/docker/compose/issues/10199)
+* Added support for `docker compose build --push`. Pull Request [compose#10148](https://github.com/docker/compose/issues/10148)
+* Added `--scale` to the `compose create` command. Fixed [compose#10208](https://github.com/docker/compose/issues/10208)
+* Renamed `convert` to `config` to align with the Compose V1 UX. Pull Request [compose#10214](https://github.com/docker/compose/issues/10214)
+* Compose now passes the proxy config as build args. Fixed [compose#8797](https://github.com/docker/compose/issues/8797)
+* Fixed parsing issue in `compose up` by ignoring containers not created by Compose. Fixed [compose#10162](https://github.com/docker/compose/issues/10162#issuecomment-1384989985)
+* Fixed the goroutine leak in log formatter initialization. Fixed [compose#10157](https://github.com/docker/compose/issues/10157)
+* Fixed an issue where compose logs don't exit when all running containers have been stopped. Pull Request [compose#10181](https://github.com/docker/compose/issues/10181)
+* Fixed the documentation to reflect `docker compose ps` being aligned with `docker ps`. Pull Request [compose#10195](https://github.com/docker/compose/issues/10195)
+* Fixed an issue where the remote Buildx driver was not found. Fixed [compose#9893](https://github.com/docker/compose/issues/9893)
+* Improved logging when recreating a service container. Pull request [compose#10236](https://github.com/docker/compose/issues/10236)
+* Fixed an issue so Compose now only waits for containers concerned by the wait condition. Fixed [compose#10200](https://github.com/docker/compose/issues/10200)
+* Compose now prevents assignment to entry in nil map. Fixed [compose#10244](https://github.com/docker/compose/issues/10244)
+* Added a dedicated GitHub Action workflow for Cucumber tests. Pull Request [compose#10165](https://github.com/docker/compose/issues/10165)
+* Cleaned the TUI lines when switching in compact log mode. Fixed [compose#10201](https://github.com/docker/compose/issues/10201)
+* Added Tilt watcher to detect code changes in watch mode. Pull Request [compose#10218](https://github.com/docker/compose/issues/10218)
+* Compose now supports Dry Run mode for `kill` command. Fixed [compose#10210](https://github.com/docker/compose/issues/10210)
+* Compose now supports Dry Run mode for `pause` command.Fixed [compose#10217](https://github.com/docker/compose/issues/10217)
+* Compose now supports Dry Run mode for `cp` command.Fixed [compose#10235](https://github.com/docker/compose/issues/10235)
 
 ## 2.15.1
-{% include release-date.html date="2023-01-09" %}
+{{< release-date date="2023-01-09" >}}
 ### Update
 - Dependencies upgrade to fix Golan CVE-2022-27664 and CVE-2022-32149
 
 ### Bug fixes and enhancements
-* Added support for UTS namespace. Fixed [compose#8408](https://github.com/docker/compose/issues/8408){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed filtering issue when no filter set. Fixed [roadmap#418](https://github.com/docker/roadmap/issues/418){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed concurrent map writes issue during build step. Pull Request [compose#10151](https://github.com/docker/compose/pull/10151){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed issue when stdin is not a terminal. Fixed [compose#9739](https://github.com/docker/compose/issues/9739){:
-  target="_blank" rel="noopener" class="_"}
+* Added support for UTS namespace. Fixed [compose#8408](https://github.com/docker/compose/issues/8408)
+* Fixed filtering issue when no filter set. Fixed [roadmap#418](https://github.com/docker/roadmap/issues/418)
+* Fixed concurrent map writes issue during build step. Pull Request [compose#10151](https://github.com/docker/compose/pull/10151)
+* Fixed issue when stdin is not a terminal. Fixed [compose#9739](https://github.com/docker/compose/issues/9739)
 
 ## 2.15.0
-{% include release-date.html date="2023-01-05" %}
+{{< release-date date="2023-01-05" >}}
 ### Update
 - Dependencies upgrade: bump compose-go to v1.8.1
 - Dependencies upgrade: bump cli-docs-tool to 0.5.1
 
 ### Bug fixes and enhancements
-* Added support of the `privileged` attribute in the `service.build` section. Pull Request [compose#10112](https://github.com/docker/compose/pull/10112){:
-  target="_blank" rel="noopener" class="_"}
-* Introduced `--ignore-buildable` to ignore buildable images on pull. Fixed [compose#8805](https://github.com/docker/compose/issues/8805){:
-  target="_blank" rel="noopener" class="_"}
-* Introduceed `--no-attach` to ignore some service outputs. Fixed [compose#8546](https://github.com/docker/compose/issues/8546){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed issue with `logs` when `driver:none` is set. Fixed [compose#9030](https://github.com/docker/compose/issues/9030){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now relies on dockerCLI.streams. Pull Request [compose#10082](https://github.com/docker/compose/pull/10082){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed issue with service hash that MUST exclude replicas. Fixed [compose#10077](https://github.com/docker/compose/issues/10077){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now checks service names based on project, not running containers. Fixed [compose#9951](https://github.com/docker/compose/issues/9951){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed security opts support (seccomp and unconfined). Fixed [compose#9505](https://github.com/docker/compose/issues/9505){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed empty file when using compose config in case of smaller source files. Fixed [compose#10121](https://github.com/docker/compose/issues/10121){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed issue with `--pull` not applied on `compose up`. Fixed [compose#10125](https://github.com/docker/compose/issues/10125){:
-  target="_blank" rel="noopener" class="_"}
-* Compose should ignore not only auto-removed containers but also "removal in progress" for orphan containers. Pull Request [compose#10136](https://github.com/docker/compose/pull/10136){:
-  target="_blank" rel="noopener" class="_"}
-* Compose limits build concurrency according to `--parallel`. Fixed [compose#9091](https://github.com/docker/compose/issues/9091){:
-  target="_blank" rel="noopener" class="_"}
+* Added support of the `privileged` attribute in the `service.build` section. Pull Request [compose#10112](https://github.com/docker/compose/pull/10112)
+* Introduced `--ignore-buildable` to ignore buildable images on pull. Fixed [compose#8805](https://github.com/docker/compose/issues/8805)
+* Introduceed `--no-attach` to ignore some service outputs. Fixed [compose#8546](https://github.com/docker/compose/issues/8546)
+* Fixed issue with `logs` when `driver:none` is set. Fixed [compose#9030](https://github.com/docker/compose/issues/9030)
+* Compose now relies on dockerCLI.streams. Pull Request [compose#10082](https://github.com/docker/compose/pull/10082)
+* Fixed issue with service hash that MUST exclude replicas. Fixed [compose#10077](https://github.com/docker/compose/issues/10077)
+* Compose now checks service names based on project, not running containers. Fixed [compose#9951](https://github.com/docker/compose/issues/9951)
+* Fixed security opts support (seccomp and unconfined). Fixed [compose#9505](https://github.com/docker/compose/issues/9505)
+* Fixed empty file when using compose config in case of smaller source files. Fixed [compose#10121](https://github.com/docker/compose/issues/10121)
+* Fixed issue with `--pull` not applied on `compose up`. Fixed [compose#10125](https://github.com/docker/compose/issues/10125)
+* Compose should ignore not only auto-removed containers but also "removal in progress" for orphan containers. Pull Request [compose#10136](https://github.com/docker/compose/pull/10136)
+* Compose limits build concurrency according to `--parallel`. Fixed [compose#9091](https://github.com/docker/compose/issues/9091)
 
 ## 2.14.2
-{% include release-date.html date="2022-12-20" %}
+{{< release-date date="2022-12-20" >}}
 ### Update
 - Dependencies upgrade: bump containerd to 1.6.14
 
 ### Bug fixes and enhancements
-* Compose now uses DOCKER_DEFAULT_PLATFORM to determine the platform when creating a container. Fixed [compose#10041](https://github.com/docker/compose/pull/10041){:
-  target="_blank" rel="noopener" class="_"}
-* Compose now detects when dependency failed to start. Fixed [compose#9732](https://github.com/docker/compose/pull/9732){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed WCOW volume mounts.  Fixed [compose#9577](https://github.com/docker/compose/pull/9577){:target="_blank" rel="noopener" class="_"}
-* List only running containers when using `--all=false`.  Fixed [compose#10085](https://github.com/docker/compose/pull/10085){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed a regression when running pull `--ignore-pull-failures`.  Fixed [compose#10089](https://github.com/docker/compose/pull/10089){:
-  target="_blank" rel="noopener" class="_"}
-* Fixed CPU quota issue. Fixed [compose#10073](https://github.com/docker/compose/pull/10073){:target="_blank" rel="noopener" class="_"}
-* Fixed race condition on compose logs. Fixed [compose#8880](https://github.com/docker/compose/pull/8880){:target="_blank" rel="noopener" class="_"}
-* Updated projectOptions to be public by renaming it to ProjectOptions. Fixed [compose#100102](https://github.com/docker/compose/pull/100102){:
-target="_blank" rel="noopener" class="_"}
+* Compose now uses DOCKER_DEFAULT_PLATFORM to determine the platform when creating a container. Fixed [compose#10041](https://github.com/docker/compose/pull/10041)
+* Compose now detects when dependency failed to start. Fixed [compose#9732](https://github.com/docker/compose/pull/9732)
+* Fixed WCOW volume mounts.  Fixed [compose#9577](https://github.com/docker/compose/pull/9577)
+* List only running containers when using `--all=false`.  Fixed [compose#10085](https://github.com/docker/compose/pull/10085)
+* Fixed a regression when running pull `--ignore-pull-failures`.  Fixed [compose#10089](https://github.com/docker/compose/pull/10089)
+* Fixed CPU quota issue. Fixed [compose#10073](https://github.com/docker/compose/pull/10073)
+* Fixed race condition on compose logs. Fixed [compose#8880](https://github.com/docker/compose/pull/8880)
+* Updated projectOptions to be public by renaming it to ProjectOptions. Fixed [compose#100102](https://github.com/docker/compose/pull/100102)
 
 ## 2.14.1
-{% include release-date.html date="2022-12-15" %}
+{{< release-date date="2022-12-15" >}}
 
 ### Updates
 - Dependencies upgrade: bump Go to 1.19.4
 - Dependencies upgrade: bump containerd to 1.6.12
 
 ### Bug fixes and enhancements
-- Added `--parallel` to limit concurrent engine calls. Pull Request [compose#10030](https://github.com/docker/compose/pull/10030){:
-  target="_blank" rel="noopener" class="_"}
-- Distinguished stdout and stderr in `up` logs. Fixed [compose#8098](https://github.com/docker/compose/issues/8098){:target="_blank" 
-rel="noopener" class="_"}
-- Aligned `compose ps` output with `docker ps`. Fixed [compose#6867](https://github.com/docker/compose/issues/6867){:target="_blank"
-rel="noopener" class="_"}
-- Added `--include-deps` to push command. Pull Request [compose#10044](https://github.com/docker/compose/pull/10044){:target="_blank"
-  rel="noopener" class="_"}
-- Introduced `--timestamp` option on `compose up`. Fixed [compose#5730](https://github.com/docker/compose/issues/5730){:target="_blank"
-  rel="noopener" class="_"}
-- Compose now applies uid/gid when creating a secret from the environment. Pull Request [compose#10084](https://github.com/docker/compose/pull/10084){:target="_blank"
-  rel="noopener" class="_"}
-- Fixed deadlock when waiting for attached-dependencies. Fixed [compose#10021](https://github.com/docker/compose/pull/10021){:target="_blank"
-  rel="noopener" class="_"}
-- Fixed race condition when collecting pulled images IDs. Fixed [compose#9897](https://github.com/docker/compose/pull/9897){:target="_blank"
-  rel="noopener" class="_"}
-- Compose doesn't stop the `pull` command for images that can be built. Fixed [compose#8724](https://github.com/docker/compose/pull/8724){:target="_blank"
-  rel="noopener" class="_"}
-- Fixed corner case when there's no container to attach to. Fixed [compose#8752](https://github.com/docker/compose/pull/8752){:target="_blank"
-  rel="noopener" class="_"}
+- Added `--parallel` to limit concurrent engine calls. Pull Request [compose#10030](https://github.com/docker/compose/pull/10030)
+- Distinguished stdout and stderr in `up` logs. Fixed [compose#8098](https://github.com/docker/compose/issues/8098)
+- Aligned `compose ps` output with `docker ps`. Fixed [compose#6867](https://github.com/docker/compose/issues/6867)
+- Added `--include-deps` to push command. Pull Request [compose#10044](https://github.com/docker/compose/pull/10044)
+- Introduced `--timestamp` option on `compose up`. Fixed [compose#5730](https://github.com/docker/compose/issues/5730)
+- Compose now applies uid/gid when creating a secret from the environment. Pull Request [compose#10084](https://github.com/docker/compose/pull/10084)
+- Fixed deadlock when waiting for attached-dependencies. Fixed [compose#10021](https://github.com/docker/compose/pull/10021)
+- Fixed race condition when collecting pulled images IDs. Fixed [compose#9897](https://github.com/docker/compose/pull/9897)
+- Compose doesn't stop the `pull` command for images that can be built. Fixed [compose#8724](https://github.com/docker/compose/pull/8724)
+- Fixed corner case when there's no container to attach to. Fixed [compose#8752](https://github.com/docker/compose/pull/8752)
 - Compose containers' startup must run sequentially for engine to assign distinct ports within a configured range. Fixed 
-[compose#8530](https://github.com/docker/compose/pull/8530){:target="_blank" rel="noopener" class="_"}
-- Fixed parsing of `repository:tag`. Fixed [compose#9208](https://github.com/docker/compose/pull/9208){:target="_blank"
-  rel="noopener" class="_"}
-- Load project from files when explicitly set by user. Fixed [compose#9554](https://github.com/docker/compose/pull/9554){:target="_blank"
-  rel="noopener" class="_"} 
+[compose#8530](https://github.com/docker/compose/pull/8530)
+- Fixed parsing of `repository:tag`. Fixed [compose#9208](https://github.com/docker/compose/pull/9208)
+- Load project from files when explicitly set by user. Fixed [compose#9554](https://github.com/docker/compose/pull/9554) 
 
 ## 2.14.0
-{% include release-date.html date="2022-12-02" %}
+{{< release-date date="2022-12-02" >}}
 
 ### Updates
 - Dependencies upgrade: bump compose-go to [v1.8.0](https://github.com/compose-spec/compose-go/releases/tag/v1.8.0)
 - Dependencies upgrade: bump Go to 1.19.3
 
 ### Bug fixes and enhancements
-- Added `oom_score_adj` field to service definition. Pull Request [compose#10019](https://github.com/docker/compose/issues/10019){:
-  target="_blank" rel="noopener" class="_"}
-- Added mode field for tmpfs mount permissions. Pull Request [compose#10031](https://github.com/docker/compose/issues/10031){:
-  target="_blank" rel="noopener" class="_"}
-- Compose now only stops services started by `up` when interrupted. Fixed [compose#10028](https://github.com/docker/compose/issues/10028){:
-  target="_blank" rel="noopener" class="_"}
-- Compose now loads implicit profiles for targeted services. Fixed [compose#10025](https://github.com/docker/compose/issues/10025){:target="
-  _blank" rel="noopener" class="_"}
-- Compose does not require `service.build.platforms` to be set if `service.platform` is set. Fixed [compose#10017](https://github.com/docker/compose/issues/10017){:
-  target="_blank" rel="noopener" class="_"}
-- Plain output is used during buildx image builds if `--ansi=never` is set. Fixed [compose#10020](https://github.com/docker/compose/issues/10020){:
-  target="_blank" rel="noopener" class="_"}
-- `COMPOSE_IGNORE_ORPHANS` environment variable now behaves more consistently. Fixed [compose#10035](https://github.com/docker/compose/issues/10035){:
-  target="_blank" rel="noopener" class="_"}
-- Compose now uses the correct image name separator in `convert`. Fixed [compose#9904](https://github.com/docker/compose/issues/9904){:target="
-  _blank" rel="noopener" class="_"}
-- Fixed `run` for services using `network_mode: service:NAME`. Fixed [compose#10036](https://github.com/docker/compose/issues/10036){:
-  target="_blank" rel="noopener" class="_"}
+- Added `oom_score_adj` field to service definition. Pull Request [compose#10019](https://github.com/docker/compose/issues/10019)
+- Added mode field for tmpfs mount permissions. Pull Request [compose#10031](https://github.com/docker/compose/issues/10031)
+- Compose now only stops services started by `up` when interrupted. Fixed [compose#10028](https://github.com/docker/compose/issues/10028)
+- Compose now loads implicit profiles for targeted services. Fixed [compose#10025](https://github.com/docker/compose/issues/10025)
+- Compose does not require `service.build.platforms` to be set if `service.platform` is set. Fixed [compose#10017](https://github.com/docker/compose/issues/10017)
+- Plain output is used during buildx image builds if `--ansi=never` is set. Fixed [compose#10020](https://github.com/docker/compose/issues/10020)
+- `COMPOSE_IGNORE_ORPHANS` environment variable now behaves more consistently. Fixed [compose#10035](https://github.com/docker/compose/issues/10035)
+- Compose now uses the correct image name separator in `convert`. Fixed [compose#9904](https://github.com/docker/compose/issues/9904)
+- Fixed `run` for services using `network_mode: service:NAME`. Fixed [compose#10036](https://github.com/docker/compose/issues/10036)
 
 ## 2.13.0
-{% include release-date.html date="2022-11-23" %}
+{{< release-date date="2022-11-23" >}}
 
 ### Updates
 - Dependencies upgrade: bump containerd to 1.6.10
 - Dependencies upgrade: bump docker-credential-helpers to v0.7.0
-- Update CI dependencies. Pull Request [compose#9982](https://github.com/docker/compose/pull/9982){:target="_blank" rel="noopener" class="_"}
+- Update CI dependencies. Pull Request [compose#9982](https://github.com/docker/compose/pull/9982)
 
 ### Bug fixes and enhancements
-- Added a `no-consistency` option to `convert` command. Fixed [compose#9963](https://github.com/docker/compose/issues/9963){:target="_blank" rel="noopener" class="_"}
-- Added a `build` option to `run` command. Fixed [compose#10003](https://github.com/docker/compose/issues/10003){:target="_blank" rel="noopener" class="_"}
-- Fixed mapping `restart_policy.condition` to engine supported values. Fixed [compose#8756](https://github.com/docker/compose/issues/8756){:target="_blank" rel="noopener" class="_"}, [docs#15936](https://github.com/docker/docs/pull/15936){:target="_blank" rel="noopener" class="_"}
-- Fixed missing support of `deploy.reservation.memory`. Fixed [compose#9902](https://github.com/docker/compose/issues/9902){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to prevent usage of `COMPOSE_PROFILES` when `--profile` arg is used. Fixed [compose#9895](https://github.com/docker/compose/issues/9895){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to prevent pulling a service's image when depending on a service which will build this image. Fixed [compose#9983](https://github.com/docker/compose/issues/9983){:target="_blank" rel="noopener" class="_"}
-- Fixed parsing issue when a container number label is not found. Fixed [compose#10004](https://github.com/docker/compose/issues/10004){:target="_blank" rel="noopener" class="_"}
-- Compose now uses the platform value defined by `DOCKER_DEFAULT_PLATFORM` when no `service.platform` defined. Fixed [compose#9889](https://github.com/docker/compose/issues/9889){:target="_blank" rel="noopener" class="_"}
-- Removed usage of the deprecated dependency `gotest.tools` v2. Pull Request [compose#9935](https://github.com/docker/compose/pull/9935){:target="_blank" rel="noopener" class="_"}
-- Excluded issues labeled with `kind/feature` from stale bot process. Fixed [compose#9988](https://github.com/docker/compose/pull/9988){:target="_blank" rel="noopener" class="_"}
+- Added a `no-consistency` option to `convert` command. Fixed [compose#9963](https://github.com/docker/compose/issues/9963)
+- Added a `build` option to `run` command. Fixed [compose#10003](https://github.com/docker/compose/issues/10003)
+- Fixed mapping `restart_policy.condition` to engine supported values. Fixed [compose#8756](https://github.com/docker/compose/issues/8756), [docs#15936](https://github.com/docker/docs/pull/15936)
+- Fixed missing support of `deploy.reservation.memory`. Fixed [compose#9902](https://github.com/docker/compose/issues/9902)
+- Fixed a bug to prevent usage of `COMPOSE_PROFILES` when `--profile` arg is used. Fixed [compose#9895](https://github.com/docker/compose/issues/9895)
+- Fixed a bug to prevent pulling a service's image when depending on a service which will build this image. Fixed [compose#9983](https://github.com/docker/compose/issues/9983)
+- Fixed parsing issue when a container number label is not found. Fixed [compose#10004](https://github.com/docker/compose/issues/10004)
+- Compose now uses the platform value defined by `DOCKER_DEFAULT_PLATFORM` when no `service.platform` defined. Fixed [compose#9889](https://github.com/docker/compose/issues/9889)
+- Removed usage of the deprecated dependency `gotest.tools` v2. Pull Request [compose#9935](https://github.com/docker/compose/pull/9935)
+- Excluded issues labeled with `kind/feature` from stale bot process. Fixed [compose#9988](https://github.com/docker/compose/pull/9988)
 
 
 ## 2.12.2
-{% include release-date.html date="2022-10-21" %}
+{{< release-date date="2022-10-21" >}}
 
 ### Updates
-- Updated Docker Engine API to restore compatibility with Golang 1.18 needed for Linux packaging. Pull Request [compose#9940](https://github.com/docker/compose/pull/9940){:target="_blank" rel="noopener" class="_"}
+- Updated Docker Engine API to restore compatibility with Golang 1.18 needed for Linux packaging. Pull Request [compose#9940](https://github.com/docker/compose/pull/9940)
 
-For the full change log or additional information, check the [Compose repository 2.12.2 release page](https://github.com/docker/compose/releases/tag/v2.12.2){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.12.2 release page](https://github.com/docker/compose/releases/tag/v2.12.2).
 
 ## 2.12.1
-{% include release-date.html date="2022-10-21" %}
+{{< release-date date="2022-10-21" >}}
 
 ### Security
-- Updated Docker Engine API to apply fix of [CVE-2022-39253](https://nvd.nist.gov/vuln/detail/CVE-2022-39253). Pull Request [compose#9934](https://github.com/docker/compose/pull/9934){:target="_blank" rel="noopener" class="_"}
+- Updated Docker Engine API to apply fix of [CVE-2022-39253](https://nvd.nist.gov/vuln/detail/CVE-2022-39253). Pull Request [compose#9934](https://github.com/docker/compose/pull/9934)
 
-For the full change log or additional information, check the [Compose repository 2.12.1 release page](https://github.com/docker/compose/releases/tag/v2.12.1){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.12.1 release page](https://github.com/docker/compose/releases/tag/v2.12.1).
 
 ## 2.12.0
-{% include release-date.html date="2022-10-18" %}
+{{< release-date date="2022-10-18" >}}
 
 ### Updates
 - CI update to the documentation repository path
 - Upgraded to compose-go from [1.5.1 to 1.6.0](https://github.com/compose-spec/compose-go/releases/tag/v1.6.0)
-{:target="_blank" rel="noopener" class="_"}
+
 - Updated to go 1.19.2 to address CVE-2022-2879, CVE-2022-2880, CVE-2022-41715
 
 ### Bug fixes and enhancements
-- Added a `quiet` option when pushing an image. Fixed [compose#9089](https://github.com/docker/compose/issues/9089){:target="_blank" rel="noopener" class="_"}
-- Fixed a misleading error message for `port` command. Pull Request [compose#9909](https://github.com/docker/compose/pull/9909){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to prevent failure when Compose tries to remove a non-existing container. Fixed by [compose#9896](https://github.com/docker/compose/pull/9896/){:target="_blank" rel="noopener" class="_"}
+- Added a `quiet` option when pushing an image. Fixed [compose#9089](https://github.com/docker/compose/issues/9089)
+- Fixed a misleading error message for `port` command. Pull Request [compose#9909](https://github.com/docker/compose/pull/9909)
+- Fixed a bug to prevent failure when Compose tries to remove a non-existing container. Fixed by [compose#9896](https://github.com/docker/compose/pull/9896/)
 - Switched GitHub issue template form
 
-For the full change log or additional information, check the [Compose repository 2.12.0 release page](https://github.com/docker/compose/releases/tag/v2.12.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.12.0 release page](https://github.com/docker/compose/releases/tag/v2.12.0).
 
 ## 2.11.2
-{% include release-date.html date="2022-09-27" %}
+{{< release-date date="2022-09-27" >}}
 
 > **Note**     
 > 
-> - Updates on environment file syntax & interpolation: see [compose#9879](https://github.com/docker/compose/issues/9879){:target="_blank" rel="noopener" class="_"}  
+> - Updates on environment file syntax & interpolation: see [compose#9879](https://github.com/docker/compose/issues/9879)  
 > - Setting `DOCKER_HOST` via `.env` files is not supported in Compose v2
 
 ### Updates
-- Upgraded to compose-go from [1.5.1 to 1.6.0](https://github.com/compose-spec/compose-go/releases/tag/v1.6.0){:target="_blank" rel="noopener" class="_"}
+- Upgraded to compose-go from [1.5.1 to 1.6.0](https://github.com/compose-spec/compose-go/releases/tag/v1.6.0)
 
 ### Bug fixes and enhancements
-- Fixed a bug to prevent "invalid template" errors on valid environment variable values. Fixes [compose##9806](https://github.com/docker/compose/issues/9806){:target="_blank" rel="noopener" class="_"}, [compose##9746](https://github.com/docker/compose/issues/9746){:target="_blank" rel="noopener" class="_"}, [compose##9704](https://github.com/docker/compose/issues/9704){:target="_blank" rel="noopener" class="_"}, [compose##9294](https://github.com/docker/compose/issues/9294){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to ensure new images from `docker compose build` are used. Fixes [compose#9856](https://github.com/docker/compose/issues/9856){:target="_blank" rel="noopener" class="_"}
-- Fixed cross-architecture builds when `DOCKER_DEFAULT_PLATFORM` not set. Fixes [compose#9864](https://github.com/docker/compose/pull/9864){:target="_blank" rel="noopener" class="_"}
-- Fixed intermittent conflict errors when using `depends_on`. Fixes [compose#9014](https://github.com/docker/compose/issues/9014){:target="_blank" rel="noopener" class="_"}
-- Cleared service `CMD` when entry point is overridden. Fixes [compose#9622](https://github.com/docker/compose/issues/9622){:target="_blank" rel="noopener" class="_"}
-- Configured default builder export when no `build.platforms` defined. Fixes [compose#9856](https://github.com/docker/compose/issues/9856){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to keep the platform defined, in priority, via DOCKER_DEFAULT_PLATFORM or the `service.platform` attribut. Fixes [compose#9864](https://github.com/docker/compose/issues/9864){:target="_blank" rel="noopener" class="_"}
-- Removed support for `DOCKER_HOST` in `.env` files. Fixes [compose#9210](https://github.com/docker/compose/issues/9210){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to ensure clean service command if entry point is overridden in run command. Fixes [compose#9622](https://github.com/docker/compose/issues/9622){:target="_blank" rel="noopener" class="_"}
-- Deps: fixed race condition during graph traversal. Fixes [compose#9014](https://github.com/docker/compose/issues/9014){:target="_blank" rel="noopener" class="_"}
+- Fixed a bug to prevent "invalid template" errors on valid environment variable values. Fixes [compose##9806](https://github.com/docker/compose/issues/9806), [compose##9746](https://github.com/docker/compose/issues/9746), [compose##9704](https://github.com/docker/compose/issues/9704), [compose##9294](https://github.com/docker/compose/issues/9294)
+- Fixed a bug to ensure new images from `docker compose build` are used. Fixes [compose#9856](https://github.com/docker/compose/issues/9856)
+- Fixed cross-architecture builds when `DOCKER_DEFAULT_PLATFORM` not set. Fixes [compose#9864](https://github.com/docker/compose/pull/9864)
+- Fixed intermittent conflict errors when using `depends_on`. Fixes [compose#9014](https://github.com/docker/compose/issues/9014)
+- Cleared service `CMD` when entry point is overridden. Fixes [compose#9622](https://github.com/docker/compose/issues/9622)
+- Configured default builder export when no `build.platforms` defined. Fixes [compose#9856](https://github.com/docker/compose/issues/9856)
+- Fixed a bug to keep the platform defined, in priority, via DOCKER_DEFAULT_PLATFORM or the `service.platform` attribut. Fixes [compose#9864](https://github.com/docker/compose/issues/9864)
+- Removed support for `DOCKER_HOST` in `.env` files. Fixes [compose#9210](https://github.com/docker/compose/issues/9210)
+- Fixed a bug to ensure clean service command if entry point is overridden in run command. Fixes [compose#9622](https://github.com/docker/compose/issues/9622)
+- Deps: fixed race condition during graph traversal. Fixes [compose#9014](https://github.com/docker/compose/issues/9014)
 - CI now runs on Windows & macOS including E2E tests via Docker Desktop
 - Added more information when `service.platform` isn't part of `service.build.platforms`
 - GitHub Workflows security hardening
 
-For the full change log or additional information, check the [Compose repository 2.11.2 release page](https://github.com/docker/compose/releases/tag/v2.11.2){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.11.2 release page](https://github.com/docker/compose/releases/tag/v2.11.2).
 
 ## 2.11.1
-{% include release-date.html date="2022-09-20" %}
+{{< release-date date="2022-09-20" >}}
 
 ### Bug fixes and enhancements
-- Fixed a bug to keep `depends_on` condition when service has `volumes_from`. Fixes [compose#9843](https://github.com/docker/compose/issues/9843){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to keep the platform defined at service level during build if no build platforms. Fixes [compose#9729](https://github.com/docker/compose/pull/9729#issuecomment-1246748144){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to keep the platform defined via DOCKER_DEFAULT_PLATFORM during build if no build platforms provided. Fixes [compose#9853](https://github.com/docker/compose/issues/9853){:target="_blank" rel="noopener" class="_"}
+- Fixed a bug to keep `depends_on` condition when service has `volumes_from`. Fixes [compose#9843](https://github.com/docker/compose/issues/9843)
+- Fixed a bug to keep the platform defined at service level during build if no build platforms. Fixes [compose#9729](https://github.com/docker/compose/pull/9729#issuecomment-1246748144)
+- Fixed a bug to keep the platform defined via DOCKER_DEFAULT_PLATFORM during build if no build platforms provided. Fixes [compose#9853](https://github.com/docker/compose/issues/9853)
 
-For the full change log or additional information, check the [Compose repository 2.11.1 release page](https://github.com/docker/compose/releases/tag/v2.11.1){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.11.1 release page](https://github.com/docker/compose/releases/tag/v2.11.1).
 
 ## 2.11.0
-{% include release-date.html date="2022-09-14" %}
+{{< release-date date="2022-09-14" >}}
 
 ### Updates
 - Dependencies upgrade: bump Golang to 1.19.1
@@ -539,163 +439,163 @@ For the full change log or additional information, check the [Compose repository
 - Dependencies upgrade: bump go.opentelemetry.io/otel from 1.9.0 to 1.10.0
 - Dependencies upgrade: bump github.com/AlecAivazis/survey/v2 from 2.3.5
 - Dependencies upgrade: bump go.opentelemetry.io/otel from 1.4.1 to 1.9.0
-- Dependencies upgrade: bump compose-go from [1.5.0 to 1.5.1](https://github.com/compose-spec/compose-go/releases/tag/v1.5.1){:target="_blank" rel="noopener" class="_"}
+- Dependencies upgrade: bump compose-go from [1.5.0 to 1.5.1](https://github.com/compose-spec/compose-go/releases/tag/v1.5.1)
 
 ### Bug fixes and enhancements
-- Added platforms build. Fixes [compose-spec#267](https://github.com/compose-spec/compose-spec/pull/267){:target="_blank" rel="noopener" class="_"}
-- Logs now filter to services from current Compose file. Fixes [compose#9801](https://github.com/docker/compose/issues/9801){:target="_blank" rel="noopener" class="_"}
-- Added an improved output warning when pulling images. Fixes [compose#9820](https://github.com/docker/compose/issues/9820){:target="_blank" rel="noopener" class="_"}
-- Fixed a bug to ensure correct capture of exit code when service has dependencies. Fixes [compose#9778](https://github.com/docker/compose/issues/9778){:target="_blank" rel="noopener" class="_"}
-- Fixed `down` with `--rmi`. Fixes [compose#9655](https://github.com/docker/compose/issues/9655){:target="_blank" rel="noopener" class="_"}
-- Fixed docker-compose convert that turns $ into $$ when using the --no-interpolate option. Fixes [compose#9160](https://github.com/docker/compose/issues/9160){:target="_blank" rel="noopener" class="_"}
-- Fixed `build.go` access custom labels directly cause panic. See [compose#9810](https://github.com/docker/compose/pull/9810){:target="_blank" rel="noopener" class="_"}
-- Applied newly loaded envvars to "DockerCli" and "APIClient". Fixes [compose#9210](https://github.com/docker/compose/issues/9210){:target="_blank" rel="noopener" class="_"}
-- Only attempt to start specified services on `compose start [services]`. Fixes [compose#9796](https://github.com/docker/compose/issues/9796){:target="_blank" rel="noopener" class="_"} [compose#9807](https://github.com/docker/compose/issues/9807){:target="_blank" rel="noopener" class="_"}
-- Label built images for reliable cleanup on `down`. Fixes [compose#9655](https://github.com/docker/compose/issues/9655){:target="_blank" rel="noopener" class="_"}
+- Added platforms build. Fixes [compose-spec#267](https://github.com/compose-spec/compose-spec/pull/267)
+- Logs now filter to services from current Compose file. Fixes [compose#9801](https://github.com/docker/compose/issues/9801)
+- Added an improved output warning when pulling images. Fixes [compose#9820](https://github.com/docker/compose/issues/9820)
+- Fixed a bug to ensure correct capture of exit code when service has dependencies. Fixes [compose#9778](https://github.com/docker/compose/issues/9778)
+- Fixed `down` with `--rmi`. Fixes [compose#9655](https://github.com/docker/compose/issues/9655)
+- Fixed docker-compose convert that turns $ into $$ when using the --no-interpolate option. Fixes [compose#9160](https://github.com/docker/compose/issues/9160)
+- Fixed `build.go` access custom labels directly cause panic. See [compose#9810](https://github.com/docker/compose/pull/9810)
+- Applied newly loaded envvars to "DockerCli" and "APIClient". Fixes [compose#9210](https://github.com/docker/compose/issues/9210)
+- Only attempt to start specified services on `compose start [services]`. Fixes [compose#9796](https://github.com/docker/compose/issues/9796) [compose#9807](https://github.com/docker/compose/issues/9807)
+- Label built images for reliable cleanup on `down`. Fixes [compose#9655](https://github.com/docker/compose/issues/9655)
 
-For the full change log or additional information, check the [Compose repository 2.11.0 release page](https://github.com/docker/compose/releases/tag/v2.11.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.11.0 release page](https://github.com/docker/compose/releases/tag/v2.11.0).
 
 ## 2.10.2
-{% include release-date.html date="2022-08-26" %}
+{{< release-date date="2022-08-26" >}}
 
 ### Bug fixes and enhancements
 
-- Properly respect `DOCKER_TLS_VERIFY` and `DOCKER_CERT_PATH` environment variables. Fixes [compose#9789](https://github.com/docker/compose/issues/9789){:target="_blank" rel="noopener" class="_"}.
-- Improved `Makefile` used in [docker/docker-ce-packaging#742](https://github.com/docker/docker-ce-packaging/pull/742){:target="_blank" rel="noopener" class="_"}.
+- Properly respect `DOCKER_TLS_VERIFY` and `DOCKER_CERT_PATH` environment variables. Fixes [compose#9789](https://github.com/docker/compose/issues/9789).
+- Improved `Makefile` used in [docker/docker-ce-packaging#742](https://github.com/docker/docker-ce-packaging/pull/742).
 
-For the full change log or additional information, check the [Compose repository 2.10.2 release page](https://github.com/docker/compose/releases/tag/v2.10.2){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.10.2 release page](https://github.com/docker/compose/releases/tag/v2.10.2).
 
 
 ## 2.10.1
-{% include release-date.html date="2022-08-24" %}
+{{< release-date date="2022-08-24" >}}
 
 ### Updates
 
-- Dependencies update: Bumped github.com/moby/buildkit from [0.10.3 to 0.10.4](https://github.com/moby/buildkit/releases/tag/v0.10.4){:target="_blank" rel="noopener" class="_"}.
+- Dependencies update: Bumped github.com/moby/buildkit from [0.10.3 to 0.10.4](https://github.com/moby/buildkit/releases/tag/v0.10.4).
 
 ### Bug fixes and enhancements
-- Fixed image pulls being skipped when `pull_policy` was not set. Fixes [compose#9773](https://github.com/docker/compose/issues/9773){:target="_blank" rel="noopener" class="_"}.
-- Restored `.sha256` checksum files in release artifacts. Fixes [compose#9772](https://github.com/docker/compose/issues/9772){:target="_blank" rel="noopener" class="_"}.
-- Removed error message showing exit code when using --exit-code-from. Fixes [compose#9782](https://github.com/docker/compose/issues/9782){:target="_blank" rel="noopener" class="_"}.
+- Fixed image pulls being skipped when `pull_policy` was not set. Fixes [compose#9773](https://github.com/docker/compose/issues/9773).
+- Restored `.sha256` checksum files in release artifacts. Fixes [compose#9772](https://github.com/docker/compose/issues/9772).
+- Removed error message showing exit code when using --exit-code-from. Fixes [compose#9782](https://github.com/docker/compose/issues/9782).
 - Fixed `compose pull` to pull images even when they existed locally if `tag=latest`.
 - CI: Fixed checksums checking and brought back individual checksum files.
 
-For the full change log or additional information, check the [Compose repository 2.10.1 release page](https://github.com/docker/compose/releases/tag/v2.10.1){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.10.1 release page](https://github.com/docker/compose/releases/tag/v2.10.1).
 
 
 ## 2.10.0
-{% include release-date.html date="2022-08-19" %}
+{{< release-date date="2022-08-19" >}}
 
 ### New
-- Applied newly loaded environment variables to `DockerCli` and `APIClient`. Fixes [compose#9210](https://github.com/docker/compose/issues/9210){:target="_blank" rel="noopener" class="_"}.
+- Applied newly loaded environment variables to `DockerCli` and `APIClient`. Fixes [compose#9210](https://github.com/docker/compose/issues/9210).
 - Added support for windows/arm64 and linux/riscv64.
 
 ### Updates
 - Updated Dockerfile syntax to latest stable and renamed docs Dockerfile.
 - Dependencies update: Upgraded BuildKit & docker/distribution.
 - Dependencies update: Updated Docker CLI version used in CI to v20.10.17.
-- Dependencies update: Bumped github.com/containerd/containerd from [1.6.6 to 1.6.7](https://github.com/containerd/containerd/releases/tag/v1.6.7){:target="_blank" rel="noopener" class="_"}.
-- Dependencies update: Bump github.com/containerd/containerd from [1.6.7 to 1.6.8](https://github.com/containerd/containerd/releases/tag/v1.6.8){:target="_blank" rel="noopener" class="_"}.
+- Dependencies update: Bumped github.com/containerd/containerd from [1.6.6 to 1.6.7](https://github.com/containerd/containerd/releases/tag/v1.6.7).
+- Dependencies update: Bump github.com/containerd/containerd from [1.6.7 to 1.6.8](https://github.com/containerd/containerd/releases/tag/v1.6.8).
 - Dependencies update: Bumped to Go 1.18.5.
-- Dependencies update: Bumped github.com/cnabio/cnab-to-oci from [0.3.5 to 0.3.6](https://github.com/cnabio/cnab-to-oci/releases/tag/v0.3.6){:target="_blank" rel="noopener" class="_"}.
+- Dependencies update: Bumped github.com/cnabio/cnab-to-oci from [0.3.5 to 0.3.6](https://github.com/cnabio/cnab-to-oci/releases/tag/v0.3.6).
 
 ### Bug fixes and enhancements
-- Reverted environment variables precedence to OS over `.env` file. Fixes [compose#9737](https://github.com/docker/compose/issues/9737){:target="_blank" rel="noopener" class="_"}.
+- Reverted environment variables precedence to OS over `.env` file. Fixes [compose#9737](https://github.com/docker/compose/issues/9737).
 - Updated usage strings for consistency.
-- Resolved environment variables case-insensitively on Windows. Fixes [compose#9431](https://github.com/docker/compose/issues/9431){:target="_blank" rel="noopener" class="_"}.
+- Resolved environment variables case-insensitively on Windows. Fixes [compose#9431](https://github.com/docker/compose/issues/9431).
 - Fixed `compose up` so dependency containers aren't stopped when a stop signal is issued. This keeps parity with v1 behavior-wise.
-- Fixes [compose#9696](https://github.com/docker/compose/issues/9696){:target="_blank" rel="noopener" class="_"}.
-- Fixed commands that start/restart/pause/unpause so that, if ran from the Compose file, the Compose model is also applied. Fixes [compose#9705](https://github.com/docker/compose/issues/9705){:target="_blank" rel="noopener" class="_"} and [compose#9705](https://github.com/docker/compose/issues/9671){:target="_blank" rel="noopener" class="_"}.
+- Fixes [compose#9696](https://github.com/docker/compose/issues/9696).
+- Fixed commands that start/restart/pause/unpause so that, if ran from the Compose file, the Compose model is also applied. Fixes [compose#9705](https://github.com/docker/compose/issues/9705) and [compose#9705](https://github.com/docker/compose/issues/9671).
 - Removed extra whitespaces in help text of some subcommands.
-- Fixed `compose create` to not override service pull policy when the value from the command line is configured as the default. Fixes [compose#9717](https://github.com/docker/compose/issues/9717){:target="_blank" rel="noopener" class="_"}.
-- Filtered out "commandConn.Close- warning" message. Fixes[compose#8544](https://github.com/docker/compose/issues/8544){:target="_blank" rel="noopener" class="_"}.
-- Fixed up/start/run to not wait for disabled dependency. Fixes [compose#9591](https://github.com/docker/compose/issues/9591){:target="_blank" rel="noopener" class="_"}.
-- Applied Compose model on `compose kill`, added `--remove-orphans` option. Fixes [compose#9742](https://github.com/docker/compose/issues/9742){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose pull` to avoid pulling the same images multiple times. Fixes [compose#8768](https://github.com/docker/compose/issues/8768){:target="_blank" rel="noopener" class="_"}.
+- Fixed `compose create` to not override service pull policy when the value from the command line is configured as the default. Fixes [compose#9717](https://github.com/docker/compose/issues/9717).
+- Filtered out "commandConn.Close- warning" message. Fixes[compose#8544](https://github.com/docker/compose/issues/8544).
+- Fixed up/start/run to not wait for disabled dependency. Fixes [compose#9591](https://github.com/docker/compose/issues/9591).
+- Applied Compose model on `compose kill`, added `--remove-orphans` option. Fixes [compose#9742](https://github.com/docker/compose/issues/9742).
+- Fixed `compose pull` to avoid pulling the same images multiple times. Fixes [compose#8768](https://github.com/docker/compose/issues/8768).
 - Fixed version of golangci-lint to v1.47.3, issue with v1.48.0 for now.
 
-For the full change log, check the [Compose repository 2.10.0 release page](https://github.com/docker/compose/releases/tag/v2.10.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log, check the [Compose repository 2.10.0 release page](https://github.com/docker/compose/releases/tag/v2.10.0).
 
 ## 2.9.0
-{% include release-date.html date="2022-08-7" %}
+{{< release-date date="2022-08-7" >}}
 
 > **Important**
 >
 > Compose v2.9.0 contains changes to the environment variable's precedence that have since been reverted. We recommend using v2.10+ to avoid compatibility issues.
 >
-{: .important}
+{ .important }
 
 > **Note**
 > 
-> This release reverts the breaking changes introduced in [Compose v2.8.0](#280) by [`compose-go v1.3.0`](https://github.com/compose-spec/compose-go/releases/tag/v1.3.0){:target="_blank" rel="noopener" class="_"}.
+> This release reverts the breaking changes introduced in [Compose v2.8.0](#280) by [`compose-go v1.3.0`](https://github.com/compose-spec/compose-go/releases/tag/v1.3.0).
 
 ### Updates
-- Updated [`compose-go` to v1.4.0](https://github.com/compose-spec/compose-go/releases/tag/v1.4.0){:target="_blank" rel="noopener" class="_"} as previous version introduced breaking changes. Fixes [compose#9700](https://github.com/docker/compose/issues/9700){:target="_blank" rel="noopener" class="_"}.
+- Updated [`compose-go` to v1.4.0](https://github.com/compose-spec/compose-go/releases/tag/v1.4.0) as previous version introduced breaking changes. Fixes [compose#9700](https://github.com/docker/compose/issues/9700).
 
 ### Bug fixes and enhancements
 
-- Overwritten parent commands PreRun code for `compose version`. Fixes [compose#9698](https://github.com/docker/compose/issues/9698){:target="_blank" rel="noopener" class="_"}.
-- Fixed `LinkLocalIPs` in V2. Fixes [compose#9692](https://github.com/docker/compose/issues/9692){:target="_blank" rel="noopener" class="_"}.
-- Linked to `BUILDING.md` for testing instructions. Fixes [compose#9439](https://github.com/docker/compose/issues/9439){:target="_blank" rel="noopener" class="_"}.
+- Overwritten parent commands PreRun code for `compose version`. Fixes [compose#9698](https://github.com/docker/compose/issues/9698).
+- Fixed `LinkLocalIPs` in V2. Fixes [compose#9692](https://github.com/docker/compose/issues/9692).
+- Linked to `BUILDING.md` for testing instructions. Fixes [compose#9439](https://github.com/docker/compose/issues/9439).
 
-For the full change log or additional information, check the [Compose repository 2.9.0 release page](https://github.com/docker/compose/releases/tag/v2.9.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.9.0 release page](https://github.com/docker/compose/releases/tag/v2.9.0).
 
 ## 2.8.0
-{% include release-date.html date="2022-07-29" %}
+{{< release-date date="2022-07-29" >}}
 
 > **Important**
 >
->This release introduced a breaking change via `compose-go v1.3.0` and this [PR](https://github.com/compose-spec/compose-go/pull/294){:target="_blank" rel="noopener" class="_"}.
+>This release introduced a breaking change via `compose-go v1.3.0` and this [PR](https://github.com/compose-spec/compose-go/pull/294).
 In this release, Docker Compose recreates new resources (networks, volumes, secrets, configs, etc.) with new names, using a `-` (dash) instead an `_` (underscore) and tries to connect to or use these newly created resources instead of your existing ones!
 >
 > Please use Compose the v2.9.0 release instead.
 >
-{: .important}
+{ .important }
 
 ### New
 
-- Introduced `--pull` flag to allow the force pull of updated service images. Fixes [compose#9451](https://github.com/docker/compose/issues/9451){:target="_blank" rel="noopener" class="_"}.
+- Introduced `--pull` flag to allow the force pull of updated service images. Fixes [compose#9451](https://github.com/docker/compose/issues/9451).
 - Increased code quality by adding `gocritic` to the linters.
 
 ### Bug fixes and enhancements
 
-- Fixed interpolation error message output. Fixes [compose-spec/compose-go#292](https://github.com/compose-spec/compose-go/pull/292){:target="_blank" rel="noopener" class="_"}.
-- Defined precedence of the environment variables evaluation. Fixes [compose#9521](https://github.com/docker/compose/issues/9606){:target="_blank" rel="noopener" class="_"}, 
-[compose#9638](https://github.com/docker/compose/issues/9638){:target="_blank" rel="noopener" class="_"},
-[compose#9608](https://github.com/docker/compose/issues/9608){:target="_blank" rel="noopener" class="_"},
-[compose#9578](https://github.com/docker/compose/issues/9578){:target="_blank" rel="noopener" class="_"}.
-[compose#9468](https://github.com/docker/compose/issues/9468){:target="_blank" rel="noopener" class="_"}, and
-[compose#9683](https://github.com/docker/compose/issues/9468){:target="_blank" rel="noopener" class="_"}.
+- Fixed interpolation error message output. Fixes [compose-spec/compose-go#292](https://github.com/compose-spec/compose-go/pull/292).
+- Defined precedence of the environment variables evaluation. Fixes [compose#9521](https://github.com/docker/compose/issues/9606), 
+[compose#9638](https://github.com/docker/compose/issues/9638),
+[compose#9608](https://github.com/docker/compose/issues/9608),
+[compose#9578](https://github.com/docker/compose/issues/9578).
+[compose#9468](https://github.com/docker/compose/issues/9468), and
+[compose#9683](https://github.com/docker/compose/issues/9468).
 - Docs CI: Fixed to use push-to-fork when creating a PR.
 - Used environmental variable for golang's version and updates GitHub Actions from v2 to v3.
-- Used [google/addlicense](https://github.com/google/addlicense){:target="_blank" rel="noopener" class="_"} instead of [kunalkushwaha/ltag](https://github.com/kunalkushwaha/ltag){:target="_blank" rel="noopener" class="_"}.
+- Used [google/addlicense](https://github.com/google/addlicense) instead of [kunalkushwaha/ltag](https://github.com/kunalkushwaha/ltag).
 
-For the full change log or additional information, check the [Compose repository 2.8.0 release page](https://github.com/docker/compose/releases/tag/v2.8.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.8.0 release page](https://github.com/docker/compose/releases/tag/v2.8.0).
 
 ## 2.7.0
-{% include release-date.html date="2022-07-20" %}
+{{< release-date date="2022-07-20" >}}
 
 ### New
 
-- Added support for environment secrets during build step. Fixes [compose#9606](https://github.com/docker/compose/issues/9606){:target="_blank" rel="noopener" class="_"}.
+- Added support for environment secrets during build step. Fixes [compose#9606](https://github.com/docker/compose/issues/9606).
 
 ### Updates
 
-- Dependencies upgrade: bumped [go to 1.18.4](https://github.com/golang/go/compare/go1.18.3...go1.18.4){:target="_blank" rel="noopener" class="_"}. 
+- Dependencies upgrade: bumped [go to 1.18.4](https://github.com/golang/go/compare/go1.18.3...go1.18.4). 
 - Dependencies upgrade: bumped [compose-go to v1.2.9](https://github.com/compose-spec/compose-go/releases/tag/v1.2.9).
 
 ### Bug fixes and enhancements
 
-- Networks: prevented issues due to duplicate names. Fixes [moby/moby#18864](https://github.com/moby/moby/issues/18864){:target="_blank" rel="noopener" class="_"}.
-- Fixed issue with close networks name on `compose up` and `compose down` commands. Fixes [compose#9630](https://github.com/docker/compose/issues/9044){:target="_blank" rel="noopener" class="_"}.
-- Used appropriate dependency condition for one-shot containers when running `compose up --wait`. Fixes [compose#9606](https://github.com/docker/compose/pull/9572){:target="_blank" rel="noopener" class="_"}.
+- Networks: prevented issues due to duplicate names. Fixes [moby/moby#18864](https://github.com/moby/moby/issues/18864).
+- Fixed issue with close networks name on `compose up` and `compose down` commands. Fixes [compose#9630](https://github.com/docker/compose/issues/9044).
+- Used appropriate dependency condition for one-shot containers when running `compose up --wait`. Fixes [compose#9606](https://github.com/docker/compose/pull/9572).
 - Fixed environment variable expansion.
-- Validated depended-on services exist in consistency check. Fixes [compose#8910](https://github.com/docker/compose/issues/8910){:target="_blank" rel="noopener" class="_"}.
-- Fixed hash usage in environment values. Fixes [compose#9509](https://github.com/docker/compose/issues/9509){:target="_blank" rel="noopener" class="_"}.
-- Docker Build: added fix to respect dependency order for classic builder. Fixes [compose#8538](https://github.com/docker/compose/issues/8538){:target="_blank" rel="noopener" class="_"}.
-- Fixed panic caused by empty string argument. Fixes [compose-switch#35](https://github.com/docker/compose-switch/issues/35){:target="_blank" rel="noopener" class="_"}.
-- Fixed start/restart as to not impact one-off containers. Fixes [compose#9509](https://github.com/docker/compose/issues/9044){:target="_blank" rel="noopener" class="_"}.
-- Fixed to keep the container reference when `volumes_from` targets a container and not a service. Fixes [compose#8874](https://github.com/docker/compose/issues/8874){:target="_blank" rel="noopener" class="_"}.
+- Validated depended-on services exist in consistency check. Fixes [compose#8910](https://github.com/docker/compose/issues/8910).
+- Fixed hash usage in environment values. Fixes [compose#9509](https://github.com/docker/compose/issues/9509).
+- Docker Build: added fix to respect dependency order for classic builder. Fixes [compose#8538](https://github.com/docker/compose/issues/8538).
+- Fixed panic caused by empty string argument. Fixes [compose-switch#35](https://github.com/docker/compose-switch/issues/35).
+- Fixed start/restart as to not impact one-off containers. Fixes [compose#9509](https://github.com/docker/compose/issues/9044).
+- Fixed to keep the container reference when `volumes_from` targets a container and not a service. Fixes [compose#8874](https://github.com/docker/compose/issues/8874).
 - build.go: added fix to initialize `CustomLabels` map if `nil`.
 - Added new targets to build Compose binary before running e2e tests.
 - CI: released workflow to open a PR on docs repo with latest changes.
@@ -703,22 +603,22 @@ For the full change log or additional information, check the [Compose repository
 - e2e: split out pause tests and add more cases.
 - e2e: add more start/stop test cases.
 
-For the full change log or additional information, check the [Compose repository 2.7.0 release page](https://github.com/docker/compose/releases/tag/v2.7.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.7.0 release page](https://github.com/docker/compose/releases/tag/v2.7.0).
 
 ## 2.6.1
-{% include release-date.html date="2022-06-23" %}
+{{< release-date date="2022-06-23" >}}
 
 ### New
 
-- Added support for setting secrets from environment variable. Fixes [compose-spec/compose-spec#251](https://github.com/compose-spec/compose-spec/issues/251){:target="_blank" rel="noopener" class="_"}.
+- Added support for setting secrets from environment variable. Fixes [compose-spec/compose-spec#251](https://github.com/compose-spec/compose-spec/issues/251).
 
 ### Updates
 
-- Upgrade: compose-go [v1.2.8](https://github.com/compose-spec/compose-go/releases/tag/v1.2.8){:target="_blank" rel="noopener" class="_"}.
-- Upgrade: buildx [v0.8.2](https://github.com/docker/buildx/releases/tag/v0.8.2){:target="_blank" rel="noopener" class="_"}.
-- Dependencies upgrade: bumped runc [to 1.1.2](https://github.com/opencontainers/runc/releases/tag/v1.1.2){:target="_blank" rel="noopener" class="_"}.
-- Dependencies upgrade: bumped golang to [1.18.3](https://go.dev/doc/devel/release#go1.18.minor){:target="_blank" rel="noopener" class="_"}.
-- Dependencies upgrade: bumped compose-go to [v1.2.8](https://github.com/compose-spec/compose-go/releases/tag/v1.2.8){:target="_blank" rel="noopener" class="_"}.
+- Upgrade: compose-go [v1.2.8](https://github.com/compose-spec/compose-go/releases/tag/v1.2.8).
+- Upgrade: buildx [v0.8.2](https://github.com/docker/buildx/releases/tag/v0.8.2).
+- Dependencies upgrade: bumped runc [to 1.1.2](https://github.com/opencontainers/runc/releases/tag/v1.1.2).
+- Dependencies upgrade: bumped golang to [1.18.3](https://go.dev/doc/devel/release#go1.18.minor).
+- Dependencies upgrade: bumped compose-go to [v1.2.8](https://github.com/compose-spec/compose-go/releases/tag/v1.2.8).
 - Dependencies upgrade: bumped github.com/theupdateframework/notary from 0.6.1 to 0.7.0.
 - Dependencies upgrade: bumped github.com/cnabio/cnab-to-oci from 0.3.1-beta1 to 0.3.3.
 - Dependencies upgrade: bumped github.com/hashicorp/go-version from 1.3.0 to 1.5.0.
@@ -729,13 +629,13 @@ For the full change log or additional information, check the [Compose repository
 
 ### Bug fixes and enhancements
 
-- Added links to container create request. Fixes [#9513](https://github.com/docker/compose/issues/9513){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose run` to start only direct dependencies. Fixes [#9459](https://github.com/docker/compose/issues/9459){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose up` 'service not found' errors when using `--no-deps` option. Fixes [#9427](https://github.com/docker/compose/issues/9427){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose down` to respect `COMPOSE_REMOVE_ORPHANS` environment variable. Fixes [#9562](https://github.com/docker/compose/issues/9562){:target="_blank" rel="noopener" class="_"}.
-- Fixed project-level bind mount volumes. Fixes [docker/for-mac#6317](https://github.com/docker/for-mac/issues/6317){:target="_blank" rel="noopener" class="_"}.
-- Fixed parsing of properties `deploy.limits.cpus` and `deploy.limits.pids` to respect floating-point values. Fixes [#9542](https://github.com/docker/compose/issues/9542){:target="_blank" rel="noopener" class="_"} and [#9501](https://github.com/docker/compose/issues/9501){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose ps` output to list all exposed ports. Fixes [#9257](https://github.com/docker/compose/issues/9527){:target="_blank" rel="noopener" class="_"}.
+- Added links to container create request. Fixes [#9513](https://github.com/docker/compose/issues/9513).
+- Fixed `compose run` to start only direct dependencies. Fixes [#9459](https://github.com/docker/compose/issues/9459).
+- Fixed `compose up` 'service not found' errors when using `--no-deps` option. Fixes [#9427](https://github.com/docker/compose/issues/9427).
+- Fixed `compose down` to respect `COMPOSE_REMOVE_ORPHANS` environment variable. Fixes [#9562](https://github.com/docker/compose/issues/9562).
+- Fixed project-level bind mount volumes. Fixes [docker/for-mac#6317](https://github.com/docker/for-mac/issues/6317).
+- Fixed parsing of properties `deploy.limits.cpus` and `deploy.limits.pids` to respect floating-point values. Fixes [#9542](https://github.com/docker/compose/issues/9542) and [#9501](https://github.com/docker/compose/issues/9501).
+- Fixed `compose ps` output to list all exposed ports. Fixes [#9257](https://github.com/docker/compose/issues/9527).
 - Fixed spelling mistakes in `compose ps` code.
 - Fixed `docker compose` to honor `--no-ansi` even when deprecated option is requested.
 - Fixed network name and network ID possible ambiguity.
@@ -747,11 +647,11 @@ For the full change log or additional information, check the [Compose repository
 - e2e: ensured all compose commands standalone compatible.
 - e2e: improved test output on failures.
 
-For the full change log or additional information, check the [Compose repository 2.6.1 release page](https://github.com/docker/compose/releases/tag/v2.6.1){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.6.1 release page](https://github.com/docker/compose/releases/tag/v2.6.1).
 
 
 ## 2.6.0
-{% include release-date.html date="2022-05-30" %}
+{{< release-date date="2022-05-30" >}}
 
 ### New
 
@@ -761,23 +661,23 @@ For the full change log or additional information, check the [Compose repository
 
 ### Updates
 
-- Dependencies update: bumping [compose-go to 1.2.6](https://github.com/compose-spec/compose-go/releases/tag/v1.2.6){:target="_blank" rel="noopener" class="_"}.
-- Dependencies update: bumping [compose-go to 1.2.7](https://github.com/compose-spec/compose-go/releases/tag/v1.2.7){:target="_blank" rel="noopener" class="_"}.
-- Dependencies update: bumping [golang to 1.18](https://go.dev/doc/devel/release#go1.18){:target="_blank" rel="noopener" class="_"}. 
+- Dependencies update: bumping [compose-go to 1.2.6](https://github.com/compose-spec/compose-go/releases/tag/v1.2.6).
+- Dependencies update: bumping [compose-go to 1.2.7](https://github.com/compose-spec/compose-go/releases/tag/v1.2.7).
+- Dependencies update: bumping [golang to 1.18](https://go.dev/doc/devel/release#go1.18). 
 
 ### Bug fixes and enhancements
 
-- Fixed `compose up` to attach only to services declared in project with enabled profiles. Fixes [#9286](https://github.com/docker/compose/issues/9286){:target="_blank" rel="noopener" class="_"}.
-- Fixed flickering prompt when pulling same image from multiple services. Fixes [#9469](https://github.com/docker/compose/issues/9469){:target="_blank" rel="noopener" class="_"}.
-- Fixed compose go to import .env file to OS environment to allow setting variables (such as DOCKER_BUILDKIT) through this file. Fixes [#9345](https://github.com/docker/compose/issues/9345){:target="_blank" rel="noopener" class="_"}.
+- Fixed `compose up` to attach only to services declared in project with enabled profiles. Fixes [#9286](https://github.com/docker/compose/issues/9286).
+- Fixed flickering prompt when pulling same image from multiple services. Fixes [#9469](https://github.com/docker/compose/issues/9469).
+- Fixed compose go to import .env file to OS environment to allow setting variables (such as DOCKER_BUILDKIT) through this file. Fixes [#9345](https://github.com/docker/compose/issues/9345).
 - Fixed `TestLocalComposeUp` that failed locally.
 - Fixed local run of make `e2e-compose-standalone`.
 
-For the full change log or additional information, check the [Compose repository 2.6.0 release page](https://github.com/docker/compose/releases/tag/v2.6.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.6.0 release page](https://github.com/docker/compose/releases/tag/v2.6.0).
 
 
 ## 2.5.1
-{% include release-date.html date="2022-05-17" %}
+{{< release-date date="2022-05-17" >}}
 
 ### Updates
 
@@ -785,51 +685,51 @@ For the full change log or additional information, check the [Compose repository
 
 ### Bug fixes and enhancements
 
-- Fixed resolution of project's working directive absolute path when a relative path is declared using '--env-file'. Fixes [docker/for-mac#6229](https://github.com/docker/for-mac/issues/6229){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose down`: now rejects all arguments in order to clarify usage. Fixes [#9151](https://github.com/docker/compose/issues/9151){:target="_blank" rel="noopener" class="_"}.
-- Fixed `compose down`: now exits with status=0 if there is nothing to remove. Fixes [#9426](https://github.com/docker/compose/issues/9426){:target="_blank" rel="noopener" class="_"}.
-- Fixed extra space printed in logs output lines with --no-log-prefix option. Fixes [#9464](https://github.com/docker/compose/issues/9464){:target="_blank" rel="noopener" class="_"}.
+- Fixed resolution of project's working directive absolute path when a relative path is declared using '--env-file'. Fixes [docker/for-mac#6229](https://github.com/docker/for-mac/issues/6229).
+- Fixed `compose down`: now rejects all arguments in order to clarify usage. Fixes [#9151](https://github.com/docker/compose/issues/9151).
+- Fixed `compose down`: now exits with status=0 if there is nothing to remove. Fixes [#9426](https://github.com/docker/compose/issues/9426).
+- Fixed extra space printed in logs output lines with --no-log-prefix option. Fixes [#9464](https://github.com/docker/compose/issues/9464).
 - Clarified what the default work dir is when multiple compose files are passed.
 - cp command: copy to all containers of a service as default behavior.
 
-For the full change log or additional information, check the [Compose repository 2.5.1 release page](https://github.com/docker/compose/releases/tag/v2.5.1){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.5.1 release page](https://github.com/docker/compose/releases/tag/v2.5.1).
 
 
 ## 2.5.0
-{% include release-date.html date="2022-04-29" %}
+{{< release-date date="2022-04-29" >}}
 
 ### Bug fixes and enhancements
 
-- Fixed panic with `compose down` command when `-p` flag specified. Fixes [#9353](https://github.com/docker/compose/issues/9353){:target="_blank" rel="noopener" class="_"}.
-- Passed newly created project as input to start services (`docker compose up`). Fixes [#9356](https://github.com/docker/compose/issues/9356){:target="_blank" rel="noopener" class="_"}.
-- Included services declared under links in docker-compose file as implicit dependencies. Fixes [#9301](https://github.com/docker/compose/issues/9301){:target="_blank" rel="noopener" class="_"}.
-- Added changes `docker compose pull` command to respect defined policy: 1) skip services configured as `pull_policy: never` and 2) ignore those with an existing image and `pull_policy: missing`. Fixes [#3660](https://github.com/docker/compose/issues/3660){:target="_blank" rel="noopener" class="_"}.
-- Error building project from resources is no longer ignored in order to prevent `down` panic. Fixes [#9383](https://github.com/docker/compose/issues/9383){:target="_blank" rel="noopener" class="_"}.
-- Enforced project name to be lowercase. Fixes [#9378](https://github.com/docker/compose/issues/9378){:target="_blank" rel="noopener" class="_"}.
-- Added support to build-time secrets. Fixes [#6358](https://github.com/docker/compose/issues/6358){:target="_blank" rel="noopener" class="_"}.
-- Changed `compose-go` to allow (re)building volume string to be used by engine `bind` API when mount can't be used. Fixes [#9380](https://github.com/docker/compose/issues/9380){:target="_blank" rel="noopener" class="_"}.
-- Provided checksums.txt file and added `--binary` to allow verification in different OS. Fixes [#9388](https://github.com/docker/compose/issues/9388){:target="_blank" rel="noopener" class="_"}.
-- Added changes so locally pulled image's ID is inspected and persisted to `com.docker.compose.image`. Fixes [#9357](https://github.com/docker/compose/issues/9357){:target="_blank" rel="noopener" class="_"}.
-- Fixed issue regarding IPAM gateway setup. Fixes [#9330](https://github.com/docker/compose/issues/9330){:target="_blank" rel="noopener" class="_"}.
+- Fixed panic with `compose down` command when `-p` flag specified. Fixes [#9353](https://github.com/docker/compose/issues/9353).
+- Passed newly created project as input to start services (`docker compose up`). Fixes [#9356](https://github.com/docker/compose/issues/9356).
+- Included services declared under links in docker-compose file as implicit dependencies. Fixes [#9301](https://github.com/docker/compose/issues/9301).
+- Added changes `docker compose pull` command to respect defined policy: 1) skip services configured as `pull_policy: never` and 2) ignore those with an existing image and `pull_policy: missing`. Fixes [#3660](https://github.com/docker/compose/issues/3660).
+- Error building project from resources is no longer ignored in order to prevent `down` panic. Fixes [#9383](https://github.com/docker/compose/issues/9383).
+- Enforced project name to be lowercase. Fixes [#9378](https://github.com/docker/compose/issues/9378).
+- Added support to build-time secrets. Fixes [#6358](https://github.com/docker/compose/issues/6358).
+- Changed `compose-go` to allow (re)building volume string to be used by engine `bind` API when mount can't be used. Fixes [#9380](https://github.com/docker/compose/issues/9380).
+- Provided checksums.txt file and added `--binary` to allow verification in different OS. Fixes [#9388](https://github.com/docker/compose/issues/9388).
+- Added changes so locally pulled image's ID is inspected and persisted to `com.docker.compose.image`. Fixes [#9357](https://github.com/docker/compose/issues/9357).
+- Fixed issue regarding IPAM gateway setup. Fixes [#9330](https://github.com/docker/compose/issues/9330).
 - Added support for ppc64le archictecture for docker compose binary.
 - Fixed search/replace typo in `--no-TTY` documentation.
 
-For the full change log or additional information, check the [Compose repository 2.5.0 release page](https://github.com/docker/compose/releases/tag/v2.5.0){:target="_blank" rel="noopener" class="_"}.
+For the full change log or additional information, check the [Compose repository 2.5.0 release page](https://github.com/docker/compose/releases/tag/v2.5.0).
 
 ## 2.4.1
-{% include release-date.html date="2022-04-04" %}
+{{< release-date date="2022-04-04" >}}
 
 ### Bug fixes and enhancements
 
-- Passed the `--rm flag` value as is to the Docker CLI when running a container with this flag. Fixes [#9314](https://github.com/docker/compose/issues/9314){:target="_blank" rel="noopener" class="_"}.
-- Added ssh config to the build options when building an image from a `docker compose up` command. Fixes [#9338](https://github.com/docker/compose/issues/9338){:target="_blank" rel="noopener" class="_"}.
-- Added inspection to container checking if a TTY is required. Running services with `tty:true` specified now show console output. Fixes [#9288](https://github.com/docker/compose/issues/9288){:target="_blank" rel="noopener" class="_"}.
+- Passed the `--rm flag` value as is to the Docker CLI when running a container with this flag. Fixes [#9314](https://github.com/docker/compose/issues/9314).
+- Added ssh config to the build options when building an image from a `docker compose up` command. Fixes [#9338](https://github.com/docker/compose/issues/9338).
+- Added inspection to container checking if a TTY is required. Running services with `tty:true` specified now show console output. Fixes [#9288](https://github.com/docker/compose/issues/9288).
 
-For the full change log or additional information, check the [Compose repository 2.4.1 release page](https://github.com/docker/compose/releases/tag/v2.4.1){:target="_blank" rel="noopener" class="_"}.  
+For the full change log or additional information, check the [Compose repository 2.4.1 release page](https://github.com/docker/compose/releases/tag/v2.4.1).  
 
 
 ## 2.4.0 
-{% include release-date.html date="2022-04-1" %}
+{{< release-date date="2022-04-1" >}}
 
 ### Updates
 
@@ -837,23 +737,23 @@ For the full change log or additional information, check the [Compose repository
 
 ### Bug fixes and enhancements
 
-- Passed the interactive flag '-i' from the Compose CLI to the Docker one to run exec command. Fixes [#9315](https://github.com/docker/compose/issues/9315){:target="_blank" rel="noopener" class="_"}.
-- Compose commands now take the value of `COMPOSE_PROJECT_NAME` environmental variable into consideration. Fixes [#9316](https://github.com/docker/compose/issues/9316){:target="_blank" rel="noopener" class="_"}.
-- Fixed issue of `compose down` command that when executed in contexts without any services started or resources to be deleted was returning an error. Error was due to command trying to delete an inexistent default network. Fixes [#9333](https://github.com/docker/compose/issues/9333){:target="_blank" rel="noopener" class="_"}.
+- Passed the interactive flag '-i' from the Compose CLI to the Docker one to run exec command. Fixes [#9315](https://github.com/docker/compose/issues/9315).
+- Compose commands now take the value of `COMPOSE_PROJECT_NAME` environmental variable into consideration. Fixes [#9316](https://github.com/docker/compose/issues/9316).
+- Fixed issue of `compose down` command that when executed in contexts without any services started or resources to be deleted was returning an error. Error was due to command trying to delete an inexistent default network. Fixes [#9333](https://github.com/docker/compose/issues/9333).
 - Introduced support for `cache_from`, `cache_to`, `no_cache` and `pull` attributes in the build section. These attributes allow forcing a complete rebuild from sources and checking with registry for images used. These changes provide the basis for offering `--no-cache` and `--pull` options for compose build (or equivalent) command down the line.
-- Introduced support of an `--ssh` flag for the `build` command from CLI and Compose file. Fixes [#7025](https://github.com/docker/compose/issues/7025){:target="_blank" rel="noopener" class="_"}.
-- Fixed typo in `--ssh` flag description. Related to [#7025](https://github.com/docker/compose/issues/7025){:target="_blank" rel="noopener" class="_"}.
+- Introduced support of an `--ssh` flag for the `build` command from CLI and Compose file. Fixes [#7025](https://github.com/docker/compose/issues/7025).
+- Fixed typo in `--ssh` flag description. Related to [#7025](https://github.com/docker/compose/issues/7025).
 - Pinned Kubernetes dependencies to the same version as in buildx.
 - Passed the interactive flag from the Compose CLI to the Docker one to run exec command.
 - Fixed race condition on start-stop end-to-end tests running in parallel.
 - Removed code regarding an obsolete warning.
 - Vendor: github.com/containerd/containerd v1.6.2. Includes a fix for CVE-2022-24769 (doesn't affect our codebase).
 
-For the full change log or additional information, check the [Compose repository 2.4.0 release page](https://github.com/docker/compose/releases/tag/v2.4.0){:target="_blank" rel="noopener" class="_"}.  
+For the full change log or additional information, check the [Compose repository 2.4.0 release page](https://github.com/docker/compose/releases/tag/v2.4.0).  
 
 
 ## 2.3.4 
-{% include release-date.html date="2022-03-25" %}
+{{< release-date date="2022-03-25" >}}
 
 ### New
 
@@ -861,30 +761,30 @@ For the full change log or additional information, check the [Compose repository
 
 ### Removed
 
-- Removed a container with no candidate now produces a warning instead of an error. Fixes [#9255](https://github.com/docker/compose/issues/9255){:target="_blank" rel="noopener" class="_"}.
-- Removed the "Deprecated" mentions from -i and -t options to run and exec commands. These options are on by default and in use. Fixes [#9229](https://github.com/docker/compose/pull/9229#discussion_r819730788){:target="_blank" rel="noopener" class="_"}.
+- Removed a container with no candidate now produces a warning instead of an error. Fixes [#9255](https://github.com/docker/compose/issues/9255).
+- Removed the "Deprecated" mentions from -i and -t options to run and exec commands. These options are on by default and in use. Fixes [#9229](https://github.com/docker/compose/pull/9229#discussion_r819730788).
 - Removed the "Deprecated" mention from the --filter flag, to keep consistency with other commands. 
 - Removed the need to get the original compose.yaml file to run 'docker compose kill'.
 
 ### Updates
-- Dependencies update: Bumped github.com/spf13/cobra from 1.3.0 to 1.4.0. Cobra library no longer requires Viper and all of its indirect dependencies [See cobra's release page](https://github.com/spf13/cobra/releases){:target="_blank" rel="noopener" class="_"}.
+- Dependencies update: Bumped github.com/spf13/cobra from 1.3.0 to 1.4.0. Cobra library no longer requires Viper and all of its indirect dependencies [See cobra's release page](https://github.com/spf13/cobra/releases).
 - Dependencies update: Bumped buildx from v0.7.1 to v0.8.0.
 
 ### Bug fixes and enhancements
 
-- Recovered behavior for 'compose up -d' of recreating containers of compose file images with refreshed content. Fixes [#9259](https://github.com/docker/compose/issues/9259){:target="_blank" rel="noopener" class="_"}.
+- Recovered behavior for 'compose up -d' of recreating containers of compose file images with refreshed content. Fixes [#9259](https://github.com/docker/compose/issues/9259).
 - Docker compose --status, --filter and --format flags documentation updates.
 - `docker compose down -v` now does not remove external volumes and networks as per the option's expected and documented behavior. Whenever project is specified it is also now used to enforce down to only remove resources listed in compose.yaml file.
-Fixes [#9172](https://github.com/docker/compose/issues/9172){:target="_blank" rel="noopener" class="_"}, [#9145](https://github.com/docker/compose/issues/9145){:target="_blank" rel="noopener" class="_"}.
+Fixes [#9172](https://github.com/docker/compose/issues/9172), [#9145](https://github.com/docker/compose/issues/9145).
 - Changed Compose API reference docs automation to pick up diffs code vs. docs.
 
-For the full change log or additional information, check the [Compose repository 2.3.4 release page](https://github.com/docker/compose/releases/tag/v2.3.4){:target="_blank" rel="noopener" class="_"}.  
+For the full change log or additional information, check the [Compose repository 2.3.4 release page](https://github.com/docker/compose/releases/tag/v2.3.4).  
 
 ## Other Releases 
 
 (2022-03-8 to 2022-04-14)
 
-For the releases later than 1.29.2 and earlier than 2.3.4, please check the [Compose repository release pages](https://github.com/docker/compose/releases){:target="_blank" rel="noopener" class="_"}.
+For the releases later than 1.29.2 and earlier than 2.3.4, please check the [Compose repository release pages](https://github.com/docker/compose/releases).
 
 ## 1.29.2
 (2021-05-10)
@@ -990,7 +890,7 @@ For the releases later than 1.29.2 and earlier than 2.3.4, please check the [Com
 
 - Removed the log driver filter.
 
-For a list of PRs and issues fixed in this release, see [Compose 1.28.3](https://github.com/docker/compose/milestone/53?closed=1){:target="_blank" rel="noopener" class="_"}.
+For a list of PRs and issues fixed in this release, see [Compose 1.28.3](https://github.com/docker/compose/milestone/53?closed=1).
 
 ## 1.28.2
 (2021-01-26)
@@ -3511,4 +3411,4 @@ Big thanks to @tomstuart, @EnTeQuAk, @schickling, @aronasorman and @GeoffreyPlit
 ## 0.0.1
 (2013-12-20)
 
-Initial release.
+Initial release.
\ No newline at end of file
diff --git a/content/compose/samples-for-compose.md b/content/compose/samples-for-compose.md
index 3aba2be936..966fd6df1b 100644
--- a/content/compose/samples-for-compose.md
+++ b/content/compose/samples-for-compose.md
@@ -39,4 +39,4 @@ These samples focus specifically on Docker Compose:
 
 ## Awesome Compose samples
 
-The Awesome Compose samples provide a starting point on how to integrate different frameworks and technologies using Docker Compose. All samples are available in the [Awesome-compose GitHub repo](https://github.com/docker/awesome-compose){:target="_blank" rel="noopener" class="_"} and are ready to run with `docker compose up`.
+The Awesome Compose samples provide a starting point on how to integrate different frameworks and technologies using Docker Compose. All samples are available in the [Awesome-compose GitHub repo](https://github.com/docker/awesome-compose) and are ready to run with `docker compose up`.
\ No newline at end of file
diff --git a/content/compose/startup-order.md b/content/compose/startup-order.md
index 7cda43da85..e77dc12e40 100644
--- a/content/compose/startup-order.md
+++ b/content/compose/startup-order.md
@@ -4,7 +4,8 @@ keywords: documentation, docs, docker, compose, startup, shutdown, order
 title: Control startup and shutdown order in Compose
 notoc: true
 ---
-{% include compose-eol.md %}
+
+{{< include "compose-eol.md" >}}
 
 You can control the order of service startup and shutdown with the
 [depends_on](compose-file/05-services.md#depends_on) option. Compose always starts and stops
@@ -26,5 +27,4 @@ The solution for detecting the ready state of a service is  to use the `conditio
 ## Reference information 
 
 - [`depends_on`](compose-file/05-services.md#depends_on)
-- [`healthcheck`](compose-file/05-services.md#healthcheck)
-
+- [`healthcheck`](compose-file/05-services.md#healthcheck)
\ No newline at end of file
diff --git a/content/compose/use-secrets.md b/content/compose/use-secrets.md
index 553db8bb8c..27c373550a 100644
--- a/content/compose/use-secrets.md
+++ b/content/compose/use-secrets.md
@@ -84,4 +84,4 @@ In the advanced example above:
 ## Resources:
 
 - [Secrets top-level element](compose-file/09-secrets.md)
-- [Secrets attribute for services top-level element](compose-file/05-services.md#secrets)
+- [Secrets attribute for services top-level element](compose-file/05-services.md#secrets)
\ No newline at end of file
diff --git a/content/config/containers/live-restore.md b/content/config/containers/live-restore.md
index ec107c5cec..65cbf3c265 100644
--- a/content/config/containers/live-restore.md
+++ b/content/config/containers/live-restore.md
@@ -2,7 +2,7 @@
 description: How to keep containers running when the daemon isn't available.
 keywords: docker, upgrade, daemon, dockerd, live-restore, daemonless container
 title: Keep containers alive during daemon downtime
-redirect_from:
+aliases:
 - /engine/admin/live-restore/
 ---
 
@@ -79,4 +79,4 @@ Mac or Docker Desktop for Windows.
 The live restore option only pertains to standalone containers, and not to swarm
 services. Swarm services are managed by swarm managers. If swarm managers are
 not available, swarm services continue to run on worker nodes but cannot be
-managed until enough swarm managers are available to maintain a quorum.
+managed until enough swarm managers are available to maintain a quorum.
\ No newline at end of file
diff --git a/content/config/containers/logging/_index.md b/content/config/containers/logging/_index.md
index 9971f191d4..e8aeafdbbd 100644
--- a/content/config/containers/logging/_index.md
+++ b/content/config/containers/logging/_index.md
@@ -2,7 +2,7 @@
 description: How to write to and view a container's logs
 keywords: docker, logging
 title: View container logs
-redirect_from:
+aliases:
 - /engine/admin/logging/
 - /engine/admin/logging/view_container_logs/
 ---
@@ -50,4 +50,4 @@ its errors to `/proc/self/fd/2` (which is `STDERR`). See the
 ## Next steps
 
 - Configure [logging drivers](configure.md).
-- Write a [Dockerfile](../../../engine/reference/builder.md).
+- Write a [Dockerfile](../../../engine/reference/builder.md).
\ No newline at end of file
diff --git a/content/config/containers/logging/awslogs.md b/content/config/containers/logging/awslogs.md
index efe7b05180..5fe46e9502 100644
--- a/content/config/containers/logging/awslogs.md
+++ b/content/config/containers/logging/awslogs.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to use the Amazon CloudWatch Logs logging driver.
 keywords: AWS, Amazon, CloudWatch, logging, driver
-redirect_from:
+title: Amazon CloudWatch Logs logging driver
+aliases:
 - /engine/reference/logging/awslogs/
 - /engine/admin/logging/awslogs/
-title: Amazon CloudWatch Logs logging driver
 ---
 
 The `awslogs` logging driver sends container logs to
@@ -261,8 +261,8 @@ INFO Another message was logged
 ### tag
 
 Specify `tag` as an alternative to the `awslogs-stream` option. `tag` interprets
-Go template markup, such as `{% raw %}{{.ID}}{% endraw %}`, `{% raw %}{{.FullID}}{% endraw %}`
-or `{% raw %}{{.Name}}{% endraw %}` `{% raw %}docker.{{.ID}}{% endraw %}`. See
+Go template markup, such as `{{.ID}}`, `{{.FullID}}`
+or `{{.Name}}` `docker.{{.ID}}`. See
 the [tag option documentation](log_tags.md) for details on supported template
 substitutions.
 
@@ -274,16 +274,16 @@ If not specified, the container ID is used as the log stream.
 > **Note**
 >
 > The CloudWatch log API does not support `:` in the log name. This can cause
-> some issues when using the {% raw %}`{{ .ImageName }}`{% endraw %} as a tag,
+> some issues when using the `{{ .ImageName }}` as a tag,
 > since a docker image has a format of `IMAGE:TAG`, such as `alpine:latest`.
 > Template markup can be used to get the proper format. To get the image name
 > and the first 12 characters of the container ID, you can use:
 > 
-> {% raw %}
+> 
 > ```bash
 > --log-opt tag='{{ with split .ImageName ":" }}{{join . "_"}}{{end}}-{{.ID}}'
 > ```
-> {% endraw %}
+> 
 > the output is something like: `alpine_latest-bf0072049c76`
 
 ### awslogs-force-flush-interval-seconds
@@ -328,4 +328,4 @@ and `logs:PutLogEvents` actions, as shown in the following example.
     }
   ]
 }
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/configure.md b/content/config/containers/logging/configure.md
index 56b8bb5f97..dc228828fa 100644
--- a/content/config/containers/logging/configure.md
+++ b/content/config/containers/logging/configure.md
@@ -1,12 +1,12 @@
 ---
 description: Configure logging driver.
 keywords: docker, logging, driver
-redirect_from:
+title: Configure logging drivers
+aliases:
 - /engine/reference/logging/overview/
 - /engine/reference/logging/
 - /engine/admin/reference/logging/
 - /engine/admin/logging/overview/
-title: Configure logging drivers
 ---
 
 Docker includes multiple logging mechanisms to help you
@@ -84,13 +84,13 @@ To find the current default logging driver for the Docker daemon, run
 `docker info` and search for `Logging Driver`. You can use the following
 command on Linux, macOS, or PowerShell on Windows:
 
-{% raw %}
+
 ```console
 $ docker info --format '{{.LoggingDriver}}'
 
 json-file
 ```
-{% endraw %}
+
 
 > **Note**
 > 
@@ -121,13 +121,13 @@ To find the current logging driver for a running container, if the daemon
 is using the `json-file` logging driver, run the following `docker inspect`
 command, substituting the container name or ID for ``:
 
-{% raw %}
+
 ```console
 $ docker inspect -f '{{.HostConfig.LogConfig.Type}}' 
 
 json-file
 ```
-{% endraw %}
+
 
 ## Configure the delivery mode of log messages from container to log driver
 
@@ -145,7 +145,7 @@ STDERR or STDOUT streams block.
 >
 > When the buffer is full, new messages will not be enqueued.  Dropping messages is often preferred to blocking the
 > log-writing process of an application.
-{: .warning}
+{ .warning }
 
 The `mode` log option controls whether to use the `blocking` (default) or
 `non-blocking` message delivery.
@@ -215,4 +215,4 @@ see more options.
   a temporary increase in disk usage (until the log entries from the rotated
   files are read) and an increased CPU usage while decompressing. 
 - The capacity of the host storage where the Docker data directory resides
-  determines the maximum size of the log file information.
+  determines the maximum size of the log file information.
\ No newline at end of file
diff --git a/content/config/containers/logging/dual-logging.md b/content/config/containers/logging/dual-logging.md
index 843b0db943..a0ed30d97d 100644
--- a/content/config/containers/logging/dual-logging.md
+++ b/content/config/containers/logging/dual-logging.md
@@ -1,6 +1,8 @@
 ---
-description: Learn how to read container logs locally when using a third party logging solution.
-keywords: docker, logging, driver, dual logging, dual-logging, cache, ring-buffer, configuration
+description: Learn how to read container logs locally when using a third party logging
+  solution.
+keywords: docker, logging, driver, dual logging, dual-logging, cache, ring-buffer,
+  configuration
 title: Use docker logs with remote logging drivers
 ---
 
@@ -177,4 +179,4 @@ $ cat /etc/docker/daemon.json
   The log entry to the cache is not retried.
 - Some logs might be lost from the cache in the default configuration because a
   ring buffer is used to prevent blocking the stdio of the container in case of
-  slow file writes. An admin must repair these while the daemon is shut down.
+  slow file writes. An admin must repair these while the daemon is shut down.
\ No newline at end of file
diff --git a/content/config/containers/logging/etwlogs.md b/content/config/containers/logging/etwlogs.md
index b2450ff1dd..212309802c 100644
--- a/content/config/containers/logging/etwlogs.md
+++ b/content/config/containers/logging/etwlogs.md
@@ -2,7 +2,7 @@
 description: Describes how to use the etwlogs logging driver.
 keywords: ETW, docker, logging, driver
 title: ETW logging driver
-redirect_from:
+aliases:
 - /engine/admin/logging/etwlogs/
 ---
 
@@ -64,4 +64,4 @@ context information. The timestamp is also available within the ETW event.
 >
 > This ETW provider emits only a message string, and not a specially structured
 > ETW event. Therefore, it is not required to register a manifest file with the
-> system to read and interpret its ETW events.
+> system to read and interpret its ETW events.
\ No newline at end of file
diff --git a/content/config/containers/logging/fluentd.md b/content/config/containers/logging/fluentd.md
index 38e97c715d..04e5f4a0c8 100644
--- a/content/config/containers/logging/fluentd.md
+++ b/content/config/containers/logging/fluentd.md
@@ -1,11 +1,11 @@
 ---
 description: Describes how to use the fluentd logging driver.
 keywords: Fluentd, docker, logging, driver
-redirect_from:
+title: Fluentd logging driver
+aliases:
 - /engine/reference/logging/fluentd/
 - /reference/logging/fluentd/
 - /engine/admin/logging/fluentd/
-title: Fluentd logging driver
 ---
 
 The `fluentd` logging driver sends container logs to the
@@ -31,7 +31,7 @@ The `docker logs` command is not available for this logging driver.
 Some options are supported by specifying `--log-opt` as many times as needed:
 
  - `fluentd-address`: specify a socket address to connect to the Fluentd daemon, ex `fluentdhost:24224` or `unix:///path/to/fluentd.sock`
- - `tag`: specify a tag for fluentd message, which interprets some markup, ex {% raw %}`{{.ID}}`, `{{.FullID}}` or `{{.Name}}` `docker.{{.ID}}`{% endraw %}
+ - `tag`: specify a tag for fluentd message, which interprets some markup, ex `{{.ID}}`, `{{.FullID}}` or `{{.Name}}` `docker.{{.ID}}`
 
 
  To use the `fluentd` driver as the default logging driver, set the `log-driver`
@@ -164,4 +164,4 @@ aggregate store.
 
 3. Start one or more containers with the `fluentd` logging driver:
 
-        $ docker run --log-driver=fluentd your/application
+        $ docker run --log-driver=fluentd your/application
\ No newline at end of file
diff --git a/content/config/containers/logging/gcplogs.md b/content/config/containers/logging/gcplogs.md
index 463c821b06..1fdb7c4fc5 100644
--- a/content/config/containers/logging/gcplogs.md
+++ b/content/config/containers/logging/gcplogs.md
@@ -2,12 +2,12 @@
 description: Describes how to use the Google Cloud Logging driver.
 keywords: gcplogs, google, docker, logging, driver
 title: Google Cloud Logging driver
-redirect_from:
+aliases:
 - /engine/admin/logging/gcplogs/
 ---
 
 The Google Cloud Logging driver sends container logs to
-[Google Cloud Logging](https://cloud.google.com/logging/docs/){: target="_blank" rel="noopener" class="_" }
+[Google Cloud Logging](https://cloud.google.com/logging/docs/)
 Logging.
 
 ## Usage
@@ -43,11 +43,11 @@ This log driver does not implement a reader so it is incompatible with
 
 If Docker detects that it is running in a Google Cloud Project, it discovers
 configuration from the
-[instance metadata service](https://cloud.google.com/compute/docs/metadata){: target="_blank" rel="noopener" class="_"}.
+[instance metadata service](https://cloud.google.com/compute/docs/metadata).
 Otherwise, the user must specify
 which project to log to using the `--gcp-project` log option and Docker
 attempts to obtain credentials from the
-[Google Application Default Credential](https://developers.google.com/identity/protocols/application-default-credentials){: target="_blank" rel="noopener" class="_"}.
+[Google Application Default Credential](https://developers.google.com/identity/protocols/application-default-credentials).
 The `--gcp-project` flag takes precedence over information discovered from the
 metadata server so a Docker daemon running in a Google Cloud Project can be
 overridden to log to a different Google Cloud Project using `--gcp-project`.
@@ -105,4 +105,4 @@ $ docker run \
     --log-opt gcp-meta-zone=west1 \
     --log-opt gcp-meta-name=`hostname` \
     your/application
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/gelf.md b/content/config/containers/logging/gelf.md
index 63a5ad5fac..e9729d6e22 100644
--- a/content/config/containers/logging/gelf.md
+++ b/content/config/containers/logging/gelf.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to use the Graylog Extended Format logging driver.
 keywords: graylog, gelf, logging, driver
-redirect_from:
+title: Graylog Extended Format logging driver
+aliases:
 - /engine/reference/logging/gelf/
 - /engine/admin/logging/gelf/
-title: Graylog Extended Format logging driver
 ---
 
 The `gelf` logging driver is a convenient format that is understood by a number of tools such as
@@ -87,4 +87,4 @@ $ docker run -dit \
     --log-driver=gelf \
     --log-opt gelf-address=udp://192.168.0.42:12201 \
     alpine sh
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/journald.md b/content/config/containers/logging/journald.md
index b74b7640a7..27f18b2a9e 100644
--- a/content/config/containers/logging/journald.md
+++ b/content/config/containers/logging/journald.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to use the Journald logging driver.
 keywords: Journald, docker, logging, driver
-redirect_from:
+title: Journald logging driver
+aliases:
 - /engine/reference/logging/journald/
 - /engine/admin/logging/journald/
-title: Journald logging driver
 ---
 
 The `journald` logging driver sends container logs to the
@@ -138,4 +138,4 @@ reader.add_match('CONTAINER_NAME=web')
 
 for msg in reader:
     print '{CONTAINER_ID_FULL}: {MESSAGE}'.format(**msg)
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/json-file.md b/content/config/containers/logging/json-file.md
index a0cf9fa35f..d7ce502c41 100644
--- a/content/config/containers/logging/json-file.md
+++ b/content/config/containers/logging/json-file.md
@@ -1,13 +1,12 @@
 ---
 description: Describes how to use the json-file logging driver.
 keywords: json-file, docker, logging, driver
-redirect_from:
+title: JSON File logging driver
+aliases:
 - /engine/reference/logging/json-file/
 - /engine/admin/logging/json-file/
-title: JSON File logging driver
 ---
 
-
 By default, Docker captures the standard output (and standard error) of all your containers,
 and writes them in files using the JSON format. The JSON format annotates each line with its
 origin (`stdout` or `stderr`) and its timestamp. Each log file contains information about
@@ -86,4 +85,4 @@ files no larger than 10 megabytes each.
 
 ```console
 $ docker run -it --log-opt max-size=10m --log-opt max-file=3 alpine ash
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/local.md b/content/config/containers/logging/local.md
index 8195c44567..880ddc545e 100644
--- a/content/config/containers/logging/local.md
+++ b/content/config/containers/logging/local.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to use the local logging driver.
 keywords: local, docker, logging, driver
-redirect_from:
+title: Local File logging driver
+aliases:
 - /engine/reference/logging/local/
 - /engine/admin/logging/local/
-title: Local File logging driver
 ---
 
 The `local` logging driver captures output from container's stdout/stderr and
@@ -73,4 +73,4 @@ files no larger than 10 megabytes each.
 
 ```console
 $ docker run -it --log-driver local --log-opt max-size=10m --log-opt max-file=3 alpine ash
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/log_tags.md b/content/config/containers/logging/log_tags.md
index d808848f0c..b259c18272 100644
--- a/content/config/containers/logging/log_tags.md
+++ b/content/config/containers/logging/log_tags.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to format tags for.
 keywords: docker, logging, driver, syslog, Fluentd, gelf, journald
-redirect_from:
+title: Customize log driver output
+aliases:
 - /engine/reference/logging/log_tags/
 - /engine/admin/logging/log_tags/
-title: Customize log driver output
 ---
 
 The `tag` log option specifies how to format a tag that identifies the
@@ -17,7 +17,7 @@ $ docker run --log-driver=fluentd --log-opt fluentd-address=myhost.local:24224 -
 
 Docker supports some special template markup you can use when specifying a tag's value:
 
-{% raw %}
+
 | Markup             | Description                                          |
 |--------------------|------------------------------------------------------|
 | `{{.ID}}`          | The first 12 characters of the container ID.         |
@@ -28,16 +28,15 @@ Docker supports some special template markup you can use when specifying a tag's
 | `{{.ImageName}}`   | The name of the image used by the container.         |
 | `{{.DaemonName}}`  | The name of the docker program (`docker`).           |
 
-{% endraw %}
 
-For example, specifying a {% raw %}`--log-opt tag="{{.ImageName}}/{{.Name}}/{{.ID}}"`{% endraw %} value yields `syslog` log lines like:
+
+For example, specifying a `--log-opt tag="{{.ImageName}}/{{.Name}}/{{.ID}}"` value yields `syslog` log lines like:
 
 ```none
 Aug  7 18:33:19 HOSTNAME hello-world/foobar/5790672ab6a0[9103]: Hello from Docker.
 ```
 
-At startup time, the system sets the `container_name` field and {% raw %}`{{.Name}}`{% endraw %} in
+At startup time, the system sets the `container_name` field and `{{.Name}}` in
 the tags. If you use `docker rename` to rename a container, the new name is not
 reflected in the log messages. Instead, these messages continue to use the
-original container name.
-
+original container name.
\ No newline at end of file
diff --git a/content/config/containers/logging/logentries.md b/content/config/containers/logging/logentries.md
index 7876b1c457..7abe73bb57 100644
--- a/content/config/containers/logging/logentries.md
+++ b/content/config/containers/logging/logentries.md
@@ -2,7 +2,7 @@
 title: Logentries logging driver
 description: Describes how to use the logentries logging driver.
 keywords: logentries, docker, logging, driver
-redirect_from:
+aliases:
 - /engine/admin/logging/logentries/
 ---
 
@@ -55,4 +55,4 @@ You could specify whether to send log message wrapped into container data (defau
 
 ```console
 $ docker run --log-driver=logentries --log-opt logentries-token=abcd1234-12ab-34cd-5678-0123456789ab --log-opt line-only=true
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/logging/plugins.md b/content/config/containers/logging/plugins.md
index a06a41b8e6..4cf334b44b 100644
--- a/content/config/containers/logging/plugins.md
+++ b/content/config/containers/logging/plugins.md
@@ -2,7 +2,7 @@
 description: How to use logging driver plugins
 title: Use a logging driver plugin
 keywords: logging, driver, plugins, monitoring
-redirect_from:
+aliases:
 - /engine/admin/logging/plugins/
 ---
 
@@ -38,4 +38,4 @@ detailed in the
 [logging overview](configure.md#configure-the-logging-driver-for-a-container).
 If the logging driver supports additional options, you can specify them using
 one or more `--log-opt` flags with the option name as the key and the option
-value as the value.
+value as the value.
\ No newline at end of file
diff --git a/content/config/containers/logging/splunk.md b/content/config/containers/logging/splunk.md
index 9391796aa1..65d0a8e403 100644
--- a/content/config/containers/logging/splunk.md
+++ b/content/config/containers/logging/splunk.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to use the Splunk logging driver.
 keywords: splunk, docker, logging, driver
-redirect_from:
+title: Splunk logging driver
+aliases:
 - /engine/reference/logging/splunk/
 - /engine/admin/logging/splunk/
-title: Splunk logging driver
 ---
 
 The `splunk` logging driver sends container logs to
@@ -73,7 +73,7 @@ The following properties let you configure the splunk logging driver.
 | `splunk-verify-connection`  | optional | Verify on start, that docker can connect to Splunk server. Defaults to true.                                                                                                                                                                                                                                                                |
 | `splunk-gzip`               | optional | Enable/disable gzip compression to send events to Splunk Enterprise or Splunk Cloud instance. Defaults to false.                                                                                                                                                                                                                            |
 | `splunk-gzip-level`         | optional | Set compression level for gzip. Valid values are -1 (default), 0 (no compression), 1 (best speed) ... 9 (best compression). Defaults to [DefaultCompression](https://golang.org/pkg/compress/gzip/#DefaultCompression).                                                                                                                     |
-| `tag`                       | optional | Specify tag for message, which interpret some markup. Default value is {% raw %}`{{.ID}}`{% endraw %} (12 characters of the container ID). Refer to the [log tag option documentation](log_tags.md) for customizing the log tag format.                                                                                                     |
+| `tag`                       | optional | Specify tag for message, which interpret some markup. Default value is `{{.ID}}` (12 characters of the container ID). Refer to the [log tag option documentation](log_tags.md) for customizing the log tag format.                                                                                                     |
 | `labels`                    | optional | Comma-separated list of keys of labels, which should be included in message, if these labels are specified for container.                                                                                                                                                                                                                   |
 | `labels-regex`              | optional | Similar to and compatible with `labels`. A regular expression to match logging-related labels. Used for advanced [log tag options](log_tags.md).                                                                                                                                                                                            |
 | `env`                       | optional | Comma-separated list of keys of environment variables, which should be included in message, if these variables are specified for container.                                                                                                                                                                                                 |
@@ -91,7 +91,7 @@ The path to the root certificate and Common Name is specified using an HTTPS
 scheme. This is used for verification. The `SplunkServerDefaultCert` is
 automatically generated by Splunk certificates.
 
-{% raw %}
+
 ```console
 $ docker run \
     --log-driver=splunk \
@@ -106,7 +106,7 @@ $ docker run \
     --label location=west \
     your/application
 ```
-{% endraw %}
+
 
 The `splunk-url` for Splunk instances hosted on Splunk Cloud is in a format
 like `https://http-inputs-XXXXXXXX.splunkcloud.com` and does not include a
@@ -195,4 +195,4 @@ Splunk Logging Driver allows you to configure few advanced options by specifying
 | `SPLUNK_LOGGING_DRIVER_POST_MESSAGES_FREQUENCY`  | `5s`          | If there is nothing to batch how often driver posts messages. You can think about this as the maximum time to wait for more messages to batch.     |
 | `SPLUNK_LOGGING_DRIVER_POST_MESSAGES_BATCH_SIZE` | `1000`        | How many messages driver should wait before sending them in one batch.                                                                             |
 | `SPLUNK_LOGGING_DRIVER_BUFFER_MAX`               | `10 * 1000`   | If driver cannot connect to remote server, what is the maximum amount of messages it can hold in buffer for retries.                               |
-| `SPLUNK_LOGGING_DRIVER_CHANNEL_SIZE`             | `4 * 1000`    | How many pending messages can be in the channel which is used to send messages to background logger worker, which batches them.                    |
+| `SPLUNK_LOGGING_DRIVER_CHANNEL_SIZE`             | `4 * 1000`    | How many pending messages can be in the channel which is used to send messages to background logger worker, which batches them.                    |
\ No newline at end of file
diff --git a/content/config/containers/logging/syslog.md b/content/config/containers/logging/syslog.md
index dbe94c37f8..4615c59420 100644
--- a/content/config/containers/logging/syslog.md
+++ b/content/config/containers/logging/syslog.md
@@ -1,10 +1,10 @@
 ---
 description: Describes how to use the syslog logging driver.
 keywords: syslog, docker, logging, driver
-redirect_from:
+title: Syslog logging driver
+aliases:
 - /engine/reference/logging/syslog/
 - /engine/admin/logging/syslog/
-title: Syslog logging driver
 ---
 
 The `syslog` logging driver routes logs to a `syslog` server. The `syslog` protocol uses
@@ -91,4 +91,4 @@ starting the container.
 | `labels`                 | Applies when starting the Docker daemon. A comma-separated list of logging-related labels this daemon accepts. Used for advanced [log tag options](log_tags.md).                                                                                                                                                 | `--log-opt labels=production_status,geo`                                                                 |
 | `labels-regex`           | Applies when starting the Docker daemon. Similar to and compatible with `labels`. A regular expression to match logging-related labels. Used for advanced [log tag options](log_tags.md).                                                                                                                        | `--log-opt labels-regex=^(production_status\|geo)`                                                       |
 | `env`                    | Applies when starting the Docker daemon. A comma-separated list of logging-related environment variables this daemon accepts. Used for advanced [log tag options](log_tags.md).                                                                                                                                  | `--log-opt env=os,customer`                                                                              |
-| `env-regex`              | Applies when starting the Docker daemon. Similar to and compatible with `env`. A regular expression to match logging-related environment variables. Used for advanced [log tag options](log_tags.md).                                                                                                            | `--log-opt env-regex=^(os\|customer)`                                                                    |
+| `env-regex`              | Applies when starting the Docker daemon. Similar to and compatible with `env`. A regular expression to match logging-related environment variables. Used for advanced [log tag options](log_tags.md).                                                                                                            | `--log-opt env-regex=^(os\|customer)`                                                                    |
\ No newline at end of file
diff --git a/content/config/containers/multi-service_container.md b/content/config/containers/multi-service_container.md
index d0411f754e..1655ca6562 100644
--- a/content/config/containers/multi-service_container.md
+++ b/content/config/containers/multi-service_container.md
@@ -1,12 +1,12 @@
 ---
 description: How to run more than one process in a container
 keywords: docker, supervisor, process management
-redirect_from:
+title: Run multiple services in a container
+aliases:
 - /articles/using_supervisord/
 - /engine/admin/multi-service_container/
 - /engine/admin/using_supervisord/
 - /engine/articles/using_supervisord/
-title: Run multiple services in a container
 ---
 
 A container's main running process is the `ENTRYPOINT` and/or `CMD` at the
@@ -140,4 +140,4 @@ logfile_maxbytes=0
 stdout_logfile=/dev/fd/1
 stdout_logfile_maxbytes=0
 redirect_stderr=true
-```
+```
\ No newline at end of file
diff --git a/content/config/containers/resource_constraints.md b/content/config/containers/resource_constraints.md
index 5623e30442..be460a77d5 100644
--- a/content/config/containers/resource_constraints.md
+++ b/content/config/containers/resource_constraints.md
@@ -1,10 +1,10 @@
 ---
-redirect_from:
+title: Runtime options with Memory, CPUs, and GPUs
+description: Specify the runtime options for a container
+keywords: docker, daemon, configuration, runtime
+aliases:
 - /engine/articles/systemd/
 - /engine/admin/resource_constraints/
-title: "Runtime options with Memory, CPUs, and GPUs"
-description: "Specify the runtime options for a container"
-keywords: "docker, daemon, configuration, runtime"
 ---
 
 By default, a container has no resource constraints and can use as much of a
@@ -49,7 +49,7 @@ number on the daemon or a container, or by setting `--oom-kill-disable` on a
 container.
 
 For more information about the Linux kernel's OOM management, see
-[Out of Memory Management](https://www.kernel.org/doc/gorman/html/understand/understand016.html){: target="_blank" rel="noopener" class="_" }.
+[Out of Memory Management](https://www.kernel.org/doc/gorman/html/understand/understand016.html).
 
 You can mitigate the risk of system instability due to OOME by:
 
@@ -212,7 +212,7 @@ before you can [configure the Docker daemon](#configure-the-docker-daemon) or
 > CPU scheduling and prioritization are advanced kernel-level features. Most
 > users do not need to change these values from their defaults. Setting these
 > values incorrectly can cause your host system to become unstable or unusable.
-{:.warning}
+{ .warning }
 
 #### Configure the host machine's kernel
 
@@ -353,4 +353,4 @@ GitHub page. These variables can be set in a Dockerfile.
 
 You can also utitize CUDA images which sets these variables automatically. See
 the [CUDA images](https://github.com/NVIDIA/nvidia-docker/wiki/CUDA) GitHub page
-for more information.
+for more information.
\ No newline at end of file
diff --git a/content/config/containers/runmetrics.md b/content/config/containers/runmetrics.md
index c2fb1d2b14..14603ec09e 100644
--- a/content/config/containers/runmetrics.md
+++ b/content/config/containers/runmetrics.md
@@ -1,12 +1,12 @@
 ---
 description: Measure the behavior of running containers
 keywords: docker, metrics, CPU, memory, disk, IO, run, runtime, stats
-redirect_from:
+title: Runtime metrics
+aliases:
 - /articles/runmetrics/
 - /engine/articles/run_metrics/
 - /engine/articles/runmetrics/
 - /engine/admin/runmetrics/
-title: Runtime metrics
 ---
 
 ## Docker stats
@@ -434,4 +434,4 @@ and remove the container control group. To remove a control group, just
 `rmdir` its directory. It's counter-intuitive to
 `rmdir` a directory as it still contains files; but
 remember that this is a pseudo-filesystem, so usual rules don't apply.
-After the cleanup is done, the collection process can exit safely.
+After the cleanup is done, the collection process can exit safely.
\ No newline at end of file
diff --git a/content/config/containers/start-containers-automatically.md b/content/config/containers/start-containers-automatically.md
index 7696d3b0f4..4dbd879017 100644
--- a/content/config/containers/start-containers-automatically.md
+++ b/content/config/containers/start-containers-automatically.md
@@ -1,11 +1,11 @@
 ---
 description: How to start containers automatically
 keywords: containers, restart, policies, automation, administration
-redirect_from:
+title: Start containers automatically
+aliases:
 - /engine/articles/host_integration/
 - /engine/admin/host_integration/
 - /engine/admin/start-containers-automatically/
-title: Start containers automatically
 ---
 
 Docker provides [restart policies](../../engine/reference/run.md#restart-policies---restart)
@@ -80,7 +80,7 @@ Docker depend on Docker containers, you can use a process manager such as
 >
 > Do not try to combine Docker restart policies with host-level process managers,
 > because this creates conflicts.
-{:.warning}
+{ .warning }
 
 To use a process manager, configure it to start your container or service using
 the same `docker start` or `docker service` command you would normally use to
@@ -98,4 +98,4 @@ running and starts/restart it if not.
 > the container. Docker does not recommend this approach, because it is
 > platform-dependent and even differs within different versions of a given Linux
 > distribution.
-{:.warning}
+{ .warning }
\ No newline at end of file
diff --git a/content/config/daemon/_index.md b/content/config/daemon/_index.md
index 0813afc316..9203b519aa 100644
--- a/content/config/daemon/_index.md
+++ b/content/config/daemon/_index.md
@@ -1,28 +1,28 @@
 ---
 description: Configuring and troubleshooting the Docker daemon
 keywords: docker, daemon, configuration, troubleshooting
-redirect_from:
-  - /articles/chef/
-  - /articles/configuring/
-  - /articles/dsc/
-  - /articles/puppet/
-  - /config/thirdparty/
-  - /config/thirdparty/ansible/
-  - /config/thirdparty/chef/
-  - /config/thirdparty/dsc/
-  - /config/thirdparty/puppet/
-  - /engine/admin/
-  - /engine/admin/ansible/
-  - /engine/admin/chef/
-  - /engine/admin/configuring/
-  - /engine/admin/dsc/
-  - /engine/admin/puppet/
-  - /engine/articles/chef/
-  - /engine/articles/configuring/
-  - /engine/articles/dsc/
-  - /engine/articles/puppet/
-  - /engine/userguide/
 title: Docker daemon configuration overview
+aliases:
+- /articles/chef/
+- /articles/configuring/
+- /articles/dsc/
+- /articles/puppet/
+- /config/thirdparty/
+- /config/thirdparty/ansible/
+- /config/thirdparty/chef/
+- /config/thirdparty/dsc/
+- /config/thirdparty/puppet/
+- /engine/admin/
+- /engine/admin/ansible/
+- /engine/admin/chef/
+- /engine/admin/configuring/
+- /engine/admin/dsc/
+- /engine/admin/puppet/
+- /engine/articles/chef/
+- /engine/articles/configuring/
+- /engine/articles/dsc/
+- /engine/articles/puppet/
+- /engine/userguide/
 ---
 
 This page shows you how to customize the Docker daemon, `dockerd`.
@@ -132,4 +132,4 @@ You can configure the Docker daemon to use a different directory, using the
 Since the state of a Docker daemon is kept on this directory, make sure you use
 a dedicated directory for each daemon. If two daemons share the same directory,
 for example, an NFS share, you are going to experience errors that are difficult
-to troubleshoot.
+to troubleshoot.
\ No newline at end of file
diff --git a/content/config/daemon/ipv6.md b/content/config/daemon/ipv6.md
index cfc07c4316..4c92c9ad03 100644
--- a/content/config/daemon/ipv6.md
+++ b/content/config/daemon/ipv6.md
@@ -2,7 +2,7 @@
 title: Enable IPv6 support
 description: How to enable IPv6 support in the Docker daemon
 keywords: daemon, network, networking, ipv6
-redirect_from:
+aliases:
 - /engine/userguide/networking/default_network/ipv6/
 ---
 
@@ -214,4 +214,4 @@ subnet supports 65 536 IPv6 addresses.
 
 ## Next steps
 
-- [Networking overview](../../network/index.md)
+- [Networking overview](../../network/index.md)
\ No newline at end of file
diff --git a/content/config/daemon/logs.md b/content/config/daemon/logs.md
index 349318faeb..0e9bf85b79 100644
--- a/content/config/daemon/logs.md
+++ b/content/config/daemon/logs.md
@@ -123,4 +123,4 @@ Look in the Docker logs for a message like the following:
 The locations where Docker saves these stack traces and dumps depends on your
 operating system and configuration. You can sometimes get useful diagnostic
 information straight from the stack traces and dumps. Otherwise, you can provide
-this information to Docker for help diagnosing the problem.
+this information to Docker for help diagnosing the problem.
\ No newline at end of file
diff --git a/content/config/daemon/prometheus.md b/content/config/daemon/prometheus.md
index 93b83d6953..30eccc6a8d 100644
--- a/content/config/daemon/prometheus.md
+++ b/content/config/daemon/prometheus.md
@@ -2,7 +2,7 @@
 description: Collecting Docker metrics with Prometheus
 keywords: prometheus, metrics
 title: Collect Docker metrics with Prometheus
-redirect_from:
+aliases:
 - /engine/admin/prometheus/
 - /config/thirdparty/monitoring/
 - /config/thirdparty/prometheus/
@@ -17,7 +17,7 @@ container, and monitor your Docker instance using Prometheus.
 >
 > The available metrics and the names of those metrics are in active
 > development and may change at any time.
-{: .warning }
+{ .warning }
 
 Currently, you can only monitor Docker itself. You cannot currently monitor your
 application using the Docker target.
@@ -172,5 +172,5 @@ level.
 
 ## Next steps
 
-- Read the [Prometheus documentation](https://prometheus.io/docs/introduction/overview/){: target="_blank" rel="noopener" class="_" }
-- Set up some [alerts](https://prometheus.io/docs/alerting/overview/){: target="_blank" rel="noopener" class="_" }
+- Read the [Prometheus documentation](https://prometheus.io/docs/introduction/overview/)
+- Set up some [alerts](https://prometheus.io/docs/alerting/overview/)
\ No newline at end of file
diff --git a/content/config/daemon/remote-access.md b/content/config/daemon/remote-access.md
index f0f3f1a1b4..6752853115 100644
--- a/content/config/daemon/remote-access.md
+++ b/content/config/daemon/remote-access.md
@@ -1,8 +1,9 @@
 ---
-description: >
-  Configuring remote access allows Docker to accept requests from remote hosts
-  by configuring it to listen on an IP address and port as well as the Unix
+description: 'Configuring remote access allows Docker to accept requests from remote
+  hosts by configuring it to listen on an IP address and port as well as the Unix
   socket
+
+  '
 keywords: configuration, daemon, remote access, engine
 title: Configure remote access for Docker daemon
 ---
@@ -23,7 +24,7 @@ refer to the
 > possible for remote non-root users to gain root access on the host. For more
 > information on how to use TLS certificates to secure this connection, check
 > [Protect the Docker daemon socket](../../engine/security/protect-access.md).
-{: .warning}
+{ .warning }
 
 You can configure Docker to accept remote connections. This can be done using
 the `docker.service` systemd unit file for Linux distributions using systemd. Or
@@ -87,5 +88,4 @@ you can use the `daemon.json` file, if your distribution doesn't use systemd.
    ```console
    $ sudo netstat -lntp | grep dockerd
    tcp        0      0 127.0.0.1:2375          0.0.0.0:*               LISTEN      3758/dockerd
-   ```
-
+   ```
\ No newline at end of file
diff --git a/content/config/daemon/start.md b/content/config/daemon/start.md
index 2236f0a8cc..f15ab477b1 100644
--- a/content/config/daemon/start.md
+++ b/content/config/daemon/start.md
@@ -45,4 +45,4 @@ INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
 ```
 
 To stop Docker when you have started it manually, issue a `Ctrl+C` in your
-terminal.
+terminal.
\ No newline at end of file
diff --git a/content/config/daemon/systemd.md b/content/config/daemon/systemd.md
index 611b6d83c3..b94467564d 100644
--- a/content/config/daemon/systemd.md
+++ b/content/config/daemon/systemd.md
@@ -1,12 +1,12 @@
 ---
 description: Controlling and configuring Docker using systemd
 keywords: dockerd, daemon, systemd, configuration, proxy, networking
-redirect_from:
-  - /articles/host_integration/
-  - /articles/systemd/
-  - /engine/admin/systemd/
-  - /engine/articles/systemd/
 title: Configure the daemon with systemd
+aliases:
+- /articles/host_integration/
+- /articles/systemd/
+- /engine/admin/systemd/
+- /engine/articles/systemd/
 ---
 
 This page describes how to customize daemon settings when using systemd.
@@ -237,4 +237,4 @@ service file, not in the `daemon.json` file or using environment variables.
    Environment=HTTP_PROXY=http://proxy.example.com:3128 HTTPS_PROXY=https://proxy.example.com:3129 NO_PROXY=localhost,127.0.0.1,docker-registry.example.com,.corp
    ```
 {{< /tab >}}
-{{< /tabs >}}
+{{< /tabs >}}
\ No newline at end of file
diff --git a/content/config/daemon/troubleshoot.md b/content/config/daemon/troubleshoot.md
index f66df28da0..025f015d52 100644
--- a/content/config/daemon/troubleshoot.md
+++ b/content/config/daemon/troubleshoot.md
@@ -72,7 +72,7 @@ starts successfully, it is now listening on the IP address specified in the
 > 
 > Setting `hosts` in the `daemon.json` is not supported on Docker
 > Desktop for Windows or Docker Desktop for Mac.
-{:.important}
+{ .important }
 
 ## Out of memory issues
 
@@ -94,4 +94,4 @@ You can also use operating system utilities, such as
 utilities.
 
 Finally, you can check in the process list for the `dockerd` process, using
-commands like `ps` or `top`.
+commands like `ps` or `top`.
\ No newline at end of file
diff --git a/content/config/formatting.md b/content/config/formatting.md
index 28c9e33bd5..2f1230f00e 100644
--- a/content/config/formatting.md
+++ b/content/config/formatting.md
@@ -2,7 +2,7 @@
 description: CLI and log output formatting reference
 keywords: format, formatting, output, templates, log
 title: Format command and log output
-redirect_from:
+aliases:
 - /engine/admin/formatting/
 ---
 
@@ -19,112 +19,111 @@ include examples of customizing the output format.
 > When using the `--format` flag, you need observe your shell environment. 
 > In a Posix shell, you can run the following with a single quote:
 >
-> {% raw %}
+> 
 > ```console
 > $ docker inspect --format '{{join .Args " , "}}'
 > ```
-> {% endraw %}
+> 
 >
 > Otherwise, in a Windows shell (for example, PowerShell), you need to use single quotes, but
 > escape the double quotes inside the params as follows:
 >
-> {% raw %}
+> 
 > ```console
 > $ docker inspect --format '{{join .Args \" , \"}}'
 > ```
-> {% endraw %}
+> 
 >
-{:.important}
+{ .important }
 
 ## join
 
 `join` concatenates a list of strings to create a single string.
 It puts a separator between each element in the list.
 
-{% raw %}
+
 ```console
 $ docker inspect --format '{{join .Args " , "}}' container
 ```
-{% endraw %}
+
 
 ## table
 
 `table` specifies which fields you want to see its output.
 
-{% raw %}
+
 ```console
 $ docker image list --format "table {{.ID}}\t{{.Repository}}\t{{.Tag}}\t{{.Size}}"
 ```
-{% endraw %}
+
 
 ## json
 
 `json` encodes an element as a json string.
 
 
-{% raw %}
+
 ```console
 $ docker inspect --format '{{json .Mounts}}' container
 ```
-{% endraw %}
+
 
 ## lower
 
 `lower` transforms a string into its lowercase representation.
 
-{% raw %}
+
 ```console
 $ docker inspect --format "{{lower .Name}}" container
 ```
-{% endraw %}
+
 
 ## split
 
 `split` slices a string into a list of strings separated by a separator.
 
-{% raw %}
+
 ```console
 $ docker inspect --format '{{split .Image ":"}}' container
 ```
-{% endraw %}
+
 
 ## title
 
 `title` capitalizes the first character of a string.
 
-{% raw %}
+
 ```console
 $ docker inspect --format "{{title .Name}}" container
 ```
-{% endraw %}
+
 
 ## upper
 
 `upper` transforms a string into its uppercase representation.
 
-{% raw %}
+
 ```console
 $ docker inspect --format "{{upper .Name}}" container
 ```
-{% endraw %}
+
 
 
 ## println
 
 `println` prints each value on a new line.
 
-{% raw %}
+
 ```console
 $ docker inspect --format='{{range .NetworkSettings.Networks}}{{println .IPAddress}}{{end}}' container
 ```
-{% endraw %}
+
 
 # Hint
 
 To find out what data can be printed, show all content as json:
 
-{% raw %} 
+ 
 ```console
 $ docker container ls --format='{{json .}}'
-```
-{% endraw %} 
+```
\ No newline at end of file
diff --git a/content/config/labels-custom-metadata.md b/content/config/labels-custom-metadata.md
index b527a694e5..7e94825513 100644
--- a/content/config/labels-custom-metadata.md
+++ b/content/config/labels-custom-metadata.md
@@ -2,7 +2,7 @@
 description: Description of labels, which are used to manage metadata on Docker objects.
 keywords: Usage, user guide, labels, metadata, docker, documentation, examples, annotating
 title: Docker object labels
-redirect_from:
+aliases:
 - /engine/userguide/labels-custom-metadata/
 ---
 
@@ -107,4 +107,4 @@ Labels on swarm nodes and services can be updated dynamically.
   - [Adding labels when creating a swarm service](../engine/reference/commandline/service_create.md#label)
   - [Updating a swarm service's labels](../engine/reference/commandline/service_update.md)
   - [Inspecting a swarm service's labels](../engine/reference/commandline/service_inspect.md)
-  - [Filtering swarm services by label](../engine/reference/commandline/service_ls.md#filter)
+  - [Filtering swarm services by label](../engine/reference/commandline/service_ls.md#filter)
\ No newline at end of file
diff --git a/content/config/pruning.md b/content/config/pruning.md
index b59661415a..43fa209583 100644
--- a/content/config/pruning.md
+++ b/content/config/pruning.md
@@ -1,8 +1,9 @@
 ---
 description: Pruning unused objects
-keywords: pruning, prune, images, volumes, containers, networks, disk, administration, garbage collection
+keywords: pruning, prune, images, volumes, containers, networks, disk, administration,
+  garbage collection
 title: Prune unused Docker objects
-redirect_from:
+aliases:
 - /engine/admin/pruning/
 ---
 
@@ -173,5 +174,4 @@ Are you sure you want to continue? [y/N] y
 ```
 
 By default, you are prompted to continue. To bypass the prompt, use the `-f` or
-`--force` flag.
-
+`--force` flag.
\ No newline at end of file
diff --git a/content/contribute/checklist.md b/content/contribute/checklist.md
index c39e9f1483..628c3d9e89 100644
--- a/content/contribute/checklist.md
+++ b/content/contribute/checklist.md
@@ -51,5 +51,4 @@ For information on how to add redirects, see [Source file conventions](file-conv
 
 ##### Completed a final spelling, punctuation, and grammar check
 
-For more in-depth information on our Style Guide, explore the [grammar](style/grammar.md) or [formatting](style/formatting.md) guides.
-
+For more in-depth information on our Style Guide, explore the [grammar](style/grammar.md) or [formatting](style/formatting.md) guides.
\ No newline at end of file
diff --git a/content/contribute/components/accordions.md b/content/contribute/components/accordions.md
index 898bacc95e..c135b3a2af 100644
--- a/content/contribute/components/accordions.md
+++ b/content/contribute/components/accordions.md
@@ -24,4 +24,4 @@ $ docker run hello-world
 ```
 
 {{}}
-````
+````
\ No newline at end of file
diff --git a/content/contribute/components/badges.md b/content/contribute/components/badges.md
index 8442f1509b..8e04209e8b 100644
--- a/content/contribute/components/badges.md
+++ b/content/contribute/components/badges.md
@@ -3,6 +3,7 @@ description: components and formatting examples used in Docker's docs
 title: Badges
 toc_max: 3
 ---
+
 ### Examples
 
 {{< badge color=blue text="blue badge" >}}
@@ -19,5 +20,4 @@ You can also make a badge a link.
 
 ```go
 {{}}
-```
-
+```
\ No newline at end of file
diff --git a/content/contribute/components/buttons.md b/content/contribute/components/buttons.md
index 7e7aed3fdb..8f1298527c 100644
--- a/content/contribute/components/buttons.md
+++ b/content/contribute/components/buttons.md
@@ -12,4 +12,4 @@ toc_max: 3
 
 ```go
 {{}}
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/call-outs.md b/content/contribute/components/call-outs.md
index bd1f8ae234..a163f4f4d3 100644
--- a/content/contribute/components/call-outs.md
+++ b/content/contribute/components/call-outs.md
@@ -107,4 +107,4 @@ For both of the following callouts, consult [the Docker release lifecycle](/rele
 > Docker Scout is an [early access](/release-lifecycle/#early-access-ea)
 > product.
 { .restricted }
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/cards.md b/content/contribute/components/cards.md
index 0e0e2dbb4d..23f4e693ed 100644
--- a/content/contribute/components/cards.md
+++ b/content/contribute/components/cards.md
@@ -4,11 +4,11 @@ title: Cards
 toc_max: 3
 grid:
 - title: Docker Desktop
-  description: 'Docker on your Desktop.'
+  description: Docker on your Desktop.
   icon: install_desktop
   link: /desktop/
 - title: Docker Engine
-  description: 'Vrrrrooooommm'
+  description: Vrrrrooooommm
   icon: developer_board
   link: /engine/
 - title: Docker Build
@@ -94,4 +94,4 @@ grid:
     description: Clang bang
     icon: "build"
     link: "/build/"
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/code-blocks.md b/content/contribute/components/code-blocks.md
index db865eecf9..eee9d7b612 100644
--- a/content/contribute/components/code-blocks.md
+++ b/content/contribute/components/code-blocks.md
@@ -159,4 +159,4 @@ authorizedkeys:
     - AUTHORIZED_KEYS=ssh-rsa AAAAB3Nsomelongsshkeystringhereu9UzQbVKy9o00NqXa5jkmZ9Yd0BJBjFmb3WwUR8sJWZVTPFL
   volumes:
     /root:/user:rw
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/images.md b/content/contribute/components/images.md
index bf251df8be..2b5d8038e0 100644
--- a/content/contribute/components/images.md
+++ b/content/contribute/components/images.md
@@ -24,4 +24,4 @@ toc_max: 3
   ![a pretty wide image](/assets/images/banner_image_24512.png)
 
 - Image size can be set using URL query parameters (`h` and `w`): ![a pretty wide image](/assets/images/banner_image_24512.png?w=100&h=50)
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/links.md b/content/contribute/components/links.md
index 97f47fbd4f..d76e7266e9 100644
--- a/content/contribute/components/links.md
+++ b/content/contribute/components/links.md
@@ -24,4 +24,4 @@ about them in advance.
 ```md
 [External links](https://docker.com)
 [Internal links](links.md)
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/lists.md b/content/contribute/components/lists.md
index 472c84e987..69aec179a1 100644
--- a/content/contribute/components/lists.md
+++ b/content/contribute/components/lists.md
@@ -76,4 +76,4 @@ Use dashes (`-`) or asterisks (`*`) for bullet points.
           | -------- | -------- |
           | Thing 1  | Thing 2  |
           | Thing 3  | Thing 4  |
-````
+````
\ No newline at end of file
diff --git a/content/contribute/components/tables.md b/content/contribute/components/tables.md
index 1631bafb2b..d18fadb328 100644
--- a/content/contribute/components/tables.md
+++ b/content/contribute/components/tables.md
@@ -51,4 +51,4 @@ character is optional (unless the last cell is supposed to be empty).
 | Debian     |       ✅       |
 | Fedora     |                |
 | Arch (btw) |       ✅       |
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/tabs.md b/content/contribute/components/tabs.md
index 85ac50dc6b..30d53a1766 100644
--- a/content/contribute/components/tabs.md
+++ b/content/contribute/components/tabs.md
@@ -96,4 +96,4 @@ resp, err := http.Get("/users/1")
 ```
 
 {{< /tab >}}
-{{< /tabs >}}
+{{< /tabs >}}
\ No newline at end of file
diff --git a/content/contribute/components/tooltips.md b/content/contribute/components/tooltips.md
index b7a43ac5a6..b858f738a9 100644
--- a/content/contribute/components/tooltips.md
+++ b/content/contribute/components/tooltips.md
@@ -3,6 +3,7 @@ description: components and formatting examples used in Docker's docs
 title: Tooltips
 toc_max: 3
 ---
+
 Tooltips aren't visible on mobile devices or touchscreens, so don't rely on them as the
 only way to communicate important info.
 
@@ -36,4 +37,4 @@ This is a paragraph that has a tooltip. We position it to the left so it doesn't
 {:data-toggle="tooltip" data-placement="left" title="Markdown tooltip example"}
 
 Test
-```
+```
\ No newline at end of file
diff --git a/content/contribute/components/videos.md b/content/contribute/components/videos.md
index c4d9c6dc0d..95ae9e7eeb 100644
--- a/content/contribute/components/videos.md
+++ b/content/contribute/components/videos.md
@@ -11,4 +11,4 @@ For example, the video embedded on the Get Started page has the following code:
 
 ```html
 
-```
+```
\ No newline at end of file
diff --git a/content/contribute/contribute-guide.md b/content/contribute/contribute-guide.md
index 95a3bf5b7c..24ce418a1e 100644
--- a/content/contribute/contribute-guide.md
+++ b/content/contribute/contribute-guide.md
@@ -17,7 +17,7 @@ There are two ways to contribute a pull request to the docs repository:
 
     This opens the GitHub editor, which means you don't need to know a lot about Git, or even about Markdown. When you save, Git prompts you to create a fork if you don't already have one, and to create a branch in your fork and submit the pull request.
 
-2. Fork the [docs GitHub repository]({{ site.repo }}). Suggest changes or add new content on your local branch, and submit a pull request (PR) to the `main` branch.
+2. Fork the [docs GitHub repository]({{% param "repo" %}}). Suggest changes or add new content on your local branch, and submit a pull request (PR) to the `main` branch.
 
     This is the manual, more advanced version of selecting 'Edit this page' on a published docs page. Initiating a docs change in a PR from your own branch gives you more flexibility, as you can submit changes to multiple pages or files under a single pull request, and even create new topics.
 
@@ -67,7 +67,7 @@ A Netlify test runs for each PR created against the `main` branch and deploys th
 On your local machine, clone the docs repository:
 
 ```bash
-git clone {{ site.repo }}.git
+git clone {{% param "repo" %}}.git
 cd docs
 ```
 
@@ -139,5 +139,4 @@ for your operating system. To enable the vale integration for your editor, insta
 
 The vale rules that implement the Docker style guide are included in the Docker docs repository,
 in the `.github/vale` directory. Vale will automatically apply these rules when invoked in this
-repository.
-
+repository.
\ No newline at end of file
diff --git a/content/contribute/file-conventions.md b/content/contribute/file-conventions.md
index 5230b4c588..ed73984bc7 100644
--- a/content/contribute/file-conventions.md
+++ b/content/contribute/file-conventions.md
@@ -61,4 +61,4 @@ The body of the page (with the exception of keywords) starts after the front mat
 
 ### Text length
 
-Splitting long lines (preferably up to 80 characters) can make it easier to provide feedback on small chunks of text.
+Splitting long lines (preferably up to 80 characters) can make it easier to provide feedback on small chunks of text.
\ No newline at end of file
diff --git a/content/contribute/overview.md b/content/contribute/overview.md
index 02913fac1f..0b05d1fe44 100644
--- a/content/contribute/overview.md
+++ b/content/contribute/overview.md
@@ -5,30 +5,30 @@ aliases:
 - /CONTRIBUTING/
 - /opensource/
 grid:
-  - title: "Contribution guidelines"
-    description: "Learn about the process of contributing to our docs."
-    icon: "description"
-    link: "/contribute/contribute-guide"
-  - title: "Grammar and style"
-    description: "Explore Docker's grammar and style guide"
-    icon: "menu_book"
-    link: "/contribute/style/grammar"
-  - title: "Formatting"
-    description: "Format your content to match the rest of our documentation."
-    icon: "newspaper"
-    link: "/contribute/style/formatting"
-  - title: "Recommended word list"
-    description: Choose the right words for your content.
-    icon: "checklist"
-    link: "/contribute/style/recommended-words"
-  - title: "Source file conventions"
-    description: "Guidelines for creating a new page."
-    icon: "note_add"
-    link: "/contribute/file-conventions"
-  - title: "Terminology"
-    description: "Explore commonly used Docker terms."
-    icon: "spellcheck"
-    link: "/contribute/style/terminology"
+- title: Contribution guidelines
+  description: Learn about the process of contributing to our docs.
+  icon: description
+  link: /contribute/contribute-guide
+- title: Grammar and style
+  description: Explore Docker's grammar and style guide
+  icon: menu_book
+  link: /contribute/style/grammar
+- title: Formatting
+  description: Format your content to match the rest of our documentation.
+  icon: newspaper
+  link: /contribute/style/formatting
+- title: Recommended word list
+  description: Choose the right words for your content.
+  icon: checklist
+  link: /contribute/style/recommended-words
+- title: Source file conventions
+  description: Guidelines for creating a new page.
+  icon: note_add
+  link: /contribute/file-conventions
+- title: Terminology
+  description: Explore commonly used Docker terms.
+  icon: spellcheck
+  link: /contribute/style/terminology
 ---
 
 We deeply value documentation contributions from the Docker community. We'd like to make it as easy
@@ -43,4 +43,4 @@ We also provide:
 - A section of useful components you can add to your documentation.
 - Information on Docker's [tone and voice](style/voice-tone.md).
 - A [writing checklist](checklist.md) to help you when you're contributing to Docker's documentation.
-- A command-line tool called vale to check the style and [help you find errors in your writing](contribute-guide.md#test-the-docs-locally). 
+- A command-line tool called vale to check the style and [help you find errors in your writing](contribute-guide.md#test-the-docs-locally).
\ No newline at end of file
diff --git a/content/contribute/style/grammar.md b/content/contribute/style/grammar.md
index 0bca40c0b7..b6c9a868a3 100644
--- a/content/contribute/style/grammar.md
+++ b/content/contribute/style/grammar.md
@@ -3,7 +3,7 @@ title: Grammar and style
 description: Grammar and style guidelines for technical documentation
 keywords: grammar, style, contribute
 toc_max: 2
---- 
+---
 
 Docker documentation should always be written in US English with US grammar. 
 
@@ -168,5 +168,4 @@ Don't use parentheses in technical documentation. They can reduce the readabilit
 
 ## Third party documentation
 
-If you are documenting a task that requires the use of a third-party product, link out to the third-party's documentation. Don't copy the content because it might violate copyright. It can also result in an unnecessary maintenance burden of having to keep the docs up-to-date when the third-party changes or updates their product. It is best practice to link to the single source of truth. 
-
+If you are documenting a task that requires the use of a third-party product, link out to the third-party's documentation. Don't copy the content because it might violate copyright. It can also result in an unnecessary maintenance burden of having to keep the docs up-to-date when the third-party changes or updates their product. It is best practice to link to the single source of truth.
\ No newline at end of file
diff --git a/content/contribute/style/recommended-words.md b/content/contribute/style/recommended-words.md
index a93f7548c4..7730f35c96 100644
--- a/content/contribute/style/recommended-words.md
+++ b/content/contribute/style/recommended-words.md
@@ -178,4 +178,4 @@ _We created a feature for you to add widgets._
 
 #### wish
 
-Don't use. Use `want` instead.
+Don't use. Use `want` instead.
\ No newline at end of file
diff --git a/content/contribute/style/terminology.md b/content/contribute/style/terminology.md
index 826f11ad7e..711b2e90c5 100644
--- a/content/contribute/style/terminology.md
+++ b/content/contribute/style/terminology.md
@@ -60,5 +60,4 @@ Online storage for Docker images.
 
 #### Repository
 
-Lets users share container images with their team, customers, or Docker community.
-
+Lets users share container images with their team, customers, or Docker community.
\ No newline at end of file
diff --git a/content/contribute/style/voice-tone.md b/content/contribute/style/voice-tone.md
index 9e244550e0..a9c708860e 100644
--- a/content/contribute/style/voice-tone.md
+++ b/content/contribute/style/voice-tone.md
@@ -2,7 +2,7 @@
 title: Voice and tone
 description: Docker's voice and tone
 keywords: style guide, voice, tone, content standards
---- 
+---
 
 ## Voice
 
@@ -46,4 +46,4 @@ For example, **instead of**:
 
 **Use**:
 
-“*Features such as Single Sign-on (SSO), Image Access Management, Registry Access Management are  available in Docker Business subscription*.”
+“*Features such as Single Sign-on (SSO), Image Access Management, Registry Access Management are  available in Docker Business subscription*.”
\ No newline at end of file
diff --git a/content/contribute/ui.md b/content/contribute/ui.md
index f8bd4ff7c4..c42ad4bb89 100644
--- a/content/contribute/ui.md
+++ b/content/contribute/ui.md
@@ -40,4 +40,4 @@ When documenting the UI, use the following prepositions.
 |Preposition   |UI element   |  Example |
 |:-----------|:------------|:-----------|
 |in          | dialogs 
fields 
lists 
menus 
panes 
windows 
| In the **Alert** dialog, select **OK**. 
 In the **Name** field, enter `wsfc-1`. 
 In the **Item** list, select **Desktop**. 
In the **File** menu, click **Tools**.
 In the **Metrics** pane, select **New**. 
In the **Task** window, select **Start**. |
-| on         |pages 
tabs 
toolbars | On the **Create an instance** page, select **Add**. 
 On the **Edit** tab, select **Save**.
 On the **Dashboard toolbar**, select **Edit**.
|
+| on         |pages 
tabs 
toolbars | On the **Create an instance** page, select **Add**. 
 On the **Edit** tab, select **Save**.
 On the **Dashboard toolbar**, select **Edit**.
|
\ No newline at end of file
diff --git a/content/desktop/_index.md b/content/desktop/_index.md
index 58ff397472..29682decb3 100644
--- a/content/desktop/_index.md
+++ b/content/desktop/_index.md
@@ -1,43 +1,48 @@
 ---
-description: Explore more of Docker Desktop, what it has to offer, and its key features. Take the next step by downloading or find additional resources.
-keywords: how to use docker desktop, what is docker desktop used for, what does docker desktop do, using docker desktop
+description: Explore more of Docker Desktop, what it has to offer, and its key features.
+  Take the next step by downloading or find additional resources.
+keywords: how to use docker desktop, what is docker desktop used for, what does docker
+  desktop do, using docker desktop
 title: Overview of Docker Desktop
-redirect_from:
+grid:
+- title: Install Docker Desktop
+  description: 'Install Docker Desktop on
+
+    [Mac](/desktop/install/mac-install/),
+
+    [Windows](/desktop/install/windows-install/), or
+
+    [Linux](/desktop/install/linux-install/).
+
+    '
+  icon: download
+- title: Explore Docker Desktop
+  description: Navigate Docker Desktop and learn about its key features.
+  icon: explore
+  link: /desktop/use-desktop
+- title: View the release notes
+  description: Find out about new features, improvements, and bug fixes.
+  icon: note_add
+  link: /desktop/release-notes
+- title: Browse common FAQs
+  description: Explore general FAQs or FAQs for specific platforms.
+  icon: help
+  link: /desktop/faqs/
+- title: Find additional resources
+  description: Find information on networking features, deploying on Kubernetes, and
+    more.
+  icon: all_inbox
+  link: /desktop/kubernetes
+- title: Give feedback
+  description: Provide feedback on Docker Desktop or Docker Desktop features.
+  icon: sms
+  link: /desktop/feedback
+aliases:
 - /desktop/opensource/
 - /docker-for-mac/dashboard/
 - /docker-for-mac/opensource/
 - /docker-for-windows/dashboard/
 - /docker-for-windows/opensource/
-grid:
-  - title: "Install Docker Desktop"
-    description: |
-      Install Docker Desktop on
-      [Mac](/desktop/install/mac-install/),
-      [Windows](/desktop/install/windows-install/), or
-      [Linux](/desktop/install/linux-install/).
-    icon: "download"
-  - title: "Explore Docker Desktop"
-    description: "Navigate Docker Desktop and learn about its key features."
-    icon: "explore"
-    link: "/desktop/use-desktop"
-  - title: "View the release notes"
-    description: "Find out about new features, improvements, and bug fixes."
-    icon: "note_add"
-    link: "/desktop/release-notes"
-  - title: "Browse common FAQs"
-    description: "Explore general FAQs or FAQs for specific platforms."
-    icon: "help"
-    link: "/desktop/faqs/"
-  - title: "Find additional resources"
-    description:
-      "Find information on networking features, deploying on Kubernetes, and more."
-    icon: "all_inbox"
-    link: "/desktop/kubernetes"
-  - title: "Give feedback"
-    description:
-      "Provide feedback on Docker Desktop or Docker Desktop features."
-    icon: "sms"
-    link: "/desktop/feedback"
 ---
 
 Docker Desktop is a one-click-install application for your Mac, Linux, or Windows environment
@@ -80,4 +85,4 @@ gives you access to a vast library of certified images and templates in
 their environment to rapidly auto-build, continuously integrate, and collaborate
 using a secure repository.
 
-{{< grid >}}
+{{< grid >}}
\ No newline at end of file
diff --git a/content/desktop/allow-list.md b/content/desktop/allow-list.md
index 71ec285ba2..32e9e3eb94 100644
--- a/content/desktop/allow-list.md
+++ b/content/desktop/allow-list.md
@@ -24,4 +24,4 @@ This page contains the domain URLs that you need to add to a firewall allowlist
 |https://registry-1.docker.io| Docker Pull/Push |
 |https://production.cloudflare.docker.com| Docker Pull/Push |
 |https://docker-pinata-support.s3.amazonaws.com| Troubleshooting |
-|https://api.dso.docker.com| Docker Scout service |
+|https://api.dso.docker.com| Docker Scout service |
\ No newline at end of file
diff --git a/content/desktop/backup-and-restore.md b/content/desktop/backup-and-restore.md
index f039d7160f..8d1d0d67a1 100644
--- a/content/desktop/backup-and-restore.md
+++ b/content/desktop/backup-and-restore.md
@@ -1,6 +1,7 @@
 ---
 title: How to back up and restore your Docker Desktop data
-keywords: Docker Desktop, backup, restore, migration, reinstall, containers, images, volumes
+keywords: Docker Desktop, backup, restore, migration, reinstall, containers, images,
+  volumes
 ---
 
 Use the following procedure to save and restore your images and container data. This is useful if you want to reset your VM disk or to move your Docker environment to a new
@@ -9,7 +10,7 @@ computer, for example.
 > Should I back up my containers?
 >
 > If you use volumes or bind-mounts to store your container data, backing up your containers may not be needed, but make sure to remember the options that were used when creating the container or use a [Docker Compose file](../compose/compose-file/index.md) if you want to re-create your containers with the same configuration after re-installation.
-{: .tip}
+{ .tip }
 
 ## Save your data
 
@@ -48,4 +49,4 @@ and [install a different version](release-notes.md) or reset Docker Desktop to f
 2. Re-create your containers if needed, using [`docker run`](../engine/reference/commandline/run.md),
    or [Docker Compose](../compose/index.md).
 
-Refer to the [backup, restore, or migrate data volumes](../storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.
+Refer to the [backup, restore, or migrate data volumes](../storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.
\ No newline at end of file
diff --git a/content/desktop/containerd/_index.md b/content/desktop/containerd/_index.md
index 982133f996..8399399fcc 100644
--- a/content/desktop/containerd/_index.md
+++ b/content/desktop/containerd/_index.md
@@ -1,7 +1,6 @@
 ---
 title: containerd image store (Beta)
-description:
-  How to activate the containerd integration feature in Docker Desktop
+description: How to activate the containerd integration feature in Docker Desktop
 keywords: Docker, containerd, engine, image store, lazy-pull
 toc_max: 3
 ---
@@ -15,7 +14,7 @@ image and file system management in the Docker Engine.
 > [Beta](../../release-lifecycle.md/#beta). We recommend that you do not use
 > this feature in production environments as this feature may change or be
 > removed from future releases.
-{: .experimental}
+{ .experimental }
 
 ## What is the containerd image store?
 
@@ -63,7 +62,7 @@ images** checkbox.
 > After switching to the containerd image store, images and containers from the
 > default image store won't be visible. All of those containers and images
 > still exist. To see them again, turn off the containerd image store feature.
-{: .tip}
+{ .tip }
 
 ## Building multi-platform images
 
@@ -100,7 +99,7 @@ ERROR: docker exporter does not currently support exporting manifest lists
 Turning on the containerd image store lets you build, and load, multi-platform images
 to your local image store, all while using the default builder.
 
-{% raw %}
+
 
 ```console
 $ docker info --format="{{ .Driver }}"
@@ -129,7 +128,7 @@ user/containerd-multiplatform     latest    7401bb14c229   14 seconds ago   3.38
 user/containerd-multiplatform     latest    7401bb14c229   14 seconds ago   3.26MB
 ```
 
-{% endraw %}
+
 
 You can push the multi-platform image to Docker Hub.
 
@@ -147,7 +146,7 @@ d28bdb47b683: Pushed
 
 Inspecting the tag on Docker Hub shows that the image is available for multiple platforms.
 
-![Multiplatform image tag on Docker Hub](../images/containerd_multiplatform.png){:width="750px"}
+![Multiplatform image tag on Docker Hub](../images/containerd_multiplatform.png)
 
 ## Known issues
 
@@ -190,5 +189,4 @@ Inspecting the tag on Docker Hub shows that the image is available for multiple
 
 Thanks for trying the new features available with `containerd`. Give feedback or
 report any bugs you may find through the issues tracker on the
-[feedback form](https://dockr.ly/3PODIhD){: target="_blank" rel="noopener"
-class="_"}.
+[feedback form](https://dockr.ly/3PODIhD).
\ No newline at end of file
diff --git a/content/desktop/dev-environments/_index.md b/content/desktop/dev-environments/_index.md
index 9a8a02c1f5..ddde4468b7 100644
--- a/content/desktop/dev-environments/_index.md
+++ b/content/desktop/dev-environments/_index.md
@@ -3,12 +3,13 @@ description: Dev Environments
 keywords: Dev Environments, share, local, Compose
 title: Overview of Dev Environments
 ---
-{% include dev-envs-changing.md %}
+
+{{< include "dev-envs-changing.md" >}}
 
 > **Beta**
 >
 > The Dev Environments feature is currently in [Beta](../../release-lifecycle.md#beta). We recommend that you do not use this in production environments.
-{: .experimental}
+{ .experimental }
 
 Dev Environments let you create a configurable developer environment with all the code and tools you need to quickly get up and running. 
 
@@ -16,7 +17,7 @@ It uses tools built into code editors that allows Docker to access code mounted
 
 You can use Dev Environments through the intuitive GUI in Docker Dashboard or straight from you terminal with the new [`docker dev` CLI plugin](dev-cli.md).
 
-![Dev environments tab in Docker Desktop](../images/dev-env.PNG){:width="700px"}
+![Dev environments tab in Docker Desktop](../images/dev-env.PNG)
 
 ## How does it work?
 
@@ -28,11 +29,11 @@ Dev Environments is powered by [Docker Compose](/compose/). This allows Dev Envi
 
 Every dev environment you want to run needs a `compose-dev.yaml` file which configures your application's services and lives in your project directory. You don't need to be an expert in Docker Compose or write a `compose-dev.yaml` file from scratch as Dev Environments creates a starter `compose-dev.yaml` files based on the main language in your project. 
 
-You can also use the many [sample dev environments](https://github.com/docker/awesome-compose){:target="_blank" rel="noopener" class="_"} as a starting point for how to integrate different services. Alternatively, see [Set up a dev environment](set-up.md) for more information. 
+You can also use the many [sample dev environments](https://github.com/docker/awesome-compose) as a starting point for how to integrate different services. Alternatively, see [Set up a dev environment](set-up.md) for more information. 
 
 ## What's next?
 
 Learn how to:
 - [Launch a dev environment](create-dev-env.md)
 - [Set up a dev environment](set-up.md)
-- [Distribute your dev environment](share.md)
+- [Distribute your dev environment](share.md)
\ No newline at end of file
diff --git a/content/desktop/dev-environments/create-dev-env.md b/content/desktop/dev-environments/create-dev-env.md
index 801392e61d..48d1ddc52d 100644
--- a/content/desktop/dev-environments/create-dev-env.md
+++ b/content/desktop/dev-environments/create-dev-env.md
@@ -2,10 +2,11 @@
 description: Dev Environments
 keywords: Dev Environments, share, Docker Desktop, Compose, launch
 title: Launch a dev environment
-redirect_from: 
+aliases:
 - /desktop/dev-environments/create-compose-dev-env/
 ---
-{% include dev-envs-changing.md %}
+
+{{< include "dev-envs-changing.md" >}}
 
 You can launch a dev environment from a:
 - Git repository
@@ -17,8 +18,8 @@ This does not conflict with any of the local files or local tooling set up on yo
 
 >Tip
 >
->Install the [Dev Environments browser extension](https://github.com/docker/dev-envs-extension){:target="_blank" rel="noopener" class="_"} for [Chrome](https://chrome.google.com/webstore/detail/docker-dev-environments/gnagpachnalcofcblcgdbofnfakdbeka){:target="_blank" rel="noopener" class="_"} or [Firefox](https://addons.mozilla.org/en-US/firefox/addon/docker-dev-environments/){:target="_blank" rel="noopener" class="_"}, to launch a dev environment faster.
-{: .tip }
+>Install the [Dev Environments browser extension](https://github.com/docker/dev-envs-extension) for [Chrome](https://chrome.google.com/webstore/detail/docker-dev-environments/gnagpachnalcofcblcgdbofnfakdbeka) or [Firefox](https://addons.mozilla.org/en-US/firefox/addon/docker-dev-environments/), to launch a dev environment faster.
+{ .tip }
 
 ## Prerequisites
 
@@ -28,9 +29,9 @@ Dev Environments is available as part of Docker Desktop 3.5.0 release. Download
 
 To get started with Dev Environments, you must also install the following tools and extension on your machine:
 
-- [Git](https://git-scm.com){:target="_blank" rel="noopener" class="_"}. Make sure add Git to your PATH if you're a Windows user. 
-- [Visual Studio Code](https://code.visualstudio.com/){:target="_blank" rel="noopener" class="_"}
-- [Visual Studio Code Remote Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers){:target="_blank" rel="noopener" class="_"}
+- [Git](https://git-scm.com). Make sure add Git to your PATH if you're a Windows user. 
+- [Visual Studio Code](https://code.visualstudio.com/)
+- [Visual Studio Code Remote Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
 
  After Git is installed, restart Docker Desktop. Select **Quit Docker Desktop**, and then start it again.
 
@@ -43,7 +44,7 @@ To get started with Dev Environments, you must also install the following tools
 > **Important**
 >
 > If you have enabled the WSL 2 integration in Docker Desktop for Windows, make sure you have an SSH agent running in your WSL 2 distribution.
-{: .important}
+{ .important }
 
 

     
     

-
+ \ No newline at end of file diff --git a/content/desktop/extensions-sdk/architecture/_index.md b/content/desktop/extensions-sdk/architecture/_index.md index 031c78cbc7..7a874523b4 100644 --- a/content/desktop/extensions-sdk/architecture/_index.md +++ b/content/desktop/extensions-sdk/architecture/_index.md @@ -30,14 +30,14 @@ When Docker Desktop installs the extension, it extracts the UI folder from the e Every time users click on the **Extensions** tab, Docker Desktop initializes the extension's UI as if it was the first time. When they navigate away from the tab, both the UI itself and all the sub-processes started by it (if any) are terminated. The frontend can invoke `docker` commands, communicate with the extension backend, or invoke extension executables -deployed on the host, through the [Extensions SDK](https://www.npmjs.com/package/@docker/extension-api-client){: target="_blank" rel="noopener" class="_"}. +deployed on the host, through the [Extensions SDK](https://www.npmjs.com/package/@docker/extension-api-client). > **Tip** > > The `docker extension init` generates a React based extension. But you can still use it as a starting point for > your own extension and use any other frontend framework, like Vue, Angular, Svelte, etc. or event stay with > vanilla Javascript. -{: .tip } +{ .tip } Learn more about [building a frontend](../build/frontend-extension-tutorial.md) for your extension. @@ -56,7 +56,7 @@ file > > The `docker extension init` generates a Go backend. But you can still use it as a starting point for > your own extension and use any other language like Node.js, Python, Java, .Net, or any other language and framework. -{: .tip } +{ .tip } Usually, the backend is made of one container that runs within the Docker Desktop VM. Internally, Docker Desktop creates a Docker Compose project, creates the container from the `image` option of the `vm` section of the `metadata.json`, and diff --git a/content/desktop/extensions-sdk/architecture/metadata.md b/content/desktop/extensions-sdk/architecture/metadata.md index 9fc5397b51..fd21aa8ed5 100644 --- a/content/desktop/extensions-sdk/architecture/metadata.md +++ b/content/desktop/extensions-sdk/architecture/metadata.md @@ -2,7 +2,7 @@ title: Extension metadata description: Docker extension metadata keywords: Docker, extensions, sdk, metadata -redirect_from: +aliases: - /desktop/extensions-sdk/extensions/METADATA --- diff --git a/content/desktop/extensions-sdk/architecture/security.md b/content/desktop/extensions-sdk/architecture/security.md index 009669227e..906722e084 100644 --- a/content/desktop/extensions-sdk/architecture/security.md +++ b/content/desktop/extensions-sdk/architecture/security.md @@ -2,7 +2,7 @@ title: Extension security description: Aspects of the security model of extensions keywords: Docker, extensions, sdk, security -redirect_from: +aliases: - /desktop/extensions-sdk/guides/security/ --- @@ -20,5 +20,4 @@ The Extensions SDK provides a set of JavaScript APIs to invoke commands or invok > **Important** > > Make sure you trust the publisher or author of the extension when you install it, as the extension has the same access rights as the user running Docker Desktop. -{: .important} - +{ .important } \ No newline at end of file diff --git a/content/desktop/extensions-sdk/build/backend-extension-tutorial.md b/content/desktop/extensions-sdk/build/backend-extension-tutorial.md index 7cde0d39ce..9f9218e39b 100644 --- a/content/desktop/extensions-sdk/build/backend-extension-tutorial.md +++ b/content/desktop/extensions-sdk/build/backend-extension-tutorial.md @@ -2,10 +2,10 @@ title: Add a backend to your extension description: Learn how to add a backend to your extension. keywords: Docker, extensions, sdk, build -redirect_from: - - /desktop/extensions-sdk/tutorials/minimal-backend-extension/ - - /desktop/extensions-sdk/build/minimal-backend-extension/ - - /desktop/extensions-sdk/build/set-up/backend-extension-tutorial/ +aliases: +- /desktop/extensions-sdk/tutorials/minimal-backend-extension/ +- /desktop/extensions-sdk/build/minimal-backend-extension/ +- /desktop/extensions-sdk/build/set-up/backend-extension-tutorial/ --- Your extension can ship a backend part with which the frontend can interact with. This page provides information on why and how to add a backend. @@ -50,14 +50,14 @@ Here is the extension folder structure with a backend: 1. Contains everything required to build the backend and copy it in the extension's container filesystem. 2. The source folder that contains the backend code of the extension. -Although you can start from an empty directory or from the `vm-ui extension` [sample](https://github.com/docker/extensions-sdk/tree/main/samples){:target="_blank" rel="noopener" class="_"}, +Although you can start from an empty directory or from the `vm-ui extension` [sample](https://github.com/docker/extensions-sdk/tree/main/samples), it is highly recommended that you start from the `docker extension init` command and change it to suit your needs. > **Tip** > > The `docker extension init` generates a Go backend. But you can still use it as a starting point for > your own extension and use any other language like Node.js, Python, Java, .Net, or any other language and framework. -{: .tip } +{ .tip } In this tutorial, the backend service simply exposes one route that returns a JSON payload that says "Hello". @@ -72,7 +72,7 @@ In this tutorial, the backend service simply exposes one route that returns a JS > on the host. Also, some Docker Desktop users are running in constrained environments where they > can't open ports on their machines. When choosing the language and framework for your backend, make sure it > supports sockets connection. -{: .important} +{ .important } {{< tabs group="lang" >}} {{< tab name="Go" >}} @@ -133,36 +133,36 @@ type HTTPMessageBody struct { > **Important** > -> We don't have a working example for Node yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Node){: target="_blank" rel="noopener" class="_"} +> We don't have a working example for Node yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Node) > and let us know if you'd like a sample for Node. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Python" >}} > **Important** > -> We don't have a working example for Python yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Python){: target="_blank" rel="noopener" class="_"} +> We don't have a working example for Python yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Python) > and let us know if you'd like a sample for Python. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Java" >}} > **Important** > -> We don't have a working example for Java yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Java){: target="_blank" rel="noopener" class="_"} +> We don't have a working example for Java yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Java) > and let us know if you'd like a sample for Java. -{: .important } +{ .important } {{< /tab >}} {{< tab name=".NET" >}} > **Important** > -> We don't have a working example for .NET. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=.Net){: target="_blank" rel="noopener" class="_"} +> We don't have a working example for .NET. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=.Net) > and let us know if you'd like a sample for .NET. -{: .important } +{ .important } {{< /tab >}} {{< /tabs >}} @@ -185,7 +185,7 @@ To deploy your Go backend when installing the extension, you need first to confi > > To ease version management, you can reuse the same image to build the frontend, build the backend service, and package the extension. -{: .tip } +{ .tip } ```dockerfile # syntax=docker/dockerfile:1 @@ -217,36 +217,36 @@ CMD /service -socket /run/guest-services/extension-allthethings-extension.sock > **Important** > -> We don't have a working Dockerfile for Node yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Node){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for Node yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Node) > and let us know if you'd like a Dockerfile for Node. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Python" >}} > **Important** > -> We don't have a working Dockerfile for Python yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Python){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for Python yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Python) > and let us know if you'd like a Dockerfile for Python. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Java" >}} > **Important** > -> We don't have a working Dockerfile for Java yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Java){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for Java yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=Java) > and let us know if you'd like a Dockerfile for Java. -{: .important } +{ .important } {{< /tab >}} {{< tab name=".NET" >}} > **Important** > -> We don't have a working Dockerfile for .Net. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=.Net){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for .Net. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.25798127=.Net) > and let us know if you'd like a Dockerfile for .Net. -{: .important } +{ .important } {{< /tab >}} {{< /tabs >}} @@ -273,7 +273,7 @@ For more information on the `vm` section of the `metadata.json`, see [Metadata]( > **Warning** > > Do not replace the `${DESKTOP_PLUGIN_IMAGE}` placeholder in the `metadata.json` file. The placeholder is replaced automatically with the correct image name when the extension is installed. -{: .warning} +{ .warning } ## Invoke the extension backend from your frontend @@ -288,7 +288,7 @@ extension.vm.service.get` that returns the body of the response. Replace the `ui/src/App.tsx` file with the following code: ```tsx -{% raw %} + // ui/src/App.tsx import React, { useEffect } from 'react'; import { createDockerDesktopClient } from "@docker/extension-api-client"; @@ -312,7 +312,7 @@ export function App() { {hello} ); } -{% endraw %} + ``` {{< /tab >}} @@ -320,27 +320,27 @@ export function App() { > **Important** > -> We don't have an example for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue) > and let us know if you'd like a sample with Vue. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Angular" >}} > **Important** > -> We don't have an example for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular) > and let us know if you'd like a sample with Angular. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Svelte" >}} > **Important** > -> We don't have an example for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte) > and let us know if you'd like a sample with Svelte. -{: .important } +{ .important } {{< /tab >}} {{< /tabs >}} @@ -365,7 +365,7 @@ Now you can see the backend service running in the **Containers8* tab of the Doc > > You may need to turn on the **Show system containers** option in **Settings** to see the backend container running. > See [Show extension containers](../dev/test-debug.md#show-the-extension-containers) for more information. -{: .tip } +{ .tip } Open Docker Dashboard and select the **Containers** tab. You should see the response from the backend service call displayed. @@ -373,4 +373,4 @@ call displayed. ## What's next? - Learn how to [share and publish your extension](../extensions/index.md). -- Learn more about extensions [architecture](../architecture/index.md). +- Learn more about extensions [architecture](../architecture/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/build/frontend-extension-tutorial.md b/content/desktop/extensions-sdk/build/frontend-extension-tutorial.md index c045a2538b..4840d38818 100644 --- a/content/desktop/extensions-sdk/build/frontend-extension-tutorial.md +++ b/content/desktop/extensions-sdk/build/frontend-extension-tutorial.md @@ -2,11 +2,11 @@ title: Create an advanced frontend extension description: Advanced frontend extension tutorial keywords: Docker, extensions, sdk, build -redirect_from: - - /desktop/extensions-sdk/tutorials/react-extension/ - - /desktop/extensions-sdk/build/set-up/react-extension/ - - /desktop/extensions-sdk/build/set-up/minimal-frontend-using-docker-cli/ - - /desktop/extensions-sdk/build/set-up/frontend-extension-tutorial/ +aliases: +- /desktop/extensions-sdk/tutorials/react-extension/ +- /desktop/extensions-sdk/build/set-up/react-extension/ +- /desktop/extensions-sdk/build/set-up/minimal-frontend-using-docker-cli/ +- /desktop/extensions-sdk/build/set-up/frontend-extension-tutorial/ --- To start creating your extension, you first need a directory with files which range from the extension’s source code to the required extension-specific files. This page provides information on how to set up an extension with a more advanced frontend. @@ -23,9 +23,9 @@ The quickest way to create a new extension is to run `docker extension init my-e > The `docker extension init` generates a React based extension. But you can still use it as a starting point for > your own extension and use any other frontend framework, like Vue, Angular, Svelte, etc. or even stay with > vanilla Javascript. -{: .tip } +{ .tip } -Although you can start from an empty directory or from the `react-extension` [sample folder](https://github.com/docker/extensions-sdk/tree/main/samples){:target="_blank" rel="noopener" class="_"}, +Although you can start from an empty directory or from the `react-extension` [sample folder](https://github.com/docker/extensions-sdk/tree/main/samples), it's highly recommended that you start from the `docker extension init` command and change it to suit your needs. ```bash @@ -105,27 +105,27 @@ COPY --from=client-builder /ui/build ui > **Important** > -> We don't have a working Dockerfile for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue) > and let us know if you'd like a Dockerfile for Vue. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Angular" >}} > **Important** > -> We don't have a working Dockerfile for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular) > and let us know if you'd like a Dockerfile for Angular. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Svelte" >}} > **Important** > -> We don't have a working Dockerfile for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte){: target="_blank" rel="noopener" class="_"} +> We don't have a working Dockerfile for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte) > and let us know if you'd like a Dockerfile for Svelte. -{: .important } +{ .important } {{< /tab >}} {{< /tabs >}} @@ -208,7 +208,7 @@ command and display the result in a table. Replace the `ui/src/App.tsx` file with the following code: ```tsx -{% raw %} + // ui/src/App.tsx import React, { useEffect } from 'react'; import { @@ -281,7 +281,7 @@ export function App() { ); } -{% endraw %} + ``` ![Screenshot of the container list.](images/react-extension.png) @@ -291,27 +291,27 @@ export function App() { > **Important** > -> We don't have an example for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue) > and let us know if you'd like a sample with Vue. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Angular" >}} > **Important** > -> We don't have an example for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular) > and let us know if you'd like a sample with Angular. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Svelte" >}} > **Important** > -> We don't have an example for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte) > and let us know if you'd like a sample with Svelte. -{: .important } +{ .important } {{< /tab >}} {{< /tabs >}} @@ -352,7 +352,7 @@ when you need to debug it. > > You can turn on [hot reloading](../dev/test-debug.md#hot-reloading-whilst-developing-the-ui) to avoid the need to > rebuild the extension every time you make a change. -{: .tip } +{ .tip } ## What's next? @@ -361,5 +361,4 @@ when you need to debug it. - Learn how to [setup CI for your extension](../dev/continuous-integration.md). - Learn more about extensions [architecture](../architecture/index.md). - For more information and guidelines on building the UI, see the [Design and UI styling section](../design/design-guidelines.md). -- If you want to set up user authentication for the extension, see [Authentication](../guides/oauth2-flow.md). - +- If you want to set up user authentication for the extension, see [Authentication](../guides/oauth2-flow.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/build/minimal-frontend-extension.md b/content/desktop/extensions-sdk/build/minimal-frontend-extension.md index 8ff46d97cb..2893f27616 100644 --- a/content/desktop/extensions-sdk/build/minimal-frontend-extension.md +++ b/content/desktop/extensions-sdk/build/minimal-frontend-extension.md @@ -2,9 +2,9 @@ title: Create a simple extension description: Minimal frontend extension tutorial keywords: Docker, extensions, sdk, build -redirect_from: - - /desktop/extensions-sdk/tutorials/minimal-frontend-extension/ - - /desktop/extensions-sdk/build/set-up/minimal-frontend-extension/ +aliases: +- /desktop/extensions-sdk/tutorials/minimal-frontend-extension/ +- /desktop/extensions-sdk/build/set-up/minimal-frontend-extension/ --- To start creating your extension, you first need a directory with files which range from the extension’s source code to the required extension-specific files. This page provides information on how to set up a minimal frontend extension based on plain HTML. @@ -17,7 +17,7 @@ Before you start, make sure you have installed the latest version of [Docker Des ## Extension folder structure -In the `minimal-frontend` [sample folder](https://github.com/docker/extensions-sdk/tree/main/samples){:target="_blank" rel="noopener" class="_"}, you can find a ready-to-go example that represents a UI Extension built on HTML. We will go through this code example in this tutorial. +In the `minimal-frontend` [sample folder](https://github.com/docker/extensions-sdk/tree/main/samples), you can find a ready-to-go example that represents a UI Extension built on HTML. We will go through this code example in this tutorial. Although you can start from an empty directory, it is highly recommended that you start from the template below and change it accordingly to suit your needs. @@ -104,4 +104,4 @@ The left-hand menu displays a new tab with the name of your extension. - Build a more [advanced frontend](./frontend-extension-tutorial.md) extension. - Learn how to [test and debug](../dev/test-debug.md) your extension. - Learn how to [setup CI for your extension](../dev/continuous-integration.md). -- Learn more about extensions [architecture](../architecture/index.md). +- Learn more about extensions [architecture](../architecture/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/design/_index.md b/content/desktop/extensions-sdk/design/_index.md index 9fe8adde5e..0edf71099f 100644 --- a/content/desktop/extensions-sdk/design/_index.md +++ b/content/desktop/extensions-sdk/design/_index.md @@ -2,12 +2,12 @@ title: UI styling overview for Docker extensions description: Docker extension design keywords: Docker, extensions, design -redirect_from: +aliases: - /desktop/extensions-sdk/design/design-overview/ - /desktop/extensions-sdk/design/overview/ --- -Our Design System is a constantly evolving set of specifications that aim to ensure visual consistency across Docker products, and meet [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance){:target="_blank" rel="noopener" class="_"}. We've opened parts of it to extension authors, documenting basic styles (color, typography) and components. See: [Docker Extensions Styleguide](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771){:target="_blank" rel="noopener" class="_"}. +Our Design System is a constantly evolving set of specifications that aim to ensure visual consistency across Docker products, and meet [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance). We've opened parts of it to extension authors, documenting basic styles (color, typography) and components. See: [Docker Extensions Styleguide](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771). We require extensions to match the wider Docker Desktop UI to a certain degree, and reserve the right to make this stricter in the future. @@ -17,9 +17,9 @@ To get started on your UI, follow the steps below. ### Recommended: React+MUI, using our theme -Docker Desktop's UI is written in React and [MUI](https://mui.com/){:target="_blank" rel="noopener" class="_"} (using Material UI to specific). This is the only officially supported framework for building extensions, and the one that our `init` command automatically configures for you. Using it brings significant benefits to authors: +Docker Desktop's UI is written in React and [MUI](https://mui.com/) (using Material UI to specific). This is the only officially supported framework for building extensions, and the one that our `init` command automatically configures for you. Using it brings significant benefits to authors: -- You can use our [Material UI theme](https://www.npmjs.com/package/@docker/docker-mui-theme){:target="_blank" rel="noopener" class="_"} to automatically replicate Docker Desktop's look & feel. +- You can use our [Material UI theme](https://www.npmjs.com/package/@docker/docker-mui-theme) to automatically replicate Docker Desktop's look & feel. - In future, we'll release utilities and components specifically targeting this combination (e.g. custom MUI components, or React hooks for interacting with Docker). Read our [MUI best practices](mui-best-practices.md) guide to learn future-proof ways to use MUI with Docker Desktop. @@ -40,7 +40,7 @@ See our [MUI best practices](mui-best-practices.md) article. ### Only use colors from our palette -With minor exceptions, displaying your logo for example, you should only use colors from our palette. These can be found in our [style guide document](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771){:target="_blank" rel="noopener" class="_"}, and will also soon be available in our MUI theme and via CSS variables. +With minor exceptions, displaying your logo for example, you should only use colors from our palette. These can be found in our [style guide document](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771), and will also soon be available in our MUI theme and via CSS variables. ### Use counterpart colors in light/dark mode @@ -49,4 +49,4 @@ Our colors have been chosen so that the counterpart colors in each variant of th ## What's next? - Take a look at our [MUI best practices](mui-best-practices.md). -- Learn how to [publish your extension](../extensions/index.md). +- Learn how to [publish your extension](../extensions/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/design/design-guidelines.md b/content/desktop/extensions-sdk/design/design-guidelines.md index fa20bc6d4d..4759a7265d 100644 --- a/content/desktop/extensions-sdk/design/design-guidelines.md +++ b/content/desktop/extensions-sdk/design/design-guidelines.md @@ -14,9 +14,9 @@ Here is a simple checklist to go through when building your extension: ## Build a consistent experience with Docker Desktop. -Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker-mui-theme){:target="_blank" rel="noopener" class="_"} and the [Docker Extensions Styleguide](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771){:target="_blank" rel="noopener" class="_"} to ensure that your extension feels like it is part of Docker Desktop to create a seamless experience for users. +Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker-mui-theme) and the [Docker Extensions Styleguide](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771) to ensure that your extension feels like it is part of Docker Desktop to create a seamless experience for users. -- Ensure the extension has both a light and dark theme. Using the components and styles as per the Docker style guide ensures that your extension meets the [level AA accessibility standard.](https://www.w3.org/WAI/WCAG2AA-Conformance){:target="_blank" rel="noopener" class="_"}. +- Ensure the extension has both a light and dark theme. Using the components and styles as per the Docker style guide ensures that your extension meets the [level AA accessibility standard.](https://www.w3.org/WAI/WCAG2AA-Conformance). ![Light and dark mode](images/light_dark_mode.png) @@ -30,7 +30,7 @@ Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker- - Avoid embedding terminal windows. The advantage we have with Docker Desktop over the CLI is that we have the opportunity to provide rich information to users. Make use of this interface as much as possible. - ![Terminal window used incorrectly](images/terminal_window_dont.png){:height="=50%" width="50%"} + ![Terminal window used incorrectly](images/terminal_window_dont.png) ![Terminal window used correctly](images/terminal_window_do.png) @@ -38,7 +38,7 @@ Use the [Docker Material UI Theme](https://www.npmjs.com/package/@docker/docker- - In order not to disrupt the flow of users, avoid scenarios where the user has to navigate outside Docker Desktop, to the CLI or a webpage for example, in order to carry out certain functionalities. Instead, build features that are native to Docker Desktop. - ![Incorrect way to switch context](images/switch_context_dont.png){:height="=50%" width="50%"} + ![Incorrect way to switch context](images/switch_context_dont.png) ![Correct way to switch context](images/switch_context_do.png) @@ -62,10 +62,10 @@ When building your extension, ensure that first time users of the extension and - Link to necessary resources such as documentation. - If your extension has particularly complex functionality, add a demo or video to the start page. This helps onboard a first time user quickly. - ![start page](images/start_page.png){:height="50%" width="50%"} + ![start page](images/start_page.png) ## What's next? - Explore our [design principles](design-principles.md). - Take a look at our [UI styling guidelines](index.md). -- Learn how to [publish your extension](../extensions/index.md). +- Learn how to [publish your extension](../extensions/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/design/design-principles.md b/content/desktop/extensions-sdk/design/design-principles.md index 8e48c547b4..7e90f00cd3 100644 --- a/content/desktop/extensions-sdk/design/design-principles.md +++ b/content/desktop/extensions-sdk/design/design-principles.md @@ -27,4 +27,4 @@ Our products focus on inclusive growth and are continuously useful and adapt to ## What's next? - Take a look at our [UI styling guidelines](index.md). -- Learn how to [publish your extension](../extensions/index.md). +- Learn how to [publish your extension](../extensions/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/design/mui-best-practices.md b/content/desktop/extensions-sdk/design/mui-best-practices.md index f44fb8da42..59b10c0633 100644 --- a/content/desktop/extensions-sdk/design/mui-best-practices.md +++ b/content/desktop/extensions-sdk/design/mui-best-practices.md @@ -4,7 +4,7 @@ description: Guidelines for using MUI to maximise compatibility with Docker Desk keywords: Docker, extensions, mui, theme, theming, material-ui, material --- -This article assumes you're following our recommended practice by using our [Material UI theme](https://www.npmjs.com/package/@docker/docker-mui-theme){:target="_blank" rel="noopener" class="_"}. +This article assumes you're following our recommended practice by using our [Material UI theme](https://www.npmjs.com/package/@docker/docker-mui-theme). Following the steps below maximises compatibility with Docker Desktop and minimises the work you need to do as an extension author. They should be considered supplementary to the non-MUI-specific guidelines found in the [UI Styling overview](index.md). @@ -38,13 +38,13 @@ Sometimes you’ll need a piece of UI that doesn’t exist in our design system. If you still decide to build it yourself after contacting us, try and define the new UI in a reuseable fashion. If you define your custom UI in just one place, it’ll make it easier to change in the future if our core theme changes. You could use: -- A new `variant` of an existing component - see [MUI docs](https://mui.com/material-ui/customization/theme-components/#creating-new-component-variants){:target="_blank" rel="noopener" class="_"} +- A new `variant` of an existing component - see [MUI docs](https://mui.com/material-ui/customization/theme-components/#creating-new-component-variants) - A MUI mixin (a freeform bundle of reuseable styling rules defined inside a theme) -- A new [reuseable component](https://mui.com/material-ui/customization/how-to-customize/#2-reusable-component){:target="_blank" rel="noopener" class="_"} +- A new [reuseable component](https://mui.com/material-ui/customization/how-to-customize/#2-reusable-component) -Some of the above options require you to extend our MUI theme. See the MUI documentation on [theme composition](https://mui.com/material-ui/customization/theming/#nesting-the-theme){:target="_blank" rel="noopener" class="_"}. +Some of the above options require you to extend our MUI theme. See the MUI documentation on [theme composition](https://mui.com/material-ui/customization/theming/#nesting-the-theme). ## What's next? - Take a look at our [UI styling guide](index.md). -- Learn how to [publish your extension](../extensions/index.md). +- Learn how to [publish your extension](../extensions/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/backend.md b/content/desktop/extensions-sdk/dev/api/backend.md index f249e1e71c..aae813b699 100644 --- a/content/desktop/extensions-sdk/dev/api/backend.md +++ b/content/desktop/extensions-sdk/dev/api/backend.md @@ -173,4 +173,4 @@ window.ddClient.spawnHostCmd( > You cannot use this to chain commands in a single `exec()` invocation (like `cmd1 $(cmd2)` or using pipe between commands). > -> You need to invoke `exec()` for each command and parse results to pass parameters to the next command if needed. +> You need to invoke `exec()` for each command and parse results to pass parameters to the next command if needed. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/dashboard-routes-navigation.md b/content/desktop/extensions-sdk/dev/api/dashboard-routes-navigation.md index 73d36e0b43..b3dc41cc2c 100644 --- a/content/desktop/extensions-sdk/dev/api/dashboard-routes-navigation.md +++ b/content/desktop/extensions-sdk/dev/api/dashboard-routes-navigation.md @@ -53,4 +53,4 @@ window.ddClient.navigateToVolumes(); window.ddClient.navigateToVolume(volume); window.ddClient.navigateToDevEnvironments(); -``` +``` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/dashboard.md b/content/desktop/extensions-sdk/dev/api/dashboard.md index 07ec887eee..1e3c005f40 100644 --- a/content/desktop/extensions-sdk/dev/api/dashboard.md +++ b/content/desktop/extensions-sdk/dev/api/dashboard.md @@ -92,4 +92,4 @@ window.ddClient.openExternal("https://docker.com"); ## Navigation to Dashboard routes -From your extension, you can also [navigate](dashboard-routes-navigation.md) to other parts of the Docker Desktop Dashboard. +From your extension, you can also [navigate](dashboard-routes-navigation.md) to other parts of the Docker Desktop Dashboard. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/docker.md b/content/desktop/extensions-sdk/dev/api/docker.md index 687e0b5a7c..b542a8a1eb 100644 --- a/content/desktop/extensions-sdk/dev/api/docker.md +++ b/content/desktop/extensions-sdk/dev/api/docker.md @@ -43,7 +43,7 @@ Extensions can also directly execute the `docker` command line. ```typescript const result = await ddClient.docker.cli.exec("info", [ "--format", - {% raw %}'"{{ json . }}"',{% endraw %} + '"{{ json . }}"', ]); ``` @@ -108,7 +108,7 @@ This `exec(streamOptions)` API can also be used to listen to docker events: ```typescript await ddClient.docker.cli.exec( "events", - {% raw %}["--format", "{{ json . }}", "--filter", "container=my-container"],{% endraw %} + ["--format", "{{ json . }}", "--filter", "container=my-container"], { stream: { onOutput(data) { @@ -142,10 +142,10 @@ See the [Exec API reference](reference/interfaces/Exec.md) for details about the const output = await window.ddClient.execDockerCmd( "info", "--format", - {% raw %}'"{{ json . }}"'{% endraw %} + '"{{ json . }}"' ); window.ddClient.spawnDockerCmd("logs", ["-f", "..."], (data, error) => { console.log(data.stdout); }); -``` +``` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/overview.md b/content/desktop/extensions-sdk/dev/api/overview.md index f936ef4651..476a4e13d5 100644 --- a/content/desktop/extensions-sdk/dev/api/overview.md +++ b/content/desktop/extensions-sdk/dev/api/overview.md @@ -32,4 +32,4 @@ The `ddClient` object gives access to various APIs: - [Dashboard](dashboard.md) - [Navigation](dashboard-routes-navigation.md) -Find the Extensions API reference [here](reference/README.md). +Find the Extensions API reference [here](reference/README.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/README.md b/content/desktop/extensions-sdk/dev/api/reference/README.md index 47f6adc4b8..4a4ee847c9 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/README.md +++ b/content/desktop/extensions-sdk/dev/api/reference/README.md @@ -36,4 +36,4 @@ skip_read_time: true - [HttpService](interfaces/HttpService.md) - [RequestConfig](interfaces/RequestConfig.md) - [ServiceError](interfaces/ServiceError.md) -- [DockerDesktopClient](interfaces/DockerDesktopClient.md) +- [DockerDesktopClient](interfaces/DockerDesktopClient.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/BackendV0.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/BackendV0.md index 10afaa3048..2c336b4502 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/BackendV0.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/BackendV0.md @@ -305,4 +305,4 @@ window.ddClient.spawnInVMExtension( #### Returns -`void` +`void` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/DesktopUI.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/DesktopUI.md index 97c18433db..889eaa716b 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/DesktopUI.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/DesktopUI.md @@ -26,4 +26,4 @@ ___ ### navigate -• `Readonly` **navigate**: [`NavigationIntents`](NavigationIntents.md) +• `Readonly` **navigate**: [`NavigationIntents`](NavigationIntents.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Dialog.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Dialog.md index 365e290f61..03283ba6dd 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Dialog.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Dialog.md @@ -32,4 +32,4 @@ ddClient.desktopUI.dialog.showOpenDialog({properties: ['openFile']}); #### Returns -`Promise`<[`OpenDialogResult`](OpenDialogResult.md)\> +`Promise`<[`OpenDialogResult`](OpenDialogResult.md)\> \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Docker.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Docker.md index 3055e12337..4acde233c4 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Docker.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Docker.md @@ -111,4 +111,4 @@ const images = await ddClient.docker.listImages(); #### Returns -`Promise`<`unknown`\> +`Promise`<`unknown`\> \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerCommand.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerCommand.md index b48bf3c794..f5a2383a97 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerCommand.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerCommand.md @@ -14,4 +14,4 @@ skip_read_time: true ### exec -• **exec**: [`Exec`](Exec.md) +• **exec**: [`Exec`](Exec.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient.md index 6290e74b98..1771bc47b1 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient.md @@ -697,4 +697,4 @@ window.ddClient.toastError("message"); #### Inherited from -DockerDesktopClientV0.toastError +DockerDesktopClientV0.toastError \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Exec.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Exec.md index f54fdbacaf..7a410b7885 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Exec.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Exec.md @@ -56,4 +56,4 @@ Specify the `stream` if the output of your command is too long or if you need to [`ExecProcess`](ExecProcess.md) -The spawned process. +The spawned process. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecOptions.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecOptions.md index 3662f0dc80..7ee0ff01ab 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecOptions.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecOptions.md @@ -26,4 +26,4 @@ ___ ### env -• `Optional` **env**: `ProcessEnv` +• `Optional` **env**: `ProcessEnv` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecProcess.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecProcess.md index cf1008df44..3f2ec7a19e 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecProcess.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecProcess.md @@ -20,4 +20,4 @@ Close the process started by exec(streamingOptions) #### Returns -`void` +`void` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResult.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResult.md index 6ce631ef71..b06d72bd32 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResult.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResult.md @@ -116,4 +116,4 @@ ___ #### Inherited from -[RawExecResult](RawExecResult.md).[stderr](RawExecResult.md#stderr) +[RawExecResult](RawExecResult.md).[stderr](RawExecResult.md#stderr) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResultV0.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResultV0.md index 35a725ff71..537626ae88 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResultV0.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecResultV0.md @@ -82,4 +82,4 @@ Parse a well-formed JSON output. `any` -The JSON object. +The JSON object. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions.md index 33c05f3049..fb1e6ff22b 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions.md @@ -89,4 +89,4 @@ ___ • `Optional` `Readonly` **splitOutputLines**: `boolean` -Specifies the behaviour invoking `onOutput(data)`. Raw output by default, splitting output at any position. If set to true, `onOutput` will be invoked once for each line. +Specifies the behaviour invoking `onOutput(data)`. Raw output by default, splitting output at any position. If set to true, `onOutput` will be invoked once for each line. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Extension.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Extension.md index 5f7e1fe628..0ae3b58124 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Extension.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Extension.md @@ -30,4 +30,4 @@ ___ **`Since`** -0.3.3 +0.3.3 \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionCli.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionCli.md index 5ddfb7e935..e936de28c4 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionCli.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionCli.md @@ -14,4 +14,4 @@ skip_read_time: true ### exec -• **exec**: [`Exec`](Exec.md) +• **exec**: [`Exec`](Exec.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionHost.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionHost.md index 86a5fad26c..17f04c6a96 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionHost.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionHost.md @@ -52,4 +52,4 @@ await ddClient.extension.host.cli.exec("kubectl", ["-h"], { }, }, }); -``` +``` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionVM.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionVM.md index e51834c1bb..5f16fcc09a 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionVM.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionVM.md @@ -76,4 +76,4 @@ ___ ### service -• `Optional` `Readonly` **service**: [`HttpService`](HttpService.md) +• `Optional` `Readonly` **service**: [`HttpService`](HttpService.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Host.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Host.md index d8dc89c4e2..0ecbadb0d1 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Host.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Host.md @@ -70,4 +70,4 @@ Returns the host name of the operating system. See https://nodejs.org/api/os.htm **`Since`** -0.2.2 +0.2.2 \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/HttpService.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/HttpService.md index 2b396bf86c..4bd0e34d63 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/HttpService.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/HttpService.md @@ -179,4 +179,4 @@ ddClient.extension.vm.service #### Returns -`Promise`<`unknown`\> +`Promise`<`unknown`\> \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/NavigationIntents.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/NavigationIntents.md index d03fbff881..39f3660e06 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/NavigationIntents.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/NavigationIntents.md @@ -250,4 +250,4 @@ await ddClient.desktopUI.navigate.viewVolume(volume) #### Returns -`Promise`<`void`\> +`Promise`<`void`\> \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult.md index 47691f5dfa..52a67118cd 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult.md @@ -32,4 +32,4 @@ ___ • `Optional` `Readonly` **bookmarks**: `string`[] -macOS only- An array matching the filePaths array of base64 encoded strings which contains security scoped bookmark data. securityScopedBookmarks must be enabled for this to be populated +macOS only- An array matching the filePaths array of base64 encoded strings which contains security scoped bookmark data. securityScopedBookmarks must be enabled for this to be populated \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/RawExecResult.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/RawExecResult.md index f8341ffbcb..52a567ce60 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/RawExecResult.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/RawExecResult.md @@ -50,4 +50,4 @@ ___ ### stderr -• `Readonly` **stderr**: `string` +• `Readonly` **stderr**: `string` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfig.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfig.md index 41fbb6cc31..ebbafd06a9 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfig.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfig.md @@ -32,4 +32,4 @@ ___ ### data -• `Readonly` **data**: `any` +• `Readonly` **data**: `any` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0.md index f0e30a44fc..45b73a626c 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0.md @@ -28,4 +28,4 @@ ___ ### data -• `Readonly` **data**: `any` +• `Readonly` **data**: `any` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ServiceError.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ServiceError.md index b3eeee13ef..4561bc46b2 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/ServiceError.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/ServiceError.md @@ -29,4 +29,4 @@ ___ ### statusCode -• **statusCode**: `number` +• **statusCode**: `number` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/SpawnOptions.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/SpawnOptions.md index 85d5d1304b..fd74149cf1 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/SpawnOptions.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/SpawnOptions.md @@ -40,4 +40,4 @@ ___ ### stream -• **stream**: [`ExecStreamOptions`](ExecStreamOptions.md) +• **stream**: [`ExecStreamOptions`](ExecStreamOptions.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Toast.md b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Toast.md index b2fff77aae..879fa17e1e 100644 --- a/content/desktop/extensions-sdk/dev/api/reference/interfaces/Toast.md +++ b/content/desktop/extensions-sdk/dev/api/reference/interfaces/Toast.md @@ -78,4 +78,4 @@ ddClient.desktopUI.toast.error("message"); #### Returns -`void` +`void` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/continuous-integration.md b/content/desktop/extensions-sdk/dev/continuous-integration.md index aef1d800c5..77810f4ab7 100644 --- a/content/desktop/extensions-sdk/dev/continuous-integration.md +++ b/content/desktop/extensions-sdk/dev/continuous-integration.md @@ -1,5 +1,5 @@ --- -title: "Continuous Integration (CI)" +title: Continuous Integration (CI) description: Automatically test and validate your extension. keywords: Docker, Extensions, sdk, CI, test, regression --- @@ -9,7 +9,7 @@ In order to help validate your extension and ensure it's functional, the Extensi > **Important** > > The [Docker Desktop Action](https://github.com/docker/desktop-action) and the [extension-test-helper library](https://www.npmjs.com/package/@docker/extension-test-helper) are both [experimental](https://docs.docker.com/release-lifecycle/#experimental). -{: .important } +{ .important } ## Setup CI environment with GitHub Actions @@ -81,4 +81,4 @@ afterAll(async () => { - Build an [advanced frontend](../build/frontend-extension-tutorial.md) extension. - Learn more about extensions [architecture](../architecture/index.md). -- Learn how to [publish your extension](../extensions/index.md). +- Learn how to [publish your extension](../extensions/index.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/test-debug.md b/content/desktop/extensions-sdk/dev/test-debug.md index c1bf293b1d..9df8ad40f6 100644 --- a/content/desktop/extensions-sdk/dev/test-debug.md +++ b/content/desktop/extensions-sdk/dev/test-debug.md @@ -1,8 +1,8 @@ --- -title: "Test and debug" +title: Test and debug description: Test and debug your extension. keywords: Docker, Extensions, sdk, preview, update, Chrome DevTools -redirect_from: +aliases: - /desktop/extensions-sdk/build/test-debug/ --- @@ -22,7 +22,7 @@ Each subsequent click on the extension tab also opens Chrome DevTools. To stop t $ docker extension dev reset ``` -After an extension is deployed, it is also possible to open Chrome DevTools from the UI extension part using a variation of the [Konami Code](https://en.wikipedia.org/wiki/Konami_Code){:target="_blank" rel="noopener" class="_"}. Click on the extension tab, and then hit the key sequence `up, up, down, down, left, right, left, right, p, d, t`. +After an extension is deployed, it is also possible to open Chrome DevTools from the UI extension part using a variation of the [Konami Code](https://en.wikipedia.org/wiki/Konami_Code). Click on the extension tab, and then hit the key sequence `up, up, down, down, left, right, left, right, p, d, t`. ### Hot reloading whilst developing the UI @@ -74,4 +74,4 @@ $ docker extension rm - Learn more about extensions [architecture](../architecture/index.md). - Explore our [design principles](../design/design-principles.md). - Take a look at our [UI styling guidelines](../design/index.md). -- Learn how to [setup CI for your extension](./continuous-integration.md). +- Learn how to [setup CI for your extension](./continuous-integration.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/dev/usage.md b/content/desktop/extensions-sdk/dev/usage.md index 526d71cac0..5202c94a84 100644 --- a/content/desktop/extensions-sdk/dev/usage.md +++ b/content/desktop/extensions-sdk/dev/usage.md @@ -2,7 +2,7 @@ title: Usage overview description: Docker extension CLI keywords: Docker, extensions, sdk, CLI -redirect_from: +aliases: - /desktop/extensions-sdk/dev/cli/usage/ --- @@ -16,4 +16,4 @@ The Extensions CLI is an extension development tool that is used to manage Docke - `docker extension ls` list installed Docker extensions. - `docker extension rm` removes a Docker extension. - `docker extension update` removes and re-installs a Docker extension. -- `docker extension validate` validates the extension metadata file against the JSON schema. +- `docker extension validate` validates the extension metadata file against the JSON schema. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/extensions/DISTRIBUTION.md b/content/desktop/extensions-sdk/extensions/DISTRIBUTION.md index e47117b297..dd14ddd105 100644 --- a/content/desktop/extensions-sdk/extensions/DISTRIBUTION.md +++ b/content/desktop/extensions-sdk/extensions/DISTRIBUTION.md @@ -13,11 +13,11 @@ Every extension image must contain a metadata.json file at the root of its files The Docker image must have several [image labels](labels.md), providing information about the extension. See how to use [extension labels](labels.md) to provide extension overview information. -To package and release an extension, you must build a Docker image (`docker build`), and push the image to [DockerHub](https://hub.docker.com/){: target="_blank" rel="noopener" class="_" } (`docker push`) with a specific tag that allows you to manage versions of the extension. +To package and release an extension, you must build a Docker image (`docker build`), and push the image to [DockerHub](https://hub.docker.com/) (`docker push`) with a specific tag that allows you to manage versions of the extension. ## Release your extension -Docker image tags must follow semver conventions in order to allow fetching the latest version of the extension, and to know if there are updates available. See [semver.org](https://semver.org/){:target="_blank" rel="noopener" class="_"} to learn more about semantic versioning. +Docker image tags must follow semver conventions in order to allow fetching the latest version of the extension, and to know if there are updates available. See [semver.org](https://semver.org/) to learn more about semantic versioning. Extension images must be multi-arch images so that users can install extensions on ARM/AMD hardware. These multi-arch images can include ARM/AMD specific binaries. Mac users will automatically use the right image based on their architecture. Extensions that install binaries on the host must also provide Windows binaries in the same extension image. See how to [build a multi-arch image](multi-arch.md) for your extension. @@ -44,4 +44,4 @@ Extension image labels must specify the API version that the extension relies up The [Docker Extension SDK](https://www.npmjs.com/package/@docker/extension-api-client) is licensed under the Apache 2.0 License and is free to use. -There is no constraint on how each extension should be licensed, this is up to the extension authors to decide when creating a new extension. +There is no constraint on how each extension should be licensed, this is up to the extension authors to decide when creating a new extension. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/extensions/_index.md b/content/desktop/extensions-sdk/extensions/_index.md index 060d4d6c6b..f01c93db45 100644 --- a/content/desktop/extensions-sdk/extensions/_index.md +++ b/content/desktop/extensions-sdk/extensions/_index.md @@ -14,7 +14,7 @@ Releasing your extension consists of: - Providing information about your extension: description, screenshots, etc. so users can decide to install your extension - [Validating](./validate.md) that the extension is built in the right format and includes the required information -- Making the extension image available on [Docker Hub](https://hub.docker.com/){: target="_blank" rel="noopener" class="_" } +- Making the extension image available on [Docker Hub](https://hub.docker.com/) See [Package and release your extension](DISTRIBUTION.md) for more details about the release process. @@ -41,5 +41,4 @@ Docker extensions published in the Marketplace benefit from update notifications In addition to providing a description of your extension's features and screenshots, you should also specify additional URLs using [extension labels](labels.md). This direct users to your website for reporting bugs and feedback, and accessing documentation and support. -{% include extensions-form.md %} - +{{< include "extensions-form.md" >}} \ No newline at end of file diff --git a/content/desktop/extensions-sdk/extensions/labels.md b/content/desktop/extensions-sdk/extensions/labels.md index 540fd17d3c..973a06f97f 100644 --- a/content/desktop/extensions-sdk/extensions/labels.md +++ b/content/desktop/extensions-sdk/extensions/labels.md @@ -20,7 +20,7 @@ Here is the list of labels you need to specify when building your extension: | `org.opencontainers.image.description` | Yes | Human-readable description of the software packaged in the image (string) | This extension is cool. | | `org.opencontainers.image.vendor` | Yes | Name of the distributing entity, organization, or individual. | Acme, Inc. | | `com.docker.desktop.extension.api.version` | Yes | Version of the Docker Extension manager that the extension is compatible with. It must follow [semantic versioning](https://semver.org/). | A specific version like `0.1.0` or, a constraint expression: `>= 0.1.0`, `>= 1.4.7, < 2.0` . For your first extension, you can use `docker extension version` to know the SDK API version and specify `>= `. | -| `com.docker.desktop.extension.icon` | Yes | The extension icon (format: .svg .png .jpg) | {{ site.docs_url }}/assets/images/engine.svg | +| `com.docker.desktop.extension.icon` | Yes | The extension icon (format: .svg .png .jpg) | {{% param "docs_url" %}}/assets/images/engine.svg | | `com.docker.extension.screenshots` | Yes | A JSON array of image URLs and an alternative text displayed to users (in the order they appear in your metadata) in your extension's details page. **Note:** The recommended size for screenshots is 2400x1600 pixels. | `[{"alt":"alternative text for image 1",` `"url":"https://foo.bar/image1.png"},` `{"alt":"alternative text for image2",` `"url":"https://foo.bar/image2.jpg"}]` | | `com.docker.extension.detailed-description` | Yes | Additional information in plain text or HTML about the extension to display in the details dialog. | `My detailed description` or `

My detailed description

` | | `com.docker.extension.publisher-url` | Yes | The publisher website URL to display in the details dialog. | `https://foo.bar` | @@ -32,14 +32,14 @@ Here is the list of labels you need to specify when building your extension: > Missing required labels > > If any of the previous **required** labels are missing in the `Dockerfile`, Docker Desktop considers the extension invalid and doesn't list it in the Marketplace. -{: .important} +{ .important } > HTML content styling > > Docker Desktop applies CSS styles to the provided HTML content. You can make sure that it renders correctly > [within the marketplace](#preview-the-extension-in-the-marketplace). Docker recommends that you follow the > [Styling guidelines](../design/index.md). -{: .tip} +{ .tip } ## Preview the extension in the Marketplace @@ -54,4 +54,4 @@ When you build and install your unpublished extension, you can preview the exten > You can re-tag your image in order to have a different image name that's not listed as a published extension. > Use `docker tag org/published-extension unpublished-extension` and then `docker extension install unpublished-extension`. -![List preview](images/list-preview.png) +![List preview](images/list-preview.png) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/extensions/multi-arch.md b/content/desktop/extensions-sdk/extensions/multi-arch.md index e6a7cce7e5..a2bc2cc0fb 100644 --- a/content/desktop/extensions-sdk/extensions/multi-arch.md +++ b/content/desktop/extensions-sdk/extensions/multi-arch.md @@ -55,7 +55,7 @@ Manifests: > Having trouble pushing the image? > > Ensure you are logged into DockerHub. Otherwise, run `docker login` to authenticate. -{: .tip} +{ .tip } For more information, see [Multi-platform images](../../../build/building/multi-platform.md) page. @@ -141,4 +141,4 @@ When the extension is installed, the extension framework copies the binaries fro ## Can I develop extensions that run Windows containers? -Although Docker Extensions is supported on Docker Desktop for Windows, Mac, and Linux, the extension framework only supports Linux containers. Therefore, you must target `linux` as the OS when you build your extension image. +Although Docker Extensions is supported on Docker Desktop for Windows, Mac, and Linux, the extension framework only supports Linux containers. Therefore, you must target `linux` as the OS when you build your extension image. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/extensions/publish.md b/content/desktop/extensions-sdk/extensions/publish.md index 85e7d094ec..67ac2ea675 100644 --- a/content/desktop/extensions-sdk/extensions/publish.md +++ b/content/desktop/extensions-sdk/extensions/publish.md @@ -6,13 +6,13 @@ keywords: Docker, extensions, publish ## Submit your extension to the marketplace -Docker Desktop displays published extensions in the Extensions Marketplace on [Docker Desktop](https://open.docker.com/extensions/marketplace){: target="_blank" rel="noopener" class="_"} and [Docker Hub](https://hub.docker.com/search?q=&type=extension){: target="_blank" rel="noopener" class="_"}. +Docker Desktop displays published extensions in the Extensions Marketplace on [Docker Desktop](https://open.docker.com/extensions/marketplace) and [Docker Hub](https://hub.docker.com/search?q=&type=extension). The Extensions Marketplace is a curated space where developers can discover extensions to improve their developer experience and propose their own extension to be available for all Desktop users. Whenever you are [ready to publish](./DISTRIBUTION.md) your extension in the Marketplace, you have two publishing options: -[Self-publish your extension](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+){: target="_blank" rel="noopener" .button .primary-btn } -[Request that Docker reviews your extension](https://www.docker.com/products/extensions/submissions/){: target="_blank" rel="noopener" .button .primary-btn } +[Self-publish your extension](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+) +[Request that Docker reviews your extension](https://www.docker.com/products/extensions/submissions/) > **Note** > @@ -34,11 +34,11 @@ These guidelines don't replace Docker's terms of service or guarantee approval: - Test your extension with potential users - Test your extension for crashes, bugs, and performance issues - Test your extension on various platforms (Mac, Windows, Linux) -- Read the [Terms of Service](https://www.docker.com/legal/extensions_marketplace_developer_agreement/){: target="_blank" rel="noopener" class="_" } +- Read the [Terms of Service](https://www.docker.com/legal/extensions_marketplace_developer_agreement/) ### Which publishing option to choose -When submitting an extension to the extensions submissions [repository](https://github.com/docker/extensions-submissions/issues/new/choose){:target="_blank" rel="noopener" class="_" }, you have two publishing options. Publish as either: +When submitting an extension to the extensions submissions [repository](https://github.com/docker/extensions-submissions/issues/new/choose), you have two publishing options. Publish as either: - A Self-published extension - A Docker-reviewed extension @@ -55,7 +55,7 @@ evolve/polish your extension. You can request a review from the Docker Extension > > Docker Desktop caches the list of extensions available in the Marketplace for 12 hours. If you don't see your > extension in the Marketplace, you can restart Docker Desktop to force the cache to be refreshed. -{: .important} +{ .important } #### Process for Docker-reviewed extensions diff --git a/content/desktop/extensions-sdk/extensions/share.md b/content/desktop/extensions-sdk/extensions/share.md index 3d2ff6e65c..f9776a6a59 100644 --- a/content/desktop/extensions-sdk/extensions/share.md +++ b/content/desktop/extensions-sdk/extensions/share.md @@ -32,4 +32,4 @@ To generate this link you can either: ![Share button](images/list-preview.png) -Previews of the extension description or screenshots, for example, are created using [extension labels](labels.md). +Previews of the extension description or screenshots, for example, are created using [extension labels](labels.md). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/extensions/validate.md b/content/desktop/extensions-sdk/extensions/validate.md index 8ea2d12bb9..7878828c70 100644 --- a/content/desktop/extensions-sdk/extensions/validate.md +++ b/content/desktop/extensions-sdk/extensions/validate.md @@ -2,7 +2,7 @@ title: Validate your extension description: Step three in the extension creation process keywords: Docker, Extensions, sdk, validate, install -redirect_from: +aliases: - /desktop/extensions-sdk/extensions/validation/ - /desktop/extensions-sdk/build/build-install/ - /desktop/extensions-sdk/dev/cli/build-test-install-extension/ @@ -35,5 +35,4 @@ Before the image is built, it is also possible to validate only the metadata.jso $ docker extension validate /path/to/metadata.json ``` -The JSON schema used to validate the `metadata.json` file against can be found under the [releases page](https://github.com/docker/extensions-sdk/releases/latest){:target="_blank" rel="noopener" class="_"}. - +The JSON schema used to validate the `metadata.json` file against can be found under the [releases page](https://github.com/docker/extensions-sdk/releases/latest). \ No newline at end of file diff --git a/content/desktop/extensions-sdk/guides/invoke-host-binaries.md b/content/desktop/extensions-sdk/guides/invoke-host-binaries.md index e7b15803a0..b8eea942d4 100644 --- a/content/desktop/extensions-sdk/guides/invoke-host-binaries.md +++ b/content/desktop/extensions-sdk/guides/invoke-host-binaries.md @@ -1,6 +1,7 @@ --- title: Invoke host binaries -description: Add invocations to host binaries from the frontend with the extension SDK. +description: Add invocations to host binaries from the frontend with the extension + SDK. keywords: Docker, extensions, sdk, build --- @@ -90,27 +91,27 @@ export function App() { > **Important** > -> We don't have an example for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Vue yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Vue) > and let us know if you'd like a sample with Vue. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Angular" >}} > **Important** > -> We don't have an example for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Angular yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Angular) > and let us know if you'd like a sample with Angular. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Svelte" >}} > **Important** > -> We don't have an example for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte){: target="_blank" rel="noopener" class="_"} +> We don't have an example for Svelte yet. [Fill out the form](https://docs.google.com/forms/d/e/1FAIpQLSdxJDGFJl5oJ06rG7uqtw1rsSBZpUhv_s9HHtw80cytkh2X-Q/viewform?usp=pp_url&entry.1333218187=Svelte) > and let us know if you'd like a sample with Svelte. -{: .important } +{ .important } {{< /tab >}} {{< /tabs >}} @@ -152,4 +153,4 @@ the extension. Once the extension is uninstalled, the binaries that were copied } ``` -The `path` must reference the path of the binary inside the container. +The `path` must reference the path of the binary inside the container. \ No newline at end of file diff --git a/content/desktop/extensions-sdk/guides/kubernetes.md b/content/desktop/extensions-sdk/guides/kubernetes.md index 7e3d31a4a9..d0686283fe 100644 --- a/content/desktop/extensions-sdk/guides/kubernetes.md +++ b/content/desktop/extensions-sdk/guides/kubernetes.md @@ -2,13 +2,13 @@ title: Interacting with Kubernetes from a Docker extension description: How to connect to a Kubernetes cluster from a Docker Extension keywords: Docker, Extensions, sdk, Kubernetes -redirect_from: - - /desktop/extensions-sdk/dev/kubernetes/ +aliases: +- /desktop/extensions-sdk/dev/kubernetes/ --- Currently, the Extensions SDK does not provide any API methods to directly interact with the Docker Desktop managed Kubernetes cluster or any other created using other tools such as KinD. However, this page provides a way for you to use other SDK APIs to interact indirectly with a Kubernetes cluster from your Docker extension. -To request an API that directly interacts with Docker Desktop-managed Kubernetes, you can upvote [this issue](https://github.com/docker/extensions-sdk/issues/181){:target="_blank" rel="noopener" class="_"} in our GitHub repository. +To request an API that directly interacts with Docker Desktop-managed Kubernetes, you can upvote [this issue](https://github.com/docker/extensions-sdk/issues/181) in our GitHub repository. ## Prerequisites @@ -26,7 +26,7 @@ To find out how to ship the `kubectl` command line tool for multiple platforms a ## Examples -The code snippets below have been put together in the [Kubernetes Sample Extension](https://github.com/docker/extensions-sdk/tree/main/samples/kubernetes-sample-extension){:target="_blank" rel="noopener" class="_"}. It shows how to interact with a Kubernetes cluster by shipping the `kubectl` command-line tool. +The code snippets below have been put together in the [Kubernetes Sample Extension](https://github.com/docker/extensions-sdk/tree/main/samples/kubernetes-sample-extension). It shows how to interact with a Kubernetes cluster by shipping the `kubectl` command-line tool. ### Check the Kubernetes API server is reachable @@ -76,7 +76,7 @@ Below there are different ways to persist and read the kubeconfig file from the > Warning > > The `kubeconfig` file is very sensitive and if found can give an attacker administrative access to the Kubernetes Cluster. -{: .warning} +{ .warning } ### Extension's backend container @@ -149,4 +149,4 @@ localStorage.setItem("kubeconfig", kubeConfig); ```typescript localStorage.getItem("kubeconfig"); -``` +``` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/guides/oauth2-flow.md b/content/desktop/extensions-sdk/guides/oauth2-flow.md index ec13cf681b..e680cb771a 100644 --- a/content/desktop/extensions-sdk/guides/oauth2-flow.md +++ b/content/desktop/extensions-sdk/guides/oauth2-flow.md @@ -2,8 +2,8 @@ title: OAuth 2.0 flow description: Docker extension OAuth 2.0 flow keywords: Docker, extensions, sdk, OAuth 2.0 -redirect_from: - - /desktop/extensions-sdk/dev/oauth2-flow/ +aliases: +- /desktop/extensions-sdk/dev/oauth2-flow/ --- > Note @@ -20,7 +20,7 @@ The Authorization Code grant type is used by confidential and public clients to After the user returns to the client via the redirect URL, the application gets the authorization code from the URL and uses it to request an access token. -![Flow for OAuth 2.0](images/oauth2-flow.png){: style=width:80% } +![Flow for OAuth 2.0](images/oauth2-flow.png) The image above shows that: @@ -57,7 +57,7 @@ You can get the authorization code from the extension UI by listing `docker-desk > **Important** > > Using this feature requires the extension SDK 0.3.3 in Docker Desktop. You need to ensure that the required SDK version for your extension set with `com.docker.desktop.extension.api.version` in [image labels](../extensions/labels.md) is higher than 0.3.3. -{: .important} +{ .important } #### Authorization @@ -93,4 +93,4 @@ It's highly recommended that you use an external source of storage to store the ## What's next -Learn how to [publish and distribute your extension](../extensions/index.md) +Learn how to [publish and distribute your extension](../extensions/index.md) \ No newline at end of file diff --git a/content/desktop/extensions-sdk/guides/use-docker-socket-from-backend.md b/content/desktop/extensions-sdk/guides/use-docker-socket-from-backend.md index d0fd3cdfd7..45f887f232 100644 --- a/content/desktop/extensions-sdk/guides/use-docker-socket-from-backend.md +++ b/content/desktop/extensions-sdk/guides/use-docker-socket-from-backend.md @@ -22,4 +22,4 @@ services: image: ${DESKTOP_PLUGIN_IMAGE} volumes: - /var/run/docker.sock.raw:/var/run/docker.sock -``` +``` \ No newline at end of file diff --git a/content/desktop/extensions-sdk/process.md b/content/desktop/extensions-sdk/process.md index 894cb03c1a..addb87042a 100644 --- a/content/desktop/extensions-sdk/process.md +++ b/content/desktop/extensions-sdk/process.md @@ -23,10 +23,10 @@ The build process consists of: > **Tip** > -> Whilst building your extension, make sure you follow the [design](design/design-guidelines.md) and [UI styling](design/index.md) guidelines to ensure visual consistency and [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance){:target="_blank" rel="noopener" class="_"}. -{: .tip} +> Whilst building your extension, make sure you follow the [design](design/design-guidelines.md) and [UI styling](design/index.md) guidelines to ensure visual consistency and [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance). +{ .tip } -For further inspiration, see the other examples in the [samples folder](https://github.com/docker/extensions-sdk/tree/main/samples){:target="_blank" rel="noopener" class="_"}. +For further inspiration, see the other examples in the [samples folder](https://github.com/docker/extensions-sdk/tree/main/samples). ## Part two: Publish and distribute your extension @@ -34,7 +34,7 @@ Docker Desktop displays published extensions in the Extensions Marketplace. The If you want your extension published in the Marketplace, read the [publish documentation](./extensions/publish.md). -{% include extensions-form.md %} +{{< include "extensions-form.md" >}} ## What’s next? @@ -44,4 +44,4 @@ Alternatively, get started with reading the "Part one: Build" section for more i For an in-depth tutorial of the entire build process, we recommend the following video walkthrough from DockerCon 2022. - + \ No newline at end of file diff --git a/content/desktop/extensions-sdk/quickstart.md b/content/desktop/extensions-sdk/quickstart.md index 07fc2d8c26..67bf7edc60 100644 --- a/content/desktop/extensions-sdk/quickstart.md +++ b/content/desktop/extensions-sdk/quickstart.md @@ -2,8 +2,8 @@ title: Quickstart description: Guide on how to build an extension quickly keywords: quickstart, extensions -redirect_from: - - desktop/extensions-sdk/tutorials/initialize/ +aliases: +- desktop/extensions-sdk/tutorials/initialize/ --- Follow this guide to get started with building a basic Docker extension. The Quickstart guide automatically generates boilerplate files for you. @@ -11,8 +11,8 @@ Follow this guide to get started with building a basic Docker extension. The Qui ## Prerequisites - [Docker Desktop](../release-notes.md) -- [NodeJS](https://nodejs.org/){:target="_blank" rel="noopener" class="_"} -- [Go](https://go.dev/dl/){:target="_blank" rel="noopener" class="_"} +- [NodeJS](https://nodejs.org/) +- [Go](https://go.dev/dl/) > Note > @@ -83,7 +83,7 @@ To remove the extension, run: $ docker extension rm ``` -{% include extensions-form.md %} +{{< include "extensions-form.md" >}} ## What's next @@ -91,4 +91,4 @@ $ docker extension rm - Learn how to [test and debug](dev/test-debug.md) your extension. - Learn how to [setup CI for your extension](dev/continuous-integration.md). - Learn more about extensions [architecture](architecture/index.md). -- Learn more about [designing the UI](design/design-guidelines.md). +- Learn more about [designing the UI](design/design-guidelines.md). \ No newline at end of file diff --git a/content/desktop/extensions/_index.md b/content/desktop/extensions/_index.md index e741353db6..8b10666b48 100644 --- a/content/desktop/extensions/_index.md +++ b/content/desktop/extensions/_index.md @@ -12,12 +12,12 @@ You can seamlessly connect your favorite development tools to your application d Anyone can use Docker Extensions and there is no limit to the number of extensions you can install. -![Extensions Marketplace](/assets/images/extensions4.22.png){:width="750px"} +![Extensions Marketplace](/assets/images/extensions4.22.png) ## What extensions are available? There is a mix of partner and community-built extensions and Docker-built extensions. -You can explore the list of available extensions in [Docker Hub](https://hub.docker.com/search?q=&type=extension){:target="_blank" rel="noopener" class="_"} or in the Extensions Marketplace within Docker Desktop. +You can explore the list of available extensions in [Docker Hub](https://hub.docker.com/search?q=&type=extension) or in the Extensions Marketplace within Docker Desktop. To find out more about Docker Extensions, we recommend the video walkthrough from DockerCon 2022: @@ -25,4 +25,4 @@ To find out more about Docker Extensions, we recommend the video walkthrough fro ## Prerequisites -Docker Extensions are available as part of Docker Desktop 4.8.0 and later releases. [Download and install Docker Desktop 4.8.0 or later](../release-notes.md). +Docker Extensions are available as part of Docker Desktop 4.8.0 and later releases. [Download and install Docker Desktop 4.8.0 or later](../release-notes.md). \ No newline at end of file diff --git a/content/desktop/extensions/marketplace.md b/content/desktop/extensions/marketplace.md index a347cb6ba3..bc56674add 100644 --- a/content/desktop/extensions/marketplace.md +++ b/content/desktop/extensions/marketplace.md @@ -49,4 +49,4 @@ You can uninstall an extension at any time. 1. From the menu bar, select the ellipsis to the right of **Extensions**. 2. Select **Manage**. This displays a list of extensions you've installed. -3. Select **Uninstall**. +3. Select **Uninstall**. \ No newline at end of file diff --git a/content/desktop/extensions/non-marketplace.md b/content/desktop/extensions/non-marketplace.md index bfd0833689..39e68e2215 100644 --- a/content/desktop/extensions/non-marketplace.md +++ b/content/desktop/extensions/non-marketplace.md @@ -1,6 +1,6 @@ --- description: Extensions -keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows, +keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows, title: Non-Marketplace extensions --- @@ -10,7 +10,7 @@ title: Non-Marketplace extensions > > Docker Extensions that are not in the Marketplace haven't gone through Docker's review process. > Extensions can install binaries, invoke commands and access files on your machine. Installing them is at your own risk. -{: .warning} +{ .warning } The Extensions Marketplace is the trusted and official place to install extensions from within Docker Desktop. These extensions have gone through a review process by Docker. However, other extensions can also be installed in Docker Desktop if you trust the extension author. @@ -55,4 +55,4 @@ Go to the Docker Dashboard to see the new extension updated. ## Uninstall an extension -To uninstall an extension which is not present in the Marketplace, you can either navigate to the **Managed** tab in the Marketplace and select the **Uninstall** button, or from a terminal type `docker extension uninstall IMAGE[:TAG]`. +To uninstall an extension which is not present in the Marketplace, you can either navigate to the **Managed** tab in the Marketplace and select the **Uninstall** button, or from a terminal type `docker extension uninstall IMAGE[:TAG]`. \ No newline at end of file diff --git a/content/desktop/extensions/settings-feedback.md b/content/desktop/extensions/settings-feedback.md index 09576dc965..c27c338070 100644 --- a/content/desktop/extensions/settings-feedback.md +++ b/content/desktop/extensions/settings-feedback.md @@ -62,4 +62,4 @@ extension, select: - Slack - Issues. You'll be sent to a page outside of Docker Desktop to submit your feedback. -If an extension doesn't provide a way for you to give feedback, contact us and we'll pass on the feedback for you. To provide feedback, select the **Give feedback** to the right of **Extensions Marketplace**. +If an extension doesn't provide a way for you to give feedback, contact us and we'll pass on the feedback for you. To provide feedback, select the **Give feedback** to the right of **Extensions Marketplace**. \ No newline at end of file diff --git a/content/desktop/faqs/general.md b/content/desktop/faqs/general.md index 0fe1178f2f..f950682410 100644 --- a/content/desktop/faqs/general.md +++ b/content/desktop/faqs/general.md @@ -1,12 +1,12 @@ --- description: Frequently asked questions for all platforms keywords: desktop, mac, windows, faqs -redirect_from: +title: General FAQs for Desktop +aliases: - /mackit/faqs/ - /docker-for-mac/faqs/ - /docker-for-windows/faqs/ - /desktop/faqs/ -title: General FAQs for Desktop --- ### What are the system requirements for Docker Desktop? @@ -27,13 +27,13 @@ By default, Docker Desktop is installed at the following location: ### Do I need to pay to use Docker Desktop? -Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open-source projects. Otherwise, it requires a paid subscription for professional use. Paid subscriptions are also required for government entities. When downloading and installing Docker Desktop, you are asked to agree to the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){: target="_blank" rel="noopener" class="_"}. +Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open-source projects. Otherwise, it requires a paid subscription for professional use. Paid subscriptions are also required for government entities. When downloading and installing Docker Desktop, you are asked to agree to the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement). -Read the [Blog](https://www.docker.com/blog/updating-product-subscriptions/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"} and [FAQs](https://www.docker.com/pricing/faq){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"} to learn more. +Read the [Blog](https://www.docker.com/blog/updating-product-subscriptions/) and [FAQs](https://www.docker.com/pricing/faq) to learn more. ### Do I need to pay to create or share Docker Extensions? -No, the [Docker Extension SDK](https://www.npmjs.com/package/@docker/extension-api-client){:target="_blank" rel="noopener" class="_"} is licensed under the Apache 2.0 License and is free to use. Anyone can create new Docker Extensions and share them without constraints. +No, the [Docker Extension SDK](https://www.npmjs.com/package/@docker/extension-api-client) is licensed under the Apache 2.0 License and is free to use. Anyone can create new Docker Extensions and share them without constraints. ### Do I need to use a specific license when I create a Docker Extension? @@ -69,9 +69,9 @@ You can find information about diagnosing and troubleshooting common issues in t If you do not find a solution in troubleshooting, browse the Github repositories or create a new issue: -- [docker/for-mac](https://github.com/docker/for-mac/issues){: target="_blank" rel="noopener" class="_"} -- [docker/for-win](https://github.com/docker/for-win/issues){: target="_blank" rel="noopener" class="_"} -- [docker/for-linux](https://github.com/docker/for-linux/issues){: target="_blank" rel="noopener" class="_"} +- [docker/for-mac](https://github.com/docker/for-mac/issues) +- [docker/for-win](https://github.com/docker/for-win/issues) +- [docker/for-linux](https://github.com/docker/for-linux/issues) ### How do I connect to the remote Docker Engine API? @@ -79,7 +79,7 @@ To connect to the remote Engine API, you might need to provide the location of t Mac and Windows WSL 2 users can connect to the Docker Engine through a Unix socket: `unix:///var/run/docker.sock`. -If you are working with applications like [Apache Maven](https://maven.apache.org/){: target="_blank" rel="noopener" class="_"} +If you are working with applications like [Apache Maven](https://maven.apache.org/) that expect settings for `DOCKER_HOST` and `DOCKER_CERT_PATH` environment variables, specify these to connect to Docker instances through Unix sockets. @@ -126,4 +126,4 @@ After updating the `settings.json` file, close and restart Docker Desktop to app ### Can I run Docker Desktop on Virtualized hardware? -No, currently this is unsupported and against terms of use. +No, currently this is unsupported and against terms of use. \ No newline at end of file diff --git a/content/desktop/faqs/linuxfaqs.md b/content/desktop/faqs/linuxfaqs.md index 595d2d7838..c7bb128c8c 100644 --- a/content/desktop/faqs/linuxfaqs.md +++ b/content/desktop/faqs/linuxfaqs.md @@ -2,7 +2,7 @@ description: Frequently asked questions keywords: desktop, linux, faqs title: FAQs for Linux -redirect_from: +aliases: - /desktop/linux/space/ --- @@ -40,7 +40,7 @@ $ sudo systemctl disable docker docker.socket containerd ``` #### How do I switch between Docker Desktop and Docker Engine -{: id="context" } +{ #context } The Docker CLI can be used to interact with multiple Docker Engines. For example, you can use the same Docker CLI to control a local Docker Engine and to control @@ -103,17 +103,17 @@ Docker Desktop for Linux runs a Virtual Machine (VM) for the following reasons: Container image vulnerabilities pose a security risk for the host environment. There is a large number of unofficial images that are not guaranteed to be verified for known vulnerabilities. Malicious users can push images to public registries and use different methods to trick users into pulling and running them. The VM approach mitigates this threat as any malware that gains root privileges is restricted to the VM environment without access to the host. - Why not run rootless Docker? Although this has the benefit of superficially limiting access to the root user so everything looks safer in "top", it allows unprivileged users to gain `CAP_SYS_ADMIN` in their own user namespace and access kernel APIs which are not expecting to be used by unprivileged users, resulting in [vulnerabilities](https://www.openwall.com/lists/oss-security/2022/01/18/7){: target="_blank" rel="noopener" class="_"}. + Why not run rootless Docker? Although this has the benefit of superficially limiting access to the root user so everything looks safer in "top", it allows unprivileged users to gain `CAP_SYS_ADMIN` in their own user namespace and access kernel APIs which are not expecting to be used by unprivileged users, resulting in [vulnerabilities](https://www.openwall.com/lists/oss-security/2022/01/18/7). 4. **To provide the benefits of feature parity and enhanced security, with minimal impact on performance** - The VM utilized by DD4L uses [`virtiofs`](https://virtio-fs.gitlab.io){:target="_blank" rel="noopener" class="_"}, a shared file system that allows virtual machines to access a directory tree located on the host. Our internal benchmarking shows that with the right resource allocation to the VM, near native file system performance can be achieved with virtiofs. + The VM utilized by DD4L uses [`virtiofs`](https://virtio-fs.gitlab.io), a shared file system that allows virtual machines to access a directory tree located on the host. Our internal benchmarking shows that with the right resource allocation to the VM, near native file system performance can be achieved with virtiofs. As such, we have adjusted the default memory available to the VM in DD4L. You can tweak this setting to your specific needs by using the **Memory** slider within the **Settings** > **Resources** tab of Docker Desktop. ### How do I enable file sharing? -Docker Desktop for Linux uses [virtiofs](https://virtio-fs.gitlab.io/){:target="_blank" rel="noopener"}{:target="_blank" rel="noopener"} as the +Docker Desktop for Linux uses [virtiofs](https://virtio-fs.gitlab.io/) as the default (and currently only) mechanism to enable file sharing between the host and Docker Desktop VM. In order not to require elevated privileges, without unnecessarily restricting operations on the shared files, Docker Desktop runs @@ -252,4 +252,4 @@ To reduce the maximum size of the disk image file: 3. Click **Apply & Restart**. -When you reduce the maximum size, the current disk image file is deleted, and therefore, all containers and images will be lost. +When you reduce the maximum size, the current disk image file is deleted, and therefore, all containers and images will be lost. \ No newline at end of file diff --git a/content/desktop/faqs/macfaqs.md b/content/desktop/faqs/macfaqs.md index a20c665a78..ccf679f69c 100644 --- a/content/desktop/faqs/macfaqs.md +++ b/content/desktop/faqs/macfaqs.md @@ -2,7 +2,7 @@ description: Frequently asked questions keywords: desktop, mac, faqs title: FAQs for Mac -redirect_from: +aliases: - /desktop/mac/space/ - /docker-for-mac/space/ --- @@ -155,7 +155,7 @@ certificates](#directory-structures-for-certificates). > take effect. For a complete explanation of how to do this, see the blog post [Adding Self-signed Registry Certs to Docker & Docker Desktop for -Mac](https://blog.container-solutions.com/adding-self-signed-registry-certs-docker-mac){:target="_blank" rel="noopener" class="_"}. +Mac](https://blog.container-solutions.com/adding-self-signed-registry-certs-docker-mac). #### Add client certificates @@ -224,10 +224,9 @@ installed both in Bash and Zsh. #### Bash Bash has [built-in support for -completion](https://www.debian-administration.org/article/316/An_introduction_to_bash_completion_part_1){:target="_blank" -class="_"} To activate completion for Docker commands, these files need to be +completion](https://www.debian-administration.org/article/316/An_introduction_to_bash_completion_part_1) To activate completion for Docker commands, these files need to be copied or symlinked to your `bash_completion.d/` directory. For example, if you -installed bash via [Homebrew](https://brew.sh){:target="_blank" rel="noopener" class="_"}: +installed bash via [Homebrew](https://brew.sh): ```bash etc=/Applications/Docker.app/Contents/Resources/etc @@ -252,10 +251,10 @@ fi #### Zsh In Zsh, the [completion -system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html){:target="_blank" rel="nooopener" class="_"} +system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html) takes care of things. To activate completion for Docker commands, these files need to be copied or symlinked to your Zsh `site-functions/` -directory. For example, if you installed Zsh via [Homebrew](https://brew.sh){:target="_blank" rel="nooopener" class="_"}: +directory. For example, if you installed Zsh via [Homebrew](https://brew.sh): ```bash etc=/Applications/Docker.app/Contents/Resources/etc @@ -266,8 +265,7 @@ ln -s $etc/docker-compose.zsh-completion /usr/local/share/zsh/site-functions/_do #### Fish-Shell Fish-shell also supports tab completion [completion -system](https://fishshell.com/docs/current/#tab-completion){:target="_blank" -class="_"}. To activate completion for Docker commands, +system](https://fishshell.com/docs/current/#tab-completion). To activate completion for Docker commands, these files need to be copied or symlinked to your Fish-shell `completions/` directory. diff --git a/content/desktop/faqs/releases.md b/content/desktop/faqs/releases.md index 7cc4b89bba..4a95b31917 100644 --- a/content/desktop/faqs/releases.md +++ b/content/desktop/faqs/releases.md @@ -26,5 +26,4 @@ Sometimes we may roll out a new version gradually over a few days. Therefore, if ### Where can I find information about Stable and Edge releases? -Starting with Docker Desktop 3.0.0, Stable and Edge releases are combined into a single, cumulative release stream for all users. - +Starting with Docker Desktop 3.0.0, Stable and Edge releases are combined into a single, cumulative release stream for all users. \ No newline at end of file diff --git a/content/desktop/faqs/windowsfaqs.md b/content/desktop/faqs/windowsfaqs.md index 8c8d2f42f0..3cf458bb64 100644 --- a/content/desktop/faqs/windowsfaqs.md +++ b/content/desktop/faqs/windowsfaqs.md @@ -6,7 +6,7 @@ title: FAQs for Windows ### Can I use VirtualBox alongside Docker Desktop? -Yes, you can run VirtualBox along with Docker Desktop if you have enabled the [Windows Hypervisor Platform](https://docs.microsoft.com/en-us/virtualization/api/){: target="_blank" rel="noopener" class="_"} feature on your machine. +Yes, you can run VirtualBox along with Docker Desktop if you have enabled the [Windows Hypervisor Platform](https://docs.microsoft.com/en-us/virtualization/api/) feature on your machine. ### Why is Windows 10 or Windows 11 required? @@ -14,7 +14,7 @@ Docker Desktop uses the Windows Hyper-V features. While older Windows versions h ### Can I install Docker Desktop on Windows 10 Home? -If you are running Windows 10 Home (starting with version 1903), you can install [Docker Desktop for Windows](https://hub.docker.com/editions/community/docker-ce-desktop-windows/){: target="_blank" rel="noopener" class="_"} with the [WSL 2 backend](../wsl/index.md). +If you are running Windows 10 Home (starting with version 1903), you can install [Docker Desktop for Windows](https://hub.docker.com/editions/community/docker-ce-desktop-windows/) with the [WSL 2 backend](../wsl/index.md). ### Can I run Docker Desktop on Windows Server? @@ -24,7 +24,7 @@ No, running Docker Desktop on Windows Server is not supported. You can install a native Windows binary which allows you to develop and run Windows containers without Docker Desktop. For more information, see the tutorial about running Windows containers on Windows Server in -[Getting Started with Windows Containers](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md){: target="_blank" rel="noopener" class="_"}. +[Getting Started with Windows Containers](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md). ### Why do I see the `Docker Desktop Access Denied` error message when I try to start Docker Desktop? @@ -44,7 +44,7 @@ Desktop. For more information, see [Docker Desktop fails to start when anti-viru Docker Desktop does not enable you to control (`chmod`) the Unix-style permissions on [shared volumes](../settings/windows.md#file-sharing) for deployed containers, but rather sets permissions to a default value of -[0777](https://chmodcommand.com/chmod-0777/){: target="_blank" rel="noopener" class="_"} +[0777](https://chmodcommand.com/chmod-0777/) (`read`, `write`, `execute` permissions for `user` and for `group`) which is not configurable. @@ -55,12 +55,12 @@ For workarounds and to learn more, see Docker Desktop supports two types of symlinks: Windows native symlinks and symlinks created inside a container. -The Windows native symlinks are visible within the containers as symlinks, whereas symlinks created inside a container are represented as [mfsymlinks](https://wiki.samba.org/index.php/UNIX_Extensions#Minshall.2BFrench_symlinks){:target="_blank" rel="noopener" class="_"}. These are regular Windows files with a special metadata. Therefore the symlinks created inside a container appear as symlinks inside the container, but not on the host. +The Windows native symlinks are visible within the containers as symlinks, whereas symlinks created inside a container are represented as [mfsymlinks](https://wiki.samba.org/index.php/UNIX_Extensions#Minshall.2BFrench_symlinks). These are regular Windows files with a special metadata. Therefore the symlinks created inside a container appear as symlinks inside the container, but not on the host. ### File sharing with Kubernetes and WSL 2 Docker Desktop mounts the Windows host filesystem under `/run/desktop` inside the container running Kubernetes. -See the [Stack Overflow post](https://stackoverflow.com/questions/67746843/clear-persistent-volume-from-a-kubernetes-cluster-running-on-docker-desktop/69273405#69273){:target="_blank" rel="noopener" class="_"} for an example of how to configure a Kubernetes Persistent Volume to represent directories on the host. +See the [Stack Overflow post](https://stackoverflow.com/questions/67746843/clear-persistent-volume-from-a-kubernetes-cluster-running-on-docker-desktop/69273405#69273) for an example of how to configure a Kubernetes Persistent Volume to represent directories on the host. ### How do I add custom CA certificates? @@ -109,15 +109,15 @@ containers, or select **Switch to Linux containers** to use Linux containers For more information on Windows containers, refer to the following documentation: -- Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index){:target="_blank" rel="noopener" class="_"}. +- Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index). -- [Build and Run Your First Windows Server Container (Blog Post)](https://blog.docker.com/2016/09/build-your-first-docker-windows-server-container/){:target="_blank" rel="noopener" class="_"} +- [Build and Run Your First Windows Server Container (Blog Post)](https://blog.docker.com/2016/09/build-your-first-docker-windows-server-container/) gives a quick tour of how to build and run native Docker Windows containers on Windows 10 and Windows Server 2016 evaluation releases. -- [Getting Started with Windows Containers (Lab)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md){:target="_blank" rel="noopener" class="_"} - shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/){:target="_blank" rel="noopener" class="_"} +- [Getting Started with Windows Containers (Lab)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md) + shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/) application with Windows containers. The MusicStore is a standard .NET application and, - [forked here to use containers](https://github.com/friism/MusicStore){:target="_blank" rel="noopener" class="_"}, is a good example of a multi-container application. + [forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application. - To understand how to connect to Windows containers from the local host, see [I want to connect to a container from Windows](../networking.md#i-want-to-connect-to-a-container-from-the-host) @@ -134,4 +134,4 @@ If you set proxies or daemon configuration in Windows containers mode, these apply only on Windows containers. If you switch back to Linux containers, proxies and daemon configurations return to what you had set for Linux containers. Your Windows container settings are retained and become available -again when you switch back. +again when you switch back. \ No newline at end of file diff --git a/content/desktop/feedback.md b/content/desktop/feedback.md index f5b75fbae1..0bd81b1197 100644 --- a/content/desktop/feedback.md +++ b/content/desktop/feedback.md @@ -1,6 +1,7 @@ --- description: Find a way to provide feedback that's right for you -keywords: Feedback, Docker Desktop, Linux, Mac, Windows, Dev Environments, Extensions, Community forum, bugs, problems, issues +keywords: Feedback, Docker Desktop, Linux, Mac, Windows, Dev Environments, Extensions, + Community forum, bugs, problems, issues title: Give feedback --- @@ -16,24 +17,24 @@ To get help from the community, review current user topics, join or start a discussion, sign in to the appropriate Docker forums: - [Docker Desktop for Mac -forum](https://forums.docker.com/c/docker-for-mac){:target="_blank" rel="noopener" class="_"} -- [Docker Desktop for Windows forum](https://forums.docker.com/c/docker-for-windows){:target="_blank" rel="noopener" class="_"} -- [Docker Desktop for Linux forum](https://forums.docker.com/c/docker-desktop-for-linux/60){:target="_blank" rel="noopener" class="_"} +forum](https://forums.docker.com/c/docker-for-mac) +- [Docker Desktop for Windows forum](https://forums.docker.com/c/docker-for-windows) +- [Docker Desktop for Linux forum](https://forums.docker.com/c/docker-desktop-for-linux/60) #### Report bugs or problems on GitHub To report bugs or problems, visit: - [Docker Desktop for Mac issues on -GitHub](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"} -- [Docker Desktop for Windows issues on GitHub](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"} +GitHub](https://github.com/docker/for-mac/issues) +- [Docker Desktop for Windows issues on GitHub](https://github.com/docker/for-win/issues) - [Docker Desktop for Linux issues on -GitHub](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"} -- [Dev Environments issues on Github](https://github.com/docker/dev-environments/issues){:target="_blank" rel="noopener" class="_"} -- [Docker Extensions issues on GitHub](https://github.com/docker/extensions-sdk/issues){:target="_blank" rel="noopener" class="_"} +GitHub](https://github.com/docker/desktop-linux/issues) +- [Dev Environments issues on Github](https://github.com/docker/dev-environments/issues) +- [Docker Extensions issues on GitHub](https://github.com/docker/extensions-sdk/issues) #### Feedback via Community Slack channels -You can also provide feedback through the following [Docker Community Slack](https://www.docker.com/community/){:target="_blank" rel="noopener" class="_"} channels: +You can also provide feedback through the following [Docker Community Slack](https://www.docker.com/community/) channels: - #docker-desktop-mac - #docker-desktop-windows diff --git a/content/desktop/get-started.md b/content/desktop/get-started.md index b95d73a778..c364c30bda 100644 --- a/content/desktop/get-started.md +++ b/content/desktop/get-started.md @@ -1,8 +1,10 @@ --- -description: Explore the Learning center and understand the benefits of signing in to Docker Desktop -keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual, learning center, guide, sign in +description: Explore the Learning center and understand the benefits of signing in + to Docker Desktop +keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual, + learning center, guide, sign in title: Sign in to Docker Desktop -redirect_from: +aliases: - /desktop/linux/ - /desktop/linux/index/ - /desktop/mac/ @@ -43,7 +45,7 @@ In large enterprises where admin access is restricted, administrators can [Confi ### Credentials management for Linux users -Docker Desktop relies on [`pass`](https://www.passwordstore.org/){: target="_blank" rel="noopener" class="_"} to store credentials in gpg2-encrypted files. +Docker Desktop relies on [`pass`](https://www.passwordstore.org/) to store credentials in gpg2-encrypted files. Before signing in to Docker Hub from the Docker Dashboard or the Docker menu, you must initialize `pass`. Docker Desktop displays a warning if you've not initialized `pass`. @@ -101,4 +103,4 @@ docker.io/molly/privateimage:latest - [Explore Docker Desktop](use-desktop/index.md) and its features. - Change your Docker Desktop settings -- [Browse common FAQs](faqs/general.md) +- [Browse common FAQs](faqs/general.md) \ No newline at end of file diff --git a/content/desktop/hardened-desktop/_index.md b/content/desktop/hardened-desktop/_index.md index 4c668cc953..b448b724ad 100644 --- a/content/desktop/hardened-desktop/_index.md +++ b/content/desktop/hardened-desktop/_index.md @@ -1,8 +1,11 @@ --- title: Overview of Hardened Docker Desktop description: Overview of what Hardened Docker Desktop is and its key features -keywords: security, hardened desktop, enhanced container isolation, registry access management, settings management root access, admins, docker desktop, image access management +keywords: security, hardened desktop, enhanced container isolation, registry access + management, settings management root access, admins, docker desktop, image access + management --- + >Note > >Hardened Docker Desktop is available to Docker Business customers only. @@ -66,4 +69,4 @@ Docker plans to continue adding more security enhancements to the Hardened Docke

Control the images developers can pull from Docker Hub.

- + \ No newline at end of file diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md b/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md index b238477296..ea43d1449a 100644 --- a/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md +++ b/content/desktop/hardened-desktop/enhanced-container-isolation/_index.md @@ -1,5 +1,6 @@ --- -description: Enhanced Container Isolation - benefits, why use it, how it differs to Docker rootless, who it is for +description: Enhanced Container Isolation - benefits, why use it, how it differs to + Docker rootless, who it is for keywords: containers, rootless, security, sysbox, runtime title: What is Enhanced Container Isolation? --- @@ -57,7 +58,7 @@ For more information on how Enhanced Container Isolation work, see [How does it >**Important** > >Enhanced Container Isolation does not protect Kubernetes pods. For more information on known limitations and workarounds, see [FAQs and known issues](faq.md). -{: .important} +{ .important } ### What host OSes / platforms is Enhanced Container Isolation supported on? @@ -85,7 +86,7 @@ To enable Enhanced Container Isolation as a developer: >**Important** > >Enhanced Container Isolation does not protect containers created prior to enabling ECI. For more information on known limitations and workarounds, see [FAQs and known issues](faq.md). -{: .important} +{ .important } #### As an admin @@ -113,7 +114,7 @@ For this to take effect: >Important > >Selecting **Restart** from the Docker menu isn't enough as it only restarts some components of Docker Desktop. - {: .important} + { .important } ### What do users see when this setting is enforced by an admin? @@ -152,7 +153,7 @@ This means that the root user in the container (0) is in fact the root user in t Since Enhanced Container Isolation [uses the Sysbox container runtime](how-eci-works.md) embedded in the Docker Desktop Linux VM, another way to determine if a container is running with Enhanced Container Isolation is by using `docker inspect`: {% highlight liquid %} -docker inspect --format={% raw %}'{{.HostConfig.Runtime}}'{% endraw %} my_container +docker inspect --format='{{.HostConfig.Runtime}}' my_container {% endhighlight %} It outputs: @@ -161,4 +162,4 @@ It outputs: sysbox-runc ``` -Without Enhanced Container Isolation, `docker inspect` outputs `runc`, which is the standard OCI runtime. +Without Enhanced Container Isolation, `docker inspect` outputs `runc`, which is the standard OCI runtime. \ No newline at end of file diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/faq.md b/content/desktop/hardened-desktop/enhanced-container-isolation/faq.md index 1bebe9448a..9e1b077481 100644 --- a/content/desktop/hardened-desktop/enhanced-container-isolation/faq.md +++ b/content/desktop/hardened-desktop/enhanced-container-isolation/faq.md @@ -1,5 +1,5 @@ --- -title: FAQs +title: FAQs description: Frequently asked questions for Enhanced Container Isolation keywords: enhanced container isolation, security, faq, sysbox, Docker Desktop toc_max: 2 @@ -82,4 +82,4 @@ See [How does it work](how-eci-works.md#enhanced-container-isolation-vs-docker-u ### How is ECI different from Rootless Docker? -See [How does it work](how-eci-works.md#enhanced-container-isolation-vs-rootless-docker) +See [How does it work](how-eci-works.md#enhanced-container-isolation-vs-rootless-docker) \ No newline at end of file diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/features-benefits.md b/content/desktop/hardened-desktop/enhanced-container-isolation/features-benefits.md index 25078bfee1..4635230060 100644 --- a/content/desktop/hardened-desktop/enhanced-container-isolation/features-benefits.md +++ b/content/desktop/hardened-desktop/enhanced-container-isolation/features-benefits.md @@ -1,12 +1,13 @@ --- description: The benefits of enhanced container isolation title: Key features and benefits -keywords: set up, enhanced container isolation, rootless, security, features, Docker Desktop +keywords: set up, enhanced container isolation, rootless, security, features, Docker + Desktop --- ### Linux User Namespace on all containers -With Enhanced Container Isolation, all user containers leverage the [Linux user-namespace](https://man7.org/linux/man-pages/man7/user_namespaces.7.html){:target="_blank" rel="noopener" class="_"} +With Enhanced Container Isolation, all user containers leverage the [Linux user-namespace](https://man7.org/linux/man-pages/man7/user_namespaces.7.html) for extra isolation. This means that the root user in the container maps to an unprivileged user in the Docker Desktop Linux VM. @@ -290,4 +291,4 @@ across the containers when programming the corresponding Linux kernel setting. This has the advantage of enabling container workloads that would otherwise require truly privileged containers to access such non-namespaced kernel resources to run with Enhanced Container Isolation enabled, thereby improving -security. +security. \ No newline at end of file diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md b/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md index 45c5a0cbf4..00a327dc16 100644 --- a/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md +++ b/content/desktop/hardened-desktop/enhanced-container-isolation/how-eci-works.md @@ -9,7 +9,7 @@ keywords: set up, enhanced container isolation, rootless, security > Enhanced Container Isolation is available to Docker Business customers only. Enhanced Container Isolation hardens container isolation using the [Sysbox -container runtime](https://github.com/nestybox/sysbox){:target="_blank" rel="noopener" class="_"}. Sysbox is a fork of the +container runtime](https://github.com/nestybox/sysbox). Sysbox is a fork of the standard OCI runc runtime that was modified to enhance container isolation and workloads. For more details see [Under the hood](#under-the-hood). @@ -91,4 +91,4 @@ and creates a stronger boundary between the containers and the Docker Engine. Enhanced Container Isolation is meant to ensure containers launched with Docker Desktop can't easily breach the Docker Desktop Linux VM and therefore modify -security settings within it. +security settings within it. \ No newline at end of file diff --git a/content/desktop/hardened-desktop/enhanced-container-isolation/limitations.md b/content/desktop/hardened-desktop/enhanced-container-isolation/limitations.md index 3398b985f7..8a9d3b4d64 100644 --- a/content/desktop/hardened-desktop/enhanced-container-isolation/limitations.md +++ b/content/desktop/hardened-desktop/enhanced-container-isolation/limitations.md @@ -81,4 +81,4 @@ that same container in production, through the standard OCI `runc` runtime. However in some cases, typically when running advanced or privileged workloads in containers, users may experience some differences. In particular, the container -may run with ECI but not with `runc`, or vice-versa. +may run with ECI but not with `runc`, or vice-versa. \ No newline at end of file diff --git a/content/desktop/hardened-desktop/image-access-management.md b/content/desktop/hardened-desktop/image-access-management.md index c339e152c4..478f5e5bb6 100644 --- a/content/desktop/hardened-desktop/image-access-management.md +++ b/content/desktop/hardened-desktop/image-access-management.md @@ -4,4 +4,4 @@ keywords: image, access, management title: Image Access Management --- -{% include admin-image-access.md product="hub" %} \ No newline at end of file +{{% admin-image-access product="hub" %}} \ No newline at end of file diff --git a/content/desktop/hardened-desktop/registry-access-management.md b/content/desktop/hardened-desktop/registry-access-management.md index 2bf0b50832..5b1440c325 100644 --- a/content/desktop/hardened-desktop/registry-access-management.md +++ b/content/desktop/hardened-desktop/registry-access-management.md @@ -1,9 +1,10 @@ --- description: What Registry Access Management is and how to use it -keywords: registry access management, Hardened Docker Desktop, Docker Desktop, images, Docker Hub +keywords: registry access management, Hardened Docker Desktop, Docker Desktop, images, + Docker Hub title: Registry Access Management -redirect_from: +aliases: - /docker-hub/registry-access-management/ --- -{% include admin-registry-access.md product="hub" %} \ No newline at end of file +{{% admin-registry-access product="hub" %}} \ No newline at end of file diff --git a/content/desktop/hardened-desktop/settings-management/_index.md b/content/desktop/hardened-desktop/settings-management/_index.md index 4ef8ab902a..b5335f4459 100644 --- a/content/desktop/hardened-desktop/settings-management/_index.md +++ b/content/desktop/hardened-desktop/settings-management/_index.md @@ -1,8 +1,10 @@ --- -description: Understand how Settings Management works, who it is for, and what the benefits are +description: Understand how Settings Management works, who it is for, and what the + benefits are keywords: Settings Management, rootless, docker desktop, hardened desktop title: What is Settings Management? --- + >**Note** > >Settings Management is available to Docker Business customers only. @@ -56,4 +58,4 @@ Docker doesn't automatically mandate that developers re-launch and re-authentica Any settings that are enforced, are grayed out in Docker Desktop and the user is unable to edit them, either via the Docker Desktop UI, CLI, or the `settings.json` file. In addition, if Enhanced Container Isolation is enforced, users can't use privileged containers or similar techniques to modify enforced settings within the Docker Desktop Linux VM, for example, reconfigure proxy and networking of reconfigure Docker Engine. -![Proxy settings grayed out](/assets/images/grayed-setting.png){:width="350px"} +![Proxy settings grayed out](/assets/images/grayed-setting.png) \ No newline at end of file diff --git a/content/desktop/hardened-desktop/settings-management/configure.md b/content/desktop/hardened-desktop/settings-management/configure.md index 69a41c7027..95430dc794 100644 --- a/content/desktop/hardened-desktop/settings-management/configure.md +++ b/content/desktop/hardened-desktop/settings-management/configure.md @@ -141,11 +141,11 @@ For settings to take effect: >**Important** > >Selecting **Restart** from the Docker menu isn't enough as it only restarts some components of Docker Desktop. - {: .important} + { .important } Docker doesn't automatically mandate that developers re-launch and sign in once a change has been made so as not to disrupt your developers' workflow. In Docker Desktop, developers see the relevant settings grayed out and the message **Locked by your administrator**. -![Proxy settings grayed out with Settings Management](/assets/images/grayed-setting.png){:width="350px"} +![Proxy settings grayed out with Settings Management](/assets/images/grayed-setting.png) \ No newline at end of file diff --git a/content/desktop/install/archlinux.md b/content/desktop/install/archlinux.md index 9fcabceac5..e71f2e7854 100644 --- a/content/desktop/install/archlinux.md +++ b/content/desktop/install/archlinux.md @@ -1,14 +1,16 @@ --- -description: Instructions for installing Docker Desktop Arch package. Mostly meant for hackers who want to try out Docker Desktop on a variety of Arch-based distributions. -keywords: Arch Linux, install, uninstall, upgrade, update, linux, desktop, docker desktop, docker desktop for linux, dd4l +description: Instructions for installing Docker Desktop Arch package. Mostly meant + for hackers who want to try out Docker Desktop on a variety of Arch-based distributions. +keywords: Arch Linux, install, uninstall, upgrade, update, linux, desktop, docker + desktop, docker desktop for linux, dd4l title: Install Docker Desktop on Arch-based distributions -redirect_from: - - /desktop/linux/install/archlinux/ +aliases: +- /desktop/linux/install/archlinux/ --- This topic discusses installation of Docker Desktop from an [Arch package](https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-x86_64.pkg.tar.zst) that Docker provides in addition to the supported platforms. Docker has not tested or verified the installation. -[Arch package (experimental)](https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-x86_64.pkg.tar.zst?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64){: .button .primary-btn } +{{< button text="Arch package (experimental)" url="https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-x86_64.pkg.tar.zst?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64" >}} _For checksums, see [Release notes](../release-notes.md)_ @@ -39,10 +41,10 @@ $ sudo pacman -S gnome-terminal ## Launch Docker Desktop -{% include desktop-linux-launch.md %} +{{< include "desktop-linux-launch.md" >}} ## Next steps - Take a look at the [Get started](../../get-started/index.md) training modules to learn how to build an image and run it as a containerized application. - [Explore Docker Desktop](../use-desktop/index.md) and all its features. -- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. +- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. \ No newline at end of file diff --git a/content/desktop/install/debian.md b/content/desktop/install/debian.md index 712e5dfec6..56329c9abc 100644 --- a/content/desktop/install/debian.md +++ b/content/desktop/install/debian.md @@ -1,15 +1,16 @@ --- description: Instructions for installing Docker Desktop on Debian -keywords: debian, install, uninstall, upgrade, update, linux, desktop, docker desktop, docker desktop for linux, dd4l +keywords: debian, install, uninstall, upgrade, update, linux, desktop, docker desktop, + docker desktop for linux, dd4l title: Install Docker Desktop on Debian toc_max: 4 -redirect_from: - - /desktop/linux/install/debian/ +aliases: +- /desktop/linux/install/debian/ --- This page contains information on how to install, launch, and upgrade Docker Desktop on a Debian distribution. -[DEB package](https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-amd64.deb?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64){: .button .primary-btn } +{{< button text="DEB package" url="https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-amd64.deb?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64" >}} _For checksums, see [Release notes](../release-notes.md)_ @@ -37,7 +38,7 @@ To install Docker Desktop successfully, you must: > > If you have installed the Docker Desktop for Linux tech preview or beta version, you need to remove all files that were generated by those packages (eg. `~/.config/systemd/user/docker-desktop.service`, `~/.local/share/systemd/user/docker-desktop.service`). -- For a Gnome Desktop environment, you must also install AppIndicator and KStatusNotifierItem [Gnome extensions](https://extensions.gnome.org/extension/615/appindicator-support/){:target="_blank" rel="noopener" class="_"}. +- For a Gnome Desktop environment, you must also install AppIndicator and KStatusNotifierItem [Gnome extensions](https://extensions.gnome.org/extension/615/appindicator-support/). - For non-Gnome Desktop environments, `gnome-terminal` must be installed: @@ -80,7 +81,7 @@ The post-install script: ## Launch Docker Desktop -{% include desktop-linux-launch.md %} +{{< include "desktop-linux-launch.md" >}} ## Upgrade Docker Desktop @@ -95,4 +96,4 @@ $ sudo apt-get install ./docker-desktop--.deb - Take a look at the [Get started](../../get-started/index.md) training modules to learn how to build an image and run it as a containerized application. - [Explore Docker Desktop](../use-desktop/index.md) and all its features. -- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. +- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. \ No newline at end of file diff --git a/content/desktop/install/fedora.md b/content/desktop/install/fedora.md index e0b20d5112..a51214c8f0 100644 --- a/content/desktop/install/fedora.md +++ b/content/desktop/install/fedora.md @@ -1,15 +1,16 @@ --- description: Instructions for installing Docker Desktop on Fedora -keywords: fedora, rpm, update install, uninstall, upgrade, update, linux, desktop, docker desktop, docker desktop for linux, dd4l +keywords: fedora, rpm, update install, uninstall, upgrade, update, linux, desktop, + docker desktop, docker desktop for linux, dd4l title: Install Docker Desktop on Fedora toc_max: 4 -redirect_from: - - /desktop/linux/install/fedora/ +aliases: +- /desktop/linux/install/fedora/ --- This page contains information on how to install, launch and upgrade Docker Desktop on a Fedora distribution. -[RPM package](https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-x86_64.rpm?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64){: .button .primary-btn } +{{< button text="RPM package" url="https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-x86_64.rpm?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64" >}} ## Prerequisites @@ -18,7 +19,7 @@ To install Docker Desktop successfully, you must: - Meet the [system requirements](linux-install.md#system-requirements). - Have a 64-bit version of either Fedora 36 or Fedora 37. -Additionally, for a Gnome Desktop environment you must install AppIndicator and KStatusNotifierItem [Gnome extensions](https://extensions.gnome.org/extension/615/appindicator-support/){:target="_blank" rel="noopener" class="_"}. +Additionally, for a Gnome Desktop environment you must install AppIndicator and KStatusNotifierItem [Gnome extensions](https://extensions.gnome.org/extension/615/appindicator-support/). For non-Gnome Desktop environments, `gnome-terminal` must be installed: @@ -51,7 +52,7 @@ The post-install script: ## Launch Docker Desktop -{% include desktop-linux-launch.md %} +{{< include "desktop-linux-launch.md" >}} ## Upgrade Docker Desktop @@ -67,4 +68,4 @@ $ sudo dnf install ./docker-desktop--.rpm - Take a look at the [Get started](../../get-started/index.md) training modules to learn how to build an image and run it as a containerized application. - [Explore Docker Desktop](../use-desktop/index.md) and all its features. -- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. +- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. \ No newline at end of file diff --git a/content/desktop/install/linux-install.md b/content/desktop/install/linux-install.md index d74eb79b4b..5ecd44fd4c 100644 --- a/content/desktop/install/linux-install.md +++ b/content/desktop/install/linux-install.md @@ -1,9 +1,14 @@ --- -description: Install Docker on Linux with ease using our step-by-step installation guide covering system requirements, supported platforms, and where to go next. -keywords: linux, docker linux install, docker linux, linux docker installation, docker for linux, docker desktop for linux, installing docker on linux, docker download linux, how to install docker on linux +description: Install Docker on Linux with ease using our step-by-step installation + guide covering system requirements, supported platforms, and where to go next. +keywords: linux, docker linux install, docker linux, linux docker installation, docker + for linux, docker desktop for linux, installing docker on linux, docker download + linux, how to install docker on linux title: Install Docker Desktop on Linux -redirect_from: +aliases: - /desktop/linux/install/ +'yes': '![yes](/assets/images/green-check.svg){: .inline style="height: 14px; margin: + 0 auto"}' --- This page contains information about general system requirements, supported platforms, and instructions on how to install Docker Desktop for Linux. @@ -15,7 +20,7 @@ This page contains information about general system requirements, supported plat >This means images and containers deployed on the Linux Docker Engine (before installation) are not available in Docker Desktop for Linux. > >For more information see [What is the difference between Docker Desktop for Linux and Docker Engine](../faqs/linuxfaqs.md#what-is-the-difference-between-docker-desktop-for-linux-and-docker-engine). -{: .important} +{ .important } ## Supported platforms @@ -23,14 +28,13 @@ Docker provides `.deb` and `.rpm` packages from the following Linux distribution and architectures: -{% assign yes = '![yes](/assets/images/green-check.svg){: .inline style="height: 14px; margin: 0 auto"}' %} | Platform | x86_64 / amd64 | |:------------------------|:-----------------------| -| [Ubuntu](ubuntu.md) | [{{ yes }}](ubuntu.md) | -| [Debian](debian.md) | [{{ yes }}](debian.md) | -| [Fedora](fedora.md) | [{{ yes }}](fedora.md) | +| [Ubuntu](ubuntu.md) | [{{% param "yes" %}}](ubuntu.md) | +| [Debian](debian.md) | [{{% param "yes" %}}](debian.md) | +| [Fedora](fedora.md) | [{{% param "yes" %}}](fedora.md) | An experimental package is available for [Arch](archlinux.md)-based distributions. Docker has not tested or verified the installation. @@ -46,7 +50,7 @@ To install Docker Desktop successfully, your Linux host must meet the following - QEMU must be version 5.2 or later. We recommend upgrading to the latest version. - systemd init system. - Gnome, KDE, or MATE Desktop environment. - - For many Linux distros, the Gnome environment does not support tray icons. To add support for tray icons, you need to install a Gnome extension. For example, [AppIndicator](https://extensions.gnome.org/extension/615/appindicator-support/){:target="_blank" rel="noopener" class="_"}. + - For many Linux distros, the Gnome environment does not support tray icons. To add support for tray icons, you need to install a Gnome extension. For example, [AppIndicator](https://extensions.gnome.org/extension/615/appindicator-support/). - At least 4 GB of RAM. - Enable configuring ID mapping in user namespaces, see [File sharing](../faqs/linuxfaqs.md#how-do-i-enable-file-sharing). - Recommended: [Initialize `pass`](../get-started.md#credentials-management-for-linux-users) for credentials management. @@ -60,7 +64,7 @@ Docker Desktop for Linux runs a Virtual Machine (VM). For more information on wh ### KVM virtualization support -Docker Desktop runs a VM that requires [KVM support](https://www.linux-kvm.org){:target="_blank" rel="noopener" class="_"}. +Docker Desktop runs a VM that requires [KVM support](https://www.linux-kvm.org). The `kvm` module should load automatically if the host has virtualization support. To load the module manually, run: @@ -119,7 +123,7 @@ Sign out and sign back in so that your group membership is re-evaluated. > subscription. Make sure you meet the system requirements outlined earlier and follow the distro-specific prerequisites. -{: .important} +{ .important } 1. Download the correct package for your Linux distribution and install it with the corresponding package manager. - [Install on Debian](debian.md) @@ -131,13 +135,13 @@ Make sure you meet the system requirements outlined earlier and follow the distr ![Docker app in Applications](images/docker-app-in-apps.png) -3. Select **Docker Desktop** to start Docker.
The Docker menu (![whale menu](images/whale-x.svg){: .inline}) displays the Docker Subscription Service Agreement. +3. Select **Docker Desktop** to start Docker.
The Docker menu ({{< inline-image src="images/whale-x.svg" alt="whale menu" >}}) displays the Docker Subscription Service Agreement. 4. Select **Accept** to continue. Docker Desktop starts after you accept the terms. Note that Docker Desktop will not run if you do not agree to the terms. You can choose to accept the terms at a later date by opening Docker Desktop. - For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){:target="_blank" rel="noopener" class="_"}. We recommend that you also read the [FAQs](https://www.docker.com/pricing/faq){: target="_blank" rel="noopener" class="_" id="dkr_docs_desktop_install_btl"}. + For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement). We recommend that you also read the [FAQs](https://www.docker.com/pricing/faq). ## Where to go next @@ -148,4 +152,4 @@ Make sure you meet the system requirements outlined earlier and follow the distr - [FAQs](../faqs/general.md) provide answers to frequently asked questions. - [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases. - [Back up and restore data](../backup-and-restore.md) provides instructions - on backing up and restoring data related to Docker. + on backing up and restoring data related to Docker. \ No newline at end of file diff --git a/content/desktop/install/mac-install.md b/content/desktop/install/mac-install.md index 17934b629a..7ee97a93a5 100644 --- a/content/desktop/install/mac-install.md +++ b/content/desktop/install/mac-install.md @@ -1,8 +1,11 @@ --- -description: Install Docker for Mac to get started. This guide covers system requirements, where to download, and instructions on how to install and update. -keywords: docker for mac, install docker macos, docker mac, docker mac install, docker install macos, install docker on mac, install docker macbook, docker desktop for mac, how to install docker on mac, setup docker on mac +description: Install Docker for Mac to get started. This guide covers system requirements, + where to download, and instructions on how to install and update. +keywords: docker for mac, install docker macos, docker mac, docker mac install, docker + install macos, install docker on mac, install docker macbook, docker desktop for + mac, how to install docker on mac, setup docker on mac title: Install Docker Desktop on Mac -redirect_from: +aliases: - /desktop/mac/install/ - /docker-for-mac/install/ - /engine/installation/mac/ @@ -14,8 +17,8 @@ redirect_from: This page contains download URLs, information about system requirements, and instructions on how to install Docker Desktop for Mac. -[Docker Desktop for Mac with Intel chip](https://desktop.docker.com/mac/main/amd64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-amd64){: .button .primary-btn } -[Docker Desktop for Mac with Apple silicon](https://desktop.docker.com/mac/main/arm64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-arm64){: .button .primary-btn } +{{< button text="Docker Desktop for Mac with Intel chip" url="https://desktop.docker.com/mac/main/amd64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-amd64" >}} +{{< button text="Docker Desktop for Mac with Apple silicon" url="https://desktop.docker.com/mac/main/arm64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-arm64" >}} *For checksums, see [Release notes](../release-notes.md).* @@ -61,15 +64,15 @@ This page contains download URLs, information about system requirements, and ins 2. Double-click `Docker.app` in the **Applications** folder to start Docker. -3. The Docker menu (![whale menu](images/whale-x.svg){: .inline}) displays the Docker Subscription Service Agreement. +3. The Docker menu ({{< inline-image src="images/whale-x.svg" alt="whale menu" >}}) displays the Docker Subscription Service Agreement. - {% include desktop-license-update.md %} + {{< include "desktop-license-update.md" >}} 4. Select **Accept** to continue. Note that Docker Desktop won't run if you do not agree to the terms. You can choose to accept the terms at a later date by opening Docker Desktop. - For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){: target="_blank" rel="noopener" class="_" }. We recommend that you also read the [FAQs](https://www.docker.com/pricing/faq){: target="_blank" rel="noopener" class="_"}. + For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement). We recommend that you also read the [FAQs](https://www.docker.com/pricing/faq). 5. From the installation window, select either: - **Use recommended settings (Requires password)**. This let's Docker Desktop automatically set the necessary configuration settings. - **Use advanced settings**. You can then set the location of the Docker CLI tools either in the system or user directory, enable the default Docker socket, and enable privileged port mapping. See [Settings](../settings/mac.md#advanced), for more information and how to set the location of the Docker CLI tools. @@ -88,9 +91,9 @@ $ sudo hdiutil detach /Volumes/Docker As macOS typically performs security checks the first time an application is used, the `install` command can take several minutes to run. The `install` command accepts the following flags: -- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){: target="_blank" rel="noopener" class="_"} now, rather than requiring it to be accepted when the application is first run. +- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run. - `--allowed-org=`: Requires the user to sign in and be part of the specified Docker Hub organization when running the application -- `--user=`: Performs the privileged configurations once during installation. This removes the need for the user to grant root privileges on first run. For more information, see [Privileged helper permission requirements](../mac/permission-requirements.md#permission-requirements){: target="_blank" rel="noopener" class="_"}. To find the username, enter `ls /Users` in the CLI. +- `--user=`: Performs the privileged configurations once during installation. This removes the need for the user to grant root privileges on first run. For more information, see [Privileged helper permission requirements](../mac/permission-requirements.md#permission-requirements). To find the username, enter `ls /Users` in the CLI. - `--admin-settings`: Automatically creates an `admin-settings.json` file which is used by administrators to control certain Docker Desktop settings on client machines within their organization. For more information, see [Settings Management](../hardened-desktop/settings-management/index.md). - It must be used together with the `--allowed-org=` flag. - For example: @@ -109,4 +112,4 @@ The `install` command accepts the following flags: - [FAQs](../faqs/general.md) provide answers to frequently asked questions. - [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases. - [Back up and restore data](../backup-and-restore.md) provides instructions - on backing up and restoring data related to Docker. + on backing up and restoring data related to Docker. \ No newline at end of file diff --git a/content/desktop/install/ubuntu.md b/content/desktop/install/ubuntu.md index 2537cf7404..b6547c2f86 100644 --- a/content/desktop/install/ubuntu.md +++ b/content/desktop/install/ubuntu.md @@ -1,15 +1,19 @@ --- -description: Learn how to install, launch and upgrade Docker Desktop on Ubuntu. This quick guide will cover prerequisites, installation methods, and more. -keywords: install docker ubuntu, ubuntu install docker, install docker on ubuntu, docker install ubuntu, how to install docker on ubuntu, ubuntu docker install, docker installation on ubuntu, docker ubuntu install, docker installing ubuntu, installing docker on ubuntu, docker desktop for ubuntu +description: Learn how to install, launch and upgrade Docker Desktop on Ubuntu. This + quick guide will cover prerequisites, installation methods, and more. +keywords: install docker ubuntu, ubuntu install docker, install docker on ubuntu, + docker install ubuntu, how to install docker on ubuntu, ubuntu docker install, docker + installation on ubuntu, docker ubuntu install, docker installing ubuntu, installing + docker on ubuntu, docker desktop for ubuntu title: Install Docker Desktop on Ubuntu toc_max: 4 -redirect_from: - - /desktop/linux/install/ubuntu/ +aliases: +- /desktop/linux/install/ubuntu/ --- This page contains information on how to install, launch and upgrade Docker Desktop on an Ubuntu distribution. -[DEB package](https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-amd64.deb?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64){: .button .primary-btn } +{{< button text="DEB package" url="https://desktop.docker.com/linux/main/amd64/docker-desktop-4.22.0-amd64.deb?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64" >}} _For checksums, see [Release notes](../release-notes.md)_ @@ -77,7 +81,7 @@ The post-install script: ## Launch Docker Desktop -{% include desktop-linux-launch.md %} +{{< include "desktop-linux-launch.md" >}} ## Upgrade Docker Desktop @@ -92,4 +96,4 @@ $ sudo apt-get install ./docker-desktop--.deb - Take a look at the [Get started](../../get-started/index.md) training modules to learn how to build an image and run it as a containerized application. - [Explore Docker Desktop](../use-desktop/index.md) and all its features. -- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. +- Review the topics in [Develop with Docker](../../develop/index.md) to learn how to build new applications using Docker. \ No newline at end of file diff --git a/content/desktop/install/windows-install.md b/content/desktop/install/windows-install.md index c0e4f86669..5a4f3c1325 100644 --- a/content/desktop/install/windows-install.md +++ b/content/desktop/install/windows-install.md @@ -1,8 +1,11 @@ --- -description: Get started with Docker for Windows. This guide covers system requirements, where to download, and instructions on how to install and update. -keywords: docker for windows, docker windows, docker desktop for windows, docker on windows, install docker windows, install docker on windows, docker windows 10, docker run on windows, installing docker for windows +description: Get started with Docker for Windows. This guide covers system requirements, + where to download, and instructions on how to install and update. +keywords: docker for windows, docker windows, docker desktop for windows, docker on + windows, install docker windows, install docker on windows, docker windows 10, docker + run on windows, installing docker for windows title: Install Docker Desktop on Windows -redirect_from: +aliases: - /desktop/windows/install/ - /docker-ee-for-windows/install/ - /docker-for-windows/install-windows-home/ @@ -17,7 +20,7 @@ redirect_from: This page contains the download URL, information about system requirements, and instructions on how to install Docker Desktop for Windows. -[Docker Desktop for Windows](https://desktop.docker.com/win/main/amd64/Docker%20Desktop%20Installer.exe){: .button .primary-btn } +{{< button text="Docker Desktop for Windows" url="https://desktop.docker.com/win/main/amd64/Docker%20Desktop%20Installer.exe" >}} _For checksums, see [Release notes](../release-notes.md)_ @@ -36,11 +39,11 @@ _For checksums, see [Release notes](../release-notes.md)_ - Windows 11 64-bit: Home or Pro version 21H2 or higher, or Enterprise or Education version 21H2 or higher. - Windows 10 64-bit: Home or Pro 21H2 (build 19044) or higher, or Enterprise or Education 21H2 (build 19044) or higher. - Turn on the WSL 2 feature on Windows. For detailed instructions, refer to the - [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10){: target="_blank" rel="noopener" class="_"}. + [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10). - The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 or Windows 11: - - 64-bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation){: target="_blank" rel="noopener" class="_"} + - 64-bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation) - 4GB system RAM - BIOS-level hardware virtualization support must be turned on in the BIOS settings. For more information, see @@ -58,7 +61,7 @@ _For checksums, see [Release notes](../release-notes.md)_ - The following hardware prerequisites are required to successfully run Client Hyper-V on Windows 10: - - 64 bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation){: target="_blank" rel="noopener" class="_"} + - 64 bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation) - 4GB system RAM - BIOS-level hardware virtualization support must be turned on in the BIOS settings. For more information, see @@ -69,7 +72,7 @@ _For checksums, see [Release notes](../release-notes.md)_ > **Note** > -> Docker only supports Docker Desktop on Windows for those versions of Windows that are still within [Microsoft’s servicing timeline](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet){:target="_blank" rel="noopener" class="_"}. +> Docker only supports Docker Desktop on Windows for those versions of Windows that are still within [Microsoft’s servicing timeline](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet). Containers and images created with Docker Desktop are shared between all user accounts on machines where it is installed. This is because all Windows @@ -89,7 +92,7 @@ Looking for information on using Windows containers? provides a tutorial on how to set up and run Windows containers on Windows 10, Windows Server 2016 and Windows Server 2019. It shows you how to use a MusicStore application with Windows containers. - Docker Container Platform for Windows [articles and blog - posts](https://www.docker.com/microsoft/){:target="_blank" rel="noopener" class="_"} on the Docker website. + posts](https://www.docker.com/microsoft/) on the Docker website. > **Note** > @@ -135,7 +138,7 @@ start /w "" "Docker Desktop Installer.exe" install The `install` command accepts the following flags: - `--quiet`: Suppresses information output when running the installer -- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){: target="_blank" rel="noopener" class="_"} now, rather than requiring it to be accepted when the application is first run +- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run - `--no-windows-containers`: Disables the Windows containers integration - `--allowed-org=`: Requires the user to sign in and be part of the specified Docker Hub organization when running the application - `--backend=`: Selects the default backend to use for Docker Desktop, `hyper-v`, `windows` or `wsl-2` (default) @@ -164,17 +167,17 @@ Docker Desktop does not start automatically after installation. To start Docker 1. Search for Docker, and select **Docker Desktop** in the search results. - ![Search for Docker app](images/docker-app-search.png){:width="300px"} + ![Search for Docker app](images/docker-app-search.png) -2. The Docker menu (![whale menu](images/whale-x.svg){: .inline}) displays the Docker Subscription Service Agreement. +2. The Docker menu ({{< inline-image src="images/whale-x.svg" alt="whale menu" >}}) displays the Docker Subscription Service Agreement. - {% include desktop-license-update.md %} + {{< include "desktop-license-update.md" >}} 3. Select **Accept** to continue. Docker Desktop starts after you accept the terms. Note that Docker Desktop won't run if you do not agree to the terms. You can choose to accept the terms at a later date by opening Docker Desktop. - For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement/){:target="_blank" rel="noopener" class="_"}. We recommend that you also read the [FAQs](https://www.docker.com/pricing/faq){: target="\_blank" rel="noopener" class="*" id="dkr_docs_desktop_install_btl"}. + For more information, see [Docker Desktop Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement/). We recommend that you also read the [FAQs](https://www.docker.com/pricing/faq). ## Where to go next @@ -185,4 +188,4 @@ Docker Desktop does not start automatically after installation. To start Docker how to get support. - [FAQs](../faqs/general.md) provide answers to frequently asked questions. - [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases. -- [Back up and restore data](../backup-and-restore.md) provides instructions on backing up and restoring data related to Docker. +- [Back up and restore data](../backup-and-restore.md) provides instructions on backing up and restoring data related to Docker. \ No newline at end of file diff --git a/content/desktop/kubernetes.md b/content/desktop/kubernetes.md index 8e8f06a26b..ecfebabddf 100644 --- a/content/desktop/kubernetes.md +++ b/content/desktop/kubernetes.md @@ -2,7 +2,7 @@ description: See how you can deploy to Kubernetes on Docker Desktop keywords: deploy, kubernetes, kubectl, orchestration, Docker Desktop title: Deploy on Kubernetes with Docker Desktop -redirect_from: +aliases: - /docker-for-windows/kubernetes/ - /docker-for-mac/kubernetes/ --- @@ -40,7 +40,7 @@ at `/usr/local/bin/kubectl` on Mac and at `C:\Program Files\Docker\Docker\Resour variable, so you may need to type the full path of the command or add it to the `PATH`. -The kubectl binary is not automatically packaged with Docker Desktop for Linux. To install the kubectl command for Linux, see [Kubernetes documentation](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/){:target="_blank" rel="noopener" class="_"}. It should be installed at `/usr/local/bin/kubectl`. +The kubectl binary is not automatically packaged with Docker Desktop for Linux. To install the kubectl command for Linux, see [Kubernetes documentation](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/). It should be installed at `/usr/local/bin/kubectl`. If you have already installed `kubectl` and it is pointing to some other environment, such as `minikube` or a GKE cluster, ensure you change the context so that `kubectl` is pointing to `docker-desktop`: @@ -55,7 +55,7 @@ $ kubectl config use-context docker-desktop > Run the `kubectl` command in a CMD or PowerShell terminal, otherwise `kubectl config get-contexts` may return an empty result. > > If you are using a different terminal and this happens, you can try setting the `kubeconfig` environment variable to the location of the `.kube/config` file. -{: .tip} +{ .tip } If you installed `kubectl` using Homebrew, or by some other method, and experience conflicts, remove `/usr/local/bin/kubectl`. @@ -70,7 +70,7 @@ docker-desktop Ready master 3h v1.19.7 ``` For more information about `kubectl`, see the -[`kubectl` documentation](https://kubernetes.io/docs/reference/kubectl/overview/){:target="_blank" rel="noopener" class="_"}. +[`kubectl` documentation](https://kubernetes.io/docs/reference/kubectl/overview/). ## Turn off Kubernetes @@ -78,4 +78,4 @@ To turn off Kubernetes in Docker Desktop: 1. From the Docker Dashboard, select the **Settings** icon. 2. Select **Kubernetes** from the left sidebar. 3. Next to **Enable Kubernetes**, clear the checkbox -4. Select **Apply & Restart** to save the settings.This stops and removes Kubernetes containers, and also removes the `/usr/local/bin/kubectl` command. +4. Select **Apply & Restart** to save the settings.This stops and removes Kubernetes containers, and also removes the `/usr/local/bin/kubectl` command. \ No newline at end of file diff --git a/content/desktop/mac/permission-requirements.md b/content/desktop/mac/permission-requirements.md index f40fb2dcc3..a4b1ac398b 100644 --- a/content/desktop/mac/permission-requirements.md +++ b/content/desktop/mac/permission-requirements.md @@ -1,8 +1,9 @@ --- -description: Understand permission requirements for Docker Desktop for Mac and the differences between versions +description: Understand permission requirements for Docker Desktop for Mac and the + differences between versions keywords: Docker Desktop, mac, security, install, permissions title: Understand permission requirements for Docker Desktop on Mac -redirect_from: +aliases: - /docker-for-mac/privileged-helper/ - /desktop/mac/privileged-helper/ --- @@ -165,6 +166,4 @@ $ rm /Library/PrivilegedHelperTools/com.docker.vmnetd ## Containers running as root within the Linux VM -The Docker daemon and containers run in a lightweight Linux VM managed by Docker. This means that although containers run by default as `root`, this doesn't grant `root` access to the Mac host machine. The Linux VM serves as a security boundary and limits what resources can be accessed from the host. Any directories from the host bind mounted into Docker containers still retain their original permissions. - - +The Docker daemon and containers run in a lightweight Linux VM managed by Docker. This means that although containers run by default as `root`, this doesn't grant `root` access to the Mac host machine. The Linux VM serves as a security boundary and limits what resources can be accessed from the host. Any directories from the host bind mounted into Docker containers still retain their original permissions. \ No newline at end of file diff --git a/content/desktop/networking.md b/content/desktop/networking.md index 47a98d412a..9738ff10a8 100644 --- a/content/desktop/networking.md +++ b/content/desktop/networking.md @@ -2,7 +2,7 @@ description: Understand how networking works on Docker Desktop and see the known limitations keywords: networking, docker desktop, proxy, vpn, Linux, Mac, Windows title: Explore networking features on Docker Desktop -redirect_from: +aliases: - /desktop/linux/networking/ - /docker-for-mac/networking/ - /mackit/networking/ @@ -163,5 +163,4 @@ $ docker run -d -P --name webserver nginx ``` See the [run command](../engine/reference/commandline/run.md) for more details on -publish options used with `docker run`. - +publish options used with `docker run`. \ No newline at end of file diff --git a/content/desktop/previous-versions/2.x-mac.md b/content/desktop/previous-versions/2.x-mac.md index 23c25d831c..eabe8e4ea9 100644 --- a/content/desktop/previous-versions/2.x-mac.md +++ b/content/desktop/previous-versions/2.x-mac.md @@ -4,7 +4,7 @@ keywords: Docker Desktop for Mac 2.x release notes title: Docker Desktop for Mac 2.x release notes toc_min: 1 toc_max: 2 -redirect_from: /desktop/mac/release-notes/2.x/ +aliases: /desktop/mac/release-notes/2.x/ --- This page contains release notes for Docker Desktop for Mac 2.x. @@ -14,9 +14,9 @@ This page contains release notes for Docker Desktop for Mac 2.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/49550/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/49550/Docker.dmg) ### Upgrades @@ -31,9 +31,9 @@ This page contains release notes for Docker Desktop for Mac 2.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/49427/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/49427/Docker.dmg) Docker Desktop 2.5.0.0 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. @@ -44,7 +44,7 @@ Docker Desktop 2.5.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus ### Security -- Fixed local privilege escalation vulnerability caused by inadequate certificate checking. See [CVE-2021-3162](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3162){:target="_blank" rel="noopener" class="_"}. +- Fixed local privilege escalation vulnerability caused by inadequate certificate checking. See [CVE-2021-3162](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3162). ### Upgrades @@ -75,9 +75,9 @@ Docker Desktop 2.5.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/48506/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/48506/Docker.dmg) Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. @@ -126,9 +126,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/48029/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/48029/Docker.dmg) ### New @@ -154,9 +154,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/46911/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/46911/Docker.dmg) ### Upgrades @@ -176,9 +176,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/45519/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/45519/Docker.dmg) ### Upgrades @@ -194,9 +194,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/45183/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/45183/Docker.dmg) ### New @@ -230,9 +230,9 @@ Docker Desktop introduces a new onboarding tutorial upon first startup. The Quic > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/43884/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/43884/Docker.dmg) ### Bug fixes and minor changes @@ -243,9 +243,9 @@ Docker Desktop introduces a new onboarding tutorial upon first startup. The Quic > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/43472/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/43472/Docker.dmg) ### Upgrades @@ -261,9 +261,9 @@ Docker Desktop introduces a new onboarding tutorial upon first startup. The Quic > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/42716/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/42716/Docker.dmg) ### Upgrades @@ -275,9 +275,9 @@ Docker Desktop introduces a new onboarding tutorial upon first startup. The Quic > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/42247/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/42247/Docker.dmg) Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. @@ -328,9 +328,9 @@ Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/40693/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/40693/Docker.dmg) Docker Desktop 2.1.0.5 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this version. @@ -345,9 +345,9 @@ Docker Desktop 2.1.0.5 contains a Kubernetes upgrade. Note that your local Kuber > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/39773/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/39773/Docker.dmg) ### Upgrades @@ -366,9 +366,9 @@ Docker Desktop now enables you to sign into Docker Hub using two-factor authenti > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/38240/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/38240/Docker.dmg) ### Upgrades @@ -383,9 +383,9 @@ Docker Desktop now enables you to sign into Docker Hub using two-factor authenti > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/37877/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/37877/Docker.dmg) Docker Desktop 2.1.0.2 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this version. @@ -401,9 +401,9 @@ Docker Desktop 2.1.0.2 contains a Kubernetes upgrade. Note that your local Kuber > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/37199/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/37199/Docker.dmg) Note that you must sign in and create a Docker ID in order to download Docker Desktop. @@ -466,9 +466,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/31259/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/31259/Docker.dmg) * Upgrades - [Docker 18.09.2](https://github.com/docker/docker-ce/releases/tag/v18.09.2), fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736) @@ -477,9 +477,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/30215/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/30215/Docker.dmg) * Upgrades - [Docker 18.09.1](https://github.com/docker/docker-ce/releases/tag/v18.09.1) @@ -495,9 +495,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/29211/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/29211/Docker.dmg) * Upgrades - [Docker compose 1.23.2](https://github.com/docker/compose/releases/tag/1.23.2) @@ -506,9 +506,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/28905/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/28905/Docker.dmg) * Upgrades - [Docker 18.09.0](https://github.com/docker/docker-ce-packaging/releases/tag/v18.09.0) @@ -529,6 +529,4 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features. - VPNKit: Improved scalability of port forwarding. Related to [docker/for-mac#2841](https://github.com/docker/for-mac/issues/2841) - VPNKit: Limit the size of the UDP NAT table. This ensures port forwarding and regular TCP traffic continue even when running very chatty UDP protocols. - Ensure Kubernetes can be installed when using a non-default internal IP subnet. - - Fix panic in diagnose - -{% include eula-modal.html %} + - Fix panic in diagnose \ No newline at end of file diff --git a/content/desktop/previous-versions/2.x-windows.md b/content/desktop/previous-versions/2.x-windows.md index e879fdd55b..e256952969 100644 --- a/content/desktop/previous-versions/2.x-windows.md +++ b/content/desktop/previous-versions/2.x-windows.md @@ -4,7 +4,7 @@ keywords: Docker Desktop for Windows 2.x, release notes title: Docker for Windows 2.x release notes toc_min: 1 toc_max: 2 -redirect_from: /desktop/windows/release-notes/2.x/ +aliases: /desktop/windows/release-notes/2.x/ --- This page contains release notes for Docker Desktop for Windows 2.x. @@ -14,9 +14,9 @@ This page contains release notes for Docker Desktop for Windows 2.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/49550/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/49550/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -28,9 +28,9 @@ This page contains release notes for Docker Desktop for Windows 2.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/49427/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/49427/Docker%20Desktop%20Installer.exe) Docker Desktop 2.5.0.0 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. @@ -70,9 +70,9 @@ Docker Desktop 2.5.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/48506/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/48506/Docker%20Desktop%20Installer.exe) Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. @@ -144,9 +144,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/48029/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/48029/Docker%20Desktop%20Installer.exe) ### New @@ -172,9 +172,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/46911/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/46911/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -197,9 +197,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/45519/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/45519/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -224,9 +224,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/45183/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/45183/Docker%20Desktop%20Installer.exe) ### New @@ -297,9 +297,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/43884/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/43884/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -314,9 +314,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/43472/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/43472/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -349,9 +349,9 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/42716/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/42716/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -455,9 +455,9 @@ Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/40693/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/40693/Docker%20Desktop%20Installer.exe) Docker Desktop 2.1.0.5 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this version. @@ -472,9 +472,9 @@ Docker Desktop 2.1.0.5 contains a Kubernetes upgrade. Note that your local Kuber > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/39773/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/39773/Docker%20Desktop%20Installer.exe) Docker Desktop 2.1.0.4 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this version. @@ -494,9 +494,9 @@ Docker Desktop now enables you to sign into Docker Hub using two-factor authenti > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/38240/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/38240/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -507,9 +507,9 @@ Docker Desktop now enables you to sign into Docker Hub using two-factor authenti > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/37877/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/37877/Docker%20Desktop%20Installer.exe) Docker Desktop 2.1.0.2 contains a Kubernetes upgrade. Your local Kubernetes cluster will be reset after installing this version. @@ -525,9 +525,9 @@ Docker Desktop 2.1.0.2 contains a Kubernetes upgrade. Your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/37199/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/37199/Docker%20Desktop%20Installer.exe) Note that you must sign in and create a Docker ID in order to download Docker Desktop. @@ -596,9 +596,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features: > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/31259/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/31259/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.09.2](https://github.com/docker/docker-ce/releases/tag/v18.09.2), fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736) @@ -610,9 +610,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features: > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/30215/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/30215/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.09.1](https://github.com/docker/docker-ce/releases/tag/v18.09.1) @@ -630,9 +630,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features: > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/29211/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/29211/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker compose 1.23.2](https://github.com/docker/compose/releases/tag/1.23.2) @@ -644,9 +644,9 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features: > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/28905/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/28905/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.09.0](https://github.com/docker/docker-ce-packaging/releases/tag/v18.09.0) @@ -671,6 +671,4 @@ Docker Desktop Community 2.1.0.0 contains the following experimental features: - LCOW does not need --platform flag on multi-arch images any more - Disk size can now be ajusted from 32GiB to drive space. - Fix dns update too verbose in logs - - Fix panic in diagnose - -{% include eula-modal.html %} + - Fix panic in diagnose \ No newline at end of file diff --git a/content/desktop/previous-versions/3.x-mac.md b/content/desktop/previous-versions/3.x-mac.md index 21297b1741..2a77c62e8d 100644 --- a/content/desktop/previous-versions/3.x-mac.md +++ b/content/desktop/previous-versions/3.x-mac.md @@ -4,10 +4,10 @@ keywords: Docker Desktop for Mac 3.x release notes title: Docker Desktop for Mac 3.x release notes toc_min: 1 toc_max: 2 -redirect_from: - - /desktop/mac/previous-versions/ - - /docker-for-mac/previous-versions/ - - /desktop/mac/release-notes/3.x/ +aliases: +- /desktop/mac/previous-versions/ +- /docker-for-mac/previous-versions/ +- /desktop/mac/release-notes/3.x/ --- This page contains release notes for Docker Desktop for Mac 3.x. @@ -17,10 +17,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/67351/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/67351/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/67351/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/67351/Docker.dmg) ### New @@ -55,10 +55,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/66501/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/66501/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/66501/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/66501/Docker.dmg) ### New @@ -90,10 +90,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/66090/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/66090/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/66090/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/66090/Docker.dmg) ### New @@ -110,10 +110,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/66024/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/66024/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/66024/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/66024/Docker.dmg) ### New @@ -149,10 +149,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/65384/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/65384/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/65384/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/65384/Docker.dmg) ### New @@ -202,10 +202,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/64133/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/64133/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/64133/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/64133/Docker.dmg) ### Upgrades @@ -221,10 +221,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/63878/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/63878/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/63878/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/63878/Docker.dmg) ### Upgrades @@ -250,10 +250,10 @@ This page contains release notes for Docker Desktop for Mac 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/63152/Docker.dmg){: .accept-eula } | -> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/63152/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/63152/Docker.dmg) | +> [Mac with Apple chip](https://desktop.docker.com/mac/stable/arm64/63152/Docker.dmg) ### New @@ -278,9 +278,9 @@ Docker Desktop is now available for Apple silicon as well as Intel chips. This e > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/62916/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/62916/Docker.dmg) ### New @@ -320,9 +320,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/61853/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/61853/Docker.dmg) ### Bug fixes and minor changes @@ -336,9 +336,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/61626/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/61626/Docker.dmg) ### Upgrades @@ -353,9 +353,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/61504/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/amd64/61504/Docker.dmg) ### New @@ -401,9 +401,9 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/51484/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/51484/Docker.dmg) ### New @@ -424,9 +424,9 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/51218/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/51218/Docker.dmg) ### Upgrades @@ -446,9 +446,9 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/51017/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/51017/Docker.dmg) ### Bug fixes and minor changes @@ -464,9 +464,9 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/50996/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/50996/Docker.dmg) ### Bug fixes and minor changes @@ -484,9 +484,9 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/50773/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/50773/Docker.dmg) ### Bug fixes and minor changes @@ -503,9 +503,9 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/stable/50684/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/stable/50684/Docker.dmg) ### New @@ -516,8 +516,8 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y - Supports the following subcommands: `up`, `down`, `logs`, `build`, `pull`, `push`, `ls`, `ps` - Supports basic volumes, bind mounts, networks, and environment variables - Let us know your feedback by creating an issue in the [compose-cli](https://github.com/docker/compose-cli/issues){: target="blank" rel="noopener" class=“”} GitHub repository. -- [Docker Hub Tool v0.2.0](https://github.com/docker/roadmap/issues/117){: target="blank" rel="noopener" class=“”} + Let us know your feedback by creating an issue in the [compose-cli](https://github.com/docker/compose-cli/issues) GitHub repository. +- [Docker Hub Tool v0.2.0](https://github.com/docker/roadmap/issues/117) ### Upgrades @@ -539,6 +539,4 @@ Docker Desktop can sometimes fail to start after updating to version 3.2.0. If y ### Known issues - Building an image with BuildKit from a git URL fails when using the form `github.com/org/repo`. To work around this issue, use the form `git://github.com/org/repo`. -- Some DNS addresses fail to resolve within containers based on Alpine Linux 3.13. - -{% include eula-modal.html %} +- Some DNS addresses fail to resolve within containers based on Alpine Linux 3.13. \ No newline at end of file diff --git a/content/desktop/previous-versions/3.x-windows.md b/content/desktop/previous-versions/3.x-windows.md index 82dd907f69..7f0484d60a 100644 --- a/content/desktop/previous-versions/3.x-windows.md +++ b/content/desktop/previous-versions/3.x-windows.md @@ -4,10 +4,10 @@ keywords: Docker Desktop for Windows 3.x, release notes title: Docker for Windows 3.x release notes toc_min: 1 toc_max: 2 -redirect_from: - - /desktop/windows/previous-versions/ - - /docker-for-windows/previous-versions/ - - /desktop/windows/release-notes/3.x/ +aliases: +- /desktop/windows/previous-versions/ +- /docker-for-windows/previous-versions/ +- /desktop/windows/release-notes/3.x/ --- This page contains release notes for Docker Desktop for Windows 3.x. @@ -17,9 +17,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/67351/Docker Desktop Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/67351/Docker Desktop Installer.exe) ### New @@ -50,7 +50,7 @@ This page contains release notes for Docker Desktop for Windows 3.x. - Fixed slowness when adding multiple ports forwarding option. - Fixed bug where the WSL 2 synchonization code creates dangling symlinks if the WSL 2 home directory if it is the same as the Windows home directory. Fixes [docker/for-win#11668](https://github.com/docker/for-win/issues/11668). - Fixed `docker context ls` after upgrade from 3.5.x when the Linux WSL 2 home directory is the same as the Windows home directory. -- Fixed the permissions on `%PROGRAMDATA%\Docker` to avoid a potential Windows containers compromise. See [CVE-2021-37841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37841){:target="_blank" rel="noopener" class="_"}. Thanks to [Alessio Dalla Piazza](http://it.linkedin.com/in/alessiodallapiazza) for discovering the issue and to @kevpar for helpful discussion. +- Fixed the permissions on `%PROGRAMDATA%\Docker` to avoid a potential Windows containers compromise. See [CVE-2021-37841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37841). Thanks to [Alessio Dalla Piazza](http://it.linkedin.com/in/alessiodallapiazza) for discovering the issue and to @kevpar for helpful discussion. - Fixed bug where the Linux home directory under WSL 2 was set to the Windows home directory e.g. `/mnt/c/Users/...`. - Fixed bug where Desktop would fail to start if it could not parse CLI contexts. Fixes [docker/for-win#11601](https://github.com/docker/for-win/issues/11601). - Fixed an issue related to log display inside a container [docker/for-win#11251](https://github.com/docker/for-win/issues/11251). @@ -61,9 +61,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/66501/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/66501/Docker%20Desktop%20Installer.exe) ### New @@ -95,9 +95,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/66090/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/66090/Docker%20Desktop%20Installer.exe) ### New @@ -115,9 +115,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/66024/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/66024/Docker%20Desktop%20Installer.exe) ### New @@ -152,9 +152,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/65384/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/65384/Docker%20Desktop%20Installer.exe) ### New @@ -195,9 +195,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/64133/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/64133/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -213,9 +213,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/63878/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/63878/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -237,9 +237,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/63152/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/63152/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -253,9 +253,9 @@ This page contains release notes for Docker Desktop for Windows 3.x. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/62916/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/62916/Docker%20Desktop%20Installer.exe) ### New @@ -289,9 +289,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/61853/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/61853/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -304,9 +304,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/61626/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/61626/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -317,9 +317,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/amd64/61504/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/amd64/61504/Docker%20Desktop%20Installer.exe) ### New @@ -366,9 +366,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/51484/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/51484/Docker%20Desktop%20Installer.exe) ### New @@ -390,9 +390,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/51218/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/51218/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -407,9 +407,9 @@ For developers in IT managed environments, who don’t have administrative acces > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://desktop.docker.com/win/stable/50684/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [For Windows](https://desktop.docker.com/win/stable/50684/Docker%20Desktop%20Installer.exe) ### New @@ -420,8 +420,8 @@ For developers in IT managed environments, who don’t have administrative acces - Supports the following subcommands: `up`, `down`, `logs`, `build`, `pull`, `push`, `ls`, `ps` - Supports basic volumes, bind mounts, networks, and environment variables - Let us know your feedback by creating an issue in the [compose-cli](https://github.com/docker/compose-cli/issues){: target="blank" rel="noopener" class=“”} GitHub repository. -- [Docker Hub Tool v0.2.0](https://github.com/docker/roadmap/issues/117){: target="blank" rel="noopener" class=“”} + Let us know your feedback by creating an issue in the [compose-cli](https://github.com/docker/compose-cli/issues) GitHub repository. +- [Docker Hub Tool v0.2.0](https://github.com/docker/roadmap/issues/117) ### Upgrades @@ -438,6 +438,4 @@ For developers in IT managed environments, who don’t have administrative acces ### Known issues - Building an image with BuildKit from a git URL fails when using the form `github.com/org/repo`. To work around this issue, use the form `git://github.com/org/repo`. -- Some DNS addresses fail to resolve within containers based on Alpine Linux 3.13. - -{% include eula-modal.html %} +- Some DNS addresses fail to resolve within containers based on Alpine Linux 3.13. \ No newline at end of file diff --git a/content/desktop/previous-versions/archive-mac.md b/content/desktop/previous-versions/archive-mac.md index 872fa239c1..9690545667 100644 --- a/content/desktop/previous-versions/archive-mac.md +++ b/content/desktop/previous-versions/archive-mac.md @@ -4,8 +4,8 @@ keywords: Docker Desktop for Mac, release notes title: Release notes for previous versions toc_min: 1 toc_max: 2 -redirect_from: - - /desktop/mac/release-notes/archive/ +aliases: +- /desktop/mac/release-notes/archive/ --- This page contains release notes for older versions of Docker Desktop for Mac. @@ -16,9 +16,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/26764/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/26764/Docker.dmg) * Upgrades - [Docker 18.06.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.1-ce) @@ -30,9 +30,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/26399/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/26399/Docker.dmg) * Upgrades - [Docker 18.06.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.0-ce) @@ -65,9 +65,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/24312/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/24312/Docker.dmg) * Upgrades - [Docker 18.03.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.1-ce) @@ -81,9 +81,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/24245/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/24245/Docker.dmg) * Upgrades - [Docker 18.03.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.1-ce) @@ -97,9 +97,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/23751/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/23751/Docker.dmg) * Bug fixes and minor changes - Fix Upgrade straight from 17.09 versions where Docker for Mac cannot restart once the upgrade has been performed. Fixes [docker/for-mac#2739](https://github.com/docker/for-mac/issues/2739) @@ -108,9 +108,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/23608/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/23608/Docker.dmg) * Upgrades - [Docker 18.03.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce) @@ -140,9 +140,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/23011/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/23011/Docker.dmg) * Bug fixes and minor changes - Revert the default disk format to qcow2 for users running macOS 10.13 (High Sierra). There are confirmed reports of file corruption using the raw format which uses sparse files on APFS. Note this change only takes effect after a reset to factory defaults (from the Whale menu -> Preferences -> Reset). Related to [docker/for-mac#2625](https://github.com/docker/for-mac/issues/2625) @@ -152,9 +152,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/21805/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/21805/Docker.dmg) * Bug fixes and minor changes - Fix error during resize/create Docker.raw disk image in some cases. Fixes [docker/for-mac#2383](https://github.com/docker/for-mac/issues/2383), [docker/for-mac#2447](https://github.com/docker/for-mac/issues/2447), [docker/for-mac#2453], (https://github.com/docker/for-mac/issues/2453), [docker/for-mac#2420](https://github.com/docker/for-mac/issues/2420) @@ -169,9 +169,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/21698/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/21698/Docker.dmg) * Bug fixes and minor changes - Fix for `docker push` to an insecure registry. Fixes [docker/for-mac#2392](https://github.com/docker/for-mac/issues/2392) @@ -181,9 +181,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/21698/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/21698/Docker.dmg) * Upgrades - [Docker 17.12.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce) @@ -213,9 +213,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/21090/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/21090/Docker.dmg) * Upgrades - [Docker 17.09.1-ce](https://github.com/docker/docker-ce/releases/tag/v17.09.1-ce) @@ -229,9 +229,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/stable/19611/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/stable/19611/Docker.dmg) * Bug fix - Fix Docker For Mac unable to start in some cases : removed use of libgmp sometimes causing the vpnkit process to die. @@ -240,9 +240,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/19543/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/19543/Docker.dmg) * Bug fix - Do not show Toolbox migration assistant when there are existing Docker For Mac data. @@ -251,9 +251,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/19506/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/19506/Docker.dmg) * Upgrades - [Docker 17.09.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.09.0-ce) @@ -290,9 +290,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/19124/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/19124/Docker.dmg) * Upgrades - [Docker 17.06.2-ce](https://github.com/docker/docker-ce/releases/tag/v17.06.2-ce) @@ -302,9 +302,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/18950/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/18950/Docker.dmg) **Upgrades** - [Docker 17.06.1-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v17.06.1-ce-rc1) @@ -321,9 +321,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/18433/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/18433/Docker.dmg) **Upgrades** @@ -370,9 +370,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/17661/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/17661/Docker.dmg) **Upgrades** @@ -382,9 +382,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/16048/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/16048/Docker.dmg) **Upgrades** @@ -395,9 +395,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/15583/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/15583/Docker.dmg) **New** @@ -443,9 +443,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/15353/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/15353/Docker.dmg) **Upgrades** @@ -464,9 +464,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/15072/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/15072/Docker.dmg) **Upgrades** @@ -522,9 +522,9 @@ This page contains release notes for older versions of Docker Desktop for Mac. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/14777/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/14777/Docker.dmg) **Upgrades** @@ -539,9 +539,9 @@ We did not distribute a 1.12.4 stable release > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/13776/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/13776/Docker.dmg) **Upgrades** @@ -610,9 +610,9 @@ We did not distribute a 1.12.4 stable release > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/1.12.1.12133/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/1.12.1.12133/Docker.dmg) **New** @@ -694,9 +694,9 @@ We did not distribute a 1.12.4 stable release > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/11213/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/11213/Docker.dmg) This bug fix release contains osxfs improvements. The fixed issues may have been seen as failures with apt-get and npm in containers, missed inotify @@ -717,9 +717,9 @@ events or unexpected unmounts. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/stable/10871/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/stable/10871/Docker.dmg) * First stable release @@ -727,6 +727,4 @@ events or unexpected unmounts. * Docker 1.12.0 * Docker Machine 0.8.0 -* Docker Compose 1.8.0 - -{% include eula-modal.html %} +* Docker Compose 1.8.0 \ No newline at end of file diff --git a/content/desktop/previous-versions/archive-windows.md b/content/desktop/previous-versions/archive-windows.md index 041d32f690..d7fe1f3514 100644 --- a/content/desktop/previous-versions/archive-windows.md +++ b/content/desktop/previous-versions/archive-windows.md @@ -4,8 +4,8 @@ keywords: Docker Desktop for Windows, release notes title: Release notes for previous versions toc_min: 1 toc_max: 2 -redirect_from: - - /desktop/windows/release-notes/archive/ +aliases: +- /desktop/windows/release-notes/archive/ --- This page contains release notes for older versions of Docker Desktop for Windows. @@ -16,9 +16,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/19507/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/19507/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.06.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.1-ce) @@ -38,9 +38,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/19098/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/19098/Docker%20for%20Windows%20Installer.exe) * New - Renewed signing certificate. The installer may show a Windows Defender popup until the renewed certificate is allowlisted. Click "More info" to view the app is published by "Docker Inc" and run it. @@ -52,9 +52,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/19075/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/19075/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.06.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.0-ce) @@ -81,9 +81,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/17513/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/17513/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.1-ce) @@ -98,9 +98,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/17438/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/17438/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.1-ce) @@ -115,9 +115,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/16762/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/16762/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce) @@ -151,9 +151,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/15139/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/15139/Docker%20for%20Windows%20Installer.exe) * Bug fixes and minor changes - Fix linuxkit port-forwarder sometimes not being able to start. Fixes [docker/for-win#1506](https://github.com/docker/for-win/issues/1506) @@ -165,9 +165,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/15048/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/15048/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 17.12.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce) @@ -193,9 +193,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/14687/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/14687/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 17.09.1-ce](https://github.com/docker/docker-ce/releases/tag/v17.09.1-ce) @@ -214,9 +214,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/13620/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/13620/Docker%20for%20Windows%20Installer.exe) * Bug fixes - Fix Docker For Windows unable to start in some cases: removed use of libgmp sometimes causing the vpnkit process to die. @@ -225,9 +225,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/13529/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/13529/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 17.09.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.09.0-ce) @@ -268,9 +268,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/13194/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/13194/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 17.06.2-ce](https://github.com/docker/docker-ce/releases/tag/v17.06.2-ce) @@ -280,9 +280,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/13025/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/13025/Docker%20for%20Windows%20Installer.exe) **Upgrades** @@ -299,9 +299,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/12627/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/12627/Docker%20for%20Windows%20Installer.exe) **Upgrades** @@ -343,9 +343,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/12058/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/12058/Docker%20for%20Windows%20Installer.exe) **Upgrades** @@ -355,9 +355,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/10743/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/10743/Docker%20for%20Windows%20Installer.exe) **New** @@ -394,9 +394,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/1.13.1.10072/InstallDocker.msi){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/1.13.1.10072/InstallDocker.msi) **Upgrades** @@ -415,9 +415,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/1.13.0.9795/InstallDocker.msi){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/1.13.0.9795/InstallDocker.msi) **Upgrades** @@ -462,9 +462,9 @@ This page contains release notes for older versions of Docker Desktop for Window > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/1.12.5.9503/InstallDocker.msi){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/1.12.5.9503/InstallDocker.msi) **Upgrades** @@ -479,9 +479,9 @@ We did not distribute a 1.12.4 stable release > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/1.12.3.8488/InstallDocker.msi){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/1.12.3.8488/InstallDocker.msi) **New** @@ -566,9 +566,9 @@ We did not distribute a 1.12.4 stable release > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/1.12.1.7135/InstallDocker.msi){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/1.12.1.7135/InstallDocker.msi) >**Important Note**: > @@ -665,9 +665,9 @@ We did not distribute a 1.12.4 stable release > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [For Windows](https://download.docker.com/win/stable/1.12.0.5968/InstallDocker.msi){: .accept-eula } +> [For Windows](https://download.docker.com/win/stable/1.12.0.5968/InstallDocker.msi) * First stable release @@ -675,6 +675,4 @@ We did not distribute a 1.12.4 stable release * Docker 1.12.0 * Docker Machine 0.8.0 -* Docker Compose 1.8.0 - -{% include eula-modal.html %} +* Docker Compose 1.8.0 \ No newline at end of file diff --git a/content/desktop/previous-versions/edge-releases-mac.md b/content/desktop/previous-versions/edge-releases-mac.md index d87be90ea7..c3d5751be0 100644 --- a/content/desktop/previous-versions/edge-releases-mac.md +++ b/content/desktop/previous-versions/edge-releases-mac.md @@ -4,8 +4,8 @@ keywords: Docker Desktop for Mac, edge, release notes title: Docker Desktop for Mac Edge release notes toc_min: 1 toc_max: 2 -redirect_from: - - /desktop/mac/release-notes/edge-releases/ +aliases: +- /desktop/mac/release-notes/edge-releases/ --- This page contains information about Docker Desktop Edge releases. Edge releases give you early access to our newest features. Note that some of the features may be experimental, and some of them may not ever reach the Stable release. @@ -18,9 +18,9 @@ For Docker Desktop system requirements, see > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://desktop.docker.com/mac/edge/50534/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://desktop.docker.com/mac/edge/50534/Docker.dmg) ### Upgrades @@ -40,9 +40,9 @@ For Docker Desktop system requirements, see > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/50261/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/50261/Docker.dmg) ### Upgrades @@ -58,9 +58,9 @@ For Docker Desktop system requirements, see > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/50165/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/50165/Docker.dmg) ### New @@ -78,9 +78,9 @@ For Docker Desktop system requirements, see > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/49923/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/49923/Docker.dmg) This release contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing Docker Desktop. @@ -105,9 +105,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/48975/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/48975/Docker.dmg) ### New @@ -139,9 +139,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/48583/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/48583/Docker.dmg) ### Upgrades @@ -161,9 +161,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/48173/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/48173/Docker.dmg) ### New @@ -195,9 +195,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/47792/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/47792/Docker.dmg) ### Upgrades @@ -212,9 +212,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/47622/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/47622/Docker.dmg) ### New @@ -243,9 +243,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/47376/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/47376/Docker.dmg) ### New @@ -277,9 +277,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/46980/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/46980/Docker.dmg) ### New @@ -289,8 +289,8 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for ### Upgrades -- [Docker ECS integration v1.0.0-beta.4](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.4){: target="_blank" rel="noopener" class="_”} -- [Kubernetes 1.18.6](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.6){: target="_blank" rel="noopener" class="_”} +- [Docker ECS integration v1.0.0-beta.4](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.4) +- [Kubernetes 1.18.6](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.6) ### Bug fixes and minor changes @@ -302,14 +302,14 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://desktop.docker.com/mac/edge/46784/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://desktop.docker.com/mac/edge/46784/Docker.dmg) ### Upgrades -- [Docker ECS integration v1.0.0-beta.2](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.2){: target="_blank" rel="noopener" class="_”} -- [Docker ACI integration 0.1.10](https://github.com/docker/aci-integration-beta/releases/tag/v0.1.10){: target="_blank" rel="noopener" class="_”} +- [Docker ECS integration v1.0.0-beta.2](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.2) +- [Docker ACI integration 0.1.10](https://github.com/docker/aci-integration-beta/releases/tag/v0.1.10) ### Bug fixes and minor changes @@ -321,9 +321,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/46574/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/46574/Docker.dmg) ### Upgrades @@ -343,9 +343,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/46268/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/46268/Docker.dmg) ### Upgrades @@ -370,15 +370,15 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://desktop.docker.com/mac/edge/45408/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://desktop.docker.com/mac/edge/45408/Docker.dmg) ### New -Docker Desktop introduces a directory caching mechanism to greatly improve disk performance in containers. This feature uses [mutagen.io](https://mutagen.io/){: target="_blank" rel="noopener" class="_"} to sync files between the host and the containers and benefits from native disk performance. +Docker Desktop introduces a directory caching mechanism to greatly improve disk performance in containers. This feature uses [mutagen.io](https://mutagen.io/) to sync files between the host and the containers and benefits from native disk performance. -We appreciate you trying out an early version of the Mutagen file sync feature. Please let us know your feedback by creating an issue in the [Docker Desktop for Mac GitHub](https://github.com/docker/for-mac/issues){: target="_blank" rel="noopener" class="_"} repository with the `Mutagen` label. +We appreciate you trying out an early version of the Mutagen file sync feature. Please let us know your feedback by creating an issue in the [Docker Desktop for Mac GitHub](https://github.com/docker/for-mac/issues) repository with the `Mutagen` label. ### Upgrades @@ -395,9 +395,9 @@ We appreciate you trying out an early version of the Mutagen file sync feature. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/44875/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/44875/Docker.dmg) ### Bug fixes and minor changes @@ -408,9 +408,9 @@ We appreciate you trying out an early version of the Mutagen file sync feature. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/44472/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/44472/Docker.dmg) ### Upgrades @@ -435,9 +435,9 @@ We appreciate you trying out an early version of the Mutagen file sync feature. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/43965/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/43965/Docker.dmg) ### Upgrades @@ -471,9 +471,9 @@ We appreciate you trying out an early version of the Mutagen file sync feature. > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/43066/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/43066/Docker.dmg) This release contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing Docker Desktop. @@ -492,9 +492,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/42746/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/42746/Docker.dmg) ### Upgrades @@ -506,9 +506,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/41561/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/41561/Docker.dmg) > **Note:** Docker Desktop Edge 2.1.7.0 is the release candidate for the upcoming major Stable release. Please help us test this version before the wider release and report any issues in the [docker/for-mac](https://github.com/docker/for-mac/issues) GitHub repository. @@ -532,9 +532,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Mac with Intel chip](https://download.docker.com/mac/edge/40807/Docker.dmg){: .accept-eula } +> [Mac with Intel chip](https://download.docker.com/mac/edge/40807/Docker.dmg) ### Upgrades @@ -555,9 +555,9 @@ Added the ability to start and stop Compose-based applications and view combined > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/40323/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/40323/Docker.dmg) This release contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installation. @@ -588,9 +588,9 @@ Fixed an issue that caused VMs running on older hardware with macOS Catalina to > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/39357/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/39357/Docker.dmg) ### Upgrades @@ -611,9 +611,9 @@ Fixed an issue that caused VMs running on older hardware with macOS Catalina to > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/38275/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/38275/Docker.dmg) ### Bug fixes and minor changes @@ -627,9 +627,9 @@ Fixed an issue that caused VMs running on older hardware with macOS Catalina to > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/38030/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/38030/Docker.dmg) #### Upgrades @@ -650,9 +650,9 @@ Fixed an issue that caused VMs running on older hardware with macOS Catalina to > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/37260/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/37260/Docker.dmg) #### Upgrades @@ -671,9 +671,9 @@ Fixed an issue that caused VMs running on older hardware with macOS Catalina to > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/36792/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/36792/Docker.dmg) This release contains Kubernetes security improvements. Note that your local Kubernetes PKI and cluster will be reset after installation. @@ -703,9 +703,9 @@ This release contains Kubernetes security improvements. Note that your local Kub > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/35318/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/35318/Docker.dmg) This is the Edge channel, which gives you early access to our newest features. Be aware that some of them may be experimental, and some of them may not ever reach the Stable release. @@ -735,9 +735,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/34207/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/34207/Docker.dmg) * Bug fixes and minor changes - Upgrade QEMU from 2.8.0 to 3.1.0 to fix an emulation issue when building and running Java applications on Arm64 devices. @@ -746,9 +746,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/33772/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/33772/Docker.dmg) * Upgrades - [Docker 19.03.0-beta3](https://github.com/docker/docker-ce/releases/tag/v19.03.0-beta3) @@ -782,9 +782,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/31778/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/31778/Docker.dmg) * Upgrades - [Docker 18.09.3](https://github.com/docker/docker-ce/releases/tag/v18.09.3) @@ -797,9 +797,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/31274/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/31274/Docker.dmg) * Upgrades - [Docker 18.09.2](https://github.com/docker/docker-ce/releases/tag/v18.09.2), fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736) @@ -808,9 +808,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/30972/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/30972/Docker.dmg) * Upgrades - [Docker Compose 1.24.0-rc1](https://github.com/docker/compose/releases/tag/1.24.0-rc1) @@ -829,9 +829,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/30090/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/30090/Docker.dmg) * Upgrades - [Docker 18.09.1](https://github.com/docker/docker-ce/releases/tag/v18.09.1) @@ -855,9 +855,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/29268/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/29268/Docker.dmg) * Upgrades - [Docker compose 1.23.2](https://github.com/docker/compose/releases/tag/1.23.2) @@ -867,9 +867,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/28700/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/28700/Docker.dmg) * Upgrades - [Docker 18.09.0](https://github.com/docker/docker-ce-packaging/releases/tag/v18.09.0) @@ -886,9 +886,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/27117/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/27117/Docker.dmg) * Upgrades - [Docker 18.09.0-ce-beta1](https://github.com/docker/docker-ce/releases/tag/v18.09.0-ce-beta1) @@ -908,9 +908,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/26766/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/26766/Docker.dmg) * Upgrades - [Docker 18.06.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.1-ce) @@ -922,9 +922,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/26398/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/26398/Docker.dmg) * Upgrades - [Docker 18.06.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.0-ce) @@ -937,9 +937,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/26342/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/26342/Docker.dmg) * Upgrades - [Docker 18.06.0-ce-rc3](https://github.com/docker/docker-ce/releases/tag/v18.06.0-ce-rc3) @@ -961,9 +961,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/25042/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/25042/Docker.dmg) * Upgrades - [LinuxKit v0.4](https://github.com/linuxkit/linuxkit/releases/tag/v0.4) @@ -982,9 +982,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/24545/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/24545/Docker.dmg) * Upgrades - [Docker 18.05.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.05.0-ce) @@ -1006,9 +1006,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/24246/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/24246/Docker.dmg) * Upgrades - [Docker 18.05.0-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v18.05.0-ce-rc1) @@ -1024,9 +1024,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23965/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23965/Docker.dmg) * Upgrades - [Docker 18.04.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.04.0-ce) @@ -1036,9 +1036,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23890/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23890/Docker.dmg) * Upgrades - [Docker 18.04.0-ce-rc2](https://github.com/docker/docker-ce/releases/tag/v18.04.0-ce-rc2) @@ -1054,9 +1054,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23607/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23607/Docker.dmg) * Upgrades - [Docker 18.03.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce) @@ -1066,9 +1066,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23352/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23352/Docker.dmg) * Upgrades - [Docker 18.03.0-ce-rc4](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce-rc4) @@ -1082,9 +1082,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23287/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23287/Docker.dmg) * Upgrades - [Docker 18.03.0-ce-rc3](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce-rc3) @@ -1101,9 +1101,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23022/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/23022/Docker.dmg) * Upgrades - [Docker 18.03.0-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce-rc1) @@ -1123,9 +1123,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22617/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22617/Docker.dmg) * Upgrades - [Docker 18.02.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.02.0-ce) @@ -1140,9 +1140,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22446/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22446/Docker.dmg) * Upgrades - [Docker 18.02.0-ce-rc2](https://github.com/docker/docker-ce/releases/tag/v18.02.0-ce-rc2) @@ -1158,9 +1158,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22256/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22256/Docker.dmg) * Upgrades - [Docker 18.02.0-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v18.02.0-ce-rc1) @@ -1174,9 +1174,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22004/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/22004/Docker.dmg) * Upgrades - [Docker 18.01.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.01.0-ce) @@ -1203,9 +1203,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/21669/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/21669/Docker.dmg) * Upgrades - [Docker 17.12.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce) @@ -1223,9 +1223,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/21438/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/21438/Docker.dmg) * Upgrades - [Docker 17.12.0-ce-rc4](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce-rc4) @@ -1239,9 +1239,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/21270/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/21270/Docker.dmg) * Upgrades - [Docker 17.12.0-ce-rc3](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce-rc3) @@ -1270,9 +1270,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/20561/Docker.dmg){: .accept-eula } +> [Download for Mac with Intel chip](https://download.docker.com/mac/edge/20561/Docker.dmg) * Upgrades - [Docker 17.11.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.11.0-ce) @@ -1318,9 +1318,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/mac/edge/19824/Docker.dmg){: .accept-eula } +> [Download](https://download.docker.com/mac/edge/19824/Docker.dmg) * Upgrades - [Docker 17.10.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.10.0-ce) @@ -2417,7 +2417,7 @@ The `osxfs` file system now persists ownership changes in an extended attribute. **Upgrades** -* docker-compose 1.7.1 (see [changelog](https://github.com/docker/compose/releases/tag/1.7.1){: target="_blank" rel="noopener" class="_" }) +* docker-compose 1.7.1 (see [changelog](https://github.com/docker/compose/releases/tag/1.7.1)) * Linux kernel 4.4.9 **Bug fixes and minor changes** @@ -2750,6 +2750,4 @@ work yet. - Fixed setting hostname -- Fixed permissions on `usr/local` symbolic links - -{% include eula-modal.html %} +- Fixed permissions on `usr/local` symbolic links \ No newline at end of file diff --git a/content/desktop/previous-versions/edge-releases-windows.md b/content/desktop/previous-versions/edge-releases-windows.md index 35ad516de3..cf30624307 100644 --- a/content/desktop/previous-versions/edge-releases-windows.md +++ b/content/desktop/previous-versions/edge-releases-windows.md @@ -4,8 +4,8 @@ keywords: Docker Desktop for Windows, edge, release notes title: Docker Desktop for Windows Edge Release notes toc_min: 1 toc_max: 2 -redirect_from: - - /desktop/windows/release-notes/edge-releases/ +aliases: +- /desktop/windows/release-notes/edge-releases/ --- This page contains information about Docker Desktop Edge releases. Edge releases give you early access to our newest features. Note that some of the features may be experimental, and some of them may not ever reach the Stable release. @@ -18,9 +18,9 @@ This page contains information about Docker Desktop Edge releases. Edge releases > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/50534/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/50534/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -37,9 +37,9 @@ This page contains information about Docker Desktop Edge releases. Edge releases > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/50261/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/50261/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -50,9 +50,9 @@ This page contains information about Docker Desktop Edge releases. Edge releases > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/50165/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/50165/Docker%20Desktop%20Installer.exe) ### New @@ -68,9 +68,9 @@ This page contains information about Docker Desktop Edge releases. Edge releases > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/49923/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/49923/Docker%20Desktop%20Installer.exe) This release contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing Docker Desktop. @@ -92,9 +92,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/48975/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/48975/Docker%20Desktop%20Installer.exe) ### New @@ -127,9 +127,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/48583/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/48583/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -147,9 +147,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/48173/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/48173/Docker%20Desktop%20Installer.exe) ### New @@ -187,9 +187,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/47842/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/47842/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -204,9 +204,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/47622/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/47622/Docker%20Desktop%20Installer.exe) ### New @@ -231,9 +231,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/47433/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/47433/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -244,9 +244,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/47357/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/47357/Docker%20Desktop%20Installer.exe) ### New @@ -275,9 +275,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/46980/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/46980/Docker%20Desktop%20Installer.exe) ### New @@ -287,8 +287,8 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for ### Upgrades -- [Docker ECS integration v1.0.0-beta.4](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.4){: target="_blank" class="_”} -- [Kubernetes 1.18.6](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.6){: target="_blank" class="_”} +- [Docker ECS integration v1.0.0-beta.4](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.4) +- [Kubernetes 1.18.6](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.6) ### Bug fixes and minor changes @@ -300,23 +300,23 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/46784/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/46784/Docker%20Desktop%20Installer.exe) ### Upgrades -- [Docker ECS integration v1.0.0-beta.2](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.2){: target="_blank" class="_”} -- [Docker ACI integration 0.1.10](https://github.com/docker/aci-integration-beta/releases/tag/v0.1.10){: target="_blank" class="_”} +- [Docker ECS integration v1.0.0-beta.2](https://github.com/docker/ecs-plugin/releases/tag/v1.0.0-beta.2) +- [Docker ACI integration 0.1.10](https://github.com/docker/aci-integration-beta/releases/tag/v0.1.10) ## Docker Desktop Community 2.3.3.1 2020-07-10 > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/46608/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/46608/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -327,9 +327,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/46574/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/46574/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -346,9 +346,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/46329/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/46329/Docker%20Desktop%20Installer.exe) ### Security @@ -385,9 +385,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://desktop.docker.com/win/edge/45408/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://desktop.docker.com/win/edge/45408/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -433,9 +433,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/44875/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/44875/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -451,9 +451,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/44472/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/44472/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -499,9 +499,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/43965/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/43965/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -561,9 +561,9 @@ the `--privileged` flag. See [docker/for-win#8326](https://github.com/docker/for > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/43066/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/43066/Docker%20Desktop%20Installer.exe) This release contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing Docker Desktop. @@ -589,9 +589,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/42746/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/42746/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -634,9 +634,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/41561/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/41561/Docker%20Desktop%20Installer.exe) > **Note:** Docker Desktop Edge 2.1.7.0 is the release candidate for the upcoming major Stable release. Please help us test this version before the wider release and report any issues in the [docker/for-win](https://github.com/docker/for-win/issues) GitHub repository. @@ -670,9 +670,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/40920/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/40920/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -688,9 +688,9 @@ Windows Insider Preview Slow Ring users running OS builds older than 19025 canno > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/40807/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/40807/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -724,9 +724,9 @@ Windows Insider Preview Slow Ring users running OS builds older than 19025 canno > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/40323/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/40323/Docker%20Desktop%20Installer.exe) This release contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installation. @@ -764,9 +764,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/39357/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/39357/Docker%20Desktop%20Installer.exe) ### Upgrades @@ -786,9 +786,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/38275/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/38275/Docker%20Desktop%20Installer.exe) ### Bug fixes and minor changes @@ -800,9 +800,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/38030/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/38030/Docker%20Desktop%20Installer.exe) #### Upgrades @@ -823,9 +823,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/37260/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/37260/Docker%20Desktop%20Installer.exe) #### Upgrades @@ -849,9 +849,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/36873/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/36873/Docker%20Desktop%20Installer.exe) This release contains Kubernetes security improvements. Note that your local Kubernetes PKI and cluster will be reset after installation. @@ -884,9 +884,9 @@ This release contains Kubernetes security improvements. Note that your local Kub > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/35318/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/35318/Docker%20Desktop%20Installer.exe) This is the Edge channel, which gives you early access to our newest features. Be aware that some of them may be experimental, and some of them may not ever reach the Stable release. @@ -921,9 +921,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/34207/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/34207/Docker%20Desktop%20Installer.exe) * Bug fixes and minor changes - Upgrade QEMU from 2.8.0 to 3.1.0 to fix an emulation issue when building and running Java applications on Arm64 devices. @@ -932,9 +932,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/33772/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/33772/Docker%20Desktop%20Installer.exe) * Upgrades - [Docker 19.03.0-beta3](https://github.com/docker/docker-ce/releases/tag/v19.03.0-beta3) @@ -971,9 +971,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/31778/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/31778/Docker%20Desktop%20Installer.exe) * Upgrades - [Docker 18.09.3](https://github.com/docker/docker-ce/releases/tag/v18.09.3) @@ -987,9 +987,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/31274/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/31274/Docker%20Desktop%20Installer.exe) * Upgrades - [Docker 18.09.2](https://github.com/docker/docker-ce/releases/tag/v18.09.2), fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736) @@ -998,9 +998,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/30972/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/30972/Docker%20Desktop%20Installer.exe) * Upgrades - [Docker Compose 1.24.0-rc1](https://github.com/docker/compose/releases/tag/1.24.0-rc1) @@ -1017,9 +1017,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/30090/Docker%20Desktop%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/30090/Docker%20Desktop%20Installer.exe) * Upgrades - [Docker 18.09.1](https://github.com/docker/docker-ce/releases/tag/v18.09.1) @@ -1044,9 +1044,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/29268/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/29268/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker compose 1.23.2](https://github.com/docker/compose/releases/tag/1.23.2) @@ -1058,9 +1058,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/28777/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/28777/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.09.0](https://github.com/docker/docker-ce-packaging/releases/tag/v18.09.0) @@ -1080,9 +1080,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/19925/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/19925/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.09.0-ce-beta1](https://github.com/docker/docker-ce/releases/tag/v18.09.0-ce-beta1) @@ -1105,9 +1105,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/19508/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/19508/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.06.1-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.1-ce) @@ -1127,9 +1127,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/19101/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/19101/Docker%20for%20Windows%20Installer.exe) * Bug fixes and minor changes - Fix bug in automatic feature enabling if "Hyper-V" and "Containers" Windows features are not enabled already when starting Docker Desktop. @@ -1138,9 +1138,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/19070/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/19070/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.06.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.06.0-ce) @@ -1149,9 +1149,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/18994/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/18994/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.06.0-ce-rc3](https://github.com/docker/docker-ce/releases/tag/v18.06.0-ce-rc3) @@ -1172,9 +1172,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/18263/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/18263/Docker%20for%20Windows%20Installer.exe) * Upgrades - [LinuxKit v0.4](https://github.com/linuxkit/linuxkit/releases/tag/v0.4) @@ -1189,9 +1189,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/17760/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/17760/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.05.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.05.0-ce) @@ -1209,9 +1209,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/17439/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/17439/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.05.0-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v18.05.0-ce-rc1) @@ -1227,9 +1227,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/17151/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/17151/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.04.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.04.0-ce) @@ -1239,9 +1239,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/17070/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/17070/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.04.0-ce-rc2](https://github.com/docker/docker-ce/releases/tag/v18.04.0-ce-rc2) @@ -1257,9 +1257,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/16761/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/16761/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce) @@ -1272,9 +1272,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/16511/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/16511/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.0-ce-rc4](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce-rc4) @@ -1287,9 +1287,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/16433/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/16433/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.0-ce-rc3](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce-rc3) @@ -1308,9 +1308,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/16164/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/16164/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.03.0-ce-rc1](https://github.com/docker/docker-ce/releases/tag/v18.03.0-ce-rc1) @@ -1334,9 +1334,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/15732/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/15732/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.02.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.02.0-ce) @@ -1374,9 +1374,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/15285/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/15285/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 18.01.0-ce](https://github.com/docker/docker-ce/releases/tag/v18.01.0-ce) @@ -1391,9 +1391,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/15017/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/15017/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 17.12.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.12.0-ce) @@ -1435,9 +1435,9 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus > Download Docker Desktop > -> {%- include eula.md -%} +> > -> [Download](https://download.docker.com/win/edge/14328/Docker%20for%20Windows%20Installer.exe){: .accept-eula } +> [Download](https://download.docker.com/win/edge/14328/Docker%20for%20Windows%20Installer.exe) * Upgrades - [Docker 17.11.0-ce](https://github.com/docker/docker-ce/releases/tag/v17.11.0-ce) @@ -2944,6 +2944,4 @@ are working on a solution. **Networking** - - live debugging Node.js application - -{% include eula-modal.html %} + - live debugging Node.js application \ No newline at end of file diff --git a/content/desktop/release-notes.md b/content/desktop/release-notes.md index ce19b40ba2..696a3c3a91 100644 --- a/content/desktop/release-notes.md +++ b/content/desktop/release-notes.md @@ -3,15 +3,15 @@ description: Release notes for Docker Desktop for Mac, Linux, and Windows keywords: Docker desktop, release notes, linux, mac, windows title: Docker Desktop release notes toc_max: 2 -redirect_from: - - /docker-for-mac/release-notes/ - - /docker-for-mac/edge-release-notes/ - - /desktop/mac/release-notes/ - - /docker-for-windows/edge-release-notes/ - - /docker-for-windows/release-notes/ - - /desktop/windows/release-notes/ - - /desktop/linux/release-notes/ - - /mackit/release-notes/ +aliases: +- /docker-for-mac/release-notes/ +- /docker-for-mac/edge-release-notes/ +- /desktop/mac/release-notes/ +- /docker-for-windows/edge-release-notes/ +- /docker-for-windows/release-notes/ +- /desktop/windows/release-notes/ +- /desktop/linux/release-notes/ +- /mackit/release-notes/ --- This page contains information about the new features, improvements, known issues, and bug fixes in Docker Desktop releases. @@ -20,15 +20,15 @@ This page contains information about the new features, improvements, known issue > > The information below is applicable to all platforms, unless stated otherwise. -Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/projects/1){: target="_blank" rel="noopener" class="_"} to see what's coming next. +Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/projects/1) to see what's coming next. For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/releases.md). ## 4.22.0 -{% include release-date.html date="2023-08-03" %} +{{< release-date date="2023-08-03" >}} -{% include desktop-install.md all=true version="4.22.0" build_path="/" %} +{{< desktop-install all=true version="4.22.0" build_path="/" >}} ### Upgrades @@ -70,9 +70,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.21.1 -{% include release-date.html date="2023-07-03" %} +{{< release-date date="2023-07-03" >}} -{% include desktop-install.md all=true version="4.21.1" build_path="/114176/" %} +{{< desktop-install all=true version="4.21.1" build_path="/114176/" >}} #### For all platforms @@ -84,9 +84,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.21.0 -{% include release-date.html date="2023-06-29" %} +{{< release-date date="2023-06-29" >}} -{% include desktop-install.md all=true version="4.21.0" build_path="/113844/" %} +{{< desktop-install all=true version="4.21.0" build_path="/113844/" >}} ### New @@ -136,9 +136,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.20.1 -{% include release-date.html date="2023-06-05" %} +{{< release-date date="2023-06-05" >}} -{% include desktop-install.md all=true version="4.20.1" build_path="/110738/" %} +{{< desktop-install all=true version="4.20.1" build_path="/110738/" >}} ### Bug fixes and enhancements @@ -153,9 +153,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.20.0 -{% include release-date.html date="2023-05-30" %} +{{< release-date date="2023-05-30" >}} -{% include desktop-install.md all=true version="4.20.0" build_path="/109717/" %} +{{< desktop-install all=true version="4.20.0" build_path="/109717/" >}} ### Upgrades @@ -194,9 +194,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.19.0 -{% include release-date.html date="2023-04-27" %} +{{< release-date date="2023-04-27" >}} -{% include desktop-install.md all=true version="4.19.0" build_path="/106363/" %} +{{< desktop-install all=true version="4.19.0" build_path="/106363/" >}} ### New @@ -267,9 +267,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.18.0 -{% include release-date.html date="2023-04-03" %} +{{< release-date date="2023-04-03" >}} -{% include desktop-install.md all=true version="4.18.0" build_path="/104112/" %} +{{< desktop-install all=true version="4.18.0" build_path="/104112/" >}} ### New @@ -321,7 +321,7 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re #### For all platforms -- Fixed [CVE-2023-1802](https://www.cve.org/cverecord?id=CVE-2023-1802){: target="_blank" rel="noopener" class="_"} where a security issue with the Artifactory Integration would cause it to fall back to sending registry credentials over plain HTTP if HTTPS check failed. Only users who have `Access experimental features` enabled are affected. Fixes [docker/for-win#13344](https://github.com/docker/for-win/issues/13344). +- Fixed [CVE-2023-1802](https://www.cve.org/cverecord?id=CVE-2023-1802) where a security issue with the Artifactory Integration would cause it to fall back to sending registry credentials over plain HTTP if HTTPS check failed. Only users who have `Access experimental features` enabled are affected. Fixes [docker/for-win#13344](https://github.com/docker/for-win/issues/13344). #### For Mac @@ -333,9 +333,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.17.1 -{% include release-date.html date="2023-03-20" %} +{{< release-date date="2023-03-20" >}} -{% include desktop-install.md win=true version="4.17.1" build_path="/101757/" %} +{{< desktop-install win=true version="4.17.1" build_path="/101757/" >}} ### Bug fixes and enhancements @@ -352,9 +352,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.17.0 -{% include release-date.html date="2023-02-27" %} +{{< release-date date="2023-02-27" >}} -{% include desktop-install.md all=true version="4.17.0" build_path="/99724/" %} +{{< desktop-install all=true version="4.17.0" build_path="/99724/" >}} ### New @@ -428,14 +428,14 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re #### For all platforms -- Fixed [CVE-2023-0628](https://www.cve.org/cverecord?id=CVE-2023-0628){: target="_blank" rel="noopener" class="_"}, which allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to open a crafted malicious `docker-desktop://` URL. -- Fixed [CVE-2023-0629](https://www.cve.org/cverecord?id=CVE-2023-0629){: target="_blank" rel="noopener" class="_"}, which allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to `docker.raw.sock`, or `npipe:////.pipe/docker_engine_linux` on Windows, via the `-H` (`--host`) CLI flag or the `DOCKER_HOST` environment variable and launch containers without the additional hardening features provided by ECI. This does not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket). +- Fixed [CVE-2023-0628](https://www.cve.org/cverecord?id=CVE-2023-0628), which allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to open a crafted malicious `docker-desktop://` URL. +- Fixed [CVE-2023-0629](https://www.cve.org/cverecord?id=CVE-2023-0629), which allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to `docker.raw.sock`, or `npipe:////.pipe/docker_engine_linux` on Windows, via the `-H` (`--host`) CLI flag or the `DOCKER_HOST` environment variable and launch containers without the additional hardening features provided by ECI. This does not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket). ## 4.16.3 -{% include release-date.html date="2023-01-30" %} +{{< release-date date="2023-01-30" >}} -{% include desktop-install.md win=true version="4.16.3" build_path="/96739/" %} +{{< desktop-install win=true version="4.16.3" build_path="/96739/" >}} ### Bug fixes and enhancements @@ -446,9 +446,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.16.2 -{% include release-date.html date="2023-01-19" %} +{{< release-date date="2023-01-19" >}} -{% include desktop-install.md all=true version="4.16.2" build_path="/95914/" %} +{{< desktop-install all=true version="4.16.2" build_path="/95914/" >}} ### Bug fixes and enhancements @@ -467,9 +467,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.16.1 -{% include release-date.html date="2023-01-13" %} +{{< release-date date="2023-01-13" >}} -{% include desktop-install.md all=true version="4.16.1" build_path="/95567/" %} +{{< desktop-install all=true version="4.16.1" build_path="/95567/" >}} ### Bug fixes and enhancements @@ -479,9 +479,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.16.0 -{% include release-date.html date="2023-01-12" %} +{{< release-date date="2023-01-12" >}} -{% include desktop-install.md all=true version="4.16.0" build_path="/95345/" %} +{{< desktop-install all=true version="4.16.0" build_path="/95345/" >}} ### New @@ -543,9 +543,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.15.0 -{% include release-date.html date="2022-12-01" %} +{{< release-date date="2022-12-01" >}} -{% include desktop-install.md all=true version="4.15.0" build_path="/93002/" %} +{{< desktop-install all=true version="4.15.0" build_path="/93002/" >}} ### New @@ -596,9 +596,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.14.1 -{% include release-date.html date="2022-11-17" %} +{{< release-date date="2022-11-17" >}} -{% include desktop-install.md all=true version="4.14.1" build_path="/91661/" %} +{{< desktop-install all=true version="4.14.1" build_path="/91661/" >}} ### Bug fixes and enhancements @@ -613,9 +613,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.14.0 -{% include release-date.html date="2022-11-10" %} +{{< release-date date="2022-11-10" >}} -{% include desktop-install.md all=true version="4.14.0" build_path="/91374/" %} +{{< desktop-install all=true version="4.14.0" build_path="/91374/" >}} ### New @@ -626,7 +626,7 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ### Updates - [Docker Engine v20.10.21](../engine/release-notes/20.10.md#201021), - which contains mitigations against a Git vulnerability, tracked in [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253){:target="\_blank" rel="noopener"}, + which contains mitigations against a Git vulnerability, tracked in [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253), and updates the handling of `image:tag@digest` image references. - [Docker Compose v2.12.2](https://github.com/docker/compose/releases/tag/v2.12.2) - [Containerd v1.6.9](https://github.com/containerd/containerd/releases/tag/v1.6.9) @@ -674,9 +674,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.13.1 -{% include release-date.html date="2022-10-31" %} +{{< release-date date="2022-10-31" >}} -{% include desktop-install.md all=true version="4.13.1" build_path="/90346/" %} +{{< desktop-install all=true version="4.13.1" build_path="/90346/" >}} ### Updates @@ -701,9 +701,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.13.0 -{% include release-date.html date="2022-10-19" %} +{{< release-date date="2022-10-19" >}} -{% include desktop-install.md all=true version="4.13.0" build_path="/89412/" %} +{{< desktop-install all=true version="4.13.0" build_path="/89412/" >}} ### New @@ -714,11 +714,11 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ### Updates - [Docker Scan v0.21.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.21.0) -- [Go 1.19.2](https://github.com/golang/go/releases/tag/go1.19.2) to address [CVE-2022-2879](https://www.cve.org/CVERecord?id=CVE-2022-2879){: target="\_blank" rel="noopener"}, [CVE-2022-2880](https://www.cve.org/CVERecord?id=CVE-2022-2880){: target="\_blank" rel="noopener"} and [CVE-2022-41715](https://www.cve.org/CVERecord?id= CVE-2022-41715){: target="\_blank" rel="noopener"} +- [Go 1.19.2](https://github.com/golang/go/releases/tag/go1.19.2) to address [CVE-2022-2879](https://www.cve.org/CVERecord?id=CVE-2022-2879), [CVE-2022-2880](https://www.cve.org/CVERecord?id=CVE-2022-2880) and [CVE-2022-41715](https://www.cve.org/CVERecord?id= CVE-2022-41715) - Updated Docker Engine and Docker CLI to [v20.10.20](../engine/release-notes/20.10.md#201020), - which contain mitigations against a Git vulnerability, tracked in [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253){:target="\_blank" rel="noopener"}, + which contain mitigations against a Git vulnerability, tracked in [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253), and updated handling of `image:tag@digest` image references, as well as a fix for [CVE-2022-36109](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36109). -- [Docker Credential Helpers v0.7.0](https://github.com/docker/docker-credential-helpers/releases/tag/v0.7.0){: target="blank" rel="noopener" class=""} +- [Docker Credential Helpers v0.7.0](https://github.com/docker/docker-credential-helpers/releases/tag/v0.7.0) - [Docker Compose v2.12.0](https://github.com/docker/compose/releases/tag/v2.12.0) - [Kubernetes v1.25.2](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.2) - [Qemu 7.0.0](https://wiki.qemu.org/ChangeLog/7.0) used for cpu emulation, inside the Docker Desktop VM. @@ -768,9 +768,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.12.0 -{% include release-date.html date="2022-09-01" %} +{{< release-date date="2022-09-01" >}} -{% include desktop-install.md all=true version="4.12.0" build_path="/85629/" %} +{{< desktop-install all=true version="4.12.0" build_path="/85629/" >}} ### New @@ -848,9 +848,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.11.1 -{% include release-date.html date="2022-08-05" %} +{{< release-date date="2022-08-05" >}} -{% include desktop-install.md all=true version="4.11.1" build_path="/84025/" %} +{{< desktop-install all=true version="4.11.1" build_path="/84025/" >}} ### Bug fixes and enhancements @@ -864,9 +864,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.11.0 -{% include release-date.html date="2022-07-28" %} +{{< release-date date="2022-07-28" >}} -{% include desktop-install.md all=true version="4.11.0" build_path="/83626/" %} +{{< desktop-install all=true version="4.11.0" build_path="/83626/" >}} ### New @@ -922,9 +922,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.10.1 -{% include release-date.html date="2022-07-05" %} +{{< release-date date="2022-07-05" >}} -{% include desktop-install.md all=true version="4.10.1" build_path="/82475/" %} +{{< desktop-install all=true version="4.10.1" build_path="/82475/" >}} ### Bug fixes and enhancements @@ -938,9 +938,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.10.0 -{% include release-date.html date="2022-06-30" %} +{{< release-date date="2022-06-30" >}} -{% include desktop-install.md all=true version="4.10.0" build_path="/82025/" %} +{{< desktop-install all=true version="4.10.0" build_path="/82025/" >}} ### New @@ -1008,9 +1008,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.9.1 -{% include release-date.html date="2022-06-16" %} +{{< release-date date="2022-06-16" >}} -{% include desktop-install.md all=true version="4.9.1" build_path="/81317/" %} +{{< desktop-install all=true version="4.9.1" build_path="/81317/" >}} ### Bug fixes and enhancements @@ -1020,9 +1020,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.9.0 -{% include release-date.html date="2022-06-02" %} +{{< release-date date="2022-06-02" >}} -{% include desktop-install.md all=true version="4.9.0" build_path="/80466/" %} +{{< desktop-install all=true version="4.9.0" build_path="/80466/" >}} ### New @@ -1070,9 +1070,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.8.2 -{% include release-date.html date="2022-05-18" %} +{{< release-date date="2022-05-18" >}} -{% include desktop-install.md all=true version="4.8.2" build_path="/79419/" %} +{{< desktop-install all=true version="4.8.2" build_path="/79419/" >}} ### Updates @@ -1092,9 +1092,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.8.1 -{% include release-date.html date="2022-05-09" %} +{{< release-date date="2022-05-09" >}} -{% include desktop-install.md all=true version="4.8.1" build_path="/78998/" %} +{{< desktop-install all=true version="4.8.1" build_path="/78998/" >}} ### New @@ -1115,9 +1115,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.8.0 -{% include release-date.html date="2022-05-06" %} +{{< release-date date="2022-05-06" >}} -{% include desktop-install.md all=true version="4.8.0" build_path="/78933/" %} +{{< desktop-install all=true version="4.8.0" build_path="/78933/" >}} ### New @@ -1177,9 +1177,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.7.1 -{% include release-date.html date="2022-04-19" %} +{{< release-date date="2022-04-19" >}} -{% include desktop-install.md win=true mac=true version="4.7.1" build_path="/77678/" %} +{{< desktop-install win=true mac=true version="4.7.1" build_path="/77678/" >}} ### Bug fixes and enhancements @@ -1194,15 +1194,15 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.7.0 -{% include release-date.html date="2022-04-07" %} +{{< release-date date="2022-04-07" >}} -{% include desktop-install.md win=true mac=true version="4.7.0" build_path="/77141/" %} +{{< desktop-install win=true mac=true version="4.7.0" build_path="/77141/" >}} ### New - IT Administrators can now install Docker Desktop remotely using the command line. - Add the Docker Software Bill of Materials (SBOM) CLI plugin. The new CLI plugin enables users to generate SBOMs for Docker images. For more information, see [Docker SBOM](../engine/sbom/index.md). -- Use [cri-dockerd](https://github.com/Mirantis/cri-dockerd){: target="_blank" rel="noopener" class="_"} for new Kubernetes clusters instead of `dockershim`. The change is transparent from the user's point of view and Kubernetes containers run on the Docker Engine as before. `cri-dockerd` allows Kubernetes to manage Docker containers using the standard [Container Runtime Interface](https://github.com/kubernetes/cri-api#readme){: target="_blank" rel="noopener" class="_"}, the same interface used to control other container runtimes. For more information, see [The Future of Dockershim is cri-dockerd](https://www.mirantis.com/blog/the-future-of-dockershim-is-cri-dockerd/){: target="_blank" rel="noopener" class="_"}. +- Use [cri-dockerd](https://github.com/Mirantis/cri-dockerd) for new Kubernetes clusters instead of `dockershim`. The change is transparent from the user's point of view and Kubernetes containers run on the Docker Engine as before. `cri-dockerd` allows Kubernetes to manage Docker containers using the standard [Container Runtime Interface](https://github.com/kubernetes/cri-api#readme), the same interface used to control other container runtimes. For more information, see [The Future of Dockershim is cri-dockerd](https://www.mirantis.com/blog/the-future-of-dockershim-is-cri-dockerd/). ### Updates @@ -1214,7 +1214,7 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ### Security -- Update Docker Engine to v20.10.14 to address [CVE-2022-24769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24769){: target="_blank" rel="noopener" class="_"} +- Update Docker Engine to v20.10.14 to address [CVE-2022-24769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24769) - Update containerd to v1.5.11 to address [CVE-2022-24769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24769) ### Bug fixes and enahncements @@ -1239,9 +1239,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.6.1 -{% include release-date.html date="2022-03-22" %} +{{< release-date date="2022-03-22" >}} -{% include desktop-install.md win=true mac=true version="4.6.1" build_path="/76265/" %} +{{< desktop-install win=true mac=true version="4.6.1" build_path="/76265/" >}} ### Updates @@ -1255,9 +1255,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.6.0 -{% include release-date.html date="2022-03-14" %} +{{< release-date date="2022-03-14" >}} -{% include desktop-install.md win=true mac=true version="4.6.0" build_path="/75818/" %} +{{< desktop-install win=true mac=true version="4.6.0" build_path="/75818/" >}} ### New @@ -1285,12 +1285,12 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re #### For all platforms -- Fixed [CVE-2022-0847](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847){: target="_blank" rel="noopener" class="_"}, aka “Dirty Pipe”, an issue that could enable attackers to modify files in container images on the host, from inside a container. +- Fixed [CVE-2022-0847](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847), aka “Dirty Pipe”, an issue that could enable attackers to modify files in container images on the host, from inside a container. If using the WSL 2 backend, you must update WSL 2 by running `wsl --update`. #### For Windows -- Fixed [CVE-2022-26659](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26659){: target="_blank" rel="noopener" class="_"}, which could allow an attacker to overwrite any administrator writable file on the system during the installation or the update of Docker Desktop. +- Fixed [CVE-2022-26659](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26659), which could allow an attacker to overwrite any administrator writable file on the system during the installation or the update of Docker Desktop. #### For Mac @@ -1327,9 +1327,9 @@ For frequently asked questions about Docker Desktop releases, see [FAQs](faqs/re ## 4.5.1 -{% include release-date.html date="2022-02-15" %} +{{< release-date date="2022-02-15" >}} -{% include desktop-install.md win=true version="4.5.1" build_path="/74721/" %} +{{< desktop-install win=true version="4.5.1" build_path="/74721/" >}} ### Bug fixes and enhancements @@ -1343,28 +1343,28 @@ Alternatively, you can edit the Docker Desktop settings file located at `%APPDAT ## 4.5.0 -{% include release-date.html date="2022-02-10" %} +{{< release-date date="2022-02-10" >}} -{% include desktop-install.md win=true mac=true version="4.5.0" build_path="/74594/" %} +{{< desktop-install win=true mac=true version="4.5.0" build_path="/74594/" >}} ### New -- Docker Desktop 4.5.0 introduces a new version of the Docker menu which creates a consistent user experience across all operating systems. For more information, see the blog post [New Docker Menu & Improved Release Highlights with Docker Desktop 4.5](https://www.docker.com/blog/new-docker-menu-improved-release-highlights-with-docker-desktop-4-5/){: target="_blank" rel="noopener" class="_"} +- Docker Desktop 4.5.0 introduces a new version of the Docker menu which creates a consistent user experience across all operating systems. For more information, see the blog post [New Docker Menu & Improved Release Highlights with Docker Desktop 4.5](https://www.docker.com/blog/new-docker-menu-improved-release-highlights-with-docker-desktop-4-5/) - The 'docker version' output now displays the version of Docker Desktop installed on the machine. ### Updates -- [Amazon ECR Credential Helper v0.6.0](https://github.com/awslabs/amazon-ecr-credential-helper/releases/tag/v0.6.0){: target="blank" rel="noopener" class=""} +- [Amazon ECR Credential Helper v0.6.0](https://github.com/awslabs/amazon-ecr-credential-helper/releases/tag/v0.6.0) ### Security #### For Mac -- Fixed [CVE-2021-44719](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44719){: target="_blank" rel="noopener" class="_"} where Docker Desktop could be used to access any user file on the host from a container, bypassing the allowed list of shared folders. +- Fixed [CVE-2021-44719](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44719) where Docker Desktop could be used to access any user file on the host from a container, bypassing the allowed list of shared folders. #### For Windows -- Fixed [CVE-2022-23774](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23774){: target="_blank" rel="noopener" class="_"} where Docker Desktop allows attackers to move arbitrary files. +- Fixed [CVE-2022-23774](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23774) where Docker Desktop allows attackers to move arbitrary files. ### Bug fixes and enhancements @@ -1393,9 +1393,9 @@ Installing Docker Desktop 4.5.0 from scratch has a bug which defaults Docker Des ## 4.4.4 -{% include release-date.html date="2022-01-24" %} +{{< release-date date="2022-01-24" >}} -{% include desktop-install.md win=true version="4.4.4" build_path="/73704/" %} +{{< desktop-install win=true version="4.4.4" build_path="/73704/" >}} ### Bug fixes and enhancements @@ -1413,9 +1413,9 @@ Installing Docker Desktop 4.5.0 from scratch has a bug which defaults Docker Des ## 4.4.3 -{% include release-date.html date="2022-01-14" %} +{{< release-date date="2022-01-14" >}} -{% include desktop-install.md win=true version="4.4.3" build_path="/73365/" %} +{{< desktop-install win=true version="4.4.3" build_path="/73365/" >}} ### Bug fixes and enhancements @@ -1433,9 +1433,9 @@ Installing Docker Desktop 4.5.0 from scratch has a bug which defaults Docker Des ## 4.4.2 -{% include release-date.html date="22-01-13" %} +{{< release-date date="22-01-13" >}} -{% include desktop-install.md win=true mac=true version="4.4.2" build_path="/73305/" %} +{{< desktop-install win=true mac=true version="4.4.2" build_path="/73305/" >}} ### New @@ -1448,7 +1448,7 @@ Installing Docker Desktop 4.5.0 from scratch has a bug which defaults Docker Des - [Docker Engine v20.10.12](../engine/release-notes/20.10.md#201012) - [Compose v2.2.3](https://github.com/docker/compose/releases/tag/v2.2.3) - [Kubernetes 1.22.5](https://github.com/kubernetes/kubernetes/releases/tag/v1.22.5) -- [docker scan v0.16.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.16.0){: target="_blank" rel="noopener" class="_"} +- [docker scan v0.16.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.16.0) ### Security @@ -1488,9 +1488,9 @@ This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user ## 4.3.2 -{% include release-date.html date="2021-12-21" %} +{{< release-date date="2021-12-21" >}} -{% include desktop-install.md win=true mac=true version="4.3.2" build_path="/72729/" %} +{{< desktop-install win=true mac=true version="4.3.2" build_path="/72729/" >}} ### Security @@ -1501,46 +1501,44 @@ This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user ### Upgrades -[docker scan v0.14.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.14.0){: target="_blank" rel="noopener" class="_"} +[docker scan v0.14.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.14.0) ### Security **Log4j 2 CVE-2021-44228**: We have updated the `docker scan` CLI plugin. This new version of `docker scan` is able to detect [Log4j 2 -CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228){: -target="_blank" rel="noopener" class="_"} and [Log4j 2 +CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) and [Log4j 2 CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046) For more information, read the blog post [Apache Log4j 2 -CVE-2021-44228](https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/){: target="_blank" rel="noopener" class="_"}. +CVE-2021-44228](https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/). ## 4.3.1 -{% include release-date.html date="2021-12-11" %} +{{< release-date date="2021-12-11" >}} -{% include desktop-install.md win=true mac=true version="4.3.1" build_path="/72247/" %} +{{< desktop-install win=true mac=true version="4.3.1" build_path="/72247/" >}} ### Upgrades -[docker scan v0.11.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.11.0){: target="_blank" rel="noopener" class="_"} +[docker scan v0.11.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.11.0) ### Security **Log4j 2 CVE-2021-44228**: We have updated the `docker scan` CLI plugin for you. Older versions of `docker scan` in Docker Desktop 4.3.0 and earlier versions are not able to detect [Log4j 2 -CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228){: -target="_blank" rel="noopener" class="_"}. +CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228). For more information, read the blog post [Apache Log4j 2 -CVE-2021-44228](https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/){: target="_blank" rel="noopener" class="_"}. +CVE-2021-44228](https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/). ## 4.3.0 -{% include release-date.html date="2021-12-02" %} +{{< release-date date="2021-12-02" >}} -{% include desktop-install.md win=true mac=true version="4.3.0" build_path="/71786/" %} +{{< desktop-install win=true mac=true version="4.3.0" build_path="/71786/" >}} ### Upgrades @@ -1586,19 +1584,19 @@ actual memory usage. See ## 4.2.0 -{% include release-date.html date="2021-11-09" %} +{{< release-date date="2021-11-09" >}} -{% include desktop-install.md win=true mac=true version="4.2.0" build_path="/70708/" %} +{{< desktop-install win=true mac=true version="4.2.0" build_path="/70708/" >}} ### New **Pause/Resume**: You can now pause your Docker Desktop session when you are not actively using it and save CPU resources on your machine. -- Ships [Docker Public Roadmap#226](https://github.com/docker/roadmap/issues/226){: target="_blank" rel="noopener" class="_"} +- Ships [Docker Public Roadmap#226](https://github.com/docker/roadmap/issues/226) **Software Updates**: The option to turn off automatic check for updates is now available for users on all Docker subscriptions, including Docker Personal and Docker Pro. All update-related settings have been moved to the **Software Updates** section. -- Ships [Docker Public Roadmap#228](https://github.com/docker/roadmap/issues/228){: target="_blank" rel="noopener" class="_"} +- Ships [Docker Public Roadmap#228](https://github.com/docker/roadmap/issues/228) **Window management**: The Docker Dashboard window size and position persists when you close and reopen Docker Desktop. @@ -1634,9 +1632,9 @@ actual memory usage. See ## 4.1.1 -{% include release-date.html date="2021-10-12" %} +{{< release-date date="2021-10-12" >}} -{% include desktop-install.md win=true mac=true version="4.1.1" build_path="/69879/" %} +{{< desktop-install win=true mac=true version="4.1.1" build_path="/69879/" >}} ### Bug fixes and minor changes @@ -1655,15 +1653,15 @@ actual memory usage. See ## 4.1.0 -{% include release-date.html date="2021-09-30" %} +{{< release-date date="2021-09-30" >}} -{% include desktop-install.md win=true mac=true version="4.1.0" build_path="/69386/" %} +{{< desktop-install win=true mac=true version="4.1.0" build_path="/69386/" >}} ### New - **Software Updates**: The Settings tab now includes a new section to help you manage Docker Desktop updates. The **Software Updates** section notifies you whenever there's a new update and allows you to download the update or view information on what's included in the newer version. - **Compose V2** You can now specify whether to use Docker Compose V2 in the General settings. -- **Volume Management**: Volume management is now available for users on any subscription, including Docker Personal. Ships [Docker Public Roadmap#215](https://github.com/docker/roadmap/issues/215){: target="_blank" rel="noopener" class="_"} +- **Volume Management**: Volume management is now available for users on any subscription, including Docker Personal. Ships [Docker Public Roadmap#215](https://github.com/docker/roadmap/issues/215) ### Upgrades @@ -1696,9 +1694,9 @@ Docker Desktop may fail to start when upgrading to 4.1.0 on some WSL-based distr ## 4.0.1 -{% include release-date.html date="2021-09-13" %} +{{< release-date date="2021-09-13" >}} -{% include desktop-install.md win=true mac=true version="4.0.1" build_path="/68347/" %} +{{< desktop-install win=true mac=true version="4.0.1" build_path="/68347/" >}} ### Upgrades @@ -1719,13 +1717,13 @@ Docker Desktop may fail to start when upgrading to 4.1.0 on some WSL-based distr ## 4.0.0 -{% include release-date.html date="2021-08-31" %} +{{< release-date date="2021-08-31" >}} -{% include desktop-install.md win=true mac=true version="4.0.0" build_path="/67817/" %} +{{< desktop-install win=true mac=true version="4.0.0" build_path="/67817/" >}} ### New -Docker has [announced](https://www.docker.com/blog/updating-product-subscriptions/){: target="_blank" rel="noopener" class="_" id="dkr_docs_relnotes_btl"} updates and extensions to the product subscriptions to increase productivity, collaboration, and added security for our developers and businesses. +Docker has [announced](https://www.docker.com/blog/updating-product-subscriptions/) updates and extensions to the product subscriptions to increase productivity, collaboration, and added security for our developers and businesses. The updated [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) includes a change to the terms for **Docker Desktop**. @@ -1736,7 +1734,7 @@ The updated [Docker Subscription Service Agreement](https://www.docker.com/legal - The existing Docker Free subscription has been renamed **Docker Personal**. - **No changes** to Docker Engine or any other upstream **open source** Docker or Moby project. -To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq){: target="_blank" rel="noopener" class="_" id="dkr_docs_relnotes_btl"}. +To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq). For more information, see [Docker subscription overview](../subscription/index.md). ### Upgrades @@ -1756,4 +1754,4 @@ For more information, see [Docker subscription overview](../subscription/index.m #### For Windows - Fixed a bug where the CLI tools would not be available in WSL 2 distros. -- Fixed a bug when switching from Linux to Windows containers due to access rights on `panic.log`. [for-win#11899](https://github.com/docker/for-win/issues/11899) +- Fixed a bug when switching from Linux to Windows containers due to access rights on `panic.log`. [for-win#11899](https://github.com/docker/for-win/issues/11899) \ No newline at end of file diff --git a/content/desktop/settings/linux.md b/content/desktop/settings/linux.md index dfc4aafb33..43f68d524a 100644 --- a/content/desktop/settings/linux.md +++ b/content/desktop/settings/linux.md @@ -1,6 +1,7 @@ --- description: Change your Docker Desktop settings on Linux -keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker Desktop, Linux +keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker + Desktop, Linux title: Change Docker Desktop settings on Linux --- @@ -8,7 +9,7 @@ This page provides information on how to configure and manage your Docker Deskto To navigate to **Settings** either: -- Select the Docker menu ![whale menu](../images/whale-x.svg){: .inline} and then **Settings** +- Select the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Settings** - Select the **Settings** icon from the Docker Dashboard. ## General @@ -105,7 +106,7 @@ File share settings are: > such as cache directories or databases, the performance will be much > better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md) > (named volume) or [data container](../../storage/volumes.md). -{: .tip} +{ .tip } ### Proxies @@ -122,7 +123,7 @@ To prevent developers from accidentally changing the proxy settings, see ### Network -{% include desktop-network-setting.md %} +{{< include "desktop-network-setting.md" >}} ## Docker Engine @@ -161,7 +162,7 @@ Select **Apply & Restart** to save your settings and restart Docker Desktop. ## Builders -{% include desktop-builders-setting.md %} +{{< include "desktop-builders-setting.md" >}} ## Kubernetes @@ -176,7 +177,7 @@ using Docker commands. Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources. For more information about using the Kubernetes integration with Docker Desktop, -see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}. +see [Deploy on Kubernetes](../kubernetes.md). ## Software Updates @@ -209,11 +210,11 @@ For more information about Docker extensions, see [Extensions](../extensions/ind On the **Feature control** tab you can control your settings for **Beta features** and **Experimental features**. -You can also sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/){:target="_blank" rel="noopener" class="_"} from the **Features in development** tab. +You can also sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/) from the **Features in development** tab. ### Beta features -{% include beta.md %} +{{< include "beta.md" >}} #### Use containerd for pulling and storing images @@ -221,4 +222,4 @@ Turns on the containerd image store. This brings new features like faster contai ### Experimental features -{% include desktop-experimental.md %} +{{< include "desktop-experimental.md" >}} \ No newline at end of file diff --git a/content/desktop/settings/mac.md b/content/desktop/settings/mac.md index 9eda8d7117..244f8a82ab 100644 --- a/content/desktop/settings/mac.md +++ b/content/desktop/settings/mac.md @@ -1,8 +1,9 @@ --- description: Change your Docker Desktop settings on Mac -keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker Desktop, Mac +keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker + Desktop, Mac title: Change Docker Desktop settings on Mac -redirect_from: +aliases: - /docker-for-mac/mutagen-caching/ - /docker-for-mac/mutagen/ - /docker-for-mac/osxfs-caching/ @@ -13,7 +14,7 @@ This page provides information on how to configure and manage your Docker Deskto To navigate to **Settings** either: -- Select the Docker menu ![whale menu](../images/whale-x.svg){: .inline} and then **Settings** +- Select the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Settings** - Select the **Settings** icon from the Docker Dashboard. You can also locate the `settings.json` file at `~/Library/Group Containers/group.com.docker/settings.json`. @@ -37,13 +38,13 @@ If you choose the integrated terminal, you can run commands in a running contain > **Tip** > > Turn this setting on to make Docker Desktop run faster. - {: .tip} + { .tip } - **Choose file sharing implementation for your containers**. Choose whether you want to share files using **VirtioFS**, **gRPC FUSE**, or **osxfs**. VirtioFS is only available for macOS versions 12.5 and above, and is turned on by default. >**Tip** > > Use VirtioFS for speedy file sharing. VirtioFS has reduced the time taken to complete filesystem operations by [up to 98%](https://github.com/docker/roadmap/issues/7#issuecomment-1044452206) - {: .tip} + { .tip } - **Send usage statistics**. Select so Docker Desktop sends diagnostics, crash reports, and usage data. This information helps Docker improve and @@ -96,7 +97,7 @@ You can also move the disk image to a different location. If you attempt to move >**Tip** > > If you're running multi-container workloads, increase the memory and disk image space allocation to something higher. -{: .tip} +{ .tip } ### File sharing @@ -144,7 +145,7 @@ File share settings are: > `Test` will fail. > > For more information, see [Volume mounting requires file sharing for any project directories outside of `/Users`](../troubleshoot/topics.md) -{: .tip} +{ .tip } ### Proxies @@ -175,7 +176,7 @@ The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY ### Network -{% include desktop-network-setting.md %} +{{< include "desktop-network-setting.md" >}} ## Docker Engine @@ -206,7 +207,7 @@ Select **Apply & Restart** to save your settings and restart Docker Desktop. ## Builders -{% include desktop-builders-setting.md %} +{{< include "desktop-builders-setting.md" >}} ## Kubernetes @@ -221,7 +222,7 @@ using Docker commands. Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources. For more information about using the Kubernetes integration with Docker Desktop, -see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}. +see [Deploy on Kubernetes](../kubernetes.md). ## Software Updates @@ -254,11 +255,11 @@ For more information about Docker extensions, see [Extensions](../extensions/ind On the **Feature control** tab you can control your settings for **Beta features** and **Experimental features**. -You can also sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/){:target="_blank" rel="noopener" class="_"} from the **Features in development** tab. +You can also sign up to the [Developer Preview program](https://www.docker.com/community/get-involved/developer-preview/) from the **Features in development** tab. ### Beta features -{% include beta.md %} +{{< include "beta.md" >}} #### Use containerd for pulling and storing images @@ -270,7 +271,7 @@ Turns on Rosetta to accelerate x86/AMD64 binary emulation on Apple Silicon. This ### Experimental features -{% include desktop-experimental.md %} +{{< include "desktop-experimental.md" >}} ## Advanced @@ -291,4 +292,4 @@ On the **Advanced** tab, you can reconfigure your initial installation settings: - **Enable privileged port mapping (Requires password)**. Starts the privileged helper process which binds the ports that are between 1 and 1024. For more information, see [permission requirements for macOS](../mac/permission-requirements.md#binding-privileged-ports). For more information on each configuration -and use case, see [Permission requirements](../mac/permission-requirements.md). +and use case, see [Permission requirements](../mac/permission-requirements.md). \ No newline at end of file diff --git a/content/desktop/settings/windows.md b/content/desktop/settings/windows.md index eec8d9c825..cf3854eb7c 100644 --- a/content/desktop/settings/windows.md +++ b/content/desktop/settings/windows.md @@ -1,6 +1,7 @@ --- description: Change your Docker Desktop settings on Windows -keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker Desktop, Windows +keywords: settings, preferences, proxy, file sharing, resources, kubernetes, Docker + Desktop, Windows title: Change Docker Desktop settings on Windows --- @@ -8,7 +9,7 @@ This page provides information on how to configure and manage your Docker Deskto To navigate to **Settings** either: -- Select the Docker menu ![whale menu](../images/whale-x.svg){: .inline} and then **Settings** +- Select the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Settings** - Select the **Settings** icon from the Docker Dashboard. You can also locate the `settings.json` file at `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings.json`. @@ -70,8 +71,7 @@ containers. > The **Advanced** tab is only available in Hyper-V mode, because Windows manages > the resources in WSL 2 mode and Windows container mode. In WSL 2 > mode, you can configure limits on the memory, CPU, and swap size allocated -> to the [WSL 2 utility VM](https://docs.microsoft.com/en-us/windows/wsl/wsl-config#configure-global-options-with-wslconfig){:target="_blank" -class="_"}. +> to the [WSL 2 utility VM](https://docs.microsoft.com/en-us/windows/wsl/wsl-config#configure-global-options-with-wslconfig). On the **Advanced** tab, you can limit resources available to Docker. @@ -130,7 +130,7 @@ File share settings are: > better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md) > (named volume) or [data container](../../storage/volumes.md). > * Docker Desktop sets permissions to read/write/execute for users, groups and -> others [0777 or a+rwx](https://chmodcommand.com/chmod-0777/){:target="_blank" rel="noopener" class="_"}. +> others [0777 or a+rwx](https://chmodcommand.com/chmod-0777/). > This is not configurable. See [Permissions errors on data directories for shared volumes](../troubleshoot/topics.md). > * Windows presents a case-insensitive view of the filesystem to applications while Linux is case-sensitive. > On Linux, it is possible to create two separate files: `test` and `Test`, @@ -143,7 +143,7 @@ File share settings are: > open `Test` will fail with the error "No such file or directory". Similarly, > once a file called `test` is created, attempts to create a second file called > `Test` will fail. -{: .tip} +{ .tip } #### Shared folders on demand @@ -156,7 +156,7 @@ popup asking if you want to share the specified folder. You can select to **Share it**, in which case it is added to your Docker Desktop Shared Folders list and available to containers. Alternatively, you can opt not to share it by selecting **Cancel**. -![Shared folder on demand](../images/shared-folder-on-demand.png){:width="600px"} +![Shared folder on demand](../images/shared-folder-on-demand.png) ### Proxies @@ -195,7 +195,7 @@ This is useful when a corporate proxy that requires authentication is manually c > The **Network** tab isn't available in the Windows container mode because > Windows manages networking. -{% include desktop-network-setting.md %} +{{< include "desktop-network-setting.md" >}} ### WSL Integration @@ -240,7 +240,7 @@ Select **Apply & Restart** to save your settings and restart Docker Desktop. ## Builders -{% include desktop-builders-setting.md %} +{{< include "desktop-builders-setting.md" >}} ## Kubernetes @@ -259,7 +259,7 @@ using Docker commands. Select **Reset Kubernetes cluster** to delete all stacks and Kubernetes resources. For more information about using the Kubernetes integration with Docker Desktop, -see [Deploy on Kubernetes](../kubernetes.md){:target="_blank" rel="noopener" class="_"}. +see [Deploy on Kubernetes](../kubernetes.md). ## Software Updates @@ -292,11 +292,11 @@ For more information about Docker extensions, see [Extensions](../extensions/ind On the **Feature control** tab you can control your settings for **Beta features** and **Experimental features**. -You can also sign up to the [Developer Preview Program](https://www.docker.com/community/get-involved/developer-preview/){:target="_blank" rel="noopener" class="_"} from the **Features in development** tab. +You can also sign up to the [Developer Preview Program](https://www.docker.com/community/get-involved/developer-preview/) from the **Features in development** tab. ### Beta features -{% include beta.md %} +{{< include "beta.md" >}} #### Use containerd for pulling and storing images @@ -304,4 +304,4 @@ Turns on the containerd image store. This brings new features like faster contai ### Experimental features -{% include desktop-experimental.md %} +{{< include "desktop-experimental.md" >}} \ No newline at end of file diff --git a/content/desktop/support.md b/content/desktop/support.md index 00329af67e..c6af82c9db 100644 --- a/content/desktop/support.md +++ b/content/desktop/support.md @@ -15,7 +15,7 @@ Find information on how to get support, and the scope of Docker Desktop support. ### How do I get Docker Desktop support? -If you have a paid Docker subscription, raise a ticket through [Docker Desktop support](https://hub.docker.com/support/desktop/){:target="_blank" rel="noopener" class="_"}. +If you have a paid Docker subscription, raise a ticket through [Docker Desktop support](https://hub.docker.com/support/desktop/). Docker Community users can get support through our Github repos for-win, for-mac, for-linux, where we respond on a best-effort basis. @@ -86,4 +86,4 @@ employees who are directly involved in diagnosing Docker Desktop issues. By default, Docker, Inc. will delete uploaded diagnostics bundles after 30 days. You may also request the removal of a diagnostics bundle by either specifying the diagnostics ID or via your GitHub ID (if the diagnostics ID is mentioned in a GitHub issue). Docker, Inc. will only use the data in the diagnostics bundle to investigate specific user issues but may derive high-level (non personal) metrics such as the rate of issues from it. -For more information, see [Docker Data Processing Agreement](https://www.docker.com/legal/data-processing-agreement){: target="_blank" rel="noopener" class="_"}. +For more information, see [Docker Data Processing Agreement](https://www.docker.com/legal/data-processing-agreement). \ No newline at end of file diff --git a/content/desktop/troubleshoot/known-issues.md b/content/desktop/troubleshoot/known-issues.md index 957b406148..49429ee3c1 100644 --- a/content/desktop/troubleshoot/known-issues.md +++ b/content/desktop/troubleshoot/known-issues.md @@ -9,7 +9,7 @@ title: Known issues * IPv6 is not yet supported on Docker Desktop. {{< /tab >}} {{< tab name="For Mac with Intel chip" >}} -* The Mac Activity Monitor reports that Docker is using twice the amount of memory it's actually using. This is due to a bug in MacOS. We have written [a detailed report](https://docs.google.com/document/d/17ZiQC1Tp9iH320K-uqVLyiJmk4DHJ3c4zgQetJiKYQM/edit?usp=sharing){:target="_blank" rel="noopener" class="_"} on this. +* The Mac Activity Monitor reports that Docker is using twice the amount of memory it's actually using. This is due to a bug in MacOS. We have written [a detailed report](https://docs.google.com/document/d/17ZiQC1Tp9iH320K-uqVLyiJmk4DHJ3c4zgQetJiKYQM/edit?usp=sharing) on this. * You might encounter errors when using `docker-compose up` with Docker Desktop (`ValueError: Extra Data`). We've identified this is likely related to data @@ -24,17 +24,17 @@ title: Known issues * Docker doesn't auto-start after sign in even when it's enabled in **Settings**. This is related to a set of issues with Docker helper, registration, and versioning. * Docker Desktop uses the `HyperKit` hypervisor - (https://github.com/docker/hyperkit){:target="_blank" rel="noopener" class="_"} in macOS 10.10 Yosemite and higher. If + (https://github.com/docker/hyperkit) in macOS 10.10 Yosemite and higher. If you are developing with tools that have conflicts with `HyperKit`, such as [Intel Hardware Accelerated Execution Manager - (HAXM)](https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager/){:target="_blank" rel="noopener" class="_"}, + (HAXM)](https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager/), the current workaround is not to run them at the same time. You can pause `HyperKit` by quitting Docker Desktop temporarily while you work with HAXM. This allows you to continue work with the other tools and prevent `HyperKit` from interfering. * If you are working with applications like [Apache - Maven](https://maven.apache.org/){:target="_blank" rel="noopener" class="_"} that expect settings for `DOCKER_HOST` and + Maven](https://maven.apache.org/) that expect settings for `DOCKER_HOST` and `DOCKER_CERT_PATH` environment variables, specify these to connect to Docker instances through Unix sockets. For example: @@ -54,7 +54,7 @@ title: Known issues - Symfony - Magento - Zend Framework - - PHP applications that use [Composer](https://getcomposer.org){:target="_blank" rel="noopener" class="_"} to install + - PHP applications that use [Composer](https://getcomposer.org) to install dependencies in a `vendor` folder As a workaround for this behavior, you can put vendor or third-party library @@ -62,7 +62,7 @@ title: Known issues outside of bind mounts, and use third-party tools like Unison or `rsync` to synchronize between container directories and bind-mounted directories. We are actively working on performance improvements using a number of different - techniques. To learn more, see the [topic on our roadmap](https://github.com/docker/roadmap/issues/7){: target="_blank" rel="noopener" class="_" }. + techniques. To learn more, see the [topic on our roadmap](https://github.com/docker/roadmap/issues/7). {{< /tab >}} {{< tab name="For Mac with Apple silicon" >}} - On Apple silicon in native `arm64` containers, older versions of `libssl` such as `debian:buster`, `ubuntu:20.04`, and `centos:8` will segfault when connected to some TLS servers, for example, `curl https://dl.yarnpkg.com`. The bug is fixed in newer versions of `libssl` in `debian:bullseye`, `ubuntu:21.04`, and `fedora:35`. @@ -73,8 +73,8 @@ title: Known issues However, attempts to run Intel-based containers on Apple silicon machines under emulation can crash as qemu sometimes fails to run the container. In addition, filesystem change notification APIs (`inotify`) do not work under qemu emulation. Even when the containers do run correctly under emulation, they will be slower and use more memory than the native equivalent. - In summary, running Intel-based containers on Arm-based machines should be regarded as "best effort" only. We recommend running arm64 containers on Apple silicon machines whenever possible, and encouraging container authors to produce arm64, or multi-arch, versions of their containers. This issue should become less common over time, as more and more images are rebuilt [supporting multiple architectures](https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/){:target="_blank" rel="noopener" class="_"}. -- `ping` from inside a container to the Internet does not work as expected. To test the network, use `curl` or `wget`. See [docker/for-mac#5322](https://github.com/docker/for-mac/issues/5322#issuecomment-809392861){:target="_blank" rel="noopener" class="_"}. + In summary, running Intel-based containers on Arm-based machines should be regarded as "best effort" only. We recommend running arm64 containers on Apple silicon machines whenever possible, and encouraging container authors to produce arm64, or multi-arch, versions of their containers. This issue should become less common over time, as more and more images are rebuilt [supporting multiple architectures](https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/). +- `ping` from inside a container to the Internet does not work as expected. To test the network, use `curl` or `wget`. See [docker/for-mac#5322](https://github.com/docker/for-mac/issues/5322#issuecomment-809392861). - Users may occasionally experience data drop when a TCP stream is half-closed. {{< /tab >}} -{{< /tabs >}} +{{< /tabs >}} \ No newline at end of file diff --git a/content/desktop/troubleshoot/overview.md b/content/desktop/troubleshoot/overview.md index 9bb4f4f7a9..055c87777e 100644 --- a/content/desktop/troubleshoot/overview.md +++ b/content/desktop/troubleshoot/overview.md @@ -1,9 +1,10 @@ --- -description: Understand how to diagnose and troubleshoot Docker Desktop, and how to check the logs. +description: Understand how to diagnose and troubleshoot Docker Desktop, and how to + check the logs. keywords: Linux, Mac, Windows, troubleshooting, logs, issues, Docker Desktop toc_max: 2 title: Troubleshoot Docker Desktop -redirect_from: +aliases: - /desktop/linux/troubleshoot/ - /desktop/mac/troubleshoot/ - /desktop/windows/troubleshoot/ @@ -27,10 +28,10 @@ This page contains information on how to diagnose and troubleshoot Docker Deskto To navigate to **Troubleshoot** either: -- Select the Docker menu ![whale menu](../images/whale-x.svg){: .inline} and then **Troubleshoot** +- Select the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Troubleshoot** - Select the **Troubleshoot** icon near the top-right corner of Docker Dashboard -![Troubleshoot menu in Docker Desktop](../images/troubleshoot.png){:width="600px"} +![Troubleshoot menu in Docker Desktop](../images/troubleshoot.png) The **Troubleshoot** page contains the following options: @@ -54,11 +55,11 @@ If you are a Mac or Linux user, you also have the option to **Uninstall** Docker 1. From **Troubleshoot**, select **Get support**. This opens the in-app **Support** page and starts collecting the diagnostics. - ![Diagnose & Feedback](../images/diagnose-support.png){:width="600px"} + ![Diagnose & Feedback](../images/diagnose-support.png) 2. When the diagnostics collection process is complete, select **Upload to get a Diagnostic ID**. 3. When the diagnostics are uploaded, Docker Desktop prints a diagnostic ID. Copy this ID. 4. Use your diagnostics ID to get help: - - If you have a paid Docker subscription, select **Contact Support**. This opens the [Docker Desktop support](https://hub.docker.com/support/desktop/){:target="_blank" rel="noopener" class="_"} form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID** field. Then, select **Submit** to request Docker Desktop support. + - If you have a paid Docker subscription, select **Contact Support**. This opens the [Docker Desktop support](https://hub.docker.com/support/desktop/) form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID** field. Then, select **Submit** to request Docker Desktop support. > **Note** > > You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/index.md). @@ -163,13 +164,13 @@ $ unzip –l /tmp/.zip #### Use your diagnostics ID to get help -If you have a paid Docker subscription, open the [Docker Desktop support](https://hub.docker.com/support/desktop/){:target="_blank" rel="noopener" class="_"} form. Fill in the information required and add the ID to the Diagnostics ID field. Make sure you provide the full diagnostics ID, and not just the user ID. Select **Submit** to request Docker Desktop support. +If you have a paid Docker subscription, open the [Docker Desktop support](https://hub.docker.com/support/desktop/) form. Fill in the information required and add the ID to the Diagnostics ID field. Make sure you provide the full diagnostics ID, and not just the user ID. Select **Submit** to request Docker Desktop support. If you don't have a paid Docker subscription, create an issue on GitHub: -- [For Linux](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"} -- [For Mac](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"} -- [For Windows](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"} +- [For Linux](https://github.com/docker/desktop-linux/issues) +- [For Mac](https://github.com/docker/for-mac/issues) +- [For Windows](https://github.com/docker/for-win/issues) ### Self-diagnose tool @@ -222,9 +223,9 @@ The tool runs a suite of checks and displays **PASS** or **FAIL** next to each c You can then create an issue on GitHub: -- [For Linux](https://github.com/docker/desktop-linux/issues){:target="_blank" rel="noopener" class="_"} -- [For Mac](https://github.com/docker/for-mac/issues){:target="_blank" rel="noopener" class="_"} -- [For Windows](https://github.com/docker/for-win/issues){:target="_blank" rel="noopener" class="_"} +- [For Linux](https://github.com/docker/desktop-linux/issues) +- [For Mac](https://github.com/docker/for-mac/issues) +- [For Windows](https://github.com/docker/for-win/issues) ## Check the logs @@ -298,4 +299,4 @@ to learn how to view the Docker Daemon logs. - View specific [troubleshoot topics](topics.md). - Implement [workarounds for common problems](workarounds.md) -- View information on [known issues](known-issues.md) +- View information on [known issues](known-issues.md) \ No newline at end of file diff --git a/content/desktop/troubleshoot/topics.md b/content/desktop/troubleshoot/topics.md index a0ef4abd7a..a2feac4b1d 100644 --- a/content/desktop/troubleshoot/topics.md +++ b/content/desktop/troubleshoot/topics.md @@ -59,7 +59,7 @@ Following are the examples of errors on MacOS which indicate that the startup fa Docker Desktop requires a processor (CPU) that supports virtualization and, more specifically, the [Apple Hypervisor -framework](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/){:target="_blank" rel="noopener" class="_"}. +framework](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/). Docker Desktop is only compatible with Mac systems that have a CPU that supports the Hypervisor framework. Most Macs built in 2010 and later support it,as described in the Apple Hypervisor Framework documentation about supported hardware: *Generally, machines with an Intel VT-x feature set that includes Extended Page @@ -77,7 +77,7 @@ If your Mac supports the Hypervisor Framework, the command prints If not, the command prints `kern.hv_support: 0`. See also, [Hypervisor Framework -Reference](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/){:target="_blank" rel="noopener" class="_"} +Reference](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/) in the Apple documentation, and Docker Desktop [Mac system requirements](../install/mac-install.md#system-requirements). ### VPNKit keeps breaking @@ -93,7 +93,7 @@ To continue using VPNKit, add `"networkType":"vpnkit"` to your `settings.json` f #### Permissions errors on data directories for shared volumes When sharing files from Windows, Docker Desktop sets permissions on [shared volumes](../settings/windows.md#file-sharing) -to a default value of [0777](https://chmodcommand.com/chmod-0777/){:target="_blank" rel="noopener" class="_"} +to a default value of [0777](https://chmodcommand.com/chmod-0777/) (`read`, `write`, `execute` permissions for `user` and for `group`). The default permissions on shared volumes are not configurable. If you are @@ -136,7 +136,7 @@ are used, `docker run` fails with syntax errors. For an example of this issue and the resolution, see this issue on GitHub: [Docker RUN fails to execute shell -script](https://github.com/moby/moby/issues/24388){:target="_blank" rel="noopener" class="_"}. +script](https://github.com/moby/moby/issues/24388). #### Path conversion on Windows @@ -233,30 +233,30 @@ Your machine must have the following features for Docker Desktop to function cor #### WSL 2 and Windows Home 1. Virtual Machine Platform -2. [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/install-win10){:target="_blank" rel="noopener" class="_"} -3. [Virtualization enabled in the BIOS](https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html){:target="_blank" rel="noopener" class="_"} +2. [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/install-win10) +3. [Virtualization enabled in the BIOS](https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html) 4. Hypervisor enabled at Windows startup -![WSL 2 enabled](../images/wsl2-enabled.png){:width="600px"} +![WSL 2 enabled](../images/wsl2-enabled.png) #### Hyper-V On Windows 10 Pro or Enterprise, you can also use Hyper-V with the following features enabled: -1. [Hyper-V](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview){:target="_blank" rel="noopener" class="_"} +1. [Hyper-V](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview) installed and working -2. [Virtualization enabled in the BIOS](https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html){:target="_blank" rel="noopener" class="_"} +2. [Virtualization enabled in the BIOS](https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html) 3. Hypervisor enabled at Windows startup -![Hyper-V on Windows features](../images/hyperv-enabled.png){:width="600px"} +![Hyper-V on Windows features](../images/hyperv-enabled.png) Docker Desktop requires Hyper-V as well as the Hyper-V Module for Windows PowerShell to be installed and enabled. The Docker Desktop installer enables it for you. -Docker Desktop also needs two CPU hardware features to use Hyper-V: Virtualization and Second Level Address Translation (SLAT), which is also called Rapid Virtualization Indexing (RVI). On some systems, Virtualization must be enabled in the BIOS. The steps required are vendor-specific, but typically the BIOS option is called `Virtualization Technology (VTx)` or something similar. Run the command `systeminfo` to check all required Hyper-V features. See [Pre-requisites for Hyper-V on Windows 10](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements){:target="_blank" rel="noopener" class="_"} for more details. +Docker Desktop also needs two CPU hardware features to use Hyper-V: Virtualization and Second Level Address Translation (SLAT), which is also called Rapid Virtualization Indexing (RVI). On some systems, Virtualization must be enabled in the BIOS. The steps required are vendor-specific, but typically the BIOS option is called `Virtualization Technology (VTx)` or something similar. Run the command `systeminfo` to check all required Hyper-V features. See [Pre-requisites for Hyper-V on Windows 10](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/hyper-v-requirements) for more details. -To install Hyper-V manually, see [Install Hyper-V on Windows 10](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install){:target="_blank" rel="noopener" class="_"}. A reboot is *required* after installation. If you install Hyper-V without rebooting, Docker Desktop does not work correctly. +To install Hyper-V manually, see [Install Hyper-V on Windows 10](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install). A reboot is *required* after installation. If you install Hyper-V without rebooting, Docker Desktop does not work correctly. From the start menu, type **Turn Windows features on or off** and press enter. In the subsequent screen, verify that Hyper-V is enabled. @@ -266,12 +266,12 @@ In the subsequent screen, verify that Hyper-V is enabled. In addition to [Hyper-V](#hyper-v) or [WSL 2](../wsl/index.md), virtualization must be turned on. Check the Performance tab on the Task Manager: -![Task Manager](../images/virtualization-enabled.png){:width="700px"} +![Task Manager](../images/virtualization-enabled.png) If you manually uninstall Hyper-V, WSL 2 or turn off virtualization, Docker Desktop cannot start. -To turn on nested virtualisation, see [Run Docker Desktop for Windows in a VM or VDI environment](../vm-vdi.md#turn-on-nested-virtualization){:target="_blank" rel="noopener" class="_"}. +To turn on nested virtualisation, see [Run Docker Desktop for Windows in a VM or VDI environment](../vm-vdi.md#turn-on-nested-virtualization). #### Hypervisor enabled at Windows startup @@ -284,7 +284,7 @@ Virtual Box) and video game installers turn off hypervisor on boot. To turn it b 2. Run `bcdedit /set hypervisorlaunchtype auto`. 3. Restart Windows. -You can also refer to the [Microsoft TechNet article](https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt){:target="_blank" rel="noopener" class="_"} on Code flow guard (CFG) settings. +You can also refer to the [Microsoft TechNet article](https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt) on Code flow guard (CFG) settings. #### Turn on nested virtualization @@ -294,7 +294,7 @@ If you are using Hyper-V and you get the following error message when running Do The Virtual Machine Management Service failed to start the virtual machine 'DockerDesktopVM' because one of the Hyper-V components is not running ``` -Try [enabling nested virtualization](../vm-vdi.md#turn-on-nested-virtualization){:target="_blank" rel="noopener" class="_"}. +Try [enabling nested virtualization](../vm-vdi.md#turn-on-nested-virtualization). ### Windows containers and Windows Server @@ -302,8 +302,8 @@ Try [enabling nested virtualization](../vm-vdi.md#turn-on-nested-virtualization) Docker Desktop is not supported on Windows Server. If you have questions about how to run Windows containers on Windows 10, see [Switch between Windows and Linux containers](../faqs/windowsfaqs.md#how-do-i-switch-between-windows-and-linux-containers). -A full tutorial is available in [docker/labs](https://github.com/docker/labs){:target="_blank" rel="noopener" class="_"} on -[Getting Started with Windows Containers](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md){:target="_blank" rel="noopener" class="_"}. +A full tutorial is available in [docker/labs](https://github.com/docker/labs) on +[Getting Started with Windows Containers](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md). You can install a native Windows binary which allows you to develop and run Windows containers without Docker Desktop. However, if you install Docker this way, you cannot develop or run Linux containers. If you try to run a Linux container on the native Docker daemon, an error occurs: @@ -312,4 +312,4 @@ Windows containers without Docker Desktop. However, if you install Docker this w C:\Program Files\Docker\docker.exe: image operating system "linux" cannot be used on this platform. See 'C:\Program Files\Docker\docker.exe run --help'. -``` +``` \ No newline at end of file diff --git a/content/desktop/troubleshoot/workarounds.md b/content/desktop/troubleshoot/workarounds.md index 515244aec9..50feb4ad06 100644 --- a/content/desktop/troubleshoot/workarounds.md +++ b/content/desktop/troubleshoot/workarounds.md @@ -44,4 +44,4 @@ typically occurs after a Windows update and manifests as an error response from the Docker daemon and a Docker Desktop start failure. For a temporary workaround, uninstall the anti-virus software, or -explore other workarounds suggested on Docker Desktop forums. +explore other workarounds suggested on Docker Desktop forums. \ No newline at end of file diff --git a/content/desktop/uninstall.md b/content/desktop/uninstall.md index dacb41380b..2df7eca97f 100644 --- a/content/desktop/uninstall.md +++ b/content/desktop/uninstall.md @@ -1,5 +1,5 @@ --- -description: How to uninstall Docker Desktop +description: How to uninstall Docker Desktop keywords: Windows, unintall, Mac, Linux, Docker Desktop title: Uninstall Docker Desktop --- @@ -19,7 +19,7 @@ To uninstall Docker Desktop from your Windows machine: > other Docker related data local to the machine, and removes the files generated > by the application. Refer to the [back up and restore data](backup-and-restore.md) > section to learn how to preserve important data before uninstalling. -{: .important } +{ .important } {{< /tab >}} {{< tab name="Mac" >}} @@ -136,7 +136,7 @@ Remove the `credsStore` and `currentContext` properties from `$HOME/.docker/conf > other Docker related data local to the machine, and removes the files generated > by the application. Refer to the [back up and restore data](backup-and-restore.md) > section to learn how to preserve important data before uninstalling. -{: .important} +{ .important } {{< /tab >}} -{{< /tabs >}} +{{< /tabs >}} \ No newline at end of file diff --git a/content/desktop/use-desktop/_index.md b/content/desktop/use-desktop/_index.md index a616cda6e4..88c4e3448b 100644 --- a/content/desktop/use-desktop/_index.md +++ b/content/desktop/use-desktop/_index.md @@ -1,14 +1,15 @@ --- description: Understand what you can do with Docker Dashboard -keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual, whale menu +keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual, + whale menu title: Explore Docker Desktop -redirect_from: +aliases: - /desktop/dashboard/ --- When you open Docker Desktop, the Docker Dashboard displays. -![Docker Dashboard on Containers view](../images/dashboard.PNG){:width="750px"} +![Docker Dashboard on Containers view](../images/dashboard.PNG) The **Containers** view provides a runtime view of all your containers and applications. It allows you to interact with containers and applications, and manage the lifecycle of your applications directly from your machine. This view also provides an intuitive interface to perform common actions to inspect, interact with, and manage your Docker objects including containers and Docker Compose-based applications. For more information, see [Explore running containers and applications](container.md). @@ -44,9 +45,9 @@ From the Docker Dashboard you can use Quick Search, which is located in the Dash ## The Docker menu -Docker Desktop also provides an easy-access tray icon that appears in the taskbar and is referred to as the Docker menu ![whale menu](../../assets/images/whale-x.svg){: .inline}. +Docker Desktop also provides an easy-access tray icon that appears in the taskbar and is referred to as the Docker menu {{< inline-image src="../../assets/images/whale-x.svg" alt="whale menu" >}}. -To display the Docker menu, select the ![whale menu](../../assets/images/whale-x.svg){: .inline} icon. It displays the following options: +To display the Docker menu, select the {{< inline-image src="../../assets/images/whale-x.svg" alt="whale menu" >}} icon. It displays the following options: - **Dashboard**. This takes you to the Docker Dashboard. - **Sign in/Create Docker ID** @@ -63,4 +64,4 @@ To display the Docker menu, select the ![whale menu](../../assets/images/whale-x - **Kubernetes** - **Pause** - **Restart** -- **Quit Docker Desktop** +- **Quit Docker Desktop** \ No newline at end of file diff --git a/content/desktop/use-desktop/builds.md b/content/desktop/use-desktop/builds.md index b632c10b1a..7320eab749 100644 --- a/content/desktop/use-desktop/builds.md +++ b/content/desktop/use-desktop/builds.md @@ -12,7 +12,7 @@ displays a list of all your ongoing and completed builds. > > The **Builds** view is currently in [Beta](../../release-lifecycle.md/#beta). > This feature may change or be removed from future releases. -{: .experimental } +{ .experimental } The **Builds** view displays metadata about the build, such as: @@ -70,5 +70,4 @@ To inspect your builders, and change your default builder, select - [Change settings, Windows](../settings/windows.md#builders) - [Change settings, Mac](../settings/mac.md#builders) -- [Change settings, Linux](../settings/linux.md#builders) - +- [Change settings, Linux](../settings/linux.md#builders) \ No newline at end of file diff --git a/content/desktop/use-desktop/container.md b/content/desktop/use-desktop/container.md index 4e8242b491..f0246e1944 100644 --- a/content/desktop/use-desktop/container.md +++ b/content/desktop/use-desktop/container.md @@ -1,7 +1,7 @@ --- description: Understand what you can do with the Containers view on Docker Dashboard keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual -title: Explore the Containers view in Docker Desktop +title: Explore the Containers view in Docker Desktop --- The **Containers** view lists all your running containers and applications. You must have running or stopped containers and applications to see them listed. @@ -68,4 +68,4 @@ To use your external terminal, navigate to the **General** tab in **Settings** a - Edit a file straight from the built-in editor - Drag and drop files and folders between the host and the container - Delete unnecessary files when you right-click on a file - - Download file and folders from the container straight to the host + - Download file and folders from the container straight to the host \ No newline at end of file diff --git a/content/desktop/use-desktop/images.md b/content/desktop/use-desktop/images.md index 4f03d4ac14..2a28696f35 100644 --- a/content/desktop/use-desktop/images.md +++ b/content/desktop/use-desktop/images.md @@ -143,5 +143,4 @@ To connect a new Artifactory registry to Docker Desktop: 3. Select the **Artifactory** tab near the top of the image view to see Artifactory images. When signed in, a new **Artifactory** tab appears in the **Images** view. -By default, the image list shows images sorted by push date: the newest images appear higher in the list. - +By default, the image list shows images sorted by push date: the newest images appear higher in the list. \ No newline at end of file diff --git a/content/desktop/use-desktop/pause.md b/content/desktop/use-desktop/pause.md index b79f886b65..11ac3d072a 100644 --- a/content/desktop/use-desktop/pause.md +++ b/content/desktop/use-desktop/pause.md @@ -8,7 +8,7 @@ When Docker Desktop is paused, the Linux VM running Docker Engine is paused, the You can either manually pause Docker Desktop or turn on the Resource Saver feature which automatically pauses Docker Desktop when no container is running. -You can manually pause Docker Desktop by selecting the Docker menu ![whale menu](../images/whale-x.svg){: .inline} and then **Pause**. To manually resume Docker Desktop, select the **Resume** option in the Docker menu, or run any Docker CLI command. +You can manually pause Docker Desktop by selecting the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Pause**. To manually resume Docker Desktop, select the **Resume** option in the Docker menu, or run any Docker CLI command. When you manually pause Docker Desktop, a paused status displays on the Docker menu and on the Docker Dashboard. You can still access the **Settings** and the **Troubleshoot** menu. @@ -17,4 +17,4 @@ When Resource Saver kicks in, a leaf icon display on the Docker menu. > **Important** > >Resource Saver is currently an experimental feature. To access this feature, make sure you have turned on access to experimental features in settings. -{: .important} \ No newline at end of file +{ .important } \ No newline at end of file diff --git a/content/desktop/vm-vdi.md b/content/desktop/vm-vdi.md index 5df5bb6265..000a8747ca 100644 --- a/content/desktop/vm-vdi.md +++ b/content/desktop/vm-vdi.md @@ -2,7 +2,7 @@ description: Instructions on how to enable nested virtualization keywords: nested virtualization, Docker Desktop, windows, VM, VDI environment title: Run Docker Desktop for Windows in a VM or VDI environment -redirect_from: +aliases: - /desktop/nested-virtualization/ --- @@ -26,13 +26,13 @@ You must turn on nested virtualization before you install Docker Desktop on a vi ### Turn on nested virtualization on VMware ESXi -Nested virtualization of other hypervisors like Hyper-V inside a vSphere VM [is not a supported scenario](https://kb.vmware.com/s/article/2009916){:target="_blank" rel="noopener" class="_"}. However, running Hyper-V VM in a VMware ESXi VM is technically possible and, depending on the version, ESXi includes hardware-assisted virtualization as a supported feature. For internal testing, we used a VM that had 1 CPU with 4 cores and 12GB of memory. +Nested virtualization of other hypervisors like Hyper-V inside a vSphere VM [is not a supported scenario](https://kb.vmware.com/s/article/2009916). However, running Hyper-V VM in a VMware ESXi VM is technically possible and, depending on the version, ESXi includes hardware-assisted virtualization as a supported feature. For internal testing, we used a VM that had 1 CPU with 4 cores and 12GB of memory. -For steps on how to expose hardware-assisted virtualization to the guest OS, [see VMware's documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A98801C-68E8-47AF-99ED-00C63E4857F6.html){:target="_blank" rel="noopener" class="_"}. +For steps on how to expose hardware-assisted virtualization to the guest OS, [see VMware's documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A98801C-68E8-47AF-99ED-00C63E4857F6.html). ### Turn on nested virtualization on Microsoft Hyper-V Nested virtualization is supported by Microsoft for running Hyper-V inside an Azure VM. -For Azure virtual machines, [check that the VM size chosen supports nested virtualization](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes){:target="_blank" rel="noopener" class="_"}. Microsoft provides [a helpful list on Azure VM sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/acu){:target="_blank" rel="noopener" class="_"} and highlights the sizes that currently support nested virtualization. For internal testing, we used D4s_v5 machines. We recommend this specification or above for optimal performance of Docker Desktop. +For Azure virtual machines, [check that the VM size chosen supports nested virtualization](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes). Microsoft provides [a helpful list on Azure VM sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/acu) and highlights the sizes that currently support nested virtualization. For internal testing, we used D4s_v5 machines. We recommend this specification or above for optimal performance of Docker Desktop. \ No newline at end of file diff --git a/content/desktop/wasm/_index.md b/content/desktop/wasm/_index.md index 8b65a84aae..7c13f51c2a 100644 --- a/content/desktop/wasm/_index.md +++ b/content/desktop/wasm/_index.md @@ -10,12 +10,11 @@ toc_max: 3 > The Wasm feature is currently in [Beta](../../release-lifecycle.md/#beta). > We recommend that you do not use this feature in production environments as > this feature may change or be removed from future releases. -{: .experimental} +{ .experimental } Wasm (short for WebAssembly) is a fast, light alternative to the Linux and Windows containers you’re using in Docker today (with -[some tradeoffs](https://www.docker.com/blog/docker-wasm-technical-preview/){:target="_blank" -rel="noopener" class="_"}). +[some tradeoffs](https://www.docker.com/blog/docker-wasm-technical-preview/)). This page provides information about the new ability to run Wasm applications alongside your Linux containers in Docker. @@ -220,5 +219,4 @@ Update your Docker Desktop to the latest version and try again. Thanks for trying out Wasm workloads with Docker. Give feedback or report any bugs you may find through the issues tracker on the -[public roadmap item](https://github.com/docker/roadmap/issues/426){: -target="_blank" rel="noopener" class="_"}. +[public roadmap item](https://github.com/docker/roadmap/issues/426). \ No newline at end of file diff --git a/content/desktop/windows/permission-requirements.md b/content/desktop/windows/permission-requirements.md index 2aec16b42b..b736be54d2 100644 --- a/content/desktop/windows/permission-requirements.md +++ b/content/desktop/windows/permission-requirements.md @@ -2,7 +2,7 @@ description: Understand permission requirements for Docker Desktop for Windows keywords: Docker Desktop, Windows, security, install title: Understand permission requirements for Windows -redirect_from: +aliases: - /desktop/windows/privileged-helper/ --- @@ -48,4 +48,4 @@ Unlike the Linux Docker engine and containers which run in a VM, Windows contain ## Networking -For network connectivity, Docker Desktop uses a user-space process (`vpnkit`), which inherits constraints like firewall rules, VPN, HTTP proxy properties etc. from the user that launched it. +For network connectivity, Docker Desktop uses a user-space process (`vpnkit`), which inherits constraints like firewall rules, VPN, HTTP proxy properties etc. from the user that launched it. \ No newline at end of file diff --git a/content/desktop/wsl/_index.md b/content/desktop/wsl/_index.md index e30c5bd7bf..fbc423f291 100644 --- a/content/desktop/wsl/_index.md +++ b/content/desktop/wsl/_index.md @@ -1,11 +1,13 @@ --- -description: Turn on the Docker WSL 2 backend and get to work using best practices, GPU support, and more in this thorough guide. -keywords: wsl, wsl2, installing wsl2, wsl installation, docker wsl2, wsl docker, wsl2 tech preview, wsl install docker, install docker wsl, how to install docker in wsl -redirect_from: +description: Turn on the Docker WSL 2 backend and get to work using best practices, + GPU support, and more in this thorough guide. +keywords: wsl, wsl2, installing wsl2, wsl installation, docker wsl2, wsl docker, wsl2 + tech preview, wsl install docker, install docker wsl, how to install docker in wsl +title: Docker Desktop WSL 2 backend on Windows +aliases: - /docker-for-windows/wsl/ - /docker-for-windows/wsl-tech-preview/ - /desktop/windows/wsl/ -title: Docker Desktop WSL 2 backend on Windows --- Windows Subsystem for Linux (WSL) 2 is a full Linux kernel built by Microsoft, which lets Linux distributions run without managing virtual machines. With Docker Desktop running on WSL 2, users can leverage Linux workspaces and avoid maintaining both Linux and Windows build scripts. In addition, WSL 2 provides improvements to file system sharing and boot time. @@ -20,14 +22,14 @@ Before you turn on the Docker Desktop WSL 2 feature, ensure you have: - At a minimum WSL version 1.1.3.0., but ideally the latest version of WSL to [avoid Docker Desktop not working as expected](best-practices.md). - Windows 10, version 21H2 or later, or Windows 11, version 21H2 or later. For more information, see [System requirements](https://docs.docker.com/desktop/install/windows-install/#system-requirements). -- Installed the WSL 2 feature on Windows. For detailed instructions, refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10){:target="_blank" rel="noopener" class="_"}. +- Installed the WSL 2 feature on Windows. For detailed instructions, refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10). ## Turn on Docker Desktop WSL 2 > **Important** > > To avoid any potential conflicts with using WSL 2 on Docker Desktop, you must uninstall any previous versions of Docker Engine and CLI installed directly through Linux distributions before installing Docker Desktop. -{: .important} +{ .important } 1. Download and install the latest version of [Docker Desktop for Windows](https://desktop.docker.com/win/main/amd64/Docker%20Desktop%20Installer.exe). 2. Follow the usual installation instructions to install Docker Desktop. Depending on which version of Windows you are using, Docker Desktop may prompt you to turn on WSL 2 during installation. Read the information displayed on the screen and turn on the WSL 2 feature to continue. @@ -82,4 +84,4 @@ Docker Desktop does not require any particular Linux distros to be installed. Th ## Additional resources - [Explore best practices](best-practices.md) -- [Understand how to develop with Docker and WSL 2 and GPU support for WSL](use-wsl.md) +- [Understand how to develop with Docker and WSL 2 and GPU support for WSL](use-wsl.md) \ No newline at end of file diff --git a/content/desktop/wsl/best-practices.md b/content/desktop/wsl/best-practices.md index 453503d711..b4d8689fc2 100644 --- a/content/desktop/wsl/best-practices.md +++ b/content/desktop/wsl/best-practices.md @@ -1,6 +1,6 @@ --- title: Best practices -description: Best practices for using Docker Desktop with WSL 2 +description: Best practices for using Docker Desktop with WSL 2 keywords: wsl, docker desktop, best practices --- @@ -17,4 +17,4 @@ keywords: wsl, docker desktop, best practices - Instead, from a Linux shell use a command like `docker run -v ~/my-project:/sources ` where `~` is expanded by the Linux shell to `$HOME`. - If you have concerns about the size of the docker-desktop-data VHDX, or need to change it, take a look at the [WSL tooling built into Windows](https://learn.microsoft.com/en-us/windows/wsl/disk-space). -- If you have concerns about CPU or memory usage, you can configure limits on the memory, CPU, and swap size allocated to the [WSL 2 utility VM](https://learn.microsoft.com/en-us/windows/wsl/wsl-config#global-configuration-options-with-wslconfig). +- If you have concerns about CPU or memory usage, you can configure limits on the memory, CPU, and swap size allocated to the [WSL 2 utility VM](https://learn.microsoft.com/en-us/windows/wsl/wsl-config#global-configuration-options-with-wslconfig). \ No newline at end of file diff --git a/content/desktop/wsl/use-wsl.md b/content/desktop/wsl/use-wsl.md index ff86698369..f35f74779f 100644 --- a/content/desktop/wsl/use-wsl.md +++ b/content/desktop/wsl/use-wsl.md @@ -6,9 +6,9 @@ keywords: wsl, wsl 2, gpu support, develop, docker desktop, windows ## Develop with Docker and WSL 2 -The following section describes how to start developing your applications using Docker and WSL 2. We recommend that you have your code in your default Linux distribution for the best development experience using Docker and WSL 2. After you have turned on the WSL 2 feature on Docker Desktop, you can start working with your code inside the Linux distro and ideally with your IDE still in Windows. This workflow is straightforward if you are using [VS Code](https://code.visualstudio.com/download){:target="_blank" rel="noopener" class="_"}. +The following section describes how to start developing your applications using Docker and WSL 2. We recommend that you have your code in your default Linux distribution for the best development experience using Docker and WSL 2. After you have turned on the WSL 2 feature on Docker Desktop, you can start working with your code inside the Linux distro and ideally with your IDE still in Windows. This workflow is straightforward if you are using [VS Code](https://code.visualstudio.com/download). -1. Open VS Code and install the [Remote - WSL](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl){:target="_blank" rel="noopener" class="_"} extension. This extension lets you to work with a remote server in the Linux distro and your IDE client still on Windows. +1. Open VS Code and install the [Remote - WSL](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl) extension. This extension lets you to work with a remote server in the Linux distro and your IDE client still on Windows. 2. Start working in VS Code remotely. To do this, open your terminal and type: ```console @@ -34,7 +34,7 @@ With Docker Desktop version 3.1.0 and later, WSL 2 GPU Paravirtualization (GPU- - A machine with an NVIDIA GPU - The latest Windows Insider version from the Dev Preview ring -- [Beta drivers](https://developer.nvidia.com/cuda/wsl){:target="_blank" rel="noopener" class="_"} from NVIDIA supporting WSL 2 GPU Paravirtualization +- [Beta drivers](https://developer.nvidia.com/cuda/wsl) from NVIDIA supporting WSL 2 GPU Paravirtualization - Update WSL 2 Linux kernel to the latest version using `wsl --update` from an elevated command prompt - Make sure the WSL 2 backend is turned on in Docker Desktop @@ -71,4 +71,4 @@ GPU Device 0: "GeForce RTX 2060 with Max-Q Design" with compute capability 7.5 30720 bodies, total time for 10 iterations: 69.280 ms = 136.219 billion interactions per second = 2724.379 single-precision GFLOP/s at 20 flops per interaction -``` +``` \ No newline at end of file diff --git a/content/develop/_index.md b/content/develop/_index.md index aa9b33f4d6..541cdc959f 100644 --- a/content/develop/_index.md +++ b/content/develop/_index.md @@ -16,20 +16,20 @@ If you're just getting started developing a brand new app on Docker, check out these resources to understand some of the most common patterns for getting the most benefits from Docker. -- Learn how to [build an image](../engine/reference/builder.md){: target="_blank" rel="noopener" class="_"} using a Dockerfile +- Learn how to [build an image](../engine/reference/builder.md) using a Dockerfile - Use [multi-stage builds](../build/building/multi-stage.md) to keep your images lean -- Manage application data using [volumes](../storage/volumes.md) and [bind mounts](../storage/bind-mounts.md){: target="_blank" rel="noopener" class="_"} -- [Scale your app with Kubernetes](../get-started/kube-deploy.md){: target="_blank" rel="noopener" class="_"} -- [Scale your app as a Swarm service](../get-started/swarm-deploy.md){: target="_blank" rel="noopener" class="_"} -- [General application development best practices](dev-best-practices.md){: target="_blank" rel="noopener" class="_"} +- Manage application data using [volumes](../storage/volumes.md) and [bind mounts](../storage/bind-mounts.md) +- [Scale your app with Kubernetes](../get-started/kube-deploy.md) +- [Scale your app as a Swarm service](../get-started/swarm-deploy.md) +- [General application development best practices](dev-best-practices.md) ## Learn about language-specific app development with Docker -- [Docker for Java developers lab](https://github.com/docker/labs/tree/master/developer-tools/java/){: target="_blank" rel="noopener" class="_"} -- [Port a node.js app to Docker lab](https://github.com/docker/labs/tree/master/developer-tools/nodejs/porting){: target="_blank" rel="noopener" class="_"} -- [Ruby on Rails app on Docker lab](https://github.com/docker/labs/tree/master/developer-tools/ruby){: target="_blank" rel="noopener" class="_"} -- [Dockerize a .Net Core application](../language/dotnet/index.md){: target="_blank" rel="noopener" class="_"} -- [ASP.NET Core application with SQL Server](https://github.com/docker/awesome-compose/tree/master/aspnet-mssql){: target="_blank" rel="noopener" class="_"} using Docker Compose +- [Docker for Java developers lab](https://github.com/docker/labs/tree/master/developer-tools/java/) +- [Port a node.js app to Docker lab](https://github.com/docker/labs/tree/master/developer-tools/nodejs/porting) +- [Ruby on Rails app on Docker lab](https://github.com/docker/labs/tree/master/developer-tools/ruby) +- [Dockerize a .Net Core application](../language/dotnet/index.md) +- [ASP.NET Core application with SQL Server](https://github.com/docker/awesome-compose/tree/master/aspnet-mssql) using Docker Compose ## Advanced development with the SDK or API @@ -37,4 +37,4 @@ After you can write Dockerfiles or Compose files and use Docker CLI, take it to the next level by using Docker Engine SDK for Go/Python or use the HTTP API directly. Visit the [Develop with Docker Engine API](../engine/api/index.md) section to learn more about developing with the Engine API, where to find SDKs -for your programming language of choice, and to see some examples. +for your programming language of choice, and to see some examples. \ No newline at end of file diff --git a/content/develop/dev-best-practices.md b/content/develop/dev-best-practices.md index cd337393e0..7d936c437c 100644 --- a/content/develop/dev-best-practices.md +++ b/content/develop/dev-best-practices.md @@ -7,7 +7,7 @@ keywords: application, development The following development patterns have proven to be helpful for people building applications with Docker. If you have discovered something we should add, -[let us know]({{ site.repo }}/issues/new?template=doc_issue.yml&labels=status%2Ftriage){: target="_blank" rel="noopener" class="_"}. +[let us know]({{% param "repo" %}}/issues/new?template=doc_issue.yml&labels=status%2Ftriage). ## How to keep your images small @@ -97,4 +97,4 @@ keep image size small: |:--------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Use bind mounts to give your container access to your source code. | Use volumes to store container data. | | Use Docker Desktop for Mac or Docker Desktop for Windows. | Use Docker Engine, if possible with [userns mapping](../engine/security/userns-remap.md) for greater isolation of Docker processes from host processes. | -| Don't worry about time drift. | Always run an NTP client on the Docker host and within each container process and sync them all to the same NTP server. If you use swarm services, also ensure that each Docker node syncs its clocks to the same time source as the containers. | +| Don't worry about time drift. | Always run an NTP client on the Docker host and within each container process and sync them all to the same NTP server. If you use swarm services, also ensure that each Docker node syncs its clocks to the same time source as the containers. | \ No newline at end of file diff --git a/content/develop/develop-images/dockerfile_best-practices.md b/content/develop/develop-images/dockerfile_best-practices.md index b14207a4b8..714c146a0b 100644 --- a/content/develop/develop-images/dockerfile_best-practices.md +++ b/content/develop/develop-images/dockerfile_best-practices.md @@ -1,13 +1,13 @@ --- description: Hints, tips and guidelines for writing clean, reliable Dockerfiles keywords: parent image, images, dockerfile, best practices, hub, official image -redirect_from: +title: Best practices for writing Dockerfiles +aliases: - /articles/dockerfile_best-practices/ - /engine/articles/dockerfile_best-practices/ - /docker-cloud/getting-started/intermediate/optimize-dockerfiles/ - /docker-cloud/tutorials/optimize-dockerfiles/ - /engine/userguide/eng-image/dockerfile_best-practices/ -title: Best practices for writing Dockerfiles --- This topic covers recommended best practices and methods for building @@ -237,7 +237,7 @@ A Dockerfile for a Go application could look like: ```dockerfile # syntax=docker/dockerfile:1 -FROM golang:{{site.example_go_version}}-alpine AS build +FROM golang:{{% param "example_go_version" %}}-alpine AS build # Install tools required for project # Run `docker build --no-cache .` to update dependencies @@ -890,5 +890,5 @@ These Official Images have exemplary Dockerfiles: * [Dockerfile Reference](../../engine/reference/builder.md) * [More about Automated Builds](../../docker-hub/builds/index.md) * [Guidelines for Creating Docker Official Images](../../docker-hub/official_images.md) -* [Best practices to containerize Node.js web applications with Docker](https://snyk.io/blog/10-best-practices-to-containerize-nodejs-web-applications-with-docker){:target="_blank" rel="noopener" class="_"} -* [More about Base Images](../../build/building/base-images.md) +* [Best practices to containerize Node.js web applications with Docker](https://snyk.io/blog/10-best-practices-to-containerize-nodejs-web-applications-with-docker) +* [More about Base Images](../../build/building/base-images.md) \ No newline at end of file diff --git a/content/develop/remote-development.md b/content/develop/remote-development.md index f0b6e045be..e6fd0642d7 100644 --- a/content/develop/remote-development.md +++ b/content/develop/remote-development.md @@ -32,11 +32,11 @@ remote resources helps simplify and speed up the inner loop. There are several tools available, commercial and open-source, that you can use to enable a hybrid local-and-remote development environment. For example: -- [Telepresence](https://app.getambassador.io/auth/realms/production/protocol/openid-connect/auth?client_id=docker-docs&response_type=code&redirect_uri=https%3A%2F%2Fapp.getambassador.io&utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker%26TP){: target="_blank" rel="noopener" class="_" } -- [CodeZero](https://www.codezero.io/){: target="_blank" rel="noopener" class="_" } -- [Gefyra](https://gefyra.dev/){: target="_blank" rel="noopener" class="_" } -- [kubefwd](https://kubefwd.com/){: target="_blank" rel="noopener" class="_" } -- [ktunnel](https://github.com/omrikiei/ktunnel){: target="_blank" rel="noopener" class="_" } +- [Telepresence](https://app.getambassador.io/auth/realms/production/protocol/openid-connect/auth?client_id=docker-docs&response_type=code&redirect_uri=https%3A%2F%2Fapp.getambassador.io&utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker%26TP) +- [CodeZero](https://www.codezero.io/) +- [Gefyra](https://gefyra.dev/) +- [kubefwd](https://kubefwd.com/) +- [ktunnel](https://github.com/omrikiei/ktunnel) ## Telepresence @@ -72,9 +72,9 @@ You have a few options for how the local containers can integrate with the clust Telepresence seamlessly integrates with Docker and it's available for you to try today. Check out the following docs to learn more: -- [Telepresence extension for Docker Desktop](https://www.getambassador.io/docs/telepresence/latest/docker/extension?utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker-TP){: target="_blank" rel="noopener" class="_" } -- [Telepresence in Docker mode](https://www.getambassador.io/docs/telepresence/latest/docker/cli?utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker-TP){: target="_blank" rel="noopener" class="_" } -- [Telepresence for Docker Compose](https://www.getambassador.io/docs/telepresence/latest/docker/compose?utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker-TP){: target="_blank" rel="noopener" class="_" } +- [Telepresence extension for Docker Desktop](https://www.getambassador.io/docs/telepresence/latest/docker/extension?utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker-TP) +- [Telepresence in Docker mode](https://www.getambassador.io/docs/telepresence/latest/docker/cli?utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker-TP) +- [Telepresence for Docker Compose](https://www.getambassador.io/docs/telepresence/latest/docker/compose?utm_source=docker-docs&utm_medium=dockerwebsite&utm_campaign=Docker-TP) ### Docker × Ambassador @@ -98,4 +98,4 @@ Docker ID to Ambassador Cloud to sign in and use Telepresence. To get started: 3. Authorize the Ambassador Cloud app. This takes you to a step-by-step guide on setting up Telepresence, -connecting to a development cluster, and creating intercepts. +connecting to a development cluster, and creating intercepts. \ No newline at end of file diff --git a/content/develop/security-best-practices.md b/content/develop/security-best-practices.md index 5ef9e15021..12d9e3fba9 100644 --- a/content/develop/security-best-practices.md +++ b/content/develop/security-best-practices.md @@ -2,8 +2,8 @@ title: Security best practices description: Image security best practices guide keywords: docker, images, containers, vulnerability, cve -redirect_from: - - /develop/scan-images/ +aliases: +- /develop/scan-images/ --- You can take a few steps to improve the security of your @@ -30,7 +30,7 @@ Docker verifying the authenticity of the content in their repositories. When you pick your base image, look out for the **Official Image** and **Verified Publisher** badges. -![Docker Hub Official and Verified Publisher images](images/hub-official-images.png){:width="700px"} +![Docker Hub Official and Verified Publisher images](images/hub-official-images.png) When building your own image from a Dockerfile, ensure you choose a minimal base image that matches your requirements. A smaller base image not only offers @@ -158,4 +158,4 @@ To summarize the topics covered in this guide: - Ensure you carefully monitor and manage the tools and dependencies you add to your image. - Ensure you scan images at multiple stages during your development lifecycle. -- Check your images frequently for vulnerabilities. +- Check your images frequently for vulnerabilities. \ No newline at end of file diff --git a/content/docker-hub/2fa/_index.md b/content/docker-hub/2fa/_index.md index 02e4beff03..ef3a88f6ff 100644 --- a/content/docker-hub/2fa/_index.md +++ b/content/docker-hub/2fa/_index.md @@ -1,6 +1,7 @@ --- description: Enabling two-factor authentication on Docker Hub -keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor authentication +keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor + authentication title: Enable two-factor authentication for Docker Hub --- @@ -36,4 +37,4 @@ Authenticator with a registered YubiKey. 7. Once you have linked your authenticator app, enter the six-digit code to in text field and then select **Next**. Two-factor authentication is now enabled. The next time you sign -in to your Docker Hub account, you will be asked for a security code. +in to your Docker Hub account, you will be asked for a security code. \ No newline at end of file diff --git a/content/docker-hub/2fa/disable-2fa.md b/content/docker-hub/2fa/disable-2fa.md index 2e6c51bc22..0d292cdb3f 100644 --- a/content/docker-hub/2fa/disable-2fa.md +++ b/content/docker-hub/2fa/disable-2fa.md @@ -1,6 +1,7 @@ --- description: Disable two-factor authentication on Docker Hub -keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor authentication +keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor + authentication title: Disable two-factor authentication on Docker Hub --- @@ -8,12 +9,10 @@ title: Disable two-factor authentication on Docker Hub > > Disabling two-factor authentication results in decreased security for your > Docker Hub account. -{: .warning } +{ .warning } ## Disable two-factor authentication 1. Sign in to your Docker Hub account. 2. Select your username and then from the dropdown menu, select **Account Settings**. 3. Navigate to the **Security** tab and select **Disable 2FA**. -4. Enter your password and select **Disable 2FA**. - - +4. Enter your password and select **Disable 2FA**. \ No newline at end of file diff --git a/content/docker-hub/2fa/new-recovery-code.md b/content/docker-hub/2fa/new-recovery-code.md index 9db3e78596..803c6ecfca 100644 --- a/content/docker-hub/2fa/new-recovery-code.md +++ b/content/docker-hub/2fa/new-recovery-code.md @@ -1,6 +1,7 @@ --- description: Generate a new 2fa recovery code -keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor authentication +keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor + authentication title: Generate a new recovery code --- @@ -15,4 +16,4 @@ access to your Docker Hub account, you can generate a new recovery code. 4. Enter your password. Your new recovery code is displayed. Remember to save your recovery code -and store it somewhere safe. +and store it somewhere safe. \ No newline at end of file diff --git a/content/docker-hub/2fa/recover-hub-account.md b/content/docker-hub/2fa/recover-hub-account.md index 1c544f4754..cc410e5c25 100644 --- a/content/docker-hub/2fa/recover-hub-account.md +++ b/content/docker-hub/2fa/recover-hub-account.md @@ -1,13 +1,13 @@ --- description: Recover your Docker Hub account -keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor authentication +keywords: Docker, docker, registry, security, Docker Hub, authentication, two-factor + authentication title: Recover your Docker Hub account --- - If you have lost access to both your two-factor authentication application and your recovery code: -1. Navigate to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} and enter your username and password. +1. Navigate to [Docker Hub](https://hub.docker.com) and enter your username and password. 2. Select **I've lost my authentication device** and **I've lost my recovery code**. -3. Complete the [Contact Support form](https://hub.docker.com/support/contact/?category=2fa-lockout){:target="_blank" rel="noopener" class="_"}. - You must enter the primary email address associated with your Docker ID in the Contact Support form for recovery instructions. +3. Complete the [Contact Support form](https://hub.docker.com/support/contact/?category=2fa-lockout). + You must enter the primary email address associated with your Docker ID in the Contact Support form for recovery instructions. \ No newline at end of file diff --git a/content/docker-hub/_index.md b/content/docker-hub/_index.md index 14e3fcb61e..041d91d4ba 100644 --- a/content/docker-hub/_index.md +++ b/content/docker-hub/_index.md @@ -1,33 +1,34 @@ --- -description: Learn about Docker Hub features and the administrative tasks available in Docker Hub +description: Learn about Docker Hub features and the administrative tasks available + in Docker Hub keywords: Docker, docker, docker hub, hub, overview title: Overview of Docker Hub grid: - - title: "Create a Docker ID" - description: - "Register and create a new Docker ID." - icon: "fingerprint" - link: "/docker-id" - - title: "Create a repository" - description: "Create a repository to share your images with your team, customers, or the Docker community." - icon: "explore" - link: "/docker-hub/repos" - - title: "Quickstart" - description: "Step-by-step instructions on getting started on Docker Hub." - icon: "checklist" - link: "/docker-hub" - - title: "Manage access tokens" - description: "Create personal access tokens as an alternative to your password." - icon: "key" - link: "/docker-hub/access-tokens" - - title: "Official images" - description: "A curated set of Docker repositories hosted on Docker Hub." - icon: "verified" - link: "/docker-hub/official_images" - - title: "Release notes" - description: "Find out about new features, improvements, and bug fixes." - icon: "note_add" - link: "/docker-hub/release-notes" +- title: Create a Docker ID + description: Register and create a new Docker ID. + icon: fingerprint + link: /docker-id +- title: Create a repository + description: Create a repository to share your images with your team, customers, + or the Docker community. + icon: explore + link: /docker-hub/repos +- title: Quickstart + description: Step-by-step instructions on getting started on Docker Hub. + icon: checklist + link: /docker-hub +- title: Manage access tokens + description: Create personal access tokens as an alternative to your password. + icon: key + link: /docker-hub/access-tokens +- title: Official images + description: A curated set of Docker repositories hosted on Docker Hub. + icon: verified + link: /docker-hub/official_images +- title: Release notes + description: Find out about new features, improvements, and bug fixes. + icon: note_add + link: /docker-hub/release-notes --- Docker Hub is a service provided by Docker for finding and sharing container images. @@ -49,8 +50,8 @@ container images from non-commercial open source projects. GitHub and Bitbucket and push them to Docker Hub. * [Webhooks](webhooks.md): Trigger actions after a successful push to a repository to integrate Docker Hub with other services. -* [Docker Hub CLI](https://github.com/docker/hub-tool#readme){: target="_blank" rel="noopener" class="_"} tool (currently experimental) and an API that allows you to interact with Docker Hub. - * Browse through the [Docker Hub API](/docker-hub/api/latest/){: target="_blank" rel="noopener" class="_"} documentation to explore the supported endpoints. +* [Docker Hub CLI](https://github.com/docker/hub-tool#readme) tool (currently experimental) and an API that allows you to interact with Docker Hub. + * Browse through the [Docker Hub API](/docker-hub/api/latest/) documentation to explore the supported endpoints. {{< /tab >}} {{< tab name="What administrative tasks can I perform in Docker Hub?" >}} * [Create and manage teams and organizations](orgs.md) @@ -64,4 +65,4 @@ GitHub and Bitbucket and push them to Docker Hub. {{< /tab >}} {{< /tabs >}} -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/docker-hub/access-tokens.md b/content/docker-hub/access-tokens.md index b5b724be1b..f7238fed97 100644 --- a/content/docker-hub/access-tokens.md +++ b/content/docker-hub/access-tokens.md @@ -1,10 +1,11 @@ --- title: Create and manage access tokens -description: Learn how to create and manage your personal Docker Hub access tokens to securely push and pull images programmatically. +description: Learn how to create and manage your personal Docker Hub access tokens + to securely push and pull images programmatically. keywords: docker hub, hub, security, PAT, personal access token --- -If you are using the [Docker Hub CLI](https://github.com/docker/hub-tool#readme){: target="_blank" rel="noopener" class="_"} +If you are using the [Docker Hub CLI](https://github.com/docker/hub-tool#readme) tool (currently experimental) to access Hub images from the Docker CLI, you can create personal access tokens (PAT) as alternatives to your password. Compared to passwords, personal access tokens provide the following advantages: @@ -25,9 +26,9 @@ any time. > **Important** > > Treat access tokens like your password and keep them secret. Store your tokens securely in a credential manager for example. -{: .important} +{ .important } -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Select your username in the top-right corner and from the drop-down menu select **Account Settings**. @@ -70,4 +71,4 @@ You can rename, activate, deactivate, or delete a token as needed. 2. Choose a token and then select **Delete** or **Edit**, or use the menu on the far right of a token row to bring up the edit screen. You can also select multiple tokens to delete at once. -3. After modifying the token, select **Save**. +3. After modifying the token, select **Save**. \ No newline at end of file diff --git a/content/docker-hub/admin-overview.md b/content/docker-hub/admin-overview.md index e66a7a5bb5..1ea1fdcfdc 100644 --- a/content/docker-hub/admin-overview.md +++ b/content/docker-hub/admin-overview.md @@ -3,32 +3,32 @@ title: Administration description: landing page for administration topic keywords: administration, docker hub, admin grid: - - title: Create your organization - icon: contact_page - description: Explore and set up an organization in Docker Hub. - link: /docker-hub/orgs/ - - title: Onboard your organization - icon: explore - link: /docker-hub/onboard/ - description: Learn how to onboard users to your organization. - - title: Use Hardened Docker Desktop - icon: lock - link: /desktop/hardened-desktop/ - description: Explore the security model for Docker Desktop. - - title: Enforce sign-in - description: Configure sign-in for members of your teams and organizations. - link: /docker-hub/configure-sign-in/ - icon: key - - title: Enable Single Sign-On - description: Understand and use Single Sign-On. - link: /single-sign-on/ - icon: group_add - - title: Set up two-factor authentication - description: Add an extra layer of authentication to your Docker account. - link: /docker-hub/2fa/ - icon: security +- title: Create your organization + icon: contact_page + description: Explore and set up an organization in Docker Hub. + link: /docker-hub/orgs/ +- title: Onboard your organization + icon: explore + link: /docker-hub/onboard/ + description: Learn how to onboard users to your organization. +- title: Use Hardened Docker Desktop + icon: lock + link: /desktop/hardened-desktop/ + description: Explore the security model for Docker Desktop. +- title: Enforce sign-in + description: Configure sign-in for members of your teams and organizations. + link: /docker-hub/configure-sign-in/ + icon: key +- title: Enable Single Sign-On + description: Understand and use Single Sign-On. + link: /single-sign-on/ + icon: group_add +- title: Set up two-factor authentication + description: Add an extra layer of authentication to your Docker account. + link: /docker-hub/2fa/ + icon: security --- Sign in to Docker Hub to change account settings and carry out administrative or security-related tasks. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/docker-hub/api/deprecated.md b/content/docker-hub/api/deprecated.md index d8a3029cf9..90b4006cc4 100644 --- a/content/docker-hub/api/deprecated.md +++ b/content/docker-hub/api/deprecated.md @@ -7,7 +7,7 @@ title: Docker Hub API v1 (deprecated) > **Deprecated** > > Docker Hub API v1 has been deprecated. Please use Docker Hub API v2 instead. -{: .warning } +{ .warning } The following API routes within the v1 path will no longer work and will return a 410 status code: * `/v1/repositories/{name}/images` @@ -26,4 +26,4 @@ If you want to continue using the Docker Hub API in your current applications, u | [/v1/repositories/{name}/tags](https://github.com/moby/moby/blob/v1.8.3/docs/reference/api/registry_api.md#list-repository-tags) | [/v2/namespaces/{namespace}/repositories/{repository}/tags](../../docker-hub/api/latest.md#tag/repositories/paths/~1v2~1namespaces~1%7Bnamespace%7D~1repositories~1%7Brepository%7D~1tags/get) | | [/v1/repositories/{namespace}/{name}/tags](https://github.com/moby/moby/blob/v1.8.3/docs/reference/api/registry_api.md#list-repository-tags) | [/v2/namespaces/{namespace}/repositories/{repository}/tags](../../docker-hub/api/latest.md#tag/repositories/paths/~1v2~1namespaces~1%7Bnamespace%7D~1repositories~1%7Brepository%7D~1tags/get) | | [/v1/repositories/{namespace}/{name}/tags](https://github.com/moby/moby/blob/v1.8.3/docs/reference/api/registry_api.md#get-image-id-for-a-particular-tag) | [/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}](../../docker-hub/api/latest.md#tag/repositories/paths/~1v2~1namespaces~1%7Bnamespace%7D~1repositories~1%7Brepository%7D~1tags~1%7Btag%7D/get) | -| [/v1/repositories/{namespace}/{name}/tags/{tag_name}](https://github.com/moby/moby/blob/v1.8.3/docs/reference/api/registry_api.md#get-image-id-for-a-particular-tag) | [/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}](../../docker-hub/api/latest.md#tag/repositories/paths/~1v2~1namespaces~1%7Bnamespace%7D~1repositories~1%7Brepository%7D~1tags~1%7Btag%7D/get) | +| [/v1/repositories/{namespace}/{name}/tags/{tag_name}](https://github.com/moby/moby/blob/v1.8.3/docs/reference/api/registry_api.md#get-image-id-for-a-particular-tag) | [/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}](../../docker-hub/api/latest.md#tag/repositories/paths/~1v2~1namespaces~1%7Bnamespace%7D~1repositories~1%7Brepository%7D~1tags~1%7Btag%7D/get) | \ No newline at end of file diff --git a/content/docker-hub/api/dvp.md b/content/docker-hub/api/dvp.md index f2831098d1..7f901918bf 100644 --- a/content/docker-hub/api/dvp.md +++ b/content/docker-hub/api/dvp.md @@ -1,3 +1,3 @@ --- layout: hub-api ---- +--- \ No newline at end of file diff --git a/content/docker-hub/api/latest.md b/content/docker-hub/api/latest.md index f2831098d1..7f901918bf 100644 --- a/content/docker-hub/api/latest.md +++ b/content/docker-hub/api/latest.md @@ -1,3 +1,3 @@ --- layout: hub-api ---- +--- \ No newline at end of file diff --git a/content/docker-hub/audit-log.md b/content/docker-hub/audit-log.md index 3e7101de86..b00f938019 100644 --- a/content/docker-hub/audit-log.md +++ b/content/docker-hub/audit-log.md @@ -8,4 +8,4 @@ title: Audit logs > > Audit logs requires a [Docker Team or Business subscription](../subscription/index.md). -{% include admin-org-audit-log.md product="hub" %} \ No newline at end of file +{{% admin-org-audit-log product="hub" %}} \ No newline at end of file diff --git a/content/docker-hub/builds/_index.md b/content/docker-hub/builds/_index.md index bbe7d4f38d..59cc22afdf 100644 --- a/content/docker-hub/builds/_index.md +++ b/content/docker-hub/builds/_index.md @@ -1,13 +1,13 @@ --- description: Set up Automated builds keywords: automated, build, images, Docker Hub -redirect_from: +title: Set up Automated Builds +aliases: - /docker-hub/builds/automated-build/ - /docker-cloud/feature-reference/automated-build/ - /docker-cloud/builds/automated-build/ - /docker-cloud/builds/ - /docker-hub/builds/classic/ -title: Set up Automated Builds --- > **Note** @@ -226,7 +226,7 @@ sources. For example, you might have ### Build images with BuildKit Autobuilds use the BuildKit build system by default. If you want to use the legacy -Docker build system, add the [environment variable](index.md#environment-variables-for-builds){: target="_blank" rel="noopener" class="_"} +Docker build system, add the [environment variable](index.md#environment-variables-for-builds) `DOCKER_BUILDKIT=0`. Refer to the [BuildKit](../../build/buildkit/index.md) page for more information on BuildKit. diff --git a/content/docker-hub/builds/advanced.md b/content/docker-hub/builds/advanced.md index cb005622e0..383dad017a 100644 --- a/content/docker-hub/builds/advanced.md +++ b/content/docker-hub/builds/advanced.md @@ -2,7 +2,7 @@ description: Automated builds keywords: automated, build, images title: Advanced options for Autobuild and Autotest -redirect_from: +aliases: - /docker-cloud/builds/advanced/ --- @@ -60,7 +60,7 @@ to perform actions in between these commands. >Use these hooks with caution. The contents of these hook files replace the basic `docker` commands, so you must include a similar build, test or push command in the hook or your automated process does not complete. -{: .important} +{ .important } To override these phases, create a folder called `hooks` in your source code repository at the same directory level as your Dockerfile. Create a file called @@ -68,10 +68,10 @@ repository at the same directory level as your Dockerfile. Create a file called builder process can execute, such as `docker` and `bash` commands (prefixed appropriately with `#!/bin/bash`). -These hooks run on an instance of [Ubuntu](https://releases.ubuntu.com/){:target="_blank" rel="noopener" class="_"}, +These hooks run on an instance of [Ubuntu](https://releases.ubuntu.com/), which includes interpreters such as Perl or Python, and utilities such as `git` or `curl`. Refer to the -[Ubuntu documentation](https://ubuntu.com/){:target="_blank" rel="noopener" class="_"} +[Ubuntu documentation](https://ubuntu.com/) for the full list of available interpreters and utilities. ## Custom build phase hooks @@ -117,7 +117,7 @@ $ docker build --build-arg CUSTOM=$VAR -f $DOCKERFILE_PATH -t $IMAGE_NAME . > > A `hooks/build` file overrides the basic [docker build](../../engine/reference/commandline/build.md) command used by the builder, so you must include a similar build command in the hook or the automated build fails. -{: .important} +{ .important } Refer to the [docker build documentation](../../engine/reference/commandline/build.md#build-arg) to learn more about Docker build-time variables. @@ -157,4 +157,4 @@ you do one of the following: ```console $ git fetch --unshallow origin - ``` + ``` \ No newline at end of file diff --git a/content/docker-hub/builds/automated-testing.md b/content/docker-hub/builds/automated-testing.md index f0fdd1e928..243123a4d4 100644 --- a/content/docker-hub/builds/automated-testing.md +++ b/content/docker-hub/builds/automated-testing.md @@ -1,10 +1,10 @@ --- description: Automated tests keywords: Automated, testing, repository -redirect_from: +title: Automated repository tests +aliases: - /docker-cloud/feature-reference/automated-testing/ - /docker-cloud/builds/automated-testing/ -title: Automated repository tests --- > **Note** @@ -110,7 +110,7 @@ Docker repository, regardless of the Autotest settings. limited on public repositories. Private images are not pulled and environment variables defined in Docker Hub are not available. Automated builds continue to work as usual. - {: .important} + { .important } 7. Select **Save** to save the settings, or select **Save and build** to save and run an initial test. @@ -122,4 +122,4 @@ From the repository's details page, select **Timeline**. From this tab you can see any pending, in-progress, successful, and failed builds and test runs for the repository. -You can choose any timeline entry to view the logs for each test run. +You can choose any timeline entry to view the logs for each test run. \ No newline at end of file diff --git a/content/docker-hub/builds/how-builds-work.md b/content/docker-hub/builds/how-builds-work.md index 7176bf0a00..0302b2aa1b 100644 --- a/content/docker-hub/builds/how-builds-work.md +++ b/content/docker-hub/builds/how-builds-work.md @@ -12,7 +12,7 @@ title: How Automated builds work Docker Hub can automatically build images from source code in an external repository and automatically push the built image to your Docker repositories. -![An automated build dashboard](images/index-dashboard.png){:width="750px"} +![An automated build dashboard](images/index-dashboard.png) When you set up Automated builds, also called autobuilds, you create a list of branches and tags that you want to build into Docker images. When you push code @@ -30,12 +30,11 @@ pushing to the registry. You can use these tests to create a continuous integration workflow where a build that fails its tests doesn't push the built image. Automated tests don't push images to the registry on their own. [Learn about automated image testing](automated-testing.md). -Depending on your [subscription](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"}, +Depending on your [subscription](https://www.docker.com/pricing), you may get concurrent builds, which means that `N` autobuilds can be run at the same time. `N` is configured according to your subscription. Once `N+1` builds are running, any additional builds go into a queue to be run later. The maximum number of pending builds in the queue is 30 and Docker Hub discards further requests. The number of concurrent builds for Pro is 5 and -for Team and Business is 15. - +for Team and Business is 15. \ No newline at end of file diff --git a/content/docker-hub/builds/link-source.md b/content/docker-hub/builds/link-source.md index e6139b04fd..d8d4f34600 100644 --- a/content/docker-hub/builds/link-source.md +++ b/content/docker-hub/builds/link-source.md @@ -1,8 +1,9 @@ --- description: Link to GitHub and BitBucket -keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, trusted, builds, trusted builds, automated builds, GitHub +keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, trusted, + builds, trusted builds, automated builds, GitHub title: Configure Automated builds from GitHub and BitBucket -redirect_from: +aliases: - /docker-hub/github/ - /docker-hub/bitbucket/ - /docker-cloud/builds/link-source/ @@ -28,13 +29,12 @@ If you are linking a source code provider to create autobuilds for a team, follo 3. Select **Link provider** for the source provider you want to link. - If you want to unlink your current GitHub account and relink to a new GitHub account, make sure to completely logout of [GitHub](https://github.com/){: target="_blank" rel="noopener" - class="_"} before linking via Docker Hub. + If you want to unlink your current GitHub account and relink to a new GitHub account, make sure to completely logout of [GitHub](https://github.com/) before linking via Docker Hub. 4. Review the settings for the **Docker Hub Builder** OAuth application. - ![Granting access to GitHub account](images/authorize-builder.png){:width="750px"} + ![Granting access to GitHub account](images/authorize-builder.png) >**Note** > @@ -151,4 +151,4 @@ the **Linked Accounts** section. > Each repository that is configured as an automated build source contains a webhook that notifies Docker Hub of changes in the repository. This webhook is not automatically removed when you revoke access to a source code -provider. +provider. \ No newline at end of file diff --git a/content/docker-hub/builds/manage-builds.md b/content/docker-hub/builds/manage-builds.md index b288224c2b..38b1c2d232 100644 --- a/content/docker-hub/builds/manage-builds.md +++ b/content/docker-hub/builds/manage-builds.md @@ -3,6 +3,7 @@ title: Manage autobuilds description: How to manage autobuilds in Docker Hub keywords: autobuilds, automated, docker hub, registry --- + > **Note** > > Automated builds require a diff --git a/content/docker-hub/company-faqs.md b/content/docker-hub/company-faqs.md index 253a1f01aa..c796b03d17 100644 --- a/content/docker-hub/company-faqs.md +++ b/content/docker-hub/company-faqs.md @@ -55,5 +55,4 @@ See [SCIM](scim.md) for more information. ### What's the definition of a company vs an organization? -A company is a collection of organizations that are managed together. An organization is a collection of repositories and teams that are managed together. - +A company is a collection of organizations that are managed together. An organization is a collection of repositories and teams that are managed together. \ No newline at end of file diff --git a/content/docker-hub/company-owner.md b/content/docker-hub/company-owner.md index 1a015b1690..cb63cf214e 100644 --- a/content/docker-hub/company-owner.md +++ b/content/docker-hub/company-owner.md @@ -8,16 +8,16 @@ As a company owner, you can configure [Single Sign-on (SSO)](../single-sign-on/c ## Add a company owner -1. Sign in to [Docker Hub](https://hub.docker.com/){: target="_blank" rel="noopener" class="_"}, navigate to the **Organizations** page, and select your company. +1. Sign in to [Docker Hub](https://hub.docker.com/), navigate to the **Organizations** page, and select your company. 2. In the **Overview** tab, select **Add owner** and enter their Docker ID or email address. 3. Once you've selected **Add Owner**, you can view the user in the **Company Owners** table. - ![company-overview](images/company-overview.png){: width="700px" } + ![company-overview](images/company-overview.png) ## Remove a company owner -1. Sign in to [Docker Hub](https://hub.docker.com/){: target="_blank" rel="noopener" class="_"}, navigate to the **Organizations** page, and select your company. +1. Sign in to [Docker Hub](https://hub.docker.com/), navigate to the **Organizations** page, and select your company. 2. In the **Overview** tab, find the **Company Owner** you want to remove. 3. Select the **Action** icon and remove the owner. - ![remove-owner](images/remove-owner.png){: width="700px" } + ![remove-owner](images/remove-owner.png) \ No newline at end of file diff --git a/content/docker-hub/configure-sign-in.md b/content/docker-hub/configure-sign-in.md index 6f088fa694..cb4cd0346a 100644 --- a/content/docker-hub/configure-sign-in.md +++ b/content/docker-hub/configure-sign-in.md @@ -20,7 +20,7 @@ Deploying a `registry.json` file and forcing users to authenticate is not requir - Authenticated users get a higher pull rate limit compared to anonymous users. For example, if you are authenticated, you get 200 pulls per 6 hour period, compared to 100 pulls per 6 hour period per IP address for anonymous users. For more information, see [Download rate limit](download-rate-limit.md). - Blocks users from accessing Docker Desktop until they are added to a specific organization. -{% include configure-registry-json.md %} +{{< include "configure-registry-json.md" >}} ## Deploy registry.json to multiple devices @@ -30,4 +30,4 @@ The previous instructions explain how to create and deploy a registry.json file After you’ve created the `registry.json` file and deployed it onto the users’ machines, you can verify whether the changes have taken effect by asking users to start Docker Desktop. -If the configuration is successful, Docker Desktop prompts the user to authenticate using the organization credentials on start. If the user fails to authenticate, they will see an error message, and they will be denied access to Docker Desktop. +If the configuration is successful, Docker Desktop prompts the user to authenticate using the organization credentials on start. If the user fails to authenticate, they will see an error message, and they will be denied access to Docker Desktop. \ No newline at end of file diff --git a/content/docker-hub/convert-account.md b/content/docker-hub/convert-account.md index b80904460a..91e69d6631 100644 --- a/content/docker-hub/convert-account.md +++ b/content/docker-hub/convert-account.md @@ -8,12 +8,12 @@ You can convert an existing user account to an organization. This is useful if y When you convert a user account to an organization, the account is migrated to a Team plan and charged $35 per month for 5 seats. For more information, -see [Docker Pricing](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"}. +see [Docker Pricing](https://www.docker.com/pricing). > **Important** > > Once you convert your account to an organization, you can’t revert it to a user account. -{: .important} +{ .important } ## Prerequisites @@ -44,4 +44,4 @@ Before you convert a user account to an organization, ensure that you meet the f 5. Enter a **Docker ID** to set an organization owner. This is the user account that will manage the organization, and the only way to access the organization settings after conversion. You cannot use the same Docker ID as the account you are trying to convert. -6. Select **Convert and Purchase** to confirm. The new owner receives a notification email. Use that owner account to log in to your new organization. +6. Select **Convert and Purchase** to confirm. The new owner receives a notification email. Use that owner account to log in to your new organization. \ No newline at end of file diff --git a/content/docker-hub/creating-companies.md b/content/docker-hub/creating-companies.md index f569b4eba7..43a996980a 100644 --- a/content/docker-hub/creating-companies.md +++ b/content/docker-hub/creating-companies.md @@ -4,7 +4,7 @@ keywords: company, multiple organizations, manage companies title: Overview --- -{% include admin-company-overview.md %} +{{< include "admin-company-overview.md" >}}
@@ -37,5 +37,4 @@ title: Overview
- - + \ No newline at end of file diff --git a/content/docker-hub/deactivate-account.md b/content/docker-hub/deactivate-account.md index 926da86f2b..b394d88ca5 100644 --- a/content/docker-hub/deactivate-account.md +++ b/content/docker-hub/deactivate-account.md @@ -9,7 +9,7 @@ You can deactivate an account at any time. >**Warning** > > If your Docker Hub account or organization is linked to other Docker products and services, deactivating your account also removes access to those products and services. -{: .warning} +{ .warning } ## Deactivate a user account @@ -40,7 +40,7 @@ Once you have completed all the steps above, you can deactivate your account. 2. From the **Deactivate Account** tab, select **Deactivate account**. > This cannot be undone. Be sure you've gathered all the data you need from your account before deactivating it. -{: .warning } +{ .warning } ## Deactivate an organization @@ -65,4 +65,4 @@ Once you have completed all the steps above, you can deactivate your organizatio 3. In **Settings**, select the **Deactivate Org** tab and then **Deactivate organization**. > This cannot be undone. Be sure you've gathered all the data you need from your organization before deactivating it. -{: .warning } +{ .warning } \ No newline at end of file diff --git a/content/docker-hub/domain-audit.md b/content/docker-hub/domain-audit.md index 835c025633..d7143c30db 100644 --- a/content/docker-hub/domain-audit.md +++ b/content/docker-hub/domain-audit.md @@ -4,4 +4,4 @@ keywords: domain audit, security title: Domain audit --- -{% include admin-domain-audit.md product="hub" %} \ No newline at end of file +{{% admin-domain-audit product="hub" %}} \ No newline at end of file diff --git a/content/docker-hub/download-rate-limit.md b/content/docker-hub/download-rate-limit.md index 363d0acb27..b31aec4a80 100644 --- a/content/docker-hub/download-rate-limit.md +++ b/content/docker-hub/download-rate-limit.md @@ -12,18 +12,18 @@ Docker Hub limits the number of Docker image downloads, or pulls, based on the a | --------- | ---------- | | Anonymous users | 100 pulls per 6 hours per IP address | | [Authenticated users](#how-do-i-authenticate-pull-requests)| 200 pulls per 6 hour period | -| Users with a paid [Docker subscription](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"} | Up to 5000 pulls per day | +| Users with a paid [Docker subscription](https://www.docker.com/pricing) | Up to 5000 pulls per day | If you require a higher number of pulls, you can also purchase an [Enhanced Service Account add-on](service-accounts.md#enhanced-service-account-add-on-pricing). -Some images are unlimited through our [Open Source](https://www.docker.com/blog/expanded-support-for-open-source-software-projects/){: target="_blank" rel="noopener" class="_"} and [Publisher](https://www.docker.com/partners/programs){: target="_blank" rel="noopener" class="_"} programs. See [Docker Pricing](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"} and [Resource Consumption Updates FAQ](https://www.docker.com/pricing/resource-consumption-updates){: target="_blank" rel="noopener" class="_"} for details. +Some images are unlimited through our [Open Source](https://www.docker.com/blog/expanded-support-for-open-source-software-projects/) and [Publisher](https://www.docker.com/partners/programs) programs. See [Docker Pricing](https://www.docker.com/pricing) and [Resource Consumption Updates FAQ](https://www.docker.com/pricing/resource-consumption-updates) for details. ## Definition of limits A user's limit is equal to the highest entitlement of their personal account or any organization they belong to. To take advantage of this, you must log in to -[Docker Hub](https://hub.docker.com/){: target="_blank" rel="noopener" class="_"} +[Docker Hub](https://hub.docker.com/) as an authenticated user. For more information, see [How do I authenticate pull requests](#how-do-i-authenticate-pull-requests). Unauthenticated (anonymous) users will have the limits enforced via IP. @@ -99,7 +99,7 @@ If you don't see any RateLimit header, it could be because the image or your IP To take advantage of the higher limits included in a paid Docker subscription, you must [authenticate pulls](#how-do-i-authenticate-pull-requests) with your user account. -A Pro, Team, or a Business tier doesn't increase limits on your images for other users. See Docker's [Open Source](https://www.docker.com/blog/expanded-support-for-open-source-software-projects/){: target="_blank" rel="noopener" class="_"}, [Publisher](https://www.docker.com/partners/programs){: target="_blank" rel="noopener" class="_"}, or [Large Organization](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"} offerings. +A Pro, Team, or a Business tier doesn't increase limits on your images for other users. See Docker's [Open Source](https://www.docker.com/blog/expanded-support-for-open-source-software-projects/), [Publisher](https://www.docker.com/partners/programs), or [Large Organization](https://www.docker.com/pricing) offerings. ## How do I authenticate pull requests? @@ -121,27 +121,27 @@ If you're running Docker Swarm, you must use the `-- with-registry-auth` flag to ### GitHub Actions -If you're using GitHub Actions to build and push Docker images to Docker Hub, see [login action](https://github.com/docker/login-action#dockerhub){: target="_blank" rel="noopener" class="_"}. If you are using another Action, you must add your username and access token in a similar way for authentication. +If you're using GitHub Actions to build and push Docker images to Docker Hub, see [login action](https://github.com/docker/login-action#dockerhub). If you are using another Action, you must add your username and access token in a similar way for authentication. ### Kubernetes -If you're running Kubernetes, follow the instructions in [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/){: target="_blank" rel="noopener" class="_"} for information on authentication. +If you're running Kubernetes, follow the instructions in [Pull an Image from a Private Registry](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for information on authentication. ### Third-party platforms If you're using any third-party platforms, follow your provider’s instructions on using registry authentication. -- [Artifactory](https://www.jfrog.com/confluence/display/JFROG/Advanced+Settings#AdvancedSettings-RemoteCredentials){: target="_blank" rel="noopener" class="_"} -- [AWS CodeBuild](https://aws.amazon.com/blogs/devops/how-to-use-docker-images-from-a-private-registry-in-aws-codebuild-for-your-build-environment/){: target="_blank" rel="noopener" class="_"} -- [AWS ECS/Fargate](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html){: target="_blank" rel="noopener" class="_"} -- [Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#sep-docreg){: target="_blank" rel="noopener" class="_"} -- [Chipper CI](https://docs.chipperci.com/builds/docker/#rate-limit-auth){: target="_blank" rel="noopener" class="_"} -- [CircleCI](https://circleci.com/docs/2.0/private-images/){: target="_blank" rel="noopener" class="_"} -- [Codefresh](https://codefresh.io/docs/docs/docker-registries/external-docker-registries/docker-hub/){: target="_blank" rel="noopener" class="_"} -- [Drone.io](https://docs.drone.io/pipeline/docker/syntax/images/#pulling-private-images){: target="_blank" rel="noopener" class="_"} -- [GitLab](https://docs.gitlab.com/ee/user/packages/container_registry/#authenticate-with-the-container-registry){: target="_blank" rel="noopener" class="_"} -- [LayerCI](https://layerci.com/docs/advanced-workflows#logging-in-to-docker){: target="_blank" rel="noopener" class="_"} -- [TeamCity](https://www.jetbrains.com/help/teamcity/integrating-teamcity-with-docker.html#Conforming+with+Docker+download+rate+limits){: target="_blank" rel="noopener" class="_"} +- [Artifactory](https://www.jfrog.com/confluence/display/JFROG/Advanced+Settings#AdvancedSettings-RemoteCredentials) +- [AWS CodeBuild](https://aws.amazon.com/blogs/devops/how-to-use-docker-images-from-a-private-registry-in-aws-codebuild-for-your-build-environment/) +- [AWS ECS/Fargate](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html) +- [Azure Pipelines](https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#sep-docreg) +- [Chipper CI](https://docs.chipperci.com/builds/docker/#rate-limit-auth) +- [CircleCI](https://circleci.com/docs/2.0/private-images/) +- [Codefresh](https://codefresh.io/docs/docs/docker-registries/external-docker-registries/docker-hub/) +- [Drone.io](https://docs.drone.io/pipeline/docker/syntax/images/#pulling-private-images) +- [GitLab](https://docs.gitlab.com/ee/user/packages/container_registry/#authenticate-with-the-container-registry) +- [LayerCI](https://layerci.com/docs/advanced-workflows#logging-in-to-docker) +- [TeamCity](https://www.jetbrains.com/help/teamcity/integrating-teamcity-with-docker.html#Conforming+with+Docker+download+rate+limits) ## Other limits @@ -156,4 +156,4 @@ regardless of account level. You can differentiate between these limits by looking at the error code. The "overall limit" returns a simple `429 Too Many Requests` response. The pull limit returns a longer error message that -includes a link to this page. +includes a link to this page. \ No newline at end of file diff --git a/content/docker-hub/dsos-program.md b/content/docker-hub/dsos-program.md index 515e200bbf..f118710825 100644 --- a/content/docker-hub/dsos-program.md +++ b/content/docker-hub/dsos-program.md @@ -4,7 +4,7 @@ title: Docker-Sponsored Open Source Program keywords: docker hub, hub, insights, analytics, open source, Docker sponsored, program --- -[Docker Sponsored Open Source images](https://hub.docker.com/search?q=&image_filter=open_source){:target="_blank" rel="noopener" class="_"} are published and maintained by open-source projects sponsored by Docker through the program. +[Docker Sponsored Open Source images](https://hub.docker.com/search?q=&image_filter=open_source) are published and maintained by open-source projects sponsored by Docker through the program. Images that are part of this program have a special badge on Docker Hub making it easier for users to identify projects that Docker has verified as trusted, secure, and active open-source projects. @@ -42,7 +42,7 @@ over the repository can change the repository logo. #### Set the repository logo -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Go to the page of the repository that you want to change the logo for. 3. Select the upload logo button, represented by a camera icon (![Camera icon](images/upload_logo_sm.png){: .inline height="22px" }) @@ -56,7 +56,7 @@ Select the **Clear** button (![Clear button](images/clear_logo_sm.png){: .inline Removing the logo makes the repository default to using the organization logo, if set, or the following default logo if not. -![Default logo which is a 3D grey cube](images/default_logo_sm.png){: width="50px" } +![Default logo which is a 3D grey cube](images/default_logo_sm.png) ### Verified Docker-Sponsored Open Source badge @@ -93,7 +93,7 @@ basis. For more about using this feature, see [Basic vulnerability scanning](/do ### Who's eligible for the Docker-Sponsored Open Source program? -To qualify for the program, a publisher must share the project namespace in public repositories, meet [the Open Source Initiative definition](https://opensource.org/docs/osd){:target="_blank" rel="noopener" class="_"}, and be in active development with no pathway to commercialization. +To qualify for the program, a publisher must share the project namespace in public repositories, meet [the Open Source Initiative definition](https://opensource.org/docs/osd), and be in active development with no pathway to commercialization. Find out more by heading to the -[Docker-Sponsored Open Source Program](https://www.docker.com/community/open-source/application/){:target="_blank" rel="noopener" class="_"} application page. +[Docker-Sponsored Open Source Program](https://www.docker.com/community/open-source/application/) application page. \ No newline at end of file diff --git a/content/docker-hub/dvp-program.md b/content/docker-hub/dvp-program.md index 2c2bbf430f..914552ac14 100644 --- a/content/docker-hub/dvp-program.md +++ b/content/docker-hub/dvp-program.md @@ -1,27 +1,27 @@ --- description: Learn what the Docker Verified Publisher Program is and how it works title: Docker Verified Publisher Program -redirect_from: - - /docker-store/byol/ - - /docker-store/certify-images/ - - /docker-store/certify-plugins-logging/ - - /docker-store/customer_faq/ - - /docker-store/publisher_faq/ - - /docker-store/trustchain/ - - /docker-store/publish/ - - /docker-hub/publish/publish/ - - /docker-hub/publish/customer_faq/ - - /docker-hub/publish/publisher_faq/ - - /docker-hub/publish/certify-images/ - - /docker-hub/publish/certify-plugins-logging/ - - /docker-hub/publish/trustchain/ - - /docker-hub/publish/byol/ - - /docker-hub/publish/publisher-center-migration/ - - /docker-hub/publish/ - - /docker-hub/publish/repository-logos/ +aliases: +- /docker-store/byol/ +- /docker-store/certify-images/ +- /docker-store/certify-plugins-logging/ +- /docker-store/customer_faq/ +- /docker-store/publisher_faq/ +- /docker-store/trustchain/ +- /docker-store/publish/ +- /docker-hub/publish/publish/ +- /docker-hub/publish/customer_faq/ +- /docker-hub/publish/publisher_faq/ +- /docker-hub/publish/certify-images/ +- /docker-hub/publish/certify-plugins-logging/ +- /docker-hub/publish/trustchain/ +- /docker-hub/publish/byol/ +- /docker-hub/publish/publisher-center-migration/ +- /docker-hub/publish/ +- /docker-hub/publish/repository-logos/ --- -[The Docker Verified Publisher Program](https://hub.docker.com/search?q=&image_filter=store){:target="_blank" rel="noopener" class="_"} provides high-quality images from commercial publishers verified by Docker. +[The Docker Verified Publisher Program](https://hub.docker.com/search?q=&image_filter=store) provides high-quality images from commercial publishers verified by Docker. These images help development teams build secure software supply chains, minimizing exposure to malicious content early in the process to save time and money later. @@ -60,7 +60,7 @@ over the repository can change the repository logo. #### Set the repository logo -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Go to the page of the repository that you want to change the logo for. 3. Select the upload logo button, represented by a camera icon (![Camera icon](./images/upload_logo_sm.png){: .inline height="22px" }) @@ -74,7 +74,7 @@ Select the **Clear** button (![Clear button](images/clear_logo_sm.png){: .inline Removing the logo makes the repository default to using the organization logo, if set, or the following default logo if not. -![Default logo which is a 3D grey cube](images/default_logo_sm.png){: width="50px" } +![Default logo which is a 3D grey cube](images/default_logo_sm.png) ### Verified publisher badge @@ -109,5 +109,4 @@ basis. For more about using this feature, see [Basic vulnerability scanning](/do Any independent software vendor who distributes software on Docker Hub can join the Verified Publisher Program. Find out more by heading to the -[Docker Verified Publisher Program](https://www.docker.com/partners/programs){:target="_blank" -rel="noopener" class="_"} page. +[Docker Verified Publisher Program](https://www.docker.com/partners/programs) page. \ No newline at end of file diff --git a/content/docker-hub/general-faqs.md b/content/docker-hub/general-faqs.md index d1f3f7e1c4..6bd6c9bafd 100644 --- a/content/docker-hub/general-faqs.md +++ b/content/docker-hub/general-faqs.md @@ -3,7 +3,7 @@ title: General FAQs for Docker Hub description: Frequently asked administration and security questions keywords: onboarding, docker, teams, orgs redirect: - - /docker-hub/onboarding-faqs/ +- /docker-hub/onboarding-faqs/ --- ### What is a Docker ID? @@ -17,8 +17,7 @@ Developers may have multiple Docker IDs in order to separate their Docker IDs th ### What if my Docker ID is taken? -All Docker IDs are first-come, first-served except for companies that have a US Trademark on a username. If you have a trademark for your namespace, [Docker Support](https://hub.docker.com/support/contact/){: target="_blank" rel="noopener" -class="_"} can retrieve the Docker ID for you. +All Docker IDs are first-come, first-served except for companies that have a US Trademark on a username. If you have a trademark for your namespace, [Docker Support](https://hub.docker.com/support/contact/) can retrieve the Docker ID for you. ### What’s an organization? diff --git a/content/docker-hub/group-mapping.md b/content/docker-hub/group-mapping.md index ff21a23cb7..32ceaf8e3f 100644 --- a/content/docker-hub/group-mapping.md +++ b/content/docker-hub/group-mapping.md @@ -4,4 +4,4 @@ keywords: Group Mapping, SCIM, Docker Hub title: Group Mapping --- -{% include admin-group-mapping.md product="hub" %} \ No newline at end of file +{{% admin-group-mapping product="hub" %}} \ No newline at end of file diff --git a/content/docker-hub/image-access-management.md b/content/docker-hub/image-access-management.md index c339e152c4..478f5e5bb6 100644 --- a/content/docker-hub/image-access-management.md +++ b/content/docker-hub/image-access-management.md @@ -4,4 +4,4 @@ keywords: image, access, management title: Image Access Management --- -{% include admin-image-access.md product="hub" %} \ No newline at end of file +{{% admin-image-access product="hub" %}} \ No newline at end of file diff --git a/content/docker-hub/image-management.md b/content/docker-hub/image-management.md index 4acb82690e..212ceac4ab 100644 --- a/content/docker-hub/image-management.md +++ b/content/docker-hub/image-management.md @@ -18,7 +18,7 @@ It provides: ## Access the Advanced Image Management dashboard -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Select **Repositories**. 3. Choose a repository. 4. Select **General** or **Tags**, and then select **Go to Advanced Image Management**. @@ -37,4 +37,4 @@ For example, let's assume that Image A is tagged as ‘latest’. You push anoth ## Advanced Image Management API -The Advanced Image Management API endpoints allow you to manage Docker images across all repositories. For more information, see [Advanced Image management API](./api/latest.md). +The Advanced Image Management API endpoints allow you to manage Docker images across all repositories. For more information, see [Advanced Image management API](./api/latest.md). \ No newline at end of file diff --git a/content/docker-hub/insights-analytics.md b/content/docker-hub/insights-analytics.md index bd2a101a8f..ca5c7b0937 100644 --- a/content/docker-hub/insights-analytics.md +++ b/content/docker-hub/insights-analytics.md @@ -2,8 +2,8 @@ title: Insights and analytics description: Discover how to access usage statistics of your images on Docker Hub keywords: docker hub, hub, insights, analytics, api, verified publisher -redirect_from: - - /docker-hub/publish/insights-analytics/ +aliases: +- /docker-hub/publish/insights-analytics/ --- Insights and analytics provides usage analytics for Docker Verified @@ -13,9 +13,9 @@ Publisher (DVP) and Docker-Sponsored Open Source (DSOS) images on Docker Hub. Th > **Tip** > > Head to the -[Docker Verified Publisher Program](https://www.docker.com/partners/programs/){: target="blank" rel="noopener" class="_" } or [Docker-Sponsored Open Source](https://www.docker.com/community/open-source/application/#){: target="blank" rel="noopener" class="_" } pages +[Docker Verified Publisher Program](https://www.docker.com/partners/programs/) or [Docker-Sponsored Open Source](https://www.docker.com/community/open-source/application/#) pages to learn more about the programs. -{: .tip } +{ .tip } ## View the analytics data @@ -38,7 +38,7 @@ To view data in the chart: > > Hovering your cursor over the chart displays a tooltip, showing precise data > for points in time. -{: .tip } +{ .tip } ### Share analytics data @@ -55,8 +55,7 @@ configuration as you had set up when creating the link. ## Exporting analytics data You can export the analytics data either from the web dashboard, or using the -[DVP Data API](/docker-hub/api/dvp/){: target="_blank" rel="noopener" -class="_"}. All members of an organization have access to the analytics data. +[DVP Data API](/docker-hub/api/dvp/). All members of an organization have access to the analytics data. The data is available as a downloadable CSV file, in a weekly (Monday through Sunday) or monthly format. Monthly data is available from the first day of the @@ -67,8 +66,7 @@ can analyze it manually as a spreadsheet. Export usage data for your organization's images using the Docker Hub website by following these steps: -1. Sign in to [Docker Hub](https://hub.docker.com/){: target="_blank" - rel="noopener" class="_"} and select **Organizations**. +1. Sign in to [Docker Hub](https://hub.docker.com/) and select **Organizations**. 2. Choose your organization and select **Insights and analytics**. @@ -85,8 +83,7 @@ Export usage data for your organization's images using the Docker Hub website by The HTTP API endpoints are available at: `https://hub.docker.com/api/publisher/analytics/v1`. Learn how to export data -using the API in the [DVP Data API documentation](/docker-hub/api/dvp/){: -target="_blank" rel="noopener" class="_"}. +using the API in the [DVP Data API documentation](/docker-hub/api/dvp/). ## Data points @@ -160,8 +157,7 @@ user grants you more insight into your users' behavior. The following table describes the rules applied for determining intent behind pulls. To provide feedback or ask questions about these rules, -[fill out the Google Form](https://forms.gle/nb7beTUQz9wzXy1b6){: -target="_blank" rel="noopener" class="_"}. +[fill out the Google Form](https://forms.gle/nb7beTUQz9wzXy1b6). | Starting event | Reference | Followed by | Resulting action | Use case(s) | Notes | | :------------- | :-------- | :-------------------------------------------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -199,7 +195,7 @@ consumers of content on Docker Hub remain completely anonymous. > > Docker never shares any Personally Identifiable Information (PII) as part of > analytics data. -{: .important } +{ .important } The summary dataset includes unique IP address count. This data point only includes the number of distinct unique IP addresses that request an image. @@ -211,4 +207,4 @@ associated with the IP address used to pull an image. If the IP type is that IP address (for example, `docker.com`). For any other IP type that's not `business`, the domain represents the internet service provider or hosting provider used to make the request. On average, only about 30% of all pulls -classify as the `business` IP type (this varies between publishers and images). +classify as the `business` IP type (this varies between publishers and images). \ No newline at end of file diff --git a/content/docker-hub/manage-a-team.md b/content/docker-hub/manage-a-team.md index b74c7d292b..fa7aa8f6f2 100644 --- a/content/docker-hub/manage-a-team.md +++ b/content/docker-hub/manage-a-team.md @@ -1,6 +1,7 @@ --- description: Docker Hub Teams & Organizations -keywords: Docker, docker, registry, teams, organizations, plans, Dockerfile, Docker Hub, docs, documentation +keywords: Docker, docker, registry, teams, organizations, plans, Dockerfile, Docker + Hub, docs, documentation title: Create and manage a team --- @@ -50,7 +51,7 @@ To give a team access to a repository 4. Choose a permission from the **Permissions** drop-down list and select **Add**. - ![Team Repo Permissions](images/team-repo-permission.png){:width="700px"} + ![Team Repo Permissions](images/team-repo-permission.png) Organization owners can also assign members the editor role to grant partial administrative access. See [Roles and permissions](/docker-hub/roles-and-permissions/) for more about the editor role. @@ -96,7 +97,7 @@ To view a team's permissions across all repositories: You can also check out the following videos for information about creating Teams and Organizations in Docker Hub. -- [Overview of organizations](https://www.youtube-nocookie.com/embed/G7lvSnAqed8){: target="_blank" rel="noopener" class="_"} -- [Create an organization](https://www.youtube-nocookie.com/embed/b0TKcIqa9Po){: target="_blank" rel="noopener" class="_"} -- [Working with Teams](https://www.youtube-nocookie.com/embed/MROKmtmWCVI){: target="_blank" rel="noopener" class="_"} -- [Create Teams](https://www.youtube-nocookie.com/embed/78wbbBoasIc){: target="_blank" rel="noopener" class="_"} \ No newline at end of file +- [Overview of organizations](https://www.youtube-nocookie.com/embed/G7lvSnAqed8) +- [Create an organization](https://www.youtube-nocookie.com/embed/b0TKcIqa9Po) +- [Working with Teams](https://www.youtube-nocookie.com/embed/MROKmtmWCVI) +- [Create Teams](https://www.youtube-nocookie.com/embed/78wbbBoasIc) \ No newline at end of file diff --git a/content/docker-hub/members.md b/content/docker-hub/members.md index 005a1945b3..d38a5f9ed7 100644 --- a/content/docker-hub/members.md +++ b/content/docker-hub/members.md @@ -6,7 +6,7 @@ title: Manage members This section describes how to manage members in your [teams and organizations](../docker-hub/orgs.md). -{% include admin-users.md product="hub" %} +{{% admin-users product="hub" %}} ## Add a member to a team @@ -14,7 +14,7 @@ Organization owners can add a member to one or more teams within an organization To add a member to a team: -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Select **Organizations**, your organization, and then **Members**. 3. Select the **Action** icon, and then select **Add to team**. @@ -32,7 +32,7 @@ To add a member to a team: To remove a member from a specific team: -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Select **Organizations**, your organization, **Teams**, and then the team. 3. Select the **X** next to the user’s name to remove them from the team. 4. When prompted, select **Remove** to confirm. \ No newline at end of file diff --git a/content/docker-hub/new-company.md b/content/docker-hub/new-company.md index 4b306fa515..baae44b98f 100644 --- a/content/docker-hub/new-company.md +++ b/content/docker-hub/new-company.md @@ -19,7 +19,7 @@ To create a new company: >**Important** > > You must be a company owner to add an organization to a company. -{: .important} +{ .important } There is no limit to the number of organizations you can have under a company layer. All organizations must have a Business subscription. @@ -27,5 +27,4 @@ There is no limit to the number of organizations you can have under a company la 2. Select your company. 3. From the company page, select **Add organization**. 4. Choose the organization you want to add from the drop-down menu. -5. Select **Add organization** to confirm. - +5. Select **Add organization** to confirm. \ No newline at end of file diff --git a/content/docker-hub/oci-artifacts.md b/content/docker-hub/oci-artifacts.md index a3f2f75277..76201571e6 100644 --- a/content/docker-hub/oci-artifacts.md +++ b/content/docker-hub/oci-artifacts.md @@ -1,8 +1,9 @@ --- title: OCI artifacts on Docker Hub keywords: oci, artifacts, docker hub -description: > - You can use Docker Hub to store software artifacts packaged as OCI artifacts. +description: 'You can use Docker Hub to store software artifacts packaged as OCI artifacts. + + ' --- You can use Docker Hub to store any kind of software artifact, not just @@ -172,4 +173,4 @@ Steps: 4. Go to the repository page on Docker Hub. The **Tags** section on that page shows the artifact tag. - ![Repository page showing an artifact in the tag list](./images/oci-artifact.png) + ![Repository page showing an artifact in the tag list](./images/oci-artifact.png) \ No newline at end of file diff --git a/content/docker-hub/official_images.md b/content/docker-hub/official_images.md index 17c79268a8..fb7b439274 100644 --- a/content/docker-hub/official_images.md +++ b/content/docker-hub/official_images.md @@ -1,17 +1,18 @@ --- description: Guidelines for Official Images on Docker Hub -keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, official,image, documentation +keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, docs, + official,image, documentation title: Docker Official Images -redirect_from: - - /docker-hub/official_repos/ +aliases: +- /docker-hub/official_repos/ --- -The [Docker Official Images](https://hub.docker.com/search?q=&type=image&image_filter=official){:target="_blank" rel="noopener" class="_"} are a +The [Docker Official Images](https://hub.docker.com/search?q=&type=image&image_filter=official) are a curated set of Docker repositories hosted on Docker Hub. These images provide essential base repositories that serve as the starting point for the majority of users. -These include operating systems such as [Ubuntu](https://hub.docker.com/_/ubuntu/){:target="_blank" rel="noopener" class="_"} and [Alpine](https://hub.docker.com/_/alpine/){:target="_blank" rel="noopener" class="_"}, programming languages such as [Python](https://hub.docker.com/_/python) and [Node](https://hub.docker.com/_/node), and other essential tools such as [Redis](https://hub.docker.com/_/redis) and [MySQL](https://hub.docker.com/_/mysql). +These include operating systems such as [Ubuntu](https://hub.docker.com/_/ubuntu/) and [Alpine](https://hub.docker.com/_/alpine/), programming languages such as [Python](https://hub.docker.com/_/python) and [Node](https://hub.docker.com/_/node), and other essential tools such as [Redis](https://hub.docker.com/_/redis) and [MySQL](https://hub.docker.com/_/mysql). The images are some of the most secure images on Docker Hub. This is particularly important as Docker Official Images are some of the most popular on Docker Hub. Typically Docker Official images have little or no vulnerabilities. @@ -73,8 +74,8 @@ Official Image. From a high level, an Official Image starts out as a proposal in the form of a set of GitHub pull requests. The following GitHub repositories detail the proposal requirements: -- [docker-library/official-images](https://github.com/docker-library/official-images){:target="_blank" rel="noopener" class="_"} -- [docker-library/docs](https://github.com/docker-library/docs){:target="_blank" rel="noopener" class="_"} +- [docker-library/official-images](https://github.com/docker-library/official-images) +- [docker-library/docs](https://github.com/docker-library/docs) The Docker Official Images team, with help from community contributors, formally review each proposal and provide feedback to the author. This initial review @@ -82,7 +83,7 @@ process may require a bit of back-and-forth before the proposal is accepted. There are subjective considerations during the review process. These subjective concerns boil down to the basic question: "is this image generally -useful?" For example, the [Python](https://hub.docker.com/_/python/){:target="_blank" rel="noopener" class="_"} +useful?" For example, the [Python](https://hub.docker.com/_/python/) Docker Official Image is "generally useful" to the larger Python developer community, whereas an obscure text adventure game written in Python last week is not. @@ -90,4 +91,4 @@ not. Once a new proposal is accepted, the author is responsible for keeping their images up-to-date and responding to user feedback. The Official Repositories team becomes responsible for publishing the images and -documentation on Docker Hub. Updates to the Docker Official Image follow the same pull request process, though with less review. The Docker Official Images team ultimately acts as a gatekeeper for all changes, which helps mitigate the risk of quality and security issues from being introduced. +documentation on Docker Hub. Updates to the Docker Official Image follow the same pull request process, though with less review. The Docker Official Images team ultimately acts as a gatekeeper for all changes, which helps mitigate the risk of quality and security issues from being introduced. \ No newline at end of file diff --git a/content/docker-hub/onboard.md b/content/docker-hub/onboard.md index 86a8c05cbd..386402217c 100644 --- a/content/docker-hub/onboard.md +++ b/content/docker-hub/onboard.md @@ -4,9 +4,9 @@ keywords: business, team, organizations, get started, onboarding title: Onboard your organization toc_min: 1 toc_max: 2 -redirect_from: +aliases: - /docker-hub/onboard-team/ - /docker-hub/onboard-business/ --- -{% include admin-org-onboarding.md %} \ No newline at end of file +{{< include "admin-org-onboarding.md" >}} \ No newline at end of file diff --git a/content/docker-hub/organization-faqs.md b/content/docker-hub/organization-faqs.md index c7808dbab9..67c8b8b372 100644 --- a/content/docker-hub/organization-faqs.md +++ b/content/docker-hub/organization-faqs.md @@ -16,8 +16,7 @@ You can create multiple organizations or multiple teams under a single company. An existing owner can add additional team members as organization owners. All they need to do is select the organization from the -[Organizations](https://hub.docker.com/orgs){: target="_blank" rel="noopener" -class="_"} page in Docker Hub, add the Docker ID/Email of the user, and then +[Organizations](https://hub.docker.com/orgs) page in Docker Hub, add the Docker ID/Email of the user, and then select the owner role from the drop-down menu. See [Organization owner](manage-a-team.md#organization-owner). ### Do users first need to authenticate with Docker before an owner can add them to an organization? diff --git a/content/docker-hub/orgs.md b/content/docker-hub/orgs.md index 4362a15639..c7dce9263d 100644 --- a/content/docker-hub/orgs.md +++ b/content/docker-hub/orgs.md @@ -1,12 +1,13 @@ --- description: Docker Hub Teams & Organizations -keywords: Docker, docker, registry, teams, organizations, plans, Dockerfile, Docker Hub, docs, documentation +keywords: Docker, docker, registry, teams, organizations, plans, Dockerfile, Docker + Hub, docs, documentation title: Create your organization -redirect_from: +aliases: - /docker-cloud/orgs/ --- -{% include admin-org-overview.md %} +{{< include "admin-org-overview.md" >}} ## Create an organization @@ -19,12 +20,11 @@ detailed instructions on converting an existing user account to an organization, To create an organization: -1. Sign in to [Docker Hub](https://hub.docker.com/){: target="_blank" -rel="noopener" class="_"} using your [Docker ID](../docker-id/index.md) or your email address. +1. Sign in to [Docker Hub](https://hub.docker.com/) using your [Docker ID](../docker-id/index.md) or your email address. 2. Select **Organizations** and then **Create Organization** to create a new organization. 3. Choose a plan for your organization and select **Buy Now**. See -[Docker Pricing](https://www.docker.com/pricing/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"} +[Docker Pricing](https://www.docker.com/pricing/) for details on the features offered in the Team and Business plan. > **Note** @@ -114,8 +114,7 @@ You can also access your invoices from this tab. You can also check out the following videos for information about creating Teams and Organizations in Docker Hub. -- [Overview of organizations](https://www.youtube-nocookie.com/embed/G7lvSnAqed8){: target="_blank" rel="noopener" class="_"} -- [Create an organization](https://www.youtube-nocookie.com/embed/b0TKcIqa9Po){: target="_blank" rel="noopener" class="_"} -- [Working with Teams](https://www.youtube-nocookie.com/embed/MROKmtmWCVI){: target="_blank" rel="noopener" class="_"} -- [Create Teams](https://www.youtube-nocookie.com/embed/78wbbBoasIc){: target="_blank" rel="noopener" class="_"} - +- [Overview of organizations](https://www.youtube-nocookie.com/embed/G7lvSnAqed8) +- [Create an organization](https://www.youtube-nocookie.com/embed/b0TKcIqa9Po) +- [Working with Teams](https://www.youtube-nocookie.com/embed/MROKmtmWCVI) +- [Create Teams](https://www.youtube-nocookie.com/embed/78wbbBoasIc) \ No newline at end of file diff --git a/content/docker-hub/publish/_index.md b/content/docker-hub/publish/_index.md index ef2c1800c8..15451df608 100644 --- a/content/docker-hub/publish/_index.md +++ b/content/docker-hub/publish/_index.md @@ -1,27 +1,27 @@ --- description: Docker Verified Publisher Program title: Docker Verified Publisher Program -redirect_from: - - /docker-store/byol/ - - /docker-store/certify-images/ - - /docker-store/certify-plugins-logging/ - - /docker-store/customer_faq/ - - /docker-store/publisher_faq/ - - /docker-store/trustchain/ - - /docker-store/publish/ - - /docker-hub/publish/publish/ - - /docker-hub/publish/customer_faq/ - - /docker-hub/publish/publisher_faq/ - - /docker-hub/publish/certify-images/ - - /docker-hub/publish/certify-plugins-logging/ - - /docker-hub/publish/trustchain/ - - /docker-hub/publish/byol/ - - /docker-hub/publish/publisher-center-migration/ - - /docker-hub/publish/ - - /docker-hub/publish/repository-logos/ +aliases: +- /docker-store/byol/ +- /docker-store/certify-images/ +- /docker-store/certify-plugins-logging/ +- /docker-store/customer_faq/ +- /docker-store/publisher_faq/ +- /docker-store/trustchain/ +- /docker-store/publish/ +- /docker-hub/publish/publish/ +- /docker-hub/publish/customer_faq/ +- /docker-hub/publish/publisher_faq/ +- /docker-hub/publish/certify-images/ +- /docker-hub/publish/certify-plugins-logging/ +- /docker-hub/publish/trustchain/ +- /docker-hub/publish/byol/ +- /docker-hub/publish/publisher-center-migration/ +- /docker-hub/publish/ +- /docker-hub/publish/repository-logos/ --- -[The Docker Verified Publisher Program](https://hub.docker.com/search?q=&image_filter=store){:target="_blank" rel="noopener" class="_"} provides high-quality images from commercial publishers verified by Docker. +[The Docker Verified Publisher Program](https://hub.docker.com/search?q=&image_filter=store) provides high-quality images from commercial publishers verified by Docker. These images help development teams build secure software supply chains, minimizing exposure to malicious content early in the process to save time and money later. @@ -74,7 +74,7 @@ Remove a logo using the clear button (![Clear button](images/clear_logo_sm.png){ Removing the logo makes the repository fallback to using the organization logo, if set, and the default logo if not. -![Default logo which is a 3D grey cube](images/default_logo_sm.png){: width="50px" } +![Default logo which is a 3D grey cube](images/default_logo_sm.png) ### Verified publisher badge @@ -85,8 +85,7 @@ to identify projects that Docker has verified as high quality publishers and wit ### Insights and analytics -The [insights and analytics](/docker-hub/publish/insights-analytics){: -target="blank" rel="noopener" class=""} service provides usage metrics for how +The [insights and analytics](/docker-hub/publish/insights-analytics) service provides usage metrics for how the community uses Docker images, granting insight into user behavior. The usage metrics show the number of image pulls by tag or by digest, and breakdowns by @@ -99,20 +98,17 @@ either a summary or raw format. ### Vulnerability analysis -[Docker Scout](/scout/){: -target="blank" rel="noopener" class=""} provides automatic vulnerability analysis +[Docker Scout](/scout/) provides automatic vulnerability analysis for DVP images published to Docker Hub. Scanning images ensures that the published content is secure, and proves to developers that they can trust the image. Analysis is enabled on a per-repository -basis, refer to [vulnerability scanning](/docker-hub/vulnerability-scanning/){: -target="blank" rel="noopener" class=""} for more information about how to use +basis, refer to [vulnerability scanning](/docker-hub/vulnerability-scanning/) for more information about how to use it. ### Who's eligible to become a verified publisher? Any independent software vendor who distributes software on Docker Hub can join the Verified Publisher Program. Find out more by heading to the -[Docker Verified Publisher Program](https://www.docker.com/partners/programs){:target="_blank" -rel="noopener" class="_"} page. +[Docker Verified Publisher Program](https://www.docker.com/partners/programs) page. \ No newline at end of file diff --git a/content/docker-hub/publish/insights-analytics.md b/content/docker-hub/publish/insights-analytics.md index b3ac2d1b62..f0500d72e2 100644 --- a/content/docker-hub/publish/insights-analytics.md +++ b/content/docker-hub/publish/insights-analytics.md @@ -2,8 +2,8 @@ title: Insights and analytics description: Provides usage statistics of your images on Docker Hub. keywords: docker hub, hub, insights, analytics, api, verified publisher -redirect_from: - - /docker-hub/publish/insights-analytics/ +aliases: +- /docker-hub/publish/insights-analytics/ --- Insights and analytics provides usage analytics for Docker Verified @@ -16,9 +16,9 @@ geolocation, cloud provider, client, and more. > **Tip** > > Head to the -[Docker Verified Publisher Program](https://www.docker.com/partners/programs/){: target="blank" rel="noopener" class="_" } or [Docker-Sponsored Open Source](https://www.docker.com/community/open-source/application/#){: target="blank" rel="noopener" class="_" } pages +[Docker Verified Publisher Program](https://www.docker.com/partners/programs/) or [Docker-Sponsored Open Source](https://www.docker.com/community/open-source/application/#) pages to learn more about the programs. -{: .tip } +{ .tip } ## View the analytics data @@ -41,7 +41,7 @@ To view data in the chart: > > Hovering your cursor over the chart displays a tooltip, showing precise data > for points in time. -{: .tip } +{ .tip } ### Share analytics data @@ -58,8 +58,7 @@ configuration as you had set up when creating the link. ## Exporting analytics data You can export the analytics data either from the web dashboard, or using the -[DVP Data API](/docker-hub/api/dvp/){: target="_blank" rel="noopener" -class="_"}. All members of an organization have access to the analytics data. +[DVP Data API](/docker-hub/api/dvp/). All members of an organization have access to the analytics data. The data is available as a downloadable CSV file, in a weekly (Monday through Sunday) or monthly format. Monthly data is available from the first day of the @@ -70,8 +69,7 @@ can analyze it manually as a spreadsheet. Export usage data for your organization's images using the Docker Hub website by following these steps: -1. Sign in to [Docker Hub](https://hub.docker.com/){: target="_blank" - rel="noopener" class="_"} and select **Organizations**. +1. Sign in to [Docker Hub](https://hub.docker.com/) and select **Organizations**. 2. Choose your organization and select **Insights and analytics**. @@ -88,8 +86,7 @@ Export usage data for your organization's images using the Docker Hub website by The HTTP API endpoints are available at: `https://hub.docker.com/api/publisher/analytics/v1`. Learn how to export data -using the API in the [DVP Data API documentation](/docker-hub/api/dvp/){: -target="_blank" rel="noopener" class="_"}. +using the API in the [DVP Data API documentation](/docker-hub/api/dvp/). ## Data points @@ -163,8 +160,7 @@ user grants you more insight into your users' behavior. The following table describes the rules applied for determining intent behind pulls. To provide feedback or ask questions about these rules, -[fill out the Google Form](https://forms.gle/nb7beTUQz9wzXy1b6){: -target="_blank" rel="noopener" class="_"}. +[fill out the Google Form](https://forms.gle/nb7beTUQz9wzXy1b6). | Starting event | Reference | Followed by | Resulting action | Use case(s) | Notes | | :------------- | :-------- | :-------------------------------------------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -202,7 +198,7 @@ consumers of content on Docker Hub remain completely anonymous. > > Docker never shares any Personally Identifiable Information (PII) as part of > analytics data. -{: .important } +{ .important } The summary dataset includes unique IP address count. This data point only includes the number of distinct unique IP addresses that request an image. @@ -214,4 +210,4 @@ associated with the IP address used to pull an image. If the IP type is that IP address (for example, `docker.com`). For any other IP type that's not `business`, the domain represents the internet service provider or hosting provider used to make the request. On average, only about 30% of all pulls -classify as the `business` IP type (this varies between publishers and images). +classify as the `business` IP type (this varies between publishers and images). \ No newline at end of file diff --git a/content/docker-hub/publish/repository-logos.md b/content/docker-hub/publish/repository-logos.md index 4b3e451e7a..efa486ac1a 100644 --- a/content/docker-hub/publish/repository-logos.md +++ b/content/docker-hub/publish/repository-logos.md @@ -34,4 +34,4 @@ Remove a logo using the clear button (![Clear button](../images/clear_logo_sm.pn Removing the logo makes the repository fallback to using the organization logo, if set, and the default logo if not. -![Default logo which is a 3D grey cube](./images/default_logo_sm.png){: .inline height="22px" } +![Default logo which is a 3D grey cube](./images/default_logo_sm.png){: .inline height="22px" } \ No newline at end of file diff --git a/content/docker-hub/quickstart.md b/content/docker-hub/quickstart.md index 5f8569d32a..a6cf0edd1f 100644 --- a/content/docker-hub/quickstart.md +++ b/content/docker-hub/quickstart.md @@ -1,8 +1,9 @@ --- description: Learn how to get started using Docker Hub -keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, accounts, organizations, repositories, groups, teams +keywords: Docker, docker, registry, accounts, plans, Dockerfile, Docker Hub, accounts, + organizations, repositories, groups, teams title: Docker Hub Quickstart -redirect_from: +aliases: - /apidocs/docker-cloud/ - /docker-cloud/ - /docker-cloud/migration/ @@ -80,7 +81,7 @@ The following section contains step-by-step instructions on how to get started w ### Step 1: Sign up for a Docker account -Start by creating a [Docker ID](https://hub.docker.com/signup){: target="_blank" rel="noopener" class="_"}. +Start by creating a [Docker ID](https://hub.docker.com/signup). A Docker ID grants you access to Docker Hub repositories and lets you explore available images from the community and verified publishers. You also need a Docker ID to share images on Docker Hub. @@ -88,7 +89,7 @@ A Docker ID grants you access to Docker Hub repositories and lets you explore av To create a repository: -1. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"}. +1. Sign in to [Docker Hub](https://hub.docker.com). 2. Select **Create a Repository** on the Docker Hub welcome page. 3. Name it **<your-username>/my-private-repo**. 4. Set the visibility to **Private**. @@ -186,4 +187,4 @@ You've successfully: - Automatically build container images from code through [builds](builds/index.md). - [Explore](https://hub.docker.com/explore) official & publisher images. - [Upgrade your subscription](https://www.docker.com/pricing) to push additional private Docker images to -Docker Hub. +Docker Hub. \ No newline at end of file diff --git a/content/docker-hub/registry-access-management.md b/content/docker-hub/registry-access-management.md index 1831b8de1b..6e719b3c40 100644 --- a/content/docker-hub/registry-access-management.md +++ b/content/docker-hub/registry-access-management.md @@ -4,4 +4,4 @@ keywords: registry, access, management title: Registry Access Management --- -{% include admin-registry-access.md product="hub" %} \ No newline at end of file +{{% admin-registry-access product="hub" %}} \ No newline at end of file diff --git a/content/docker-hub/release-notes.md b/content/docker-hub/release-notes.md index 637f905af6..c5e1ddd59b 100644 --- a/content/docker-hub/release-notes.md +++ b/content/docker-hub/release-notes.md @@ -1,6 +1,7 @@ --- title: Docker Hub release notes -description: Learn about the new features, bug fixes, and breaking changes for Docker Hub +description: Learn about the new features, bug fixes, and breaking changes for Docker + Hub keywords: docker hub, whats new, release notes toc_min: 1 toc_max: 2 @@ -9,7 +10,7 @@ toc_max: 2 Here you can learn about the latest changes, new features, bug fixes, and known issues for each Docker Hub release. -Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/projects/1){: target="_blank" rel="noopener" class="_"} to see what's coming next. +Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/projects/1) to see what's coming next. ## 2023-07-26 @@ -94,7 +95,7 @@ Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/pro ### New -Docker has [announced](https://www.docker.com/blog/updating-product-subscriptions/){: target="*blank" rel="noopener" class="*" id="dkr_docs_relnotes_btl"} updates and extensions to the product subscriptions to increase productivity, collaboration, and added security for our developers and businesses. Docker subscription tiers now include Personal, Pro, Team, and Business. +Docker has [announced](https://www.docker.com/blog/updating-product-subscriptions/) updates and extensions to the product subscriptions to increase productivity, collaboration, and added security for our developers and businesses. Docker subscription tiers now include Personal, Pro, Team, and Business. The updated [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) includes a change to the terms for **Docker Desktop**. @@ -105,7 +106,7 @@ The updated [Docker Subscription Service Agreement](https://www.docker.com/legal - The existing Docker Free subscription has been renamed **Docker Personal**. - **No changes** to Docker Engine or any other upstream **open source** Docker or Moby project. - To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq){: target="*blank" rel="noopener" class="*" id="dkr_docs_relnotes_btl"}. For more information, see [Docker subscription overview](../subscription/index.md). + To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq). For more information, see [Docker subscription overview](../subscription/index.md). ## 2021-05-05 @@ -187,7 +188,7 @@ to `hub.docker.com`. You can access the page at its new URL: [https://hub.docker > If you lose both your 2FA authentication device and recovery code, you may > not be able to recover your account. - {: .important } + { .important } ### Enhancements * As a security measure, when two-factor authentication is enabled, the Docker CLI requires a personal access token instead of a password to log in. @@ -257,4 +258,4 @@ has been updated. ### Known Issues -* Scan results don't appear for some official images. +* Scan results don't appear for some official images. \ No newline at end of file diff --git a/content/docker-hub/repos/_index.md b/content/docker-hub/repos/_index.md index 4593d82f66..8fc617461f 100644 --- a/content/docker-hub/repos/_index.md +++ b/content/docker-hub/repos/_index.md @@ -1,8 +1,9 @@ --- description: Learn how to use repositories on Docker Hub -keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub, webhooks, docs, documentation, manage, repos +keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub, + webhooks, docs, documentation, manage, repos title: Manage repositories -redirect_from: +aliases: - /engine/tutorials/dockerrepos/ --- @@ -15,7 +16,7 @@ redirect_from: You get one free private repository with your Docker Hub user account (not available for organizations you're a member of). If you need more private -repositories for your user account, upgrade your Docker Hub subscription from your [Billing Information](https://hub.docker.com/billing/plan){: target="_blank" rel="noopener" class="_"} page. +repositories for your user account, upgrade your Docker Hub subscription from your [Billing Information](https://hub.docker.com/billing/plan) page. ## Move images between repositories @@ -23,7 +24,7 @@ repositories for your user account, upgrade your Docker Hub subscription from yo When consolidating personal repositories, you can pull private images from the initial repository and push them into another repository owned by you. To avoid losing your private images, perform the following steps: -1. Navigate to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} create a new Docker ID and select the personal subscription. +1. Navigate to [Docker Hub](https://hub.docker.com) create a new Docker ID and select the personal subscription. 2. Using `docker login` from the CLI, sign in using your original Docker ID and pull your private images. 3. Tag your private images with your newly created Docker ID, for example: @@ -42,9 +43,9 @@ The private images that existed in your previous account are now available in yo To avoid losing your private images, you can pull your private images from your personal account and push them to an organization that's owned by you. -1. Navigate to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} and select **Organizations**. +1. Navigate to [Docker Hub](https://hub.docker.com) and select **Organizations**. 2. Select the applicable organization and verify that your user account is a member of the organization. -3. Sign in to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} using your original Docker ID, and pull your images: +3. Sign in to [Docker Hub](https://hub.docker.com) using your original Docker ID, and pull your images: ```console $ docker pull namespace1/docker101tutorial @@ -67,7 +68,7 @@ The private images that existed in your user account are now available for your > **Warning** > > Deleting a repository deletes all the images it contains and its build settings. This action can't be undone. -{: .warning} +{ .warning } 1. Navigate to your repository. 2. Select the **Settings** tab. diff --git a/content/docker-hub/repos/access/_index.md b/content/docker-hub/repos/access/_index.md index 89a853a768..a7b6654fec 100644 --- a/content/docker-hub/repos/access/_index.md +++ b/content/docker-hub/repos/access/_index.md @@ -1,6 +1,7 @@ --- description: Discover how to access repositories on Docker Hub -keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub, webhooks, docs, documentation, collaborators, viewing, searching, starring +keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub, + webhooks, docs, documentation, collaborators, viewing, searching, starring title: Access repositories --- @@ -83,4 +84,4 @@ You now have an image from which you can run containers. ## Star repositories -Stars are a way to show that you like a repository. They're also an easy way of bookmarking your favorites. +Stars are a way to show that you like a repository. They're also an easy way of bookmarking your favorites. \ No newline at end of file diff --git a/content/docker-hub/repos/create.md b/content/docker-hub/repos/create.md index 6563b60126..cd3e6aacb4 100644 --- a/content/docker-hub/repos/create.md +++ b/content/docker-hub/repos/create.md @@ -1,9 +1,10 @@ --- description: Learn how to create repositories on Docker Hub -keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub, webhooks, docs, documentation, manage, repos +keywords: Docker, docker, trusted, registry, accounts, plans, Dockerfile, Docker Hub, + webhooks, docs, documentation, manage, repos title: Create repositories toc_max: 3 -redirect_from: +aliases: - /docker-hub/repos/configure/ --- diff --git a/content/docker-hub/roles-and-permissions.md b/content/docker-hub/roles-and-permissions.md index 55f3e6e6a6..46652b2814 100644 --- a/content/docker-hub/roles-and-permissions.md +++ b/content/docker-hub/roles-and-permissions.md @@ -1,5 +1,6 @@ --- -description: Use roles in your organization to control who has access to content, registry, and organization management permissions. +description: Use roles in your organization to control who has access to content, + registry, and organization management permissions. keywords: members, teams, organization, company, roles, access title: Roles and permissions --- @@ -75,4 +76,4 @@ The following outlines organization management permissions for member, editor, o | Manage seats | ❌ | ❌ | ✅ | ✅ | | Upgrade and downgrade plans | ❌ | ❌ | ✅ | ✅ | -_* If not part of a company_ +_* If not part of a company_ \ No newline at end of file diff --git a/content/docker-hub/scim.md b/content/docker-hub/scim.md index 1824ffc165..d2ce6da433 100644 --- a/content/docker-hub/scim.md +++ b/content/docker-hub/scim.md @@ -2,8 +2,8 @@ description: System for Cross-domain Identity Management keywords: SCIM, SSO title: SCIM -direct_from: +direct_from: - /docker-hub/company-scim/ --- -{% include admin-scim.md %} +{{< include "admin-scim.md" >}} \ No newline at end of file diff --git a/content/docker-hub/service-accounts.md b/content/docker-hub/service-accounts.md index 1025e24735..af4f8b575f 100644 --- a/content/docker-hub/service-accounts.md +++ b/content/docker-hub/service-accounts.md @@ -3,6 +3,7 @@ description: Docker Service accounts keywords: Docker, service, accounts, Docker Hub title: Service accounts --- + > **Note** > > Service accounts requires a @@ -24,7 +25,7 @@ Refer to the following table for details on the Enhanced Service Account add-on | 2 | 10,000-25,000 | $17,950/yr | | 3 | 25,000-50,000 | $32,950/yr | | 4 | 50,000-100,000 | $58,950/yr | -| 5 | 100,000+ | [Contact Sales](https://www.docker.com/pricing/contact-sales/){:target="_blank" rel="noopener" class="_"} | +| 5 | 100,000+ | [Contact Sales](https://www.docker.com/pricing/contact-sales/) | *Once you establish the initial Tier, that's the minimum fee for the year. Annual commitment required. The service account may exceed Pulls by up to 25% for up to 20 days during the year without incurring additional fees. Reports on consumption are available upon request. At the end of the initial 1-year term, the appropriate Tier will be established for the following year. @@ -56,4 +57,4 @@ official images and other public images, you don't have to grant any access perm Refer to the following topics for additional information: - [Mirroring Docker Hub](../registry/recipes/mirror.md) -- [Resource Consumption Updates FAQ](https://www.docker.com/pricing/resource-consumption-updates){:target="_blank" rel="noopener" class="_"} +- [Resource Consumption Updates FAQ](https://www.docker.com/pricing/resource-consumption-updates) \ No newline at end of file diff --git a/content/docker-hub/slack_integration.md b/content/docker-hub/slack_integration.md index 00d25651b9..682a839ab3 100644 --- a/content/docker-hub/slack_integration.md +++ b/content/docker-hub/slack_integration.md @@ -1,11 +1,11 @@ --- 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 sitemap: false +aliases: +- /docker-cloud/tutorials/slack-integration/ +- /docker-cloud/slack-integration/ --- Docker Hub can integrate with your **Slack** team to provide notifications about builds. @@ -45,4 +45,4 @@ Enjoy your new Slack channel 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 Slack App Management page and search for "Docker Hub". Click the result to see all of the Docker Hub notification channels set for the Slack team. +* Alternately, go to the Slack App Management page and search for "Docker Hub". Click the result to see all of the Docker Hub notification channels set for the Slack team. \ No newline at end of file diff --git a/content/docker-hub/vulnerability-scanning.md b/content/docker-hub/vulnerability-scanning.md index 800a5e6e3a..396d250fb5 100644 --- a/content/docker-hub/vulnerability-scanning.md +++ b/content/docker-hub/vulnerability-scanning.md @@ -72,8 +72,7 @@ Business tier. To enable Basic vulnerability scanning: -1. Sign in to your [Docker Hub](https://hub.docker.com){: target="_blank" - rel="noopener" class="_"} account. +1. Sign in to your [Docker Hub](https://hub.docker.com) account. 2. Select **Repositories** and then choose a repository. 3. Go to the **Settings** tab. 4. Under **Image insight settings**, select **Basic Hub vulnerability @@ -107,14 +106,13 @@ repository for which you have turned on scanning: To view the vulnerability report: -1. Go to [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" - class="_"} and open the repository page to view a summary of the Basic +1. Go to [Docker Hub](https://hub.docker.com) and open the repository page to view a summary of the Basic vulnerability scanning report. It may take a couple of minutes for the vulnerability report to appear in your repository. - ![Vulnerability scan report](images/vuln-scan-report.png){:width="700px"} + ![Vulnerability scan report](images/vuln-scan-report.png) 2. Select the **Tags** tab, then **Digest**, then **Vulnerabilities** to view the detailed scan report. @@ -125,7 +123,7 @@ To view the vulnerability report: version in which it was introduced, and whether the vulnerability is fixed in a later version. - ![Vulnerability scan details](images/vuln-scan-details.png){:width="700px"} + ![Vulnerability scan details](images/vuln-scan-details.png) For more information on this view, see [Image details view](../scout/image-details-view.md). @@ -164,9 +162,8 @@ improving image security. For more information, see Repository owners and administrators can disable Basic vulnerability scanning on a repository. To disable scanning: -1. Sign in to your [Docker Hub](https://hub.docker.com){: target="_blank" - rel="noopener" class="_"} account. +1. Sign in to your [Docker Hub](https://hub.docker.com) account. 2. Go to **Repositories** and then select a repository from the list. 3. Go to the **Settings** tab. 4. Under **Image insight settings**, select **None**. -5. Select **Save**. +5. Select **Save**. \ No newline at end of file diff --git a/content/docker-hub/webhooks.md b/content/docker-hub/webhooks.md index 70fd896441..0cc4cf85ac 100644 --- a/content/docker-hub/webhooks.md +++ b/content/docker-hub/webhooks.md @@ -86,4 +86,4 @@ The following parameters are recognized in callback data: "description": "387 tests PASSED", "context": "Continuous integration by Acme CI", "target_url": "https://ci.acme.com/results/afd339c1c3d27" - } + } \ No newline at end of file diff --git a/content/docker-id/_index.md b/content/docker-id/_index.md index 7260a8b82d..4da8a60ede 100644 --- a/content/docker-id/_index.md +++ b/content/docker-id/_index.md @@ -1,8 +1,9 @@ --- description: Learn how to register for a Docker ID and log in to your account -keywords: accounts, docker ID, billing, paid plans, support, Hub, Store, Forums, knowledge base, beta access, email, activation, verification +keywords: accounts, docker ID, billing, paid plans, support, Hub, Store, Forums, knowledge + base, beta access, email, activation, verification title: Create an account -redirect_from: +aliases: - /docker-cloud/dockerid/ - /docker-hub/accounts/ --- @@ -45,13 +46,12 @@ You can also sign in through the CLI using the `docker login` command. For more stored in your home directory in `.docker/config.json`. The password is base64-encoded in this file. > > We recommend using one of the [Docker credential helpers](https://github.com/docker/docker-credential-helpers) for secure storage of passwords. For extra security, you can also use a [personal access token](../docker-hub/access-tokens.md) to log in instead, which is still encoded in this file (without a Docker credential helper) but doesn't allow admin actions (such as changing the password). -{:.warning} +{ .warning } ## Troubleshooting -If you run into trouble with your Docker ID account, know that we're here to help! If you want to retrieve or reset your password, [enter your email address](https://id.docker.com/reset-password/){: target="_blank" rel="noopener" class="_"} for additional instructions. +If you run into trouble with your Docker ID account, know that we're here to help! If you want to retrieve or reset your password, [enter your email address](https://id.docker.com/reset-password/) for additional instructions. You can use the [Docker forums](https://forums.docker.com/) to ask questions amongst other Docker community members, while our [hub-feedback GitHub repository](https://github.com/docker/hub-feedback) allows you to provide feedback on how we can better improve the experience with Docker Hub. -If you still need any help, [create a support ticket](https://hub.docker.com/support/contact/) and let us know how we can help you. - +If you still need any help, [create a support ticket](https://hub.docker.com/support/contact/) and let us know how we can help you. \ No newline at end of file diff --git a/content/engine/_index.md b/content/engine/_index.md index 55f3ed686a..e262ea6220 100644 --- a/content/engine/_index.md +++ b/content/engine/_index.md @@ -1,51 +1,50 @@ --- description: Engine keywords: Engine -redirect_from: - - /edge/ - - /engine/ce-ee-node-activate/ - - /engine/misc/ - - /linux/ - - /manuals/ # TODO remove this redirect after we've created a landing page for the product manuals section title: Docker Engine overview grid: - - title: "Install Docker Engine" - description: - "Learn how to install the open source Docker Engine for your distribution." - icon: "download" - link: "/engine/install" - - title: "Storage" - description: "Use persistent data with Docker containers." - icon: "database" - link: "/storage" - - title: "Networking" - description: "Manage network connections between containers." - icon: "lan" - link: "/network" - - title: "Container logs" - description: "Learn how to view and read container logs." - icon: "feed" - link: "/config/containers/logging/" - - title: "Prune" - description: "Tidy up unused resources." - icon: "cut" - link: "/config/pruning" - - title: "Configure the daemon" - description: "Delve into the configuration options of the Docker daemon." - icon: "tune" - link: "/config/daemon" - - title: "Rootless mode" - description: "Run Docker without root privileges." - icon: "security" - link: "/security" - - title: "Deprecated features" - description: "Find out what features of Docker Engine you should stop using." - icon: "note_add" - link: "/engine/deprecated/" - - title: "Release notes" - description: "Read the release notes for the latest version." - icon: "note_add" - link: "/engine/release-notes" +- title: Install Docker Engine + description: Learn how to install the open source Docker Engine for your distribution. + icon: download + link: /engine/install +- title: Storage + description: Use persistent data with Docker containers. + icon: database + link: /storage +- title: Networking + description: Manage network connections between containers. + icon: lan + link: /network +- title: Container logs + description: Learn how to view and read container logs. + icon: feed + link: /config/containers/logging/ +- title: Prune + description: Tidy up unused resources. + icon: cut + link: /config/pruning +- title: Configure the daemon + description: Delve into the configuration options of the Docker daemon. + icon: tune + link: /config/daemon +- title: Rootless mode + description: Run Docker without root privileges. + icon: security + link: /security +- title: Deprecated features + description: Find out what features of Docker Engine you should stop using. + icon: note_add + link: /engine/deprecated/ +- title: Release notes + description: Read the release notes for the latest version. + icon: note_add + link: /engine/release-notes +aliases: +- /edge/ +- /engine/ce-ee-node-activate/ +- /engine/misc/ +- /linux/ +- /manuals/ --- Docker Engine is an open source containerization technology for building and @@ -73,5 +72,4 @@ For more details, see The Docker Engine is licensed under the Apache License, Version 2.0. See [LICENSE](https://github.com/moby/moby/blob/master/LICENSE) for the full license -text. - +text. \ No newline at end of file diff --git a/content/engine/alternative-runtimes.md b/content/engine/alternative-runtimes.md index 6807c5a74f..6c4b37991c 100644 --- a/content/engine/alternative-runtimes.md +++ b/content/engine/alternative-runtimes.md @@ -1,9 +1,12 @@ --- title: Alternative container runtimes -description: | - Docker Engine uses runc as the default container runtime, but you +description: 'Docker Engine uses runc as the default container runtime, but you + can specify alternative runtimes using the CLI or by configuring + the daemon + + ' keywords: engine, runtime, containerd, runtime v2, shim --- @@ -14,21 +17,21 @@ By default, containerd uses runc as its container runtime. ## What runtimes can I use? You can use any runtime that implements the containerd -[shim API](https://github.com/containerd/containerd/blob/main/runtime/v2/README.md){: target="blank" rel="noopener"}. +[shim API](https://github.com/containerd/containerd/blob/main/runtime/v2/README.md). Such runtimes ship with a containerd shim, and you can use them without any additional configuration. See [Use containerd shims](#use-containerd-shims). Examples of runtimes that implement their own containerd shims include: -- [Wasmtime](https://wasmtime.dev/){: target="blank" rel="noopener"} -- [gVisor](https://github.com/google/gvisor){: target="blank" rel="noopener"} -- [Kata Containers](https://katacontainers.io/){: target="blank" rel="noopener"} +- [Wasmtime](https://wasmtime.dev/) +- [gVisor](https://github.com/google/gvisor) +- [Kata Containers](https://katacontainers.io/) You can also use runtimes designed as drop-in replacements for runc. Such runtimes depend on the runc containerd shim for invoking the runtime binary. You must manually register such runtimes in the daemon configuration. -[youki](https://github.com/containers/youki){: target="blank" rel="noopener"} +[youki](https://github.com/containers/youki) is one example of a runtime that can function as a runc drop-in replacement. Refer to the [youki example](#youki) explaining the setup. @@ -131,7 +134,7 @@ To add youki as a container runtime: 1. Install youki and its dependencies. For instructions, refer to the - [official setup guide](https://containers.github.io/youki/user/basic_setup.html){: target="\_blank" rel="noopener"}. + [official setup guide](https://containers.github.io/youki/user/basic_setup.html). 2. Register youki as a runtime for Docker by editing the Docker daemon configuration file, located at `/etc/docker/daemon.json` by default. @@ -165,7 +168,7 @@ $ docker run --rm --runtime youki hello-world ### Wasmtime Wasmtime is a -[Bytecode Alliance](https://bytecodealliance.org/){:target="\_blank" rel="noopener"} +[Bytecode Alliance](https://bytecodealliance.org/) project, and a Wasm runtime that lets you run Wasm containers. Running Wasm containers with Docker provides two layers of security. You get all the benefits from container isolation, @@ -232,4 +235,4 @@ $ docker run --rm \ - To learn more about the configuration options for container runtimes, see [Configure container runtimes](./reference/commandline/dockerd.md#configure-container-runtimes). - You can configure which runtime that the daemon should use as its default. - Refer to [Configure the default container runtime](./reference/commandline/dockerd.md#configure-the-default-container-runtime). + Refer to [Configure the default container runtime](./reference/commandline/dockerd.md#configure-the-default-container-runtime). \ No newline at end of file diff --git a/content/engine/api/_index.md b/content/engine/api/_index.md index 647cb07e32..1143d36886 100644 --- a/content/engine/api/_index.md +++ b/content/engine/api/_index.md @@ -2,7 +2,7 @@ title: Develop with Docker Engine API description: Using Docker APIs to automate Docker tasks in your language of choice keywords: developing, api -redirect_from: +aliases: - /engine/reference/api/ - /engine/reference/api/docker_remote_api/ - /reference/api/ @@ -119,15 +119,15 @@ You can specify the API version to use, in one of the following ways: that is used. - For the SDKs, you can also specify the API version programmatically, as a parameter to the `client` object. See the - [Go constructor](https://pkg.go.dev/github.com/docker/docker/client#NewClientWithOpts){: target="_blank" rel="noopener" class="_"} + [Go constructor](https://pkg.go.dev/github.com/docker/docker/client#NewClientWithOpts) or the - [Python SDK documentation for `client`](https://docker-py.readthedocs.io/en/stable/client.html){: target="_blank" rel="noopener" class="_"}. + [Python SDK documentation for `client`](https://docker-py.readthedocs.io/en/stable/client.html). ### API version matrix -{% include api-version-matrix.md %} +{{< include "api-version-matrix.md" >}} ### Archived API versions Documentation for older versions of the API has been archived, but can be found -in the [docker code repository on GitHub](https://github.com/moby/moby/tree/v1.9.1/docs/reference/api){: target="_blank" rel="noopener" class="_"} +in the [docker code repository on GitHub](https://github.com/moby/moby/tree/v1.9.1/docs/reference/api) \ No newline at end of file diff --git a/content/engine/api/sdk/_index.md b/content/engine/api/sdk/_index.md index ee284f25ea..1de7b0d712 100644 --- a/content/engine/api/sdk/_index.md +++ b/content/engine/api/sdk/_index.md @@ -2,7 +2,7 @@ title: Develop with Docker Engine SDKs description: Using Docker SDKs to automate Docker tasks in your language of choice keywords: developing, sdk -redirect_from: +aliases: - /engine/api/sdks/ - /develop/sdk/ --- @@ -147,15 +147,15 @@ print(client.containers.run("alpine", ["echo", "hello", "world"])) ```console $ curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" \ -d '{"Image": "alpine", "Cmd": ["echo", "hello world"]}' \ - -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/create + -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/create {"Id":"1c6594faf5","Warnings":null} -$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/start +$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/start -$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/wait +$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/wait {"StatusCode":0} -$ curl --unix-socket /var/run/docker.sock "http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/logs?stdout=1" +$ curl --unix-socket /var/run/docker.sock "http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/logs?stdout=1" hello world ``` @@ -165,12 +165,12 @@ examples above use `localhost`, but any hostname would work. > **Using cURL 7.47.0 or below?** > > The examples above assume you are using cURL 7.50.0 or above. Older versions of -> cURL used a [non-standard URL notation](https://github.com/moby/moby/issues/17960){:target="_blank" rel="noopener" class="_"} +> cURL used a [non-standard URL notation](https://github.com/moby/moby/issues/17960) > when using a socket connection. > > If you are using an older version of cURL, use `http://` instead, -> for example, `http:/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/start` -{: .important} +> for example, `http:/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/start` +{ .important } {{< /tab >}} {{< /tabs >}} @@ -209,4 +209,4 @@ file them with the library maintainers. | Rust | [shiplift](https://github.com/softprops/shiplift) | | Scala | [tugboat](https://github.com/softprops/tugboat) | | Scala | [reactive-docker](https://github.com/almoehi/reactive-docker) | -| Swift | [docker-client-swift](https://github.com/valeriomazzeo/docker-client-swift) | +| Swift | [docker-client-swift](https://github.com/valeriomazzeo/docker-client-swift) | \ No newline at end of file diff --git a/content/engine/api/sdk/examples.md b/content/engine/api/sdk/examples.md index bec35abe4a..a6351ad7f1 100644 --- a/content/engine/api/sdk/examples.md +++ b/content/engine/api/sdk/examples.md @@ -1,8 +1,9 @@ --- title: Examples using the Docker Engine SDKs and Docker API -description: Examples on how to perform a given Docker operation using the Go and Python SDKs and the HTTP API using curl. +description: Examples on how to perform a given Docker operation using the Go and + Python SDKs and the HTTP API using curl. keywords: developing, api, sdk, developers, rest, curl, python, go -redirect_from: +aliases: - /engine/api/getting-started/ - /engine/api/client-libraries/ - /engine/reference/api/remote_api_client_libraries/ @@ -106,15 +107,15 @@ print(client.containers.run("alpine", ["echo", "hello", "world"])) ```console $ curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" \ -d '{"Image": "alpine", "Cmd": ["echo", "hello world"]}' \ - -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/create + -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/create {"Id":"1c6594faf5","Warnings":null} -$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/start +$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/start -$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/wait +$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/wait {"StatusCode":0} -$ curl --unix-socket /var/run/docker.sock "http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/logs?stdout=1" +$ curl --unix-socket /var/run/docker.sock "http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/logs?stdout=1" hello world ``` @@ -124,12 +125,12 @@ examples above use `localhost`, but any hostname would work. > **Using cURL 7.47.0 or below?** > > The examples above assume you are using cURL 7.50.0 or above. Older versions of -> cURL used a [non-standard URL notation](https://github.com/moby/moby/issues/17960){:target="_blank" rel="noopener" class="_"} +> cURL used a [non-standard URL notation](https://github.com/moby/moby/issues/17960) > when using a socket connection. > > If you are using an older version of cURL, use `http://` instead, -> for example, `http:/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/start` -{: .important} +> for example, `http:/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/start` +{ .important } {{< /tab >}} {{< /tabs >}} @@ -204,10 +205,10 @@ print(container.id) ```console $ curl --unix-socket /var/run/docker.sock -H "Content-Type: application/json" \ -d '{"Image": "bfirsh/reticulate-splines"}' \ - -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/create + -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/create {"Id":"1c6594faf5","Warnings":null} -$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/1c6594faf5/start +$ curl --unix-socket /var/run/docker.sock -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/1c6594faf5/start ``` {{< /tab >}} @@ -265,7 +266,7 @@ for container in client.containers.list(): {{< tab name="HTTP" >}} ```console -$ curl --unix-socket /var/run/docker.sock http://localhost/v{{ site.latest_engine_api_version}}/containers/json +$ curl --unix-socket /var/run/docker.sock http://localhost/v{{% param "latest_engine_api_version" %}}/containers/json [{ "Id":"ae63e8b89a26f01f6b4b2c9a7817c31a1b6196acf560f66586fbc8809ffcd772", "Names":["/tender_wing"], @@ -339,7 +340,7 @@ for container in client.containers.list(): {{< tab name="HTTP" >}} ```console -$ curl --unix-socket /var/run/docker.sock http://localhost/v{{ site.latest_engine_api_version}}/containers/json +$ curl --unix-socket /var/run/docker.sock http://localhost/v{{% param "latest_engine_api_version" %}}/containers/json [{ "Id":"ae63e8b89a26f01f6b4b2c9a7817c31a1b6196acf560f66586fbc8809ffcd772", "Names":["/tender_wing"], @@ -348,7 +349,7 @@ $ curl --unix-socket /var/run/docker.sock http://localhost/v{{ site.latest_engin }] $ curl --unix-socket /var/run/docker.sock \ - -X POST http://localhost/v{{ site.latest_engine_api_version}}/containers/ae63e8b89a26/stop + -X POST http://localhost/v{{% param "latest_engine_api_version" %}}/containers/ae63e8b89a26/stop ``` {{< /tab >}} @@ -408,7 +409,7 @@ print(container.logs()) {{< tab name="HTTP" >}} ```console -$ curl --unix-socket /var/run/docker.sock "http://localhost/v{{ site.latest_engine_api_version}}/containers/ca5f55cdb/logs?stdout=1" +$ curl --unix-socket /var/run/docker.sock "http://localhost/v{{% param "latest_engine_api_version" %}}/containers/ca5f55cdb/logs?stdout=1" Reticulating spline 1... Reticulating spline 2... Reticulating spline 3... @@ -470,7 +471,7 @@ for image in client.images.list(): {{< tab name="HTTP" >}} ```console -$ curl --unix-socket /var/run/docker.sock http://localhost/v{{ site.latest_engine_api_version}}/images/json +$ curl --unix-socket /var/run/docker.sock http://localhost/v{{% param "latest_engine_api_version" %}}/images/json [{ "Id":"sha256:31d9a31e1dd803470c5a151b8919ef1988ac3efd44281ac59d43ad623f275dcd", "ParentId":"sha256:ee4603260daafe1a8c2f3b78fd760922918ab2441cbb2853ed5c439e59c52f96", @@ -534,7 +535,7 @@ print(image.id) ```console $ curl --unix-socket /var/run/docker.sock \ - -X POST "http://localhost/v{{ site.latest_engine_api_version}}/images/create?fromImage=alpine" + -X POST "http://localhost/v{{% param "latest_engine_api_version" %}}/images/create?fromImage=alpine" {"status":"Pulling from library/alpine","id":"3.1"} {"status":"Pulling fs layer","progressDetail":{},"id":"8f13703509f7"} {"status":"Downloading","progressDetail":{"current":32768,"total":2244027},"progress":"[\u003e ] 32.77 kB/2.244 MB","id":"8f13703509f7"} @@ -602,8 +603,7 @@ func main() { The Python SDK retrieves authentication information from the [credentials store](/engine/reference/commandline/login/#credentials-store) file and integrates with [credential -helpers](https://github.com/docker/docker-credential-helpers){: target="_blank" -class="_" }. It is possible to override these credentials, but that is out of +helpers](https://github.com/docker/docker-credential-helpers). It is possible to override these credentials, but that is out of scope for this Getting Started guide. After using `docker login`, the Python SDK uses these credentials automatically. @@ -626,7 +626,7 @@ $ JSON=$(echo '{"username": "string", "password": "string", "serveraddress": "st $ curl --unix-socket /var/run/docker.sock \ -H "Content-Type: application/tar" - -X POST "http://localhost/v{{ site.latest_engine_api_version}}/images/create?fromImage=alpine" + -X POST "http://localhost/v{{% param "latest_engine_api_version" %}}/images/create?fromImage=alpine" -H "X-Registry-Auth" -d "$JSON" {"status":"Pulling from library/alpine","id":"3.1"} @@ -714,9 +714,9 @@ print(image.id) $ docker run -d alpine touch /helloworld 0888269a9d584f0fa8fc96b3c0d8d57969ceea3a64acf47cd34eebb4744dbc52 $ curl --unix-socket /var/run/docker.sock\ - -X POST "http://localhost/v{{ site.latest_engine_api_version}}/commit?container=0888269a9d&repo=helloworld" + -X POST "http://localhost/v{{% param "latest_engine_api_version" %}}/commit?container=0888269a9d&repo=helloworld" {"Id":"sha256:6c86a5cd4b87f2771648ce619e319f3e508394b5bfc2cdbd2d60f59d52acda6c"} ``` {{< /tab >}} -{{< /tabs >}} +{{< /tabs >}} \ No newline at end of file diff --git a/content/engine/api/v1.25.md b/content/engine/api/v1.25.md index 84bb01c802..31d4f17e54 100644 --- a/content/engine/api/v1.25.md +++ b/content/engine/api/v1.25.md @@ -1,5 +1,5 @@ --- layout: engine-api -redirect_from: - - /engine/reference/api/docker_remote_api_v1.25/ ---- +aliases: +- /engine/reference/api/docker_remote_api_v1.25/ +--- \ No newline at end of file diff --git a/content/engine/api/v1.26.md b/content/engine/api/v1.26.md index 4f9f113f36..0b5443338b 100644 --- a/content/engine/api/v1.26.md +++ b/content/engine/api/v1.26.md @@ -1,5 +1,5 @@ --- layout: engine-api -redirect_from: - - /engine/reference/api/docker_remote_api_v1.26/ ---- +aliases: +- /engine/reference/api/docker_remote_api_v1.26/ +--- \ No newline at end of file diff --git a/content/engine/api/v1.27.md b/content/engine/api/v1.27.md index 953f0221ac..f5f2217957 100644 --- a/content/engine/api/v1.27.md +++ b/content/engine/api/v1.27.md @@ -1,5 +1,5 @@ --- layout: engine-api -redirect_from: - - /engine/reference/api/docker_remote_api_v1.27/ ---- +aliases: +- /engine/reference/api/docker_remote_api_v1.27/ +--- \ No newline at end of file diff --git a/content/engine/api/v1.28.md b/content/engine/api/v1.28.md index 6cb5c39bc6..b27f524273 100644 --- a/content/engine/api/v1.28.md +++ b/content/engine/api/v1.28.md @@ -1,5 +1,5 @@ --- layout: engine-api -redirect_from: - - /engine/reference/api/docker_remote_api_v1.28/ ---- +aliases: +- /engine/reference/api/docker_remote_api_v1.28/ +--- \ No newline at end of file diff --git a/content/engine/api/v1.29.md b/content/engine/api/v1.29.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.29.md +++ b/content/engine/api/v1.29.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.30.md b/content/engine/api/v1.30.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.30.md +++ b/content/engine/api/v1.30.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.31.md b/content/engine/api/v1.31.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.31.md +++ b/content/engine/api/v1.31.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.32.md b/content/engine/api/v1.32.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.32.md +++ b/content/engine/api/v1.32.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.33.md b/content/engine/api/v1.33.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.33.md +++ b/content/engine/api/v1.33.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.34.md b/content/engine/api/v1.34.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.34.md +++ b/content/engine/api/v1.34.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.35.md b/content/engine/api/v1.35.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.35.md +++ b/content/engine/api/v1.35.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.36.md b/content/engine/api/v1.36.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.36.md +++ b/content/engine/api/v1.36.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.37.md b/content/engine/api/v1.37.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.37.md +++ b/content/engine/api/v1.37.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.38.md b/content/engine/api/v1.38.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.38.md +++ b/content/engine/api/v1.38.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.39.md b/content/engine/api/v1.39.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.39.md +++ b/content/engine/api/v1.39.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.40.md b/content/engine/api/v1.40.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.40.md +++ b/content/engine/api/v1.40.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.41.md b/content/engine/api/v1.41.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.41.md +++ b/content/engine/api/v1.41.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.42.md b/content/engine/api/v1.42.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.42.md +++ b/content/engine/api/v1.42.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/api/v1.43.md b/content/engine/api/v1.43.md index 4b058956a8..caa6d1129b 100644 --- a/content/engine/api/v1.43.md +++ b/content/engine/api/v1.43.md @@ -1,3 +1,3 @@ --- layout: engine-api ---- +--- \ No newline at end of file diff --git a/content/engine/breaking_changes.md b/content/engine/breaking_changes.md index ad292d4ca2..ea584e13f7 100644 --- a/content/engine/breaking_changes.md +++ b/content/engine/breaking_changes.md @@ -1,9 +1,9 @@ --- -redirect_from: -- /engine/misc/breaking/ description: Breaking changes keywords: docker, documentation, about, technology, breaking, incompatibilities title: Breaking changes and incompatibilities +aliases: +- /engine/misc/breaking/ --- Every Engine release strives to be backward compatible with its predecessors, @@ -48,4 +48,4 @@ work as you would expect. Engine older than the current 1.10 cannot pull images from repositories that have enabled key delegation. Key delegation is a feature which requires a -manual action to enable. +manual action to enable. \ No newline at end of file diff --git a/content/engine/context/working-with-contexts.md b/content/engine/context/working-with-contexts.md index eeb0bf382f..4d93fa8f91 100644 --- a/content/engine/context/working-with-contexts.md +++ b/content/engine/context/working-with-contexts.md @@ -4,7 +4,6 @@ description: Learn about Docker Context keywords: engine, context, cli, kubernetes --- - ## Introduction This guide shows how _contexts_ make it easy for a **single Docker CLI** to manage multiple Swarm clusters, multiple Kubernetes clusters, and multiple individual Docker nodes. @@ -269,4 +268,4 @@ The following example updates the "Description" field in the existing `k8s-test` $ docker context update k8s-test --description "Test Kubernetes cluster" k8s-test Successfully updated context "k8s-test" -``` +``` \ No newline at end of file diff --git a/content/engine/faq.md b/content/engine/faq.md index 044e3f5218..9ca1571b07 100644 --- a/content/engine/faq.md +++ b/content/engine/faq.md @@ -1,9 +1,9 @@ --- description: Most frequently asked questions. keywords: faq, questions, documentation, docker -redirect_from: -- /engine/misc/faq/ title: Docker frequently asked questions (FAQ) +aliases: +- /engine/misc/faq/ --- ### Does Docker run on Linux, macOS, and Windows? @@ -63,7 +63,7 @@ use it as a base for 10 different applications. Your ideal PostgreSQL setup can be re-used for all your future projects. And so on. - *Sharing.* Docker has access to a public registry [on Docker -Hub](https://hub.docker.com/){: target="_blank" rel="noopener" class="_"} where thousands of +Hub](https://hub.docker.com/) where thousands of people have uploaded useful images: anything from Redis, CouchDB, PostgreSQL to IRC bouncers to Rails app servers to Hadoop to base images for various Linux distros. The [*registry*](../registry/index.md) also includes an official "standard @@ -83,7 +83,7 @@ private containers, for internal server deployments for example. ### What is different between a Docker container and a VM? There's a great StackOverflow answer [showing the differences]( -https://stackoverflow.com/questions/16047306/how-is-docker-io-different-from-a-normal-virtual-machine){: target="_blank" rel="noopener" class="_"}. +https://stackoverflow.com/questions/16047306/how-is-docker-io-different-from-a-normal-virtual-machine). ### Do I lose my data when the container exits? @@ -119,12 +119,12 @@ You can learn about the project's security policy ### Why do I need to sign my commits to Docker with the DCO? Read [our blog post]( -https://www.docker.com/blog/docker-code-contributions-require-developer-certificate-of-origin/){: target="_blank" rel="noopener" class="_"} on the introduction of the DCO. +https://www.docker.com/blog/docker-code-contributions-require-developer-certificate-of-origin/) on the introduction of the DCO. ### When building an image, should I prefer system libraries or bundled ones? *This is a summary of a discussion on the [docker-dev mailing list]( -https://groups.google.com/forum/#!topic/docker-dev/L2RBSPDu1L0){: target="_blank" rel="noopener" class="_"}.* +https://groups.google.com/forum/#!topic/docker-dev/L2RBSPDu1L0).* Virtually all programs depend on third-party libraries. Most frequently, they use dynamic linking and some kind of package dependency, so that when @@ -141,7 +141,7 @@ The key point about system libraries is not about saving disk or memory space. It is about security. All major distributions handle security seriously, by having dedicated security teams, following up closely with published vulnerabilities, and disclosing advisories themselves. (Look at the [Debian -Security Information](https://www.debian.org/security/){: target="_blank" rel="noopener" class="_"} +Security Information](https://www.debian.org/security/) for an example of those procedures.) Upstream developers, however, do not always implement similar practices. @@ -155,7 +155,7 @@ Likewise, before using packages built by others, you should check if the channels providing those packages implement similar security best practices. Downloading and installing an "all-in-one" .deb or .rpm sounds great at first, except if you have no way to figure out that it contains a copy of the OpenSSL -library vulnerable to the [Heartbleed](https://heartbleed.com){: target="_blank" rel="noopener" class="_"} bug. +library vulnerable to the [Heartbleed](https://heartbleed.com) bug. ### Why is `DEBIAN_FRONTEND=noninteractive` discouraged in Dockerfiles? @@ -185,7 +185,7 @@ Because of this, and because setting `DEBIAN_FRONTEND` to `noninteractive` is mainly a 'cosmetic' change, we *discourage* changing it. If you *really* need to change its setting, make sure to change it back to its -[default value](https://www.debian.org/releases/stable/amd64/ch05s03.en.html#installer-args){: target="_blank" rel="noopener" class="_"} +[default value](https://www.debian.org/releases/stable/amd64/ch05s03.en.html#installer-args) afterwards. ### Why do I get `Connection reset by peer` when making a request to a service running in a container? @@ -222,8 +222,8 @@ You need to tell Docker to talk to that machine. You can do this with the You can find more answers on: -- [Docker community Slack channel](https://dockr.ly/slack){: target="_blank" rel="noopener" class="_"} -- [Docker Support Forums](https://forums.docker.com){: target="_blank" rel="noopener" class="_"} -- [GitHub](https://github.com/moby/moby){: target="_blank" rel="noopener" class="_"} -- [Ask questions on Stackoverflow](https://stackoverflow.com/search?q=docker){: target="_blank" rel="noopener" class="_"} -- [Join the conversation on Twitter](https://twitter.com/docker){: target="_blank" rel="noopener" class="_"} +- [Docker community Slack channel](https://dockr.ly/slack) +- [Docker Support Forums](https://forums.docker.com) +- [GitHub](https://github.com/moby/moby) +- [Ask questions on Stackoverflow](https://stackoverflow.com/search?q=docker) +- [Join the conversation on Twitter](https://twitter.com/docker) \ No newline at end of file diff --git a/content/engine/install/_index.md b/content/engine/install/_index.md index 36315791b6..7522da56ba 100644 --- a/content/engine/install/_index.md +++ b/content/engine/install/_index.md @@ -1,8 +1,11 @@ --- -title: Install Docker Engine -description: Choose the best method for you to install Docker Engine. This client-server application is available on Linux, Mac, Windows, and as a static binary. -keywords: install engine, docker engine install, install docker engine, docker engine installation, engine install, docker ce installation, docker ce install, engine installer, installing docker engine, docker server install -redirect_from: +title: Install Docker Engine +description: Choose the best method for you to install Docker Engine. This client-server + application is available on Linux, Mac, Windows, and as a static binary. +keywords: install engine, docker engine install, install docker engine, docker engine + installation, engine install, docker ce installation, docker ce install, engine + installer, installing docker engine, docker server install +aliases: - /cs-engine/ - /cs-engine/1.12/ - /cs-engine/1.12/upgrade/ @@ -26,6 +29,8 @@ redirect_from: - /engine/installation/oracle/ - /enterprise/supported-platforms/ - /install/linux/docker-ee/oracle/ +'yes': '![yes](/assets/images/green-check.svg){: .inline style="height: 14px; margin: + 0 auto"}' --- > **Docker Desktop for Linux** @@ -34,7 +39,7 @@ redirect_from: > Windows as you do on Linux. Docker Desktop for > Linux is now GA. For more information, see [Docker Desktop for Linux](../../desktop/install/linux-install.md). -{: .important} +{ .important } ## Supported platforms @@ -45,13 +50,12 @@ your preferred operating system below. ### Desktop -{% assign yes = '![yes](/assets/images/green-check.svg){: .inline style="height: 14px; margin: 0 auto"}' %} | Platform | x86_64 / amd64 | arm64 (Apple Silicon) | | :--------------------------------------------------------------------- | :---------------------------------------------------: | :-----------------------------------------------: | -| [Docker Desktop for Linux](../../desktop/install/linux-install.md) | [{{ yes }}](../../desktop/install/linux-install.md) | | -| [Docker Desktop for Mac (macOS)](../../desktop/install/mac-install.md) | [{{ yes }}](../../desktop/install/mac-install.md) | [{{ yes }}](../../desktop/install/mac-install.md) | -| [Docker Desktop for Windows](../../desktop/install/windows-install.md) | [{{ yes }}](../../desktop/install/windows-install.md) | | +| [Docker Desktop for Linux](../../desktop/install/linux-install.md) | [{{% param "yes" %}}](../../desktop/install/linux-install.md) | | +| [Docker Desktop for Mac (macOS)](../../desktop/install/mac-install.md) | [{{% param "yes" %}}](../../desktop/install/mac-install.md) | [{{% param "yes" %}}](../../desktop/install/mac-install.md) | +| [Docker Desktop for Windows](../../desktop/install/windows-install.md) | [{{% param "yes" %}}](../../desktop/install/windows-install.md) | | ### Server @@ -60,14 +64,14 @@ and architectures: | Platform | x86_64 / amd64 | arm64 / aarch64 | arm (32-bit) | ppc64le | s390x | | :------------------------------------ | :--------------------- | :--------------------- | :------------------------------ | :--------------------- | :--------------------- | -| [CentOS](centos.md) | [{{ yes }}](centos.md) | [{{ yes }}](centos.md) | | [{{ yes }}](centos.md) | | -| [Debian](debian.md) | [{{ yes }}](debian.md) | [{{ yes }}](debian.md) | [{{ yes }}](debian.md) | [{{ yes }}](debian.md) | | -| [Fedora](fedora.md) | [{{ yes }}](fedora.md) | [{{ yes }}](fedora.md) | | [{{ yes }}](fedora.md) | | -| [Raspberry Pi OS](raspberry-pi-os.md) | | | [{{ yes }}](raspberry-pi-os.md) | | | -| [RHEL](rhel.md) | | | | | [{{ yes }}](rhel.md) | -| [SLES](sles.md) | | | | | [{{ yes }}](sles.md) | -| [Ubuntu](ubuntu.md) | [{{ yes }}](ubuntu.md) | [{{ yes }}](ubuntu.md) | [{{ yes }}](ubuntu.md) | [{{ yes }}](ubuntu.md) | [{{ yes }}](ubuntu.md) | -| [Binaries](binaries.md) | [{{yes}}](binaries.md) | [{{yes}}](binaries.md) | [{{yes}}](binaries.md) | | | +| [CentOS](centos.md) | [{{% param "yes" %}}](centos.md) | [{{% param "yes" %}}](centos.md) | | [{{% param "yes" %}}](centos.md) | | +| [Debian](debian.md) | [{{% param "yes" %}}](debian.md) | [{{% param "yes" %}}](debian.md) | [{{% param "yes" %}}](debian.md) | [{{% param "yes" %}}](debian.md) | | +| [Fedora](fedora.md) | [{{% param "yes" %}}](fedora.md) | [{{% param "yes" %}}](fedora.md) | | [{{% param "yes" %}}](fedora.md) | | +| [Raspberry Pi OS](raspberry-pi-os.md) | | | [{{% param "yes" %}}](raspberry-pi-os.md) | | | +| [RHEL](rhel.md) | | | | | [{{% param "yes" %}}](rhel.md) | +| [SLES](sles.md) | | | | | [{{% param "yes" %}}](sles.md) | +| [Ubuntu](ubuntu.md) | [{{% param "yes" %}}](ubuntu.md) | [{{% param "yes" %}}](ubuntu.md) | [{{% param "yes" %}}](ubuntu.md) | [{{% param "yes" %}}](ubuntu.md) | [{{% param "yes" %}}](ubuntu.md) | +| [Binaries](binaries.md) | [{{% param "yes" %}}](binaries.md) | [{{% param "yes" %}}](binaries.md) | [{{% param "yes" %}}](binaries.md) | | | ### Other Linux distros @@ -115,7 +119,7 @@ Docker provides support for Docker products, including Docker Desktop, which use Docker Engine as one of its components. For information about the open source project, refer to the -[Moby project website](https://mobyproject.org/){:target="_blank" rel="noopener"}. +[Moby project website](https://mobyproject.org/). ### Upgrade path @@ -138,4 +142,4 @@ Security reports are greatly appreciated, and Docker will publicly thank you for ## Get started After setting up Docker, you can learn the basics with -[Getting started with Docker](../../get-started/index.md). +[Getting started with Docker](../../get-started/index.md). \ No newline at end of file diff --git a/content/engine/install/binaries.md b/content/engine/install/binaries.md index 40097c4cf7..342a0e337b 100644 --- a/content/engine/install/binaries.md +++ b/content/engine/install/binaries.md @@ -1,8 +1,9 @@ --- -description: Instructions for installing Docker as a binary. Mostly meant for hackers who want to try out Docker on a variety of environments. +description: Instructions for installing Docker as a binary. Mostly meant for hackers + who want to try out Docker on a variety of environments. keywords: binaries, installation, docker, documentation, linux title: Install Docker Engine from binaries -redirect_from: +aliases: - /engine/installation/binaries/ - /engine/installation/linux/docker-ce/binaries/ - /install/linux/docker-ce/binaries/ @@ -30,7 +31,7 @@ redirect_from: > On Windows and Mac, we recommend that you install [Docker Desktop](../../desktop/index.md) > instead. For Linux, we recommend that you follow the instructions specific for > your distribution. -{: .important} +{ .important } If you want to try Docker or use it in a testing environment, but you're not on a supported platform, you can try installing from static binaries. If possible, @@ -85,7 +86,7 @@ instructions for enabling and configuring AppArmor or SELinux. > If either of the security mechanisms is enabled, do not disable it as a > work-around to make Docker or its containers run. Instead, configure it > correctly to fix any problems. -{:.warning} +{ .warning } ##### Docker daemon considerations @@ -139,7 +140,7 @@ instructions for enabling and configuring AppArmor or SELinux. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} ## Install client binaries on macOS @@ -253,4 +254,4 @@ version. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/centos.md b/content/engine/install/centos.md index f41f483acc..31841dab1c 100644 --- a/content/engine/install/centos.md +++ b/content/engine/install/centos.md @@ -1,7 +1,11 @@ --- -description: Learn how to install Docker Engine on CentOS. These instructions cover the different installation methods, how to uninstall, and next steps. -keywords: install docker centos, centos install docker, docker install centos, yum install docker, install docker centos 7, install docker centos 8, centos docker-ce -redirect_from: +description: Learn how to install Docker Engine on CentOS. These instructions cover + the different installation methods, how to uninstall, and next steps. +keywords: install docker centos, centos install docker, docker install centos, yum + install docker, install docker centos 7, install docker centos 8, centos docker-ce +title: Install Docker Engine on CentOS +toc_max: 4 +aliases: - /ee/docker-ee/centos/ - /engine/installation/centos/ - /engine/installation/linux/centos/ @@ -10,8 +14,7 @@ redirect_from: - /install/linux/centos/ - /install/linux/docker-ce/centos/ - /install/linux/docker-ee/centos/ -title: Install Docker Engine on CentOS -toc_max: 4 +download-url-base: https://download.docker.com/linux/centos --- To get started with Docker Engine on CentOS, make sure you @@ -31,7 +34,7 @@ CentOS versions: The `centos-extras` repository must be enabled. This repository is enabled by default, but if you have disabled it, you need to -[re-enable it](https://wiki.centos.org/AdditionalResources/Repositories){: target="_blank" rel="noopener" class="_" }. +[re-enable it](https://wiki.centos.org/AdditionalResources/Repositories). ### Uninstall old versions @@ -80,14 +83,13 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/centos" %} Install the `yum-utils` package (which provides the `yum-config-manager` utility) and set up the repository. ```console $ sudo yum install -y yum-utils -$ sudo yum-config-manager --add-repo {{ download-url-base }}/docker-ce.repo +$ sudo yum-config-manager --add-repo {{% param "download-url-base" %}}/docker-ce.repo ``` #### Install Docker Engine @@ -162,7 +164,7 @@ $ sudo yum-config-manager --add-repo {{ download-url-base }}/docker-ce.repo You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -175,7 +177,7 @@ If you can't use Docker's `rpm` repository to install Docker Engine, you can download the `.rpm` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [{{ download-url-base }}/]({{ download-url-base }}/){: target="_blank" rel="noopener" class="_" } +1. Go to [{{% param "download-url-base" %}}/]({{% param "download-url-base" %}}/) and choose your version of CentOS. Then browse to `x86_64/stable/Packages/` and download the `.rpm` file for the Docker version you want to install. @@ -207,7 +209,7 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -215,7 +217,7 @@ To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), using `yum -y upgrade` instead of `yum -y install`, and point to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -239,4 +241,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/debian.md b/content/engine/install/debian.md index 798ebd8424..3bd0399eb2 100644 --- a/content/engine/install/debian.md +++ b/content/engine/install/debian.md @@ -1,14 +1,14 @@ --- description: Instructions for installing Docker Engine on Debian -keywords: - requirements, apt, installation, debian, install, uninstall, upgrade, update -redirect_from: - - /engine/installation/debian/ - - /engine/installation/linux/debian/ - - /engine/installation/linux/docker-ce/debian/ - - /install/linux/docker-ce/debian/ +keywords: requirements, apt, installation, debian, install, uninstall, upgrade, update title: Install Docker Engine on Debian toc_max: 4 +aliases: +- /engine/installation/debian/ +- /engine/installation/linux/debian/ +- /engine/installation/linux/docker-ce/debian/ +- /install/linux/docker-ce/debian/ +download-url-base: https://download.docker.com/linux/debian --- To get started with Docker Engine on Debian, make sure you @@ -93,7 +93,6 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/debian" %} 1. Update the `apt` package index and install packages to allow `apt` to use a repository over HTTPS: @@ -107,7 +106,7 @@ Docker from the repository. ```console $ sudo install -m 0755 -d /etc/apt/keyrings - $ curl -fsSL {{ download-url-base }}/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg + $ curl -fsSL {{% param "download-url-base" %}}/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg $ sudo chmod a+r /etc/apt/keyrings/docker.gpg ``` @@ -115,7 +114,7 @@ Docker from the repository. ```console $ echo \ - "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] {{ download-url-base }} \ + "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] {{% param "download-url-base" %}} \ "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null ``` @@ -186,7 +185,7 @@ Docker from the repository. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -200,8 +199,7 @@ If you can't use Docker's `apt` repository to install Docker Engine, you can download the `deb` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [`{{ download-url-base }}/dists/`]({{ download-url-base }}/dists/){: - target="_blank" rel="noopener" class="_" }. +1. Go to [`{{% param "download-url-base" %}}/dists/`]({{% param "download-url-base" %}}/dists/). 2. Select your Debian version in the list. @@ -243,14 +241,14 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), pointing to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -274,4 +272,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/fedora.md b/content/engine/install/fedora.md index ffc332db2b..98d68be156 100644 --- a/content/engine/install/fedora.md +++ b/content/engine/install/fedora.md @@ -1,13 +1,15 @@ --- description: Instructions for installing Docker Engine on Fedora -keywords: requirements, apt, installation, fedora, rpm, install, uninstall, upgrade, update -redirect_from: +keywords: requirements, apt, installation, fedora, rpm, install, uninstall, upgrade, + update +title: Install Docker Engine on Fedora +toc_max: 4 +aliases: - /engine/installation/fedora/ - /engine/installation/linux/fedora/ - /engine/installation/linux/docker-ce/fedora/ - /install/linux/docker-ce/fedora/ -title: Install Docker Engine on Fedora -toc_max: 4 +download-url-base: https://download.docker.com/linux/fedora --- To get started with Docker Engine on Fedora, make sure you @@ -73,14 +75,13 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/fedora" %} Install the `dnf-plugins-core` package (which provides the commands to manage your DNF repositories) and set up the repository. ```console $ sudo dnf -y install dnf-plugins-core -$ sudo dnf config-manager --add-repo {{ download-url-base }}/docker-ce.repo +$ sudo dnf config-manager --add-repo {{% param "download-url-base" %}}/docker-ce.repo ``` #### Install Docker Engine @@ -154,7 +155,7 @@ $ sudo dnf config-manager --add-repo {{ download-url-base }}/docker-ce.repo You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -167,7 +168,7 @@ If you can't use Docker's `rpm` repository to install Docker Engine, you can download the `.rpm` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [{{ download-url-base }}/]({{ download-url-base }}/){: target="_blank" rel="noopener" class="_" } +1. Go to [{{% param "download-url-base" %}}/]({{% param "download-url-base" %}}/) and choose your version of Fedora. Then browse to `x86_64/stable/Packages/` and download the `.rpm` file for the Docker version you want to install. @@ -199,7 +200,7 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -207,7 +208,7 @@ To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), using `dnf -y upgrade` instead of `dnf -y install`, and point to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -231,4 +232,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/linux-postinstall.md b/content/engine/install/linux-postinstall.md index b0387ee348..454430e20f 100644 --- a/content/engine/install/linux-postinstall.md +++ b/content/engine/install/linux-postinstall.md @@ -1,11 +1,14 @@ --- -description: Find the recommended Docker Engine post-installation steps for Linux users, including how to run Docker as a non-root user and more. -keywords: run docker without sudo, docker running as root, docker post install, docker post installation, run docker as non root, docker non root user, how to run docker in linux, how to run docker linux, how to start docker in linux, run docker on linux +description: Find the recommended Docker Engine post-installation steps for Linux + users, including how to run Docker as a non-root user and more. +keywords: run docker without sudo, docker running as root, docker post install, docker + post installation, run docker as non root, docker non root user, how to run docker + in linux, how to run docker linux, how to start docker in linux, run docker on linux title: Linux post-installation steps for Docker Engine -redirect_from: - - /engine/installation/linux/docker-ee/linux-postinstall/ - - /engine/installation/linux/linux-postinstall/ - - /install/linux/linux-postinstall/ +aliases: +- /engine/installation/linux/docker-ee/linux-postinstall/ +- /engine/installation/linux/linux-postinstall/ +- /install/linux/linux-postinstall/ --- These optional post-installation procedures shows you how to configure your @@ -30,7 +33,7 @@ manually create the group. > The `docker` group grants root-level privileges to the user. For > details on how this impacts security in your system, see > [Docker Daemon Attack Surface](../security/index.md#docker-daemon-attack-surface). -{: .warning} +{ .warning } > **Note** > @@ -139,4 +142,4 @@ options: - Read the [Get started](../../get-started/index.md) training modules to learn how to build an image and run it as a containerized application. - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/raspberry-pi-os.md b/content/engine/install/raspberry-pi-os.md index ff52821178..5ad09904d1 100644 --- a/content/engine/install/raspberry-pi-os.md +++ b/content/engine/install/raspberry-pi-os.md @@ -1,12 +1,13 @@ --- description: Instructions for installing Docker Engine on Raspberry Pi OS -keywords: - requirements, apt, installation, Raspberry Pi OS, install, uninstall, upgrade, update -redirect_from: - - /engine/installation/linux/raspbian/ - - /engine/install/raspbian/ +keywords: requirements, apt, installation, Raspberry Pi OS, install, uninstall, upgrade, + update title: Install Docker Engine on Raspberry Pi OS toc_max: 4 +aliases: +- /engine/installation/linux/raspbian/ +- /engine/install/raspbian/ +download-url-base: https://download.docker.com/linux/raspbian --- To get started with Docker Engine on Raspberry Pi OS, make sure you @@ -93,7 +94,6 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/raspbian" %} 1. Update the `apt` package index and install packages to allow `apt` to use a repository over HTTPS: @@ -107,7 +107,7 @@ Docker from the repository. ```console $ sudo install -m 0755 -d /etc/apt/keyrings - $ curl -fsSL {{ download-url-base }}/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg + $ curl -fsSL {{% param "download-url-base" %}}/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg $ sudo chmod a+r /etc/apt/keyrings/docker.gpg ``` @@ -115,7 +115,7 @@ Docker from the repository. ```console $ echo \ - "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] {{ download-url-base }} \ + "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] {{% param "download-url-base" %}} \ "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null ``` @@ -177,7 +177,7 @@ Docker from the repository. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -191,8 +191,7 @@ If you can't use Docker's `apt` repository to install Docker Engine, you can download the `deb` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [`{{ download-url-base }}/dists/`]({{ download-url-base }}/dists/){: - target="_blank" rel="noopener" class="_" }. +1. Go to [`{{% param "download-url-base" %}}/dists/`]({{% param "download-url-base" %}}/dists/). 2. Select your Raspberry Pi OS version in the list. @@ -234,14 +233,14 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), pointing to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -265,4 +264,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/rhel.md b/content/engine/install/rhel.md index 77f30f09d0..0f78bc07dc 100644 --- a/content/engine/install/rhel.md +++ b/content/engine/install/rhel.md @@ -1,7 +1,10 @@ --- description: Instructions for installing Docker Engine on RHEL -keywords: requirements, apt, installation, rhel, rpm, install, uninstall, upgrade, update, s390x, ibm-z -redirect_from: +keywords: requirements, apt, installation, rhel, rpm, install, uninstall, upgrade, + update, s390x, ibm-z +title: Install Docker Engine on RHEL +toc_max: 4 +aliases: - /ee/docker-ee/rhel/ - /engine/installation/linux/docker-ce/rhel/ - /engine/installation/linux/docker-ee/rhel/ @@ -10,8 +13,7 @@ redirect_from: - /engine/installation/rhel/ - /install/linux/docker-ee/rhel/ - /installation/rhel/ -title: Install Docker Engine on RHEL -toc_max: 4 +download-url-base: https://download.docker.com/linux/rhel --- To get started with Docker Engine on RHEL, make sure you @@ -85,14 +87,13 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/rhel" %} Install the `yum-utils` package (which provides the `yum-config-manager` utility) and set up the repository. ```console $ sudo yum install -y yum-utils -$ sudo yum-config-manager --add-repo {{ download-url-base }}/docker-ce.repo +$ sudo yum-config-manager --add-repo {{% param "download-url-base" %}}/docker-ce.repo ``` #### Install Docker Engine @@ -166,7 +167,7 @@ $ sudo yum-config-manager --add-repo {{ download-url-base }}/docker-ce.repo You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -179,7 +180,7 @@ If you can't use Docker's `rpm` repository to install Docker Engine, you can download the `.rpm` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [{{ download-url-base }}/]({{ download-url-base }}/){: target="_blank" rel="noopener" class="_" } +1. Go to [{{% param "download-url-base" %}}/]({{% param "download-url-base" %}}/) and choose your version of RHEL. Then browse to `s390x/stable/Packages/` and download the `.rpm` file for the Docker version you want to install. @@ -211,7 +212,7 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -219,7 +220,7 @@ To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), using `yum -y upgrade` instead of `yum -y install`, and point to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -243,4 +244,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/sles.md b/content/engine/install/sles.md index 660a0c4328..e70e813c1f 100644 --- a/content/engine/install/sles.md +++ b/content/engine/install/sles.md @@ -1,7 +1,10 @@ --- description: Instructions for installing Docker Engine on SLES -keywords: requirements, apt, installation, centos, rpm, sles, install, uninstall, upgrade, update, s390x, ibm-z -redirect_from: +keywords: requirements, apt, installation, centos, rpm, sles, install, uninstall, + upgrade, update, s390x, ibm-z +title: Install Docker Engine on SLES +toc_max: 4 +aliases: - /ee/docker-ee/sles/ - /ee/docker-ee/suse/ - /engine/installation/linux/docker-ce/sles/ @@ -17,8 +20,7 @@ redirect_from: - /install/linux/docker-ee/suse/ - /install/linux/sles/ - /installation/sles/ -title: Install Docker Engine on SLES -toc_max: 4 +download-url-base: https://download.docker.com/linux/sles --- To get started with Docker Engine on SLES, make sure you @@ -109,12 +111,11 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/sles" %} Set up the repository. ```console -$ sudo zypper addrepo {{ download-url-base }}/docker-ce.repo +$ sudo zypper addrepo {{% param "download-url-base" %}}/docker-ce.repo ``` #### Install Docker Engine @@ -187,7 +188,7 @@ $ sudo zypper addrepo {{ download-url-base }}/docker-ce.repo You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -200,7 +201,7 @@ If you can't use Docker's `rpm` repository to install Docker Engine, you can download the `.rpm` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [{{ download-url-base }}/]({{ download-url-base }}/){: target="_blank" rel="noopener" class="_" } +1. Go to [{{% param "download-url-base" %}}/]({{% param "download-url-base" %}}/) and choose your version of SLES. Then browse to `s390x/stable/Packages/` and download the `.rpm` file for the Docker version you want to install. @@ -232,7 +233,7 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -240,7 +241,7 @@ To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), using `zypper -y upgrade` instead of `zypper -y install`, and point to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -264,4 +265,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/install/troubleshoot.md b/content/engine/install/troubleshoot.md index 502ed25b7a..9e7b5064c1 100644 --- a/content/engine/install/troubleshoot.md +++ b/content/engine/install/troubleshoot.md @@ -1,7 +1,6 @@ --- title: Troubleshoot Docker Engine installation -description: - Diagnose and resolve error messages related to the Docker Engine installation +description: Diagnose and resolve error messages related to the Docker Engine installation keywords: Docker Engine, troubleshooting, error, Linux --- @@ -219,8 +218,7 @@ To turn off `dnsmasq` on RHEL, CentOS, or Fedora: ``` 2. Configure the DNS servers manually using the - [Red Hat documentation](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html){: - target="_blank" rel="noopener" class="_"}. + [Red Hat documentation](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html). ## Allow access to the remote API through a firewall @@ -290,4 +288,4 @@ Docker isn't running. An error occurs if your GRUB configuration file has incorrect syntax. In this case, repeat steps 2 and 3. - The changes take effect when you reboot the system. + The changes take effect when you reboot the system. \ No newline at end of file diff --git a/content/engine/install/ubuntu.md b/content/engine/install/ubuntu.md index 90d221f7ae..7a8a643132 100644 --- a/content/engine/install/ubuntu.md +++ b/content/engine/install/ubuntu.md @@ -1,19 +1,23 @@ --- -description: Jumpstart your client-side server applications with Docker Engine on Ubuntu. This guide details prerequisites and multiple methods to install. -keywords: docker install script, ubuntu docker server, ubuntu server docker, install docker engine ubuntu, install docker on ubuntu server, ubuntu 22.04 docker-ce, install docker engine on ubuntu, ubuntu install docker ce, ubuntu install docker engine -redirect_from: - - /ee/docker-ee/ubuntu/ - - /engine/installation/linux/docker-ce/ubuntu/ - - /engine/installation/linux/docker-ee/ubuntu/ - - /engine/installation/linux/ubuntu/ - - /engine/installation/linux/ubuntulinux/ - - /engine/installation/ubuntulinux/ - - /install/linux/docker-ce/ubuntu/ - - /install/linux/docker-ee/ubuntu/ - - /install/linux/ubuntu/ - - /installation/ubuntulinux/ +description: Jumpstart your client-side server applications with Docker Engine on + Ubuntu. This guide details prerequisites and multiple methods to install. +keywords: docker install script, ubuntu docker server, ubuntu server docker, install + docker engine ubuntu, install docker on ubuntu server, ubuntu 22.04 docker-ce, install + docker engine on ubuntu, ubuntu install docker ce, ubuntu install docker engine title: Install Docker Engine on Ubuntu toc_max: 4 +aliases: +- /ee/docker-ee/ubuntu/ +- /engine/installation/linux/docker-ce/ubuntu/ +- /engine/installation/linux/docker-ee/ubuntu/ +- /engine/installation/linux/ubuntu/ +- /engine/installation/linux/ubuntulinux/ +- /engine/installation/ubuntulinux/ +- /install/linux/docker-ce/ubuntu/ +- /install/linux/docker-ee/ubuntu/ +- /install/linux/ubuntu/ +- /installation/ubuntulinux/ +download-url-base: https://download.docker.com/linux/ubuntu --- To get started with Docker Engine on Ubuntu, make sure you @@ -100,7 +104,6 @@ Docker from the repository. #### Set up the repository -{% assign download-url-base = "https://download.docker.com/linux/ubuntu" %} 1. Update the `apt` package index and install packages to allow `apt` to use a repository over HTTPS: @@ -114,7 +117,7 @@ Docker from the repository. ```console $ sudo install -m 0755 -d /etc/apt/keyrings - $ curl -fsSL {{ download-url-base }}/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg + $ curl -fsSL {{% param "download-url-base" %}}/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg $ sudo chmod a+r /etc/apt/keyrings/docker.gpg ``` @@ -122,7 +125,7 @@ Docker from the repository. ```console $ echo \ - "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] {{ download-url-base }} \ + "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] {{% param "download-url-base" %}} \ "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \ sudo tee /etc/apt/sources.list.d/docker.list > /dev/null ``` @@ -188,7 +191,7 @@ Docker from the repository. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine @@ -201,7 +204,7 @@ If you can't use Docker's `apt` repository to install Docker Engine, you can download the `deb` file for your release and install it manually. You need to download a new file each time you want to upgrade Docker Engine. -1. Go to [`{{ download-url-base }}/dists/`]({{ download-url-base }}/dists/){: target="_blank" rel="noopener" class="_" }. +1. Go to [`{{% param "download-url-base" %}}/dists/`]({{% param "download-url-base" %}}/dists/). 2. Select your Ubuntu version in the list. @@ -243,14 +246,14 @@ download a new file each time you want to upgrade Docker Engine. You have now successfully installed and started Docker Engine. -{% include root-errors.md %} +{{< include "root-errors.md" >}} #### Upgrade Docker Engine To upgrade Docker Engine, download the newer package files and repeat the [installation procedure](#install-from-a-package), pointing to the new files. -{% include install-script.md %} +{{< include "install-script.md" >}} ## Uninstall Docker Engine @@ -274,4 +277,4 @@ You have to delete any edited configuration files manually. - Continue to [Post-installation steps for Linux](linux-postinstall.md). - Review the topics in [Develop with Docker](../../develop/index.md) to learn - how to build new applications using Docker. + how to build new applications using Docker. \ No newline at end of file diff --git a/content/engine/migration.md b/content/engine/migration.md index ef37a2472b..c94aead216 100644 --- a/content/engine/migration.md +++ b/content/engine/migration.md @@ -74,4 +74,4 @@ the default path then you would run: If you use the devicemapper storage driver, you also need to pass the flag `--privileged` to -give the tool access to your storage devices. +give the tool access to your storage devices. \ No newline at end of file diff --git a/content/engine/reference/commandline/README.md b/content/engine/reference/commandline/README.md index e20e394308..8c72c20fca 100644 --- a/content/engine/reference/commandline/README.md +++ b/content/engine/reference/commandline/README.md @@ -1,3 +1,7 @@ +--- +{} +--- + # About these files The files in this directory are stub files which include the file @@ -26,4 +30,4 @@ release branch of `docker/cli`, for example, the `19.03` branch. After generating the YAML files, replace the YAML files in [https://github.com/docker/docs/tree/main/_data/engine-cli](https://github.com/docker/docs/tree/main/_data/engine-cli) -with the newly-generated files. Submit a pull request. +with the newly-generated files. Submit a pull request. \ No newline at end of file diff --git a/content/engine/reference/commandline/attach.md b/content/engine/reference/commandline/attach.md index 0104e83f39..e41a6a6b0e 100644 --- a/content/engine/reference/commandline/attach.md +++ b/content/engine/reference/commandline/attach.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_attach title: docker attach -redirect_from: - - /edge/engine/reference/commandline/attach/ +aliases: +- /edge/engine/reference/commandline/attach/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/build.md b/content/engine/reference/commandline/build.md index 77539819a2..ae89d8d42a 100644 --- a/content/engine/reference/commandline/build.md +++ b/content/engine/reference/commandline/build.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_build title: docker build -redirect_from: - - /edge/engine/reference/commandline/build/ +aliases: +- /edge/engine/reference/commandline/build/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/builder.md b/content/engine/reference/commandline/builder.md index 4f904c8e08..761a0d61dd 100644 --- a/content/engine/reference/commandline/builder.md +++ b/content/engine/reference/commandline/builder.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_builder title: docker builder +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/builder_build.md b/content/engine/reference/commandline/builder_build.md index 2a6d5b96fa..38bcb03793 100644 --- a/content/engine/reference/commandline/builder_build.md +++ b/content/engine/reference/commandline/builder_build.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_builder_build title: docker builder build +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/builder_prune.md b/content/engine/reference/commandline/builder_prune.md index 7a3149c618..3ccbd7d0d7 100644 --- a/content/engine/reference/commandline/builder_prune.md +++ b/content/engine/reference/commandline/builder_prune.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_builder_prune title: docker builder prune +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx.md b/content/engine/reference/commandline/buildx.md index 451bfdd703..3e0e2154d1 100644 --- a/content/engine/reference/commandline/buildx.md +++ b/content/engine/reference/commandline/buildx.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx title: docker buildx +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_bake.md b/content/engine/reference/commandline/buildx_bake.md index 844399a725..a9045eff2e 100644 --- a/content/engine/reference/commandline/buildx_bake.md +++ b/content/engine/reference/commandline/buildx_bake.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_bake title: docker buildx bake +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_build.md b/content/engine/reference/commandline/buildx_build.md index 20c1d934c3..bbcc9d8de8 100644 --- a/content/engine/reference/commandline/buildx_build.md +++ b/content/engine/reference/commandline/buildx_build.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_build title: docker buildx build +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_create.md b/content/engine/reference/commandline/buildx_create.md index d70c469a5e..70fdc5d5d8 100644 --- a/content/engine/reference/commandline/buildx_create.md +++ b/content/engine/reference/commandline/buildx_create.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_create title: docker buildx create +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_debug-shell.md b/content/engine/reference/commandline/buildx_debug-shell.md index 052a6bc09e..d66d067009 100644 --- a/content/engine/reference/commandline/buildx_debug-shell.md +++ b/content/engine/reference/commandline/buildx_debug-shell.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_debug-shell title: docker buildx debug-shell +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_du.md b/content/engine/reference/commandline/buildx_du.md index ff8c19f462..6e817a76e4 100644 --- a/content/engine/reference/commandline/buildx_du.md +++ b/content/engine/reference/commandline/buildx_du.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_du title: docker buildx du +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_imagetools.md b/content/engine/reference/commandline/buildx_imagetools.md index 8288a2a8e7..e0aa1aa9e6 100644 --- a/content/engine/reference/commandline/buildx_imagetools.md +++ b/content/engine/reference/commandline/buildx_imagetools.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_imagetools title: docker buildx imagetools +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_imagetools_create.md b/content/engine/reference/commandline/buildx_imagetools_create.md index 713d4865be..e0078fdcf1 100644 --- a/content/engine/reference/commandline/buildx_imagetools_create.md +++ b/content/engine/reference/commandline/buildx_imagetools_create.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_imagetools_create title: docker buildx imagetools create +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_imagetools_inspect.md b/content/engine/reference/commandline/buildx_imagetools_inspect.md index d384c48055..e089d58f71 100644 --- a/content/engine/reference/commandline/buildx_imagetools_inspect.md +++ b/content/engine/reference/commandline/buildx_imagetools_inspect.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_imagetools_inspect title: docker buildx imagetools inspect +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_inspect.md b/content/engine/reference/commandline/buildx_inspect.md index 79c8e215d7..81ee90cfa7 100644 --- a/content/engine/reference/commandline/buildx_inspect.md +++ b/content/engine/reference/commandline/buildx_inspect.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_inspect title: docker buildx inspect +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_ls.md b/content/engine/reference/commandline/buildx_ls.md index 9517aa313b..67611c6bf5 100644 --- a/content/engine/reference/commandline/buildx_ls.md +++ b/content/engine/reference/commandline/buildx_ls.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_ls title: docker buildx ls +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_prune.md b/content/engine/reference/commandline/buildx_prune.md index 782b92eb81..4b51f35a98 100644 --- a/content/engine/reference/commandline/buildx_prune.md +++ b/content/engine/reference/commandline/buildx_prune.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_prune title: docker buildx prune +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_rm.md b/content/engine/reference/commandline/buildx_rm.md index bbc37ec1a4..d410692116 100644 --- a/content/engine/reference/commandline/buildx_rm.md +++ b/content/engine/reference/commandline/buildx_rm.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_rm title: docker buildx rm +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_stop.md b/content/engine/reference/commandline/buildx_stop.md index d11f87f187..74c8711d14 100644 --- a/content/engine/reference/commandline/buildx_stop.md +++ b/content/engine/reference/commandline/buildx_stop.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_stop title: docker buildx stop +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_use.md b/content/engine/reference/commandline/buildx_use.md index dc233d614f..ce293dadee 100644 --- a/content/engine/reference/commandline/buildx_use.md +++ b/content/engine/reference/commandline/buildx_use.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_use title: docker buildx use +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/buildx_version.md b/content/engine/reference/commandline/buildx_version.md index 8e757c1e0b..2b28956aed 100644 --- a/content/engine/reference/commandline/buildx_version.md +++ b/content/engine/reference/commandline/buildx_version.md @@ -2,12 +2,13 @@ datafolder: buildx datafile: docker_buildx_version title: docker buildx version +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/checkpoint.md b/content/engine/reference/commandline/checkpoint.md index 836aa2ecd7..bbda5c336f 100644 --- a/content/engine/reference/commandline/checkpoint.md +++ b/content/engine/reference/commandline/checkpoint.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_checkpoint title: docker checkpoint -redirect_from: - - /edge/engine/reference/commandline/checkpoint/ +aliases: +- /edge/engine/reference/commandline/checkpoint/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/checkpoint_create.md b/content/engine/reference/commandline/checkpoint_create.md index b10c512d86..bc309c9a44 100644 --- a/content/engine/reference/commandline/checkpoint_create.md +++ b/content/engine/reference/commandline/checkpoint_create.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_checkpoint_create title: docker checkpoint create -redirect_from: - - /edge/engine/reference/commandline/checkpoint_create/ +aliases: +- /edge/engine/reference/commandline/checkpoint_create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/checkpoint_ls.md b/content/engine/reference/commandline/checkpoint_ls.md index fd68dc0ea5..37f1eef78b 100644 --- a/content/engine/reference/commandline/checkpoint_ls.md +++ b/content/engine/reference/commandline/checkpoint_ls.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_checkpoint_ls title: docker checkpoint ls -redirect_from: - - /edge/engine/reference/commandline/checkpoint_ls/ +aliases: +- /edge/engine/reference/commandline/checkpoint_ls/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/checkpoint_rm.md b/content/engine/reference/commandline/checkpoint_rm.md index 8461e7116a..7b195c4283 100644 --- a/content/engine/reference/commandline/checkpoint_rm.md +++ b/content/engine/reference/commandline/checkpoint_rm.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_checkpoint_rm title: docker checkpoint rm -redirect_from: - - /edge/engine/reference/commandline/checkpoint_rm/ +aliases: +- /edge/engine/reference/commandline/checkpoint_rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/commit.md b/content/engine/reference/commandline/commit.md index eec7898a56..c72d265e63 100644 --- a/content/engine/reference/commandline/commit.md +++ b/content/engine/reference/commandline/commit.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_commit title: docker commit -redirect_from: - - /edge/engine/reference/commandline/commit/ +aliases: +- /edge/engine/reference/commandline/commit/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose.md b/content/engine/reference/commandline/compose.md index a58ae290d7..e6a4abc30a 100644 --- a/content/engine/reference/commandline/compose.md +++ b/content/engine/reference/commandline/compose.md @@ -2,14 +2,15 @@ datafolder: compose-cli datafile: docker_compose title: docker compose -redirect_from: +aliases: - /compose/reference/docker-compose/ - /compose/reference/help/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_build.md b/content/engine/reference/commandline/compose_build.md index ac51ca74b5..398c41bbea 100644 --- a/content/engine/reference/commandline/compose_build.md +++ b/content/engine/reference/commandline/compose_build.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_build title: docker compose build -redirect_from: +aliases: - /compose/reference/build/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_config.md b/content/engine/reference/commandline/compose_config.md index 8a7b4c8602..1dbc2c31d6 100644 --- a/content/engine/reference/commandline/compose_config.md +++ b/content/engine/reference/commandline/compose_config.md @@ -2,14 +2,15 @@ datafolder: compose-cli datafile: docker_compose_config title: docker compose config -redirect_from: - - /compose/reference/config/ - - /engine/reference/commandline/compose_convert/ +aliases: +- /compose/reference/config/ +- /engine/reference/commandline/compose_convert/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_cp.md b/content/engine/reference/commandline/compose_cp.md index d200eca15a..9f1325fd55 100644 --- a/content/engine/reference/commandline/compose_cp.md +++ b/content/engine/reference/commandline/compose_cp.md @@ -2,11 +2,12 @@ datafolder: compose-cli datafile: docker_compose_cp title: docker compose cp +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_create.md b/content/engine/reference/commandline/compose_create.md index 847b18e428..dcf1b1e3ea 100644 --- a/content/engine/reference/commandline/compose_create.md +++ b/content/engine/reference/commandline/compose_create.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_create title: docker compose create -redirect_from: +aliases: - /compose/reference/create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_down.md b/content/engine/reference/commandline/compose_down.md index e5dff73c98..6b7cb993cb 100644 --- a/content/engine/reference/commandline/compose_down.md +++ b/content/engine/reference/commandline/compose_down.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_down title: docker compose down -redirect_from: +aliases: - /compose/reference/down/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_events.md b/content/engine/reference/commandline/compose_events.md index 72e7f0816b..797f41db42 100644 --- a/content/engine/reference/commandline/compose_events.md +++ b/content/engine/reference/commandline/compose_events.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_events title: docker compose events -redirect_from: +aliases: - /compose/reference/events/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_exec.md b/content/engine/reference/commandline/compose_exec.md index 1423c2aa9c..5cd9c3ded2 100644 --- a/content/engine/reference/commandline/compose_exec.md +++ b/content/engine/reference/commandline/compose_exec.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_exec title: docker compose exec -redirect_from: +aliases: - /compose/reference/exec/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_images.md b/content/engine/reference/commandline/compose_images.md index 2be1369a8b..76bb3ff918 100644 --- a/content/engine/reference/commandline/compose_images.md +++ b/content/engine/reference/commandline/compose_images.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_images title: docker compose images -redirect_from: +aliases: - /compose/reference/images/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_kill.md b/content/engine/reference/commandline/compose_kill.md index be83c3d213..37530b706c 100644 --- a/content/engine/reference/commandline/compose_kill.md +++ b/content/engine/reference/commandline/compose_kill.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_kill title: docker compose kill -redirect_from: +aliases: - /compose/reference/kill/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_logs.md b/content/engine/reference/commandline/compose_logs.md index a631106e87..aa212a96a4 100644 --- a/content/engine/reference/commandline/compose_logs.md +++ b/content/engine/reference/commandline/compose_logs.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_logs title: docker compose logs -redirect_from: +aliases: - /compose/reference/logs/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_ls.md b/content/engine/reference/commandline/compose_ls.md index 5487055257..4b307a7d7c 100644 --- a/content/engine/reference/commandline/compose_ls.md +++ b/content/engine/reference/commandline/compose_ls.md @@ -2,11 +2,12 @@ datafolder: compose-cli datafile: docker_compose_ls title: docker compose ls +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_pause.md b/content/engine/reference/commandline/compose_pause.md index e4ee178f72..93fc195aa7 100644 --- a/content/engine/reference/commandline/compose_pause.md +++ b/content/engine/reference/commandline/compose_pause.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_pause title: docker compose pause -redirect_from: +aliases: - /compose/reference/pause/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_port.md b/content/engine/reference/commandline/compose_port.md index 9ae7e177a1..1ed033da5d 100644 --- a/content/engine/reference/commandline/compose_port.md +++ b/content/engine/reference/commandline/compose_port.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_port title: docker compose port -redirect_from: +aliases: - /compose/reference/port/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_ps.md b/content/engine/reference/commandline/compose_ps.md index 2b2c2e0802..e57fd57c3f 100644 --- a/content/engine/reference/commandline/compose_ps.md +++ b/content/engine/reference/commandline/compose_ps.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_ps title: docker compose ps -redirect_from: +aliases: - /compose/reference/ps/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_pull.md b/content/engine/reference/commandline/compose_pull.md index ab4c752d30..13949f3029 100644 --- a/content/engine/reference/commandline/compose_pull.md +++ b/content/engine/reference/commandline/compose_pull.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_pull title: docker compose pull -redirect_from: +aliases: - /compose/reference/pull/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_push.md b/content/engine/reference/commandline/compose_push.md index b14061d162..db48a33b73 100644 --- a/content/engine/reference/commandline/compose_push.md +++ b/content/engine/reference/commandline/compose_push.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_push title: docker compose push -redirect_from: +aliases: - /compose/reference/push/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_restart.md b/content/engine/reference/commandline/compose_restart.md index 38f276fdff..54ac5523d3 100644 --- a/content/engine/reference/commandline/compose_restart.md +++ b/content/engine/reference/commandline/compose_restart.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_restart title: docker compose restart -redirect_from: +aliases: - /compose/reference/restart/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_rm.md b/content/engine/reference/commandline/compose_rm.md index 02c195d5e5..db3a7513ae 100644 --- a/content/engine/reference/commandline/compose_rm.md +++ b/content/engine/reference/commandline/compose_rm.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_rm title: docker compose rm -redirect_from: +aliases: - /compose/reference/rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_run.md b/content/engine/reference/commandline/compose_run.md index cc9399ae78..85eba39334 100644 --- a/content/engine/reference/commandline/compose_run.md +++ b/content/engine/reference/commandline/compose_run.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_run title: docker compose run -redirect_from: +aliases: - /compose/reference/run/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_start.md b/content/engine/reference/commandline/compose_start.md index cc0fde86c4..9bba56f3f2 100644 --- a/content/engine/reference/commandline/compose_start.md +++ b/content/engine/reference/commandline/compose_start.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_start title: docker compose start -redirect_from: +aliases: - /compose/reference/start/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_stop.md b/content/engine/reference/commandline/compose_stop.md index 8e917d6840..70841cc6a5 100644 --- a/content/engine/reference/commandline/compose_stop.md +++ b/content/engine/reference/commandline/compose_stop.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_stop title: docker compose stop -redirect_from: +aliases: - /compose/reference/stop/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_top.md b/content/engine/reference/commandline/compose_top.md index 0a58e3e5d2..04b369a736 100644 --- a/content/engine/reference/commandline/compose_top.md +++ b/content/engine/reference/commandline/compose_top.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_top title: docker compose top -redirect_from: +aliases: - /compose/reference/top/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_unpause.md b/content/engine/reference/commandline/compose_unpause.md index 05e4e22e52..0a019cb301 100644 --- a/content/engine/reference/commandline/compose_unpause.md +++ b/content/engine/reference/commandline/compose_unpause.md @@ -2,13 +2,14 @@ datafolder: compose-cli datafile: docker_compose_unpause title: docker compose unpause -redirect_from: +aliases: - /compose/reference/unpause/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_up.md b/content/engine/reference/commandline/compose_up.md index 531eb8eaa6..b3b27a8a43 100644 --- a/content/engine/reference/commandline/compose_up.md +++ b/content/engine/reference/commandline/compose_up.md @@ -2,14 +2,15 @@ datafolder: compose-cli datafile: docker_compose_up title: docker compose up -redirect_from: +aliases: - /compose/reference/up/ - /compose/reference/scale/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/compose_version.md b/content/engine/reference/commandline/compose_version.md index 76a0cf75f3..52d60356d2 100644 --- a/content/engine/reference/commandline/compose_version.md +++ b/content/engine/reference/commandline/compose_version.md @@ -2,11 +2,12 @@ datafolder: compose-cli datafile: docker_compose_version title: docker compose version +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/config.md b/content/engine/reference/commandline/config.md index 567c6ab7d3..a89056f298 100644 --- a/content/engine/reference/commandline/config.md +++ b/content/engine/reference/commandline/config.md @@ -2,9 +2,11 @@ datafolder: engine-cli datafile: docker_config title: docker config -redirect_from: - - /edge/engine/reference/commandline/config/ +aliases: +- /edge/engine/reference/commandline/config/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} + ## More info -[Store configuration data using Docker Configs](../../swarm/configs.md) +[Store configuration data using Docker Configs](../../swarm/configs.md) \ No newline at end of file diff --git a/content/engine/reference/commandline/config_create.md b/content/engine/reference/commandline/config_create.md index 0581e73985..c4c56688ed 100644 --- a/content/engine/reference/commandline/config_create.md +++ b/content/engine/reference/commandline/config_create.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_config_create title: docker config create -redirect_from: - - /edge/engine/reference/commandline/config_create/ +aliases: +- /edge/engine/reference/commandline/config_create/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/config_inspect.md b/content/engine/reference/commandline/config_inspect.md index 04a9c6e079..1b219893c1 100644 --- a/content/engine/reference/commandline/config_inspect.md +++ b/content/engine/reference/commandline/config_inspect.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_config_inspect title: docker config inspect -redirect_from: - - /edge/engine/reference/commandline/config_inspect/ +aliases: +- /edge/engine/reference/commandline/config_inspect/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/config_ls.md b/content/engine/reference/commandline/config_ls.md index 1a2ef37b18..0406daa53e 100644 --- a/content/engine/reference/commandline/config_ls.md +++ b/content/engine/reference/commandline/config_ls.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_config_ls title: docker config ls -redirect_from: - - /edge/engine/reference/commandline/config_ls/ +aliases: +- /edge/engine/reference/commandline/config_ls/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/config_rm.md b/content/engine/reference/commandline/config_rm.md index 6ce1f38b48..55397c6394 100644 --- a/content/engine/reference/commandline/config_rm.md +++ b/content/engine/reference/commandline/config_rm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_config_rm title: docker config rm -redirect_from: - - /edge/engine/reference/commandline/config_rm/ +aliases: +- /edge/engine/reference/commandline/config_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container.md b/content/engine/reference/commandline/container.md index 65123874f4..66ea447ed5 100644 --- a/content/engine/reference/commandline/container.md +++ b/content/engine/reference/commandline/container.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container title: docker container -redirect_from: - - /edge/engine/reference/commandline/container/ +aliases: +- /edge/engine/reference/commandline/container/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_attach.md b/content/engine/reference/commandline/container_attach.md index 723c3616d5..e28e847b23 100644 --- a/content/engine/reference/commandline/container_attach.md +++ b/content/engine/reference/commandline/container_attach.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_attach title: docker container attach -redirect_from: - - /edge/engine/reference/commandline/container_attach/ +aliases: +- /edge/engine/reference/commandline/container_attach/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_commit.md b/content/engine/reference/commandline/container_commit.md index ca1259b7c8..0029f6fbb1 100644 --- a/content/engine/reference/commandline/container_commit.md +++ b/content/engine/reference/commandline/container_commit.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_commit title: docker container commit -redirect_from: - - /edge/engine/reference/commandline/container_commit/ +aliases: +- /edge/engine/reference/commandline/container_commit/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_cp.md b/content/engine/reference/commandline/container_cp.md index 4fc18ede63..92adc074ac 100644 --- a/content/engine/reference/commandline/container_cp.md +++ b/content/engine/reference/commandline/container_cp.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_cp title: docker container cp -redirect_from: - - /edge/engine/reference/commandline/container_cp/ +aliases: +- /edge/engine/reference/commandline/container_cp/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_create.md b/content/engine/reference/commandline/container_create.md index 6c246cf055..be14d03a53 100644 --- a/content/engine/reference/commandline/container_create.md +++ b/content/engine/reference/commandline/container_create.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_create title: docker container create -redirect_from: - - /edge/engine/reference/commandline/container_create/ +aliases: +- /edge/engine/reference/commandline/container_create/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_diff.md b/content/engine/reference/commandline/container_diff.md index 97c97555cd..9de56b1164 100644 --- a/content/engine/reference/commandline/container_diff.md +++ b/content/engine/reference/commandline/container_diff.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_diff title: docker container diff -redirect_from: - - /edge/engine/reference/commandline/container_diff/ +aliases: +- /edge/engine/reference/commandline/container_diff/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_exec.md b/content/engine/reference/commandline/container_exec.md index 30b2c006fa..17c79f2e93 100644 --- a/content/engine/reference/commandline/container_exec.md +++ b/content/engine/reference/commandline/container_exec.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_exec title: docker container exec -redirect_from: - - /edge/engine/reference/commandline/container_exec/ +aliases: +- /edge/engine/reference/commandline/container_exec/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_export.md b/content/engine/reference/commandline/container_export.md index 244b4fc49f..f375ab873f 100644 --- a/content/engine/reference/commandline/container_export.md +++ b/content/engine/reference/commandline/container_export.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_export title: docker container export -redirect_from: - - /edge/engine/reference/commandline/container_export/ +aliases: +- /edge/engine/reference/commandline/container_export/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_inspect.md b/content/engine/reference/commandline/container_inspect.md index 9b12db38a3..161f6d8c8f 100644 --- a/content/engine/reference/commandline/container_inspect.md +++ b/content/engine/reference/commandline/container_inspect.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_inspect title: docker container inspect -redirect_from: - - /edge/engine/reference/commandline/container_inspect/ +aliases: +- /edge/engine/reference/commandline/container_inspect/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_kill.md b/content/engine/reference/commandline/container_kill.md index 2b48e5c8b8..3087bdb895 100644 --- a/content/engine/reference/commandline/container_kill.md +++ b/content/engine/reference/commandline/container_kill.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_kill title: docker container kill -redirect_from: - - /edge/engine/reference/commandline/container_kill/ +aliases: +- /edge/engine/reference/commandline/container_kill/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_logs.md b/content/engine/reference/commandline/container_logs.md index 23acbcd1a7..d1e7828357 100644 --- a/content/engine/reference/commandline/container_logs.md +++ b/content/engine/reference/commandline/container_logs.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_logs title: docker container logs -redirect_from: - - /edge/engine/reference/commandline/container_logs/ +aliases: +- /edge/engine/reference/commandline/container_logs/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_ls.md b/content/engine/reference/commandline/container_ls.md index 5cc995f2b3..b95d003b48 100644 --- a/content/engine/reference/commandline/container_ls.md +++ b/content/engine/reference/commandline/container_ls.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_ls title: docker container ls -redirect_from: - - /edge/engine/reference/commandline/container_ls/ +aliases: +- /edge/engine/reference/commandline/container_ls/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_pause.md b/content/engine/reference/commandline/container_pause.md index df2c5a2615..7bda777ddc 100644 --- a/content/engine/reference/commandline/container_pause.md +++ b/content/engine/reference/commandline/container_pause.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_pause title: docker container pause -redirect_from: - - /edge/engine/reference/commandline/container_pause/ +aliases: +- /edge/engine/reference/commandline/container_pause/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_port.md b/content/engine/reference/commandline/container_port.md index 0d27d164d3..a5f163858a 100644 --- a/content/engine/reference/commandline/container_port.md +++ b/content/engine/reference/commandline/container_port.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_port title: docker container port -redirect_from: - - /edge/engine/reference/commandline/container_port/ +aliases: +- /edge/engine/reference/commandline/container_port/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_prune.md b/content/engine/reference/commandline/container_prune.md index 764793dc5c..9d7b46bcea 100644 --- a/content/engine/reference/commandline/container_prune.md +++ b/content/engine/reference/commandline/container_prune.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_prune title: docker container prune -redirect_from: - - /edge/engine/reference/commandline/container_prune/ +aliases: +- /edge/engine/reference/commandline/container_prune/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_rename.md b/content/engine/reference/commandline/container_rename.md index 43722ed94c..595c5fdf91 100644 --- a/content/engine/reference/commandline/container_rename.md +++ b/content/engine/reference/commandline/container_rename.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_rename title: docker container rename -redirect_from: - - /edge/engine/reference/commandline/container_rename/ +aliases: +- /edge/engine/reference/commandline/container_rename/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_restart.md b/content/engine/reference/commandline/container_restart.md index a0fd69f7b5..af3d44c6a9 100644 --- a/content/engine/reference/commandline/container_restart.md +++ b/content/engine/reference/commandline/container_restart.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_restart title: docker container restart -redirect_from: - - /edge/engine/reference/commandline/container_restart/ +aliases: +- /edge/engine/reference/commandline/container_restart/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_rm.md b/content/engine/reference/commandline/container_rm.md index 812fe0e472..fad62d8922 100644 --- a/content/engine/reference/commandline/container_rm.md +++ b/content/engine/reference/commandline/container_rm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_rm title: docker container rm -redirect_from: - - /edge/engine/reference/commandline/container_rm/ +aliases: +- /edge/engine/reference/commandline/container_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_run.md b/content/engine/reference/commandline/container_run.md index c2aa9bda10..7ee1d5bf0d 100644 --- a/content/engine/reference/commandline/container_run.md +++ b/content/engine/reference/commandline/container_run.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_run title: docker container run -redirect_from: - - /edge/engine/reference/commandline/container_rm/ +aliases: +- /edge/engine/reference/commandline/container_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_start.md b/content/engine/reference/commandline/container_start.md index a497f96a97..42a98a8235 100644 --- a/content/engine/reference/commandline/container_start.md +++ b/content/engine/reference/commandline/container_start.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_start title: docker container start -redirect_from: - - /edge/engine/reference/commandline/container_start/ +aliases: +- /edge/engine/reference/commandline/container_start/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_stats.md b/content/engine/reference/commandline/container_stats.md index 5da904595c..e59197cce9 100644 --- a/content/engine/reference/commandline/container_stats.md +++ b/content/engine/reference/commandline/container_stats.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_stats title: docker container stats -redirect_from: - - /edge/engine/reference/commandline/container_stats/ +aliases: +- /edge/engine/reference/commandline/container_stats/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_stop.md b/content/engine/reference/commandline/container_stop.md index fb17b1bd1e..b14eb64067 100644 --- a/content/engine/reference/commandline/container_stop.md +++ b/content/engine/reference/commandline/container_stop.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_stop title: docker container stop -redirect_from: - - /edge/engine/reference/commandline/container_stop/ +aliases: +- /edge/engine/reference/commandline/container_stop/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_top.md b/content/engine/reference/commandline/container_top.md index 6791dcba97..6fc216518c 100644 --- a/content/engine/reference/commandline/container_top.md +++ b/content/engine/reference/commandline/container_top.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_top title: docker container top -redirect_from: - - /edge/engine/reference/commandline/container_top/ +aliases: +- /edge/engine/reference/commandline/container_top/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_unpause.md b/content/engine/reference/commandline/container_unpause.md index 4bcd5014ac..7b050663b4 100644 --- a/content/engine/reference/commandline/container_unpause.md +++ b/content/engine/reference/commandline/container_unpause.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_unpause title: docker container unpause -redirect_from: - - /edge/engine/reference/commandline/container_unpause/ +aliases: +- /edge/engine/reference/commandline/container_unpause/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_update.md b/content/engine/reference/commandline/container_update.md index 1e518dd840..29f2cc4819 100644 --- a/content/engine/reference/commandline/container_update.md +++ b/content/engine/reference/commandline/container_update.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_update title: docker container update -redirect_from: - - /edge/engine/reference/commandline/container_update/ +aliases: +- /edge/engine/reference/commandline/container_update/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/container_wait.md b/content/engine/reference/commandline/container_wait.md index 2b38e07f5e..760cdfa704 100644 --- a/content/engine/reference/commandline/container_wait.md +++ b/content/engine/reference/commandline/container_wait.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_container_wait title: docker container wait -redirect_from: - - /edge/engine/reference/commandline/container_wait/ +aliases: +- /edge/engine/reference/commandline/container_wait/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context.md b/content/engine/reference/commandline/context.md index 89a688b4ff..e04765434d 100644 --- a/content/engine/reference/commandline/context.md +++ b/content/engine/reference/commandline/context.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context title: docker context +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_create.md b/content/engine/reference/commandline/context_create.md index 64efcdc94d..4708f5b982 100644 --- a/content/engine/reference/commandline/context_create.md +++ b/content/engine/reference/commandline/context_create.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_create title: docker context create +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_export.md b/content/engine/reference/commandline/context_export.md index 49a1c7103b..48d9dada17 100644 --- a/content/engine/reference/commandline/context_export.md +++ b/content/engine/reference/commandline/context_export.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_export title: docker context export +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_import.md b/content/engine/reference/commandline/context_import.md index 2645fe06a4..72f2ba0ce6 100644 --- a/content/engine/reference/commandline/context_import.md +++ b/content/engine/reference/commandline/context_import.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_import title: docker context import +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_inspect.md b/content/engine/reference/commandline/context_inspect.md index 2c095d1473..569166c509 100644 --- a/content/engine/reference/commandline/context_inspect.md +++ b/content/engine/reference/commandline/context_inspect.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_inspect title: docker context inspect +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_ls.md b/content/engine/reference/commandline/context_ls.md index ea04c5ebaf..e5d324fb18 100644 --- a/content/engine/reference/commandline/context_ls.md +++ b/content/engine/reference/commandline/context_ls.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_ls title: docker context ls +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_rm.md b/content/engine/reference/commandline/context_rm.md index 80af95efd7..26f6f3dbff 100644 --- a/content/engine/reference/commandline/context_rm.md +++ b/content/engine/reference/commandline/context_rm.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_rm title: docker context rm +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_show.md b/content/engine/reference/commandline/context_show.md index fb95323519..86811c8407 100644 --- a/content/engine/reference/commandline/context_show.md +++ b/content/engine/reference/commandline/context_show.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_show title: docker context show +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_update.md b/content/engine/reference/commandline/context_update.md index 144cb702bb..a1a8a0c214 100644 --- a/content/engine/reference/commandline/context_update.md +++ b/content/engine/reference/commandline/context_update.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_update title: docker context update +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/context_use.md b/content/engine/reference/commandline/context_use.md index e64e5d70a9..b3e27daaea 100644 --- a/content/engine/reference/commandline/context_use.md +++ b/content/engine/reference/commandline/context_use.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_context_use title: docker context use +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/cp.md b/content/engine/reference/commandline/cp.md index 5886637971..cc24a93390 100644 --- a/content/engine/reference/commandline/cp.md +++ b/content/engine/reference/commandline/cp.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_cp title: docker cp -redirect_from: - - /edge/engine/reference/commandline/cp/ +aliases: +- /edge/engine/reference/commandline/cp/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/create.md b/content/engine/reference/commandline/create.md index 5bd9310fbd..05134539f8 100644 --- a/content/engine/reference/commandline/create.md +++ b/content/engine/reference/commandline/create.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_create title: docker create -redirect_from: - - /edge/engine/reference/commandline/create/ +aliases: +- /edge/engine/reference/commandline/create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/diff.md b/content/engine/reference/commandline/diff.md index 14b97f6880..a3d8caffbf 100644 --- a/content/engine/reference/commandline/diff.md +++ b/content/engine/reference/commandline/diff.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_diff title: docker diff -redirect_from: - - /edge/engine/reference/commandline/diff/ +aliases: +- /edge/engine/reference/commandline/diff/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/docker.md b/content/engine/reference/commandline/docker.md index a649a4b7bc..55862b44f0 100644 --- a/content/engine/reference/commandline/docker.md +++ b/content/engine/reference/commandline/docker.md @@ -2,24 +2,24 @@ datafolder: engine-cli datafile: docker title: docker -redirect_from: - - /edge/engine/reference/commandline/ - - /engine/reference/commandline/ - - /engine/reference/commandline/registry/ - - /engine/reference/commandline/registry_events/ - - /engine/reference/commandline/registry_history/ - - /engine/reference/commandline/registry_info/ - - /engine/reference/commandline/registry_inspect/ - - /engine/reference/commandline/registry_joblogs/ - - /engine/reference/commandline/registry_ls/ - - /engine/reference/commandline/registry_rmi/ +aliases: +- /edge/engine/reference/commandline/ +- /engine/reference/commandline/ +- /engine/reference/commandline/registry/ +- /engine/reference/commandline/registry_events/ +- /engine/reference/commandline/registry_history/ +- /engine/reference/commandline/registry_info/ +- /engine/reference/commandline/registry_inspect/ +- /engine/reference/commandline/registry_joblogs/ +- /engine/reference/commandline/registry_ls/ +- /engine/reference/commandline/registry_rmi/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/events.md b/content/engine/reference/commandline/events.md index f0060d3a19..87cee646b6 100644 --- a/content/engine/reference/commandline/events.md +++ b/content/engine/reference/commandline/events.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_events title: docker events -redirect_from: - - /edge/engine/reference/commandline/events/ +aliases: +- /edge/engine/reference/commandline/events/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/exec.md b/content/engine/reference/commandline/exec.md index ed30dd5dfd..6467d4d677 100644 --- a/content/engine/reference/commandline/exec.md +++ b/content/engine/reference/commandline/exec.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_exec title: docker exec -redirect_from: - - /edge/engine/reference/commandline/exec/ +aliases: +- /edge/engine/reference/commandline/exec/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/export.md b/content/engine/reference/commandline/export.md index 95033c084f..0311afa1f0 100644 --- a/content/engine/reference/commandline/export.md +++ b/content/engine/reference/commandline/export.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_export title: docker export -redirect_from: - - /edge/engine/reference/commandline/export/ +aliases: +- /edge/engine/reference/commandline/export/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/history.md b/content/engine/reference/commandline/history.md index 74aec857ed..ead222e929 100644 --- a/content/engine/reference/commandline/history.md +++ b/content/engine/reference/commandline/history.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_history title: docker history -redirect_from: - - /edge/engine/reference/commandline/history/ +aliases: +- /edge/engine/reference/commandline/history/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image.md b/content/engine/reference/commandline/image.md index f4f872504a..a5259833e9 100644 --- a/content/engine/reference/commandline/image.md +++ b/content/engine/reference/commandline/image.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image title: docker image -redirect_from: - - /edge/engine/reference/commandline/image/ +aliases: +- /edge/engine/reference/commandline/image/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_build.md b/content/engine/reference/commandline/image_build.md index 296e67c03b..b0931baef4 100644 --- a/content/engine/reference/commandline/image_build.md +++ b/content/engine/reference/commandline/image_build.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_build title: docker image build -redirect_from: - - /edge/engine/reference/commandline/image_build/ +aliases: +- /edge/engine/reference/commandline/image_build/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_history.md b/content/engine/reference/commandline/image_history.md index 4da81d9509..8005a3e062 100644 --- a/content/engine/reference/commandline/image_history.md +++ b/content/engine/reference/commandline/image_history.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_history title: docker image history -redirect_from: - - /edge/engine/reference/commandline/image_history/ +aliases: +- /edge/engine/reference/commandline/image_history/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_import.md b/content/engine/reference/commandline/image_import.md index 2b71979763..4675b4dbee 100644 --- a/content/engine/reference/commandline/image_import.md +++ b/content/engine/reference/commandline/image_import.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_import title: docker image import -redirect_from: - - /edge/engine/reference/commandline/image_import/ +aliases: +- /edge/engine/reference/commandline/image_import/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_inspect.md b/content/engine/reference/commandline/image_inspect.md index c8e70ee53c..ac3800dbbd 100644 --- a/content/engine/reference/commandline/image_inspect.md +++ b/content/engine/reference/commandline/image_inspect.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_inspect title: docker image inspect -redirect_from: - - /edge/engine/reference/commandline/image_inspect/ +aliases: +- /edge/engine/reference/commandline/image_inspect/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_load.md b/content/engine/reference/commandline/image_load.md index d575a75c44..116c20a476 100644 --- a/content/engine/reference/commandline/image_load.md +++ b/content/engine/reference/commandline/image_load.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_load title: docker image load -redirect_from: - - /edge/engine/reference/commandline/image_load/ +aliases: +- /edge/engine/reference/commandline/image_load/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_ls.md b/content/engine/reference/commandline/image_ls.md index 231614c069..8a32a287c9 100644 --- a/content/engine/reference/commandline/image_ls.md +++ b/content/engine/reference/commandline/image_ls.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_ls title: docker image ls -redirect_from: - - /edge/engine/reference/commandline/image_ls/ +aliases: +- /edge/engine/reference/commandline/image_ls/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_prune.md b/content/engine/reference/commandline/image_prune.md index ae1eada48b..d714e33417 100644 --- a/content/engine/reference/commandline/image_prune.md +++ b/content/engine/reference/commandline/image_prune.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_prune title: docker image prune -redirect_from: - - /edge/engine/reference/commandline/image_prune/ +aliases: +- /edge/engine/reference/commandline/image_prune/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_pull.md b/content/engine/reference/commandline/image_pull.md index 723a9e16b7..23b0988d2f 100644 --- a/content/engine/reference/commandline/image_pull.md +++ b/content/engine/reference/commandline/image_pull.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_pull title: docker image pull -redirect_from: - - /edge/engine/reference/commandline/image_pull/ +aliases: +- /edge/engine/reference/commandline/image_pull/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_push.md b/content/engine/reference/commandline/image_push.md index 7b9f3dfa89..a7a3045a7a 100644 --- a/content/engine/reference/commandline/image_push.md +++ b/content/engine/reference/commandline/image_push.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_push title: docker image push -redirect_from: - - /edge/engine/reference/commandline/image_push/ +aliases: +- /edge/engine/reference/commandline/image_push/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_rm.md b/content/engine/reference/commandline/image_rm.md index 2cdf8f23d8..3117c9c4bb 100644 --- a/content/engine/reference/commandline/image_rm.md +++ b/content/engine/reference/commandline/image_rm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_rm title: docker image rm -redirect_from: - - /edge/engine/reference/commandline/image_rm/ +aliases: +- /edge/engine/reference/commandline/image_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_save.md b/content/engine/reference/commandline/image_save.md index 1a6caca842..9ea22d161a 100644 --- a/content/engine/reference/commandline/image_save.md +++ b/content/engine/reference/commandline/image_save.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_save title: docker image save -redirect_from: - - /edge/engine/reference/commandline/image_save/ +aliases: +- /edge/engine/reference/commandline/image_save/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/image_tag.md b/content/engine/reference/commandline/image_tag.md index b1a5f24c4b..f5a6a6a4f6 100644 --- a/content/engine/reference/commandline/image_tag.md +++ b/content/engine/reference/commandline/image_tag.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_image_tag title: docker image tag -redirect_from: - - /edge/engine/reference/commandline/image_tag/ +aliases: +- /edge/engine/reference/commandline/image_tag/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/images.md b/content/engine/reference/commandline/images.md index 6cd6e51eeb..87afebbf08 100644 --- a/content/engine/reference/commandline/images.md +++ b/content/engine/reference/commandline/images.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_images title: docker images -redirect_from: - - /edge/engine/reference/commandline/images/ +aliases: +- /edge/engine/reference/commandline/images/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/import.md b/content/engine/reference/commandline/import.md index ce31e71d40..f60eef87e0 100644 --- a/content/engine/reference/commandline/import.md +++ b/content/engine/reference/commandline/import.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_import title: docker import -redirect_from: - - /edge/engine/reference/commandline/import/ +aliases: +- /edge/engine/reference/commandline/import/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/info.md b/content/engine/reference/commandline/info.md index dd090f6ba1..ea2fc28fa0 100644 --- a/content/engine/reference/commandline/info.md +++ b/content/engine/reference/commandline/info.md @@ -2,9 +2,11 @@ datafolder: engine-cli datafile: docker_info title: docker info -redirect_from: - - /edge/engine/reference/commandline/info/ +aliases: +- /edge/engine/reference/commandline/info/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} + ## Warnings about kernel support @@ -29,4 +31,4 @@ WARNING: No swap limit support You can ignore these warnings unless you actually need the ability to [limit these resources](../../../config/containers/resource_constraints.md), in which case you -should consult your operating system's documentation for enabling them. +should consult your operating system's documentation for enabling them. \ No newline at end of file diff --git a/content/engine/reference/commandline/init.md b/content/engine/reference/commandline/init.md index b93e7beb72..8b46853e36 100644 --- a/content/engine/reference/commandline/init.md +++ b/content/engine/reference/commandline/init.md @@ -2,7 +2,9 @@ datafolder: init-cli datafile: docker_init title: docker init +layout: cli --- + > **Beta** > -> The Docker Init plugin is currently in [Beta](../../../release-lifecycle.md#beta). Docker recommends that you do not use this in production environments. - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +> The Docker Init plugin is currently in [Beta](../../../release-lifecycle.md#beta). Docker recommends that you do not use this in production environments. \ No newline at end of file diff --git a/content/engine/reference/commandline/inspect.md b/content/engine/reference/commandline/inspect.md index 81c904146b..aecd0948aa 100644 --- a/content/engine/reference/commandline/inspect.md +++ b/content/engine/reference/commandline/inspect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_inspect title: docker inspect -redirect_from: - - /edge/engine/reference/commandline/inspect/ +aliases: +- /edge/engine/reference/commandline/inspect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/kill.md b/content/engine/reference/commandline/kill.md index 6e46a74eea..a25c02aa37 100644 --- a/content/engine/reference/commandline/kill.md +++ b/content/engine/reference/commandline/kill.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_kill title: docker kill -redirect_from: - - /edge/engine/reference/commandline/kill/ +aliases: +- /edge/engine/reference/commandline/kill/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/load.md b/content/engine/reference/commandline/load.md index 7b688fac38..1416f6f70d 100644 --- a/content/engine/reference/commandline/load.md +++ b/content/engine/reference/commandline/load.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_load title: docker load -redirect_from: - - /edge/engine/reference/commandline/load/ +aliases: +- /edge/engine/reference/commandline/load/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/login.md b/content/engine/reference/commandline/login.md index 90796a8498..23d7e7cb97 100644 --- a/content/engine/reference/commandline/login.md +++ b/content/engine/reference/commandline/login.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_login title: docker login -redirect_from: - - /edge/engine/reference/commandline/login/ +aliases: +- /edge/engine/reference/commandline/login/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/logout.md b/content/engine/reference/commandline/logout.md index 75f6d88ccc..6ad574fe78 100644 --- a/content/engine/reference/commandline/logout.md +++ b/content/engine/reference/commandline/logout.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_logout title: docker logout -redirect_from: - - /edge/engine/reference/commandline/logout/ +aliases: +- /edge/engine/reference/commandline/logout/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/logs.md b/content/engine/reference/commandline/logs.md index 8a55cbb181..977d637b16 100644 --- a/content/engine/reference/commandline/logs.md +++ b/content/engine/reference/commandline/logs.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_logs title: docker logs -redirect_from: - - /edge/engine/reference/commandline/logs/ +aliases: +- /edge/engine/reference/commandline/logs/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/manifest.md b/content/engine/reference/commandline/manifest.md index c3f9d52965..108a90dde9 100644 --- a/content/engine/reference/commandline/manifest.md +++ b/content/engine/reference/commandline/manifest.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_manifest title: docker manifest -redirect_from: - - /edge/engine/reference/commandline/manifest/ +aliases: +- /edge/engine/reference/commandline/manifest/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/manifest_annotate.md b/content/engine/reference/commandline/manifest_annotate.md index 9ffa7a9168..13b41483e9 100644 --- a/content/engine/reference/commandline/manifest_annotate.md +++ b/content/engine/reference/commandline/manifest_annotate.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_manifest_annotate title: docker manifest annotate -redirect_from: - - /edge/engine/reference/commandline/manifest_annotate/ +aliases: +- /edge/engine/reference/commandline/manifest_annotate/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/manifest_create.md b/content/engine/reference/commandline/manifest_create.md index 976377eda0..c07245d516 100644 --- a/content/engine/reference/commandline/manifest_create.md +++ b/content/engine/reference/commandline/manifest_create.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_manifest_create title: docker manifest create -redirect_from: - - /edge/engine/reference/commandline/manifest_create/ +aliases: +- /edge/engine/reference/commandline/manifest_create/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/manifest_inspect.md b/content/engine/reference/commandline/manifest_inspect.md index cfe75e9e56..612f44443a 100644 --- a/content/engine/reference/commandline/manifest_inspect.md +++ b/content/engine/reference/commandline/manifest_inspect.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_manifest_inspect title: docker manifest inspect -redirect_from: - - /edge/engine/reference/commandline/manifest_inspect/ +aliases: +- /edge/engine/reference/commandline/manifest_inspect/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/manifest_push.md b/content/engine/reference/commandline/manifest_push.md index 9814a35bc7..e749976ffe 100644 --- a/content/engine/reference/commandline/manifest_push.md +++ b/content/engine/reference/commandline/manifest_push.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_manifest_push title: docker manifest push -redirect_from: - - /edge/engine/reference/commandline/manifest_push/ +aliases: +- /edge/engine/reference/commandline/manifest_push/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/manifest_rm.md b/content/engine/reference/commandline/manifest_rm.md index 325cd7c416..5210413e4d 100644 --- a/content/engine/reference/commandline/manifest_rm.md +++ b/content/engine/reference/commandline/manifest_rm.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_manifest_rm title: docker manifest rm +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network.md b/content/engine/reference/commandline/network.md index 0ad72facd7..e7866f60ee 100644 --- a/content/engine/reference/commandline/network.md +++ b/content/engine/reference/commandline/network.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network title: docker network -redirect_from: - - /edge/engine/reference/commandline/network/ +aliases: +- /edge/engine/reference/commandline/network/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_connect.md b/content/engine/reference/commandline/network_connect.md index b04286cd20..1bff2ee8fe 100644 --- a/content/engine/reference/commandline/network_connect.md +++ b/content/engine/reference/commandline/network_connect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_connect title: docker network connect -redirect_from: - - /edge/engine/reference/commandline/network_connect/ +aliases: +- /edge/engine/reference/commandline/network_connect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_create.md b/content/engine/reference/commandline/network_create.md index f234d6d1bf..d44dfcf0f1 100644 --- a/content/engine/reference/commandline/network_create.md +++ b/content/engine/reference/commandline/network_create.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_create title: docker network create -redirect_from: - - /edge/engine/reference/commandline/network_create/ +aliases: +- /edge/engine/reference/commandline/network_create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_disconnect.md b/content/engine/reference/commandline/network_disconnect.md index 7e39b6804a..f55fdebfbc 100644 --- a/content/engine/reference/commandline/network_disconnect.md +++ b/content/engine/reference/commandline/network_disconnect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_disconnect title: docker network disconnect -redirect_from: - - /edge/engine/reference/commandline/network_disconnect/ +aliases: +- /edge/engine/reference/commandline/network_disconnect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_inspect.md b/content/engine/reference/commandline/network_inspect.md index 1b9346186f..c986a81abf 100644 --- a/content/engine/reference/commandline/network_inspect.md +++ b/content/engine/reference/commandline/network_inspect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_inspect title: docker network inspect -redirect_from: - - /edge/engine/reference/commandline/network_inspect/ +aliases: +- /edge/engine/reference/commandline/network_inspect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_ls.md b/content/engine/reference/commandline/network_ls.md index fba416e8b9..bf1a0a7b89 100644 --- a/content/engine/reference/commandline/network_ls.md +++ b/content/engine/reference/commandline/network_ls.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_ls title: docker network ls -redirect_from: - - /edge/engine/reference/commandline/network_ls/ +aliases: +- /edge/engine/reference/commandline/network_ls/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_prune.md b/content/engine/reference/commandline/network_prune.md index 3142fd2688..55615d0eb5 100644 --- a/content/engine/reference/commandline/network_prune.md +++ b/content/engine/reference/commandline/network_prune.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_prune title: docker network prune -redirect_from: - - /edge/engine/reference/commandline/network_prune/ +aliases: +- /edge/engine/reference/commandline/network_prune/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/network_rm.md b/content/engine/reference/commandline/network_rm.md index e72889f7c5..f137ec329d 100644 --- a/content/engine/reference/commandline/network_rm.md +++ b/content/engine/reference/commandline/network_rm.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_network_rm title: docker network rm -redirect_from: - - /edge/engine/reference/commandline/network_rm/ +aliases: +- /edge/engine/reference/commandline/network_rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node.md b/content/engine/reference/commandline/node.md index 4c92fadd68..a2748bc340 100644 --- a/content/engine/reference/commandline/node.md +++ b/content/engine/reference/commandline/node.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node title: docker node -redirect_from: - - /edge/engine/reference/commandline/node/ +aliases: +- /edge/engine/reference/commandline/node/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_demote.md b/content/engine/reference/commandline/node_demote.md index 54bc028df7..2bc72e4eb4 100644 --- a/content/engine/reference/commandline/node_demote.md +++ b/content/engine/reference/commandline/node_demote.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_demote title: docker node demote -redirect_from: - - /edge/engine/reference/commandline/node_demote/ +aliases: +- /edge/engine/reference/commandline/node_demote/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_inspect.md b/content/engine/reference/commandline/node_inspect.md index 00a4896022..b1512d4636 100644 --- a/content/engine/reference/commandline/node_inspect.md +++ b/content/engine/reference/commandline/node_inspect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_inspect title: docker node inspect -redirect_from: - - /edge/engine/reference/commandline/node_inspect/ +aliases: +- /edge/engine/reference/commandline/node_inspect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_ls.md b/content/engine/reference/commandline/node_ls.md index a93d66dd58..a0513f41a9 100644 --- a/content/engine/reference/commandline/node_ls.md +++ b/content/engine/reference/commandline/node_ls.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_ls title: docker node ls -redirect_from: - - /edge/engine/reference/commandline/node_ls/ +aliases: +- /edge/engine/reference/commandline/node_ls/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_promote.md b/content/engine/reference/commandline/node_promote.md index 451e969f9d..a15a09f7d3 100644 --- a/content/engine/reference/commandline/node_promote.md +++ b/content/engine/reference/commandline/node_promote.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_promote title: docker node promote -redirect_from: - - /edge/engine/reference/commandline/node_promote/ +aliases: +- /edge/engine/reference/commandline/node_promote/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_ps.md b/content/engine/reference/commandline/node_ps.md index c8501c0c44..4585169700 100644 --- a/content/engine/reference/commandline/node_ps.md +++ b/content/engine/reference/commandline/node_ps.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_ps title: docker node ps -redirect_from: - - /edge/engine/reference/commandline/node_ps/ +aliases: +- /edge/engine/reference/commandline/node_ps/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_rm.md b/content/engine/reference/commandline/node_rm.md index e4fb013927..2d9e415272 100644 --- a/content/engine/reference/commandline/node_rm.md +++ b/content/engine/reference/commandline/node_rm.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_rm title: docker node rm -redirect_from: - - /edge/engine/reference/commandline/node_rm/ +aliases: +- /edge/engine/reference/commandline/node_rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/node_update.md b/content/engine/reference/commandline/node_update.md index 78461981c8..e75af3c4d6 100644 --- a/content/engine/reference/commandline/node_update.md +++ b/content/engine/reference/commandline/node_update.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_node_update title: docker node update -redirect_from: - - /edge/engine/reference/commandline/node_update/ +aliases: +- /edge/engine/reference/commandline/node_update/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/pause.md b/content/engine/reference/commandline/pause.md index 272da90dbb..cb9634c94a 100644 --- a/content/engine/reference/commandline/pause.md +++ b/content/engine/reference/commandline/pause.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_pause title: docker pause -redirect_from: - - /edge/engine/reference/commandline/pause/ +aliases: +- /edge/engine/reference/commandline/pause/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin.md b/content/engine/reference/commandline/plugin.md index 4a8a0364b7..f38ba8b4f3 100644 --- a/content/engine/reference/commandline/plugin.md +++ b/content/engine/reference/commandline/plugin.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin title: docker plugin -redirect_from: - - /edge/engine/reference/commandline/plugin/ +aliases: +- /edge/engine/reference/commandline/plugin/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_create.md b/content/engine/reference/commandline/plugin_create.md index 299766d45d..2b67336da9 100644 --- a/content/engine/reference/commandline/plugin_create.md +++ b/content/engine/reference/commandline/plugin_create.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_create title: docker plugin create -redirect_from: - - /edge/engine/reference/commandline/plugin_create/ +aliases: +- /edge/engine/reference/commandline/plugin_create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_disable.md b/content/engine/reference/commandline/plugin_disable.md index 905f1619c0..3e756358a6 100644 --- a/content/engine/reference/commandline/plugin_disable.md +++ b/content/engine/reference/commandline/plugin_disable.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_disable title: docker plugin disable -redirect_from: - - /edge/engine/reference/commandline/plugin_disable/ +aliases: +- /edge/engine/reference/commandline/plugin_disable/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_enable.md b/content/engine/reference/commandline/plugin_enable.md index bca9acbab0..a99f5c40d2 100644 --- a/content/engine/reference/commandline/plugin_enable.md +++ b/content/engine/reference/commandline/plugin_enable.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_enable title: docker plugin enable -redirect_from: - - /edge/engine/reference/commandline/plugin_enable/ +aliases: +- /edge/engine/reference/commandline/plugin_enable/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_inspect.md b/content/engine/reference/commandline/plugin_inspect.md index 6689db5db3..40ef2c086b 100644 --- a/content/engine/reference/commandline/plugin_inspect.md +++ b/content/engine/reference/commandline/plugin_inspect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_inspect title: docker plugin inspect -redirect_from: - - /edge/engine/reference/commandline/plugin_inspect/ +aliases: +- /edge/engine/reference/commandline/plugin_inspect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_install.md b/content/engine/reference/commandline/plugin_install.md index b07301f4ac..69c5286dc1 100644 --- a/content/engine/reference/commandline/plugin_install.md +++ b/content/engine/reference/commandline/plugin_install.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_install title: docker plugin install -redirect_from: - - /edge/engine/reference/commandline/plugin_install/ +aliases: +- /edge/engine/reference/commandline/plugin_install/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_ls.md b/content/engine/reference/commandline/plugin_ls.md index 24222e2d9d..9489864a64 100644 --- a/content/engine/reference/commandline/plugin_ls.md +++ b/content/engine/reference/commandline/plugin_ls.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_ls title: docker plugin ls -redirect_from: - - /edge/engine/reference/commandline/plugin_ls/ +aliases: +- /edge/engine/reference/commandline/plugin_ls/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_push.md b/content/engine/reference/commandline/plugin_push.md index 0309b34335..987ebdc9a5 100644 --- a/content/engine/reference/commandline/plugin_push.md +++ b/content/engine/reference/commandline/plugin_push.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_push title: docker plugin push -redirect_from: - - /edge/engine/reference/commandline/plugin_push/ +aliases: +- /edge/engine/reference/commandline/plugin_push/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_rm.md b/content/engine/reference/commandline/plugin_rm.md index 32a3583c10..3114db380a 100644 --- a/content/engine/reference/commandline/plugin_rm.md +++ b/content/engine/reference/commandline/plugin_rm.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_rm title: docker plugin rm -redirect_from: - - /edge/engine/reference/commandline/plugin_rm/ +aliases: +- /edge/engine/reference/commandline/plugin_rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_set.md b/content/engine/reference/commandline/plugin_set.md index 98228481ca..b336f4d51e 100644 --- a/content/engine/reference/commandline/plugin_set.md +++ b/content/engine/reference/commandline/plugin_set.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_set title: docker plugin set -redirect_from: - - /edge/engine/reference/commandline/plugin_set/ +aliases: +- /edge/engine/reference/commandline/plugin_set/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/plugin_upgrade.md b/content/engine/reference/commandline/plugin_upgrade.md index e38695f574..6069201f3d 100644 --- a/content/engine/reference/commandline/plugin_upgrade.md +++ b/content/engine/reference/commandline/plugin_upgrade.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_plugin_upgrade title: docker plugin upgrade -redirect_from: - - /edge/engine/reference/commandline/plugin_upgrade/ +aliases: +- /edge/engine/reference/commandline/plugin_upgrade/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/port.md b/content/engine/reference/commandline/port.md index 9a1a14f9a8..c80015207e 100644 --- a/content/engine/reference/commandline/port.md +++ b/content/engine/reference/commandline/port.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_port title: docker port -redirect_from: - - /edge/engine/reference/commandline/port/ +aliases: +- /edge/engine/reference/commandline/port/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/ps.md b/content/engine/reference/commandline/ps.md index 914c570356..4487095507 100644 --- a/content/engine/reference/commandline/ps.md +++ b/content/engine/reference/commandline/ps.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_ps title: docker ps -redirect_from: - - /edge/engine/reference/commandline/ps/ +aliases: +- /edge/engine/reference/commandline/ps/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/pull.md b/content/engine/reference/commandline/pull.md index a65c85b56f..8e85769af4 100644 --- a/content/engine/reference/commandline/pull.md +++ b/content/engine/reference/commandline/pull.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_pull title: docker pull -redirect_from: - - /edge/engine/reference/commandline/pull/ +aliases: +- /edge/engine/reference/commandline/pull/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/push.md b/content/engine/reference/commandline/push.md index a361bb4964..1d61e207f6 100644 --- a/content/engine/reference/commandline/push.md +++ b/content/engine/reference/commandline/push.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_push title: docker push -redirect_from: - - /edge/engine/reference/commandline/push/ +aliases: +- /edge/engine/reference/commandline/push/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/rename.md b/content/engine/reference/commandline/rename.md index 19b88c296e..833f93ba11 100644 --- a/content/engine/reference/commandline/rename.md +++ b/content/engine/reference/commandline/rename.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_rename title: docker rename -redirect_from: - - /edge/engine/reference/commandline/rename/ +aliases: +- /edge/engine/reference/commandline/rename/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/restart.md b/content/engine/reference/commandline/restart.md index aef64f84b7..5f5e7fa2f9 100644 --- a/content/engine/reference/commandline/restart.md +++ b/content/engine/reference/commandline/restart.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_restart title: docker restart -redirect_from: - - /edge/engine/reference/commandline/restart/ +aliases: +- /edge/engine/reference/commandline/restart/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/rm.md b/content/engine/reference/commandline/rm.md index 73b889a7fd..f67112d52f 100644 --- a/content/engine/reference/commandline/rm.md +++ b/content/engine/reference/commandline/rm.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_rm title: docker rm -redirect_from: - - /edge/engine/reference/commandline/rm/ +aliases: +- /edge/engine/reference/commandline/rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/rmi.md b/content/engine/reference/commandline/rmi.md index 98849f2cfc..6f00403d73 100644 --- a/content/engine/reference/commandline/rmi.md +++ b/content/engine/reference/commandline/rmi.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_rmi title: docker rmi -redirect_from: - - /edge/engine/reference/commandline/rmi/ +aliases: +- /edge/engine/reference/commandline/rmi/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/run.md b/content/engine/reference/commandline/run.md index 992dd55986..c8b611c38b 100644 --- a/content/engine/reference/commandline/run.md +++ b/content/engine/reference/commandline/run.md @@ -2,17 +2,19 @@ datafolder: engine-cli datafile: docker_run title: docker run -description: Learn all there is to know about the docker run command and how to use it in the Docker CLI. -redirect_from: - - /reference/run/ - - /edge/engine/reference/commandline/run/ - - /reference/commandline/run/ +description: Learn all there is to know about the docker run command and how to use + it in the Docker CLI. +aliases: +- /reference/run/ +- /edge/engine/reference/commandline/run/ +- /reference/commandline/run/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/save.md b/content/engine/reference/commandline/save.md index ef3d074a44..97c3460ef8 100644 --- a/content/engine/reference/commandline/save.md +++ b/content/engine/reference/commandline/save.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_save title: docker save -redirect_from: - - /edge/engine/reference/commandline/save/ +aliases: +- /edge/engine/reference/commandline/save/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/scout.md b/content/engine/reference/commandline/scout.md index 93ade9e288..1f7ede4aeb 100644 --- a/content/engine/reference/commandline/scout.md +++ b/content/engine/reference/commandline/scout.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout title: docker scout +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_compare.md b/content/engine/reference/commandline/scout_compare.md index fe04802b31..bcb8eef5f9 100644 --- a/content/engine/reference/commandline/scout_compare.md +++ b/content/engine/reference/commandline/scout_compare.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_compare title: docker scout compare +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_cves.md b/content/engine/reference/commandline/scout_cves.md index 76352e6c03..6072b444d4 100644 --- a/content/engine/reference/commandline/scout_cves.md +++ b/content/engine/reference/commandline/scout_cves.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_cves title: docker scout cves +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_entitlement.md b/content/engine/reference/commandline/scout_entitlement.md index e6e0e83d3b..6e4fae6ce2 100644 --- a/content/engine/reference/commandline/scout_entitlement.md +++ b/content/engine/reference/commandline/scout_entitlement.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_entitlement title: docker scout entitlement +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_quickview.md b/content/engine/reference/commandline/scout_quickview.md index d4df0d4dbd..25e258aa39 100644 --- a/content/engine/reference/commandline/scout_quickview.md +++ b/content/engine/reference/commandline/scout_quickview.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_quickview title: docker scout quickview +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_recommendations.md b/content/engine/reference/commandline/scout_recommendations.md index ae2523a45f..b221ca1698 100644 --- a/content/engine/reference/commandline/scout_recommendations.md +++ b/content/engine/reference/commandline/scout_recommendations.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_recommendations title: docker scout recommendations +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_repo.md b/content/engine/reference/commandline/scout_repo.md index 9e00ae13a5..b86197b335 100644 --- a/content/engine/reference/commandline/scout_repo.md +++ b/content/engine/reference/commandline/scout_repo.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_repo title: docker scout repo +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_repo_disable.md b/content/engine/reference/commandline/scout_repo_disable.md index 88242aee9d..d2c1af0476 100644 --- a/content/engine/reference/commandline/scout_repo_disable.md +++ b/content/engine/reference/commandline/scout_repo_disable.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_repo_disable title: docker scout repo disable +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_repo_enable.md b/content/engine/reference/commandline/scout_repo_enable.md index 6a4b14f116..d4af66607b 100644 --- a/content/engine/reference/commandline/scout_repo_enable.md +++ b/content/engine/reference/commandline/scout_repo_enable.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_repo_enable title: docker scout repo enable +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_repo_list.md b/content/engine/reference/commandline/scout_repo_list.md index 77ead85881..c8f4bd06da 100644 --- a/content/engine/reference/commandline/scout_repo_list.md +++ b/content/engine/reference/commandline/scout_repo_list.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_repo_list title: docker scout repo list +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_sbom.md b/content/engine/reference/commandline/scout_sbom.md index 98f45aa8d0..cc6d7b9299 100644 --- a/content/engine/reference/commandline/scout_sbom.md +++ b/content/engine/reference/commandline/scout_sbom.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_sbom title: docker scout sbom +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_stream.md b/content/engine/reference/commandline/scout_stream.md index aedfffb817..8102e6ad2f 100644 --- a/content/engine/reference/commandline/scout_stream.md +++ b/content/engine/reference/commandline/scout_stream.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_stream title: docker scout stream +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/scout_version.md b/content/engine/reference/commandline/scout_version.md index ea66a0e8b3..06c5b6f93c 100644 --- a/content/engine/reference/commandline/scout_version.md +++ b/content/engine/reference/commandline/scout_version.md @@ -2,7 +2,9 @@ datafolder: scout-cli datafile: docker_scout_version title: docker scout version +layout: cli --- + -{% include scout-early-access.md %} - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +{{< include "scout-early-access.md" >}} \ No newline at end of file diff --git a/content/engine/reference/commandline/search.md b/content/engine/reference/commandline/search.md index efb539025e..8bd662a9ff 100644 --- a/content/engine/reference/commandline/search.md +++ b/content/engine/reference/commandline/search.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_search title: docker search -redirect_from: - - /edge/engine/reference/commandline/search/ +aliases: +- /edge/engine/reference/commandline/search/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/secret.md b/content/engine/reference/commandline/secret.md index dcc6df0e6f..6e89cbeb2c 100644 --- a/content/engine/reference/commandline/secret.md +++ b/content/engine/reference/commandline/secret.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_secret title: docker secret -redirect_from: - - /edge/engine/reference/commandline/secret/ +aliases: +- /edge/engine/reference/commandline/secret/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/secret_create.md b/content/engine/reference/commandline/secret_create.md index 6edfd39fae..8df403b788 100644 --- a/content/engine/reference/commandline/secret_create.md +++ b/content/engine/reference/commandline/secret_create.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_secret_create title: docker secret create -redirect_from: - - /edge/engine/reference/commandline/secret_create/ +aliases: +- /edge/engine/reference/commandline/secret_create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/secret_inspect.md b/content/engine/reference/commandline/secret_inspect.md index 4179eec58a..0656aaccbc 100644 --- a/content/engine/reference/commandline/secret_inspect.md +++ b/content/engine/reference/commandline/secret_inspect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_secret_inspect title: docker secret inspect -redirect_from: - - /edge/engine/reference/commandline/secret_inspect/ +aliases: +- /edge/engine/reference/commandline/secret_inspect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/secret_ls.md b/content/engine/reference/commandline/secret_ls.md index f4f6fe9c92..3deef3d04b 100644 --- a/content/engine/reference/commandline/secret_ls.md +++ b/content/engine/reference/commandline/secret_ls.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_secret_ls title: docker secret ls -redirect_from: - - /edge/engine/reference/commandline/secret_ls/ +aliases: +- /edge/engine/reference/commandline/secret_ls/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/secret_rm.md b/content/engine/reference/commandline/secret_rm.md index 1b503ef2ea..0b34726b7c 100644 --- a/content/engine/reference/commandline/secret_rm.md +++ b/content/engine/reference/commandline/secret_rm.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_secret_rm title: docker secret rm -redirect_from: - - /edge/engine/reference/commandline/secret_rm/ +aliases: +- /edge/engine/reference/commandline/secret_rm/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service.md b/content/engine/reference/commandline/service.md index 1964f100fb..8823379248 100644 --- a/content/engine/reference/commandline/service.md +++ b/content/engine/reference/commandline/service.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service title: docker service -redirect_from: - - /edge/engine/reference/commandline/service/ +aliases: +- /edge/engine/reference/commandline/service/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_create.md b/content/engine/reference/commandline/service_create.md index e63299f1b8..81b42b396c 100644 --- a/content/engine/reference/commandline/service_create.md +++ b/content/engine/reference/commandline/service_create.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_service_create title: docker service create -redirect_from: - - /edge/engine/reference/commandline/service_create/ +aliases: +- /edge/engine/reference/commandline/service_create/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_inspect.md b/content/engine/reference/commandline/service_inspect.md index f102d93453..d2244eb05c 100644 --- a/content/engine/reference/commandline/service_inspect.md +++ b/content/engine/reference/commandline/service_inspect.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_service_inspect title: docker service inspect -redirect_from: - - /edge/engine/reference/commandline/service_inspect/ +aliases: +- /edge/engine/reference/commandline/service_inspect/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_logs.md b/content/engine/reference/commandline/service_logs.md index 1e32dba2ea..375e2d0a0c 100644 --- a/content/engine/reference/commandline/service_logs.md +++ b/content/engine/reference/commandline/service_logs.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service_logs title: docker service logs -redirect_from: - - /edge/engine/reference/commandline/service_logs/ +aliases: +- /edge/engine/reference/commandline/service_logs/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_ls.md b/content/engine/reference/commandline/service_ls.md index f6791c2a7a..e4f3a9e2d0 100644 --- a/content/engine/reference/commandline/service_ls.md +++ b/content/engine/reference/commandline/service_ls.md @@ -2,14 +2,15 @@ datafolder: engine-cli datafile: docker_service_ls title: docker service ls -redirect_from: - - /edge/engine/reference/commandline/service_ls/ +aliases: +- /edge/engine/reference/commandline/service_ls/ +layout: cli --- + -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_ps.md b/content/engine/reference/commandline/service_ps.md index 13afb06b40..6f299e862d 100644 --- a/content/engine/reference/commandline/service_ps.md +++ b/content/engine/reference/commandline/service_ps.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service_ps title: docker service ps -redirect_from: - - /edge/engine/reference/commandline/service_ps/ +aliases: +- /edge/engine/reference/commandline/service_ps/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_rm.md b/content/engine/reference/commandline/service_rm.md index 150c0f8ca9..87455098c6 100644 --- a/content/engine/reference/commandline/service_rm.md +++ b/content/engine/reference/commandline/service_rm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service_rm title: docker service rm -redirect_from: - - /edge/engine/reference/commandline/service_rm/ +aliases: +- /edge/engine/reference/commandline/service_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_rollback.md b/content/engine/reference/commandline/service_rollback.md index d17cef86cd..1725fce345 100644 --- a/content/engine/reference/commandline/service_rollback.md +++ b/content/engine/reference/commandline/service_rollback.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service_rollback title: docker service rollback -redirect_from: - - /edge/engine/reference/commandline/service_rollback/ +aliases: +- /edge/engine/reference/commandline/service_rollback/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_scale.md b/content/engine/reference/commandline/service_scale.md index d70ece23dd..e5adfd4553 100644 --- a/content/engine/reference/commandline/service_scale.md +++ b/content/engine/reference/commandline/service_scale.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service_scale title: docker service scale -redirect_from: - - /edge/engine/reference/commandline/service_scale/ +aliases: +- /edge/engine/reference/commandline/service_scale/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/service_update.md b/content/engine/reference/commandline/service_update.md index df53eb9ddd..99d9150107 100644 --- a/content/engine/reference/commandline/service_update.md +++ b/content/engine/reference/commandline/service_update.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_service_update title: docker service update -redirect_from: - - /edge/engine/reference/commandline/service_update/ +aliases: +- /edge/engine/reference/commandline/service_update/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack.md b/content/engine/reference/commandline/stack.md index f05d003338..7f620984cf 100644 --- a/content/engine/reference/commandline/stack.md +++ b/content/engine/reference/commandline/stack.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_stack title: docker stack -redirect_from: - - /edge/engine/reference/commandline/stack/ +aliases: +- /edge/engine/reference/commandline/stack/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack_config.md b/content/engine/reference/commandline/stack_config.md index c4b5ed1f71..35196b9def 100644 --- a/content/engine/reference/commandline/stack_config.md +++ b/content/engine/reference/commandline/stack_config.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_stack_config title: docker stack config +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack_deploy.md b/content/engine/reference/commandline/stack_deploy.md index 3dd12b257e..118e3bd1b4 100644 --- a/content/engine/reference/commandline/stack_deploy.md +++ b/content/engine/reference/commandline/stack_deploy.md @@ -2,18 +2,18 @@ datafolder: engine-cli datafile: docker_stack_deploy title: docker stack deploy -redirect_from: - - /compose/bundles/ - - /engine/reference/commandline/deploy/ - - /edge/engine/reference/commandline/deploy/ - - /edge/engine/reference/commandline/stack_deploy/ +aliases: +- /compose/bundles/ +- /engine/reference/commandline/deploy/ +- /edge/engine/reference/commandline/deploy/ +- /edge/engine/reference/commandline/stack_deploy/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack_ls.md b/content/engine/reference/commandline/stack_ls.md index 0fd7eb1952..9c87098853 100644 --- a/content/engine/reference/commandline/stack_ls.md +++ b/content/engine/reference/commandline/stack_ls.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_stack_ls title: docker stack ls -redirect_from: - - /edge/engine/reference/commandline/stack_ls/ +aliases: +- /edge/engine/reference/commandline/stack_ls/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack_ps.md b/content/engine/reference/commandline/stack_ps.md index 99e6adf864..e9d0f6cd23 100644 --- a/content/engine/reference/commandline/stack_ps.md +++ b/content/engine/reference/commandline/stack_ps.md @@ -2,17 +2,17 @@ datafolder: engine-cli datafile: docker_stack_ps title: docker stack ps -redirect_from: - - /engine/reference/commandline/stack_tasks/ - - /edge/engine/reference/commandline/stack_ps/ - - /edge/engine/reference/commandline/stack_tasks/ +aliases: +- /engine/reference/commandline/stack_tasks/ +- /edge/engine/reference/commandline/stack_ps/ +- /edge/engine/reference/commandline/stack_tasks/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack_rm.md b/content/engine/reference/commandline/stack_rm.md index a9914fc68c..a7b984438d 100644 --- a/content/engine/reference/commandline/stack_rm.md +++ b/content/engine/reference/commandline/stack_rm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_stack_rm title: docker stack rm -redirect_from: - - /edge/engine/reference/commandline/stack_rm/ +aliases: +- /edge/engine/reference/commandline/stack_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stack_services.md b/content/engine/reference/commandline/stack_services.md index 7676d3edf0..d52d36a0c7 100644 --- a/content/engine/reference/commandline/stack_services.md +++ b/content/engine/reference/commandline/stack_services.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_stack_services title: docker stack services -redirect_from: - - /edge/engine/reference/commandline/stack_services/ +aliases: +- /edge/engine/reference/commandline/stack_services/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/start.md b/content/engine/reference/commandline/start.md index d05c80fc88..2d74b1c6c6 100644 --- a/content/engine/reference/commandline/start.md +++ b/content/engine/reference/commandline/start.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_start title: docker start -redirect_from: - - /edge/engine/reference/commandline/start/ +aliases: +- /edge/engine/reference/commandline/start/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stats.md b/content/engine/reference/commandline/stats.md index 3b1dbcb988..a88c28cf16 100644 --- a/content/engine/reference/commandline/stats.md +++ b/content/engine/reference/commandline/stats.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_stats title: docker stats -redirect_from: - - /edge/engine/reference/commandline/stats/ +aliases: +- /edge/engine/reference/commandline/stats/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/stop.md b/content/engine/reference/commandline/stop.md index 46d27c9244..64179894d8 100644 --- a/content/engine/reference/commandline/stop.md +++ b/content/engine/reference/commandline/stop.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_stop title: docker stop -redirect_from: - - /edge/engine/reference/commandline/stop/ +aliases: +- /edge/engine/reference/commandline/stop/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm.md b/content/engine/reference/commandline/swarm.md index 68741be7c3..e58913b7bf 100644 --- a/content/engine/reference/commandline/swarm.md +++ b/content/engine/reference/commandline/swarm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm title: docker swarm -redirect_from: - - /edge/engine/reference/commandline/swarm/ +aliases: +- /edge/engine/reference/commandline/swarm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_ca.md b/content/engine/reference/commandline/swarm_ca.md index ec600eaaa3..3bbcdcb0e3 100644 --- a/content/engine/reference/commandline/swarm_ca.md +++ b/content/engine/reference/commandline/swarm_ca.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_ca title: docker swarm ca -redirect_from: - - /edge/engine/reference/commandline/swarm_ca/ +aliases: +- /edge/engine/reference/commandline/swarm_ca/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_init.md b/content/engine/reference/commandline/swarm_init.md index bf1e9c70e7..7997a512fe 100644 --- a/content/engine/reference/commandline/swarm_init.md +++ b/content/engine/reference/commandline/swarm_init.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_init title: docker swarm init -redirect_from: - - /edge/engine/reference/commandline/swarm_init/ +aliases: +- /edge/engine/reference/commandline/swarm_init/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_join-token.md b/content/engine/reference/commandline/swarm_join-token.md index f41ce81345..c02847ed29 100644 --- a/content/engine/reference/commandline/swarm_join-token.md +++ b/content/engine/reference/commandline/swarm_join-token.md @@ -2,17 +2,17 @@ datafolder: engine-cli datafile: docker_swarm_join-token title: docker swarm join-token -redirect_from: - - /engine/reference/commandline/swarm_join_token/ - - /edge/engine/reference/commandline/swarm_join_token/ - - /edge/engine/reference/commandline/swarm_join-token/ +aliases: +- /engine/reference/commandline/swarm_join_token/ +- /edge/engine/reference/commandline/swarm_join_token/ +- /edge/engine/reference/commandline/swarm_join-token/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_join.md b/content/engine/reference/commandline/swarm_join.md index 8b6a84b4ff..8c78499352 100644 --- a/content/engine/reference/commandline/swarm_join.md +++ b/content/engine/reference/commandline/swarm_join.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_join title: docker swarm join -redirect_from: - - /edge/engine/reference/commandline/swarm_join/ +aliases: +- /edge/engine/reference/commandline/swarm_join/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_leave.md b/content/engine/reference/commandline/swarm_leave.md index 5bf1dcc5b5..9a31ed60ce 100644 --- a/content/engine/reference/commandline/swarm_leave.md +++ b/content/engine/reference/commandline/swarm_leave.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_leave title: docker swarm leave -redirect_from: - - /edge/engine/reference/commandline/swarm_leave/ +aliases: +- /edge/engine/reference/commandline/swarm_leave/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_unlock-key.md b/content/engine/reference/commandline/swarm_unlock-key.md index 6849b7ea9b..8a99cfd22c 100644 --- a/content/engine/reference/commandline/swarm_unlock-key.md +++ b/content/engine/reference/commandline/swarm_unlock-key.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_unlock-key title: docker swarm unlock-key -redirect_from: - - /edge/engine/reference/commandline/swarm_unlock-key/ +aliases: +- /edge/engine/reference/commandline/swarm_unlock-key/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_unlock.md b/content/engine/reference/commandline/swarm_unlock.md index 045a047f9d..9cc938d74e 100644 --- a/content/engine/reference/commandline/swarm_unlock.md +++ b/content/engine/reference/commandline/swarm_unlock.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_unlock title: docker swarm unlock -redirect_from: - - /edge/engine/reference/commandline/swarm_unlock/ +aliases: +- /edge/engine/reference/commandline/swarm_unlock/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/swarm_update.md b/content/engine/reference/commandline/swarm_update.md index 7e548eaec2..10b874c332 100644 --- a/content/engine/reference/commandline/swarm_update.md +++ b/content/engine/reference/commandline/swarm_update.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_swarm_update title: docker swarm update -redirect_from: - - /edge/engine/reference/commandline/swarm_update/ +aliases: +- /edge/engine/reference/commandline/swarm_update/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/system.md b/content/engine/reference/commandline/system.md index eb97a71c86..18bbb5defc 100644 --- a/content/engine/reference/commandline/system.md +++ b/content/engine/reference/commandline/system.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_system title: docker system -redirect_from: - - /edge/engine/reference/commandline/system/ +aliases: +- /edge/engine/reference/commandline/system/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/system_df.md b/content/engine/reference/commandline/system_df.md index 0d98b4fc58..d3c4981d4d 100644 --- a/content/engine/reference/commandline/system_df.md +++ b/content/engine/reference/commandline/system_df.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_system_df title: docker system df -redirect_from: - - /edge/engine/reference/commandline/system_df/ +aliases: +- /edge/engine/reference/commandline/system_df/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/system_events.md b/content/engine/reference/commandline/system_events.md index 504dcc10be..a82c5c8116 100644 --- a/content/engine/reference/commandline/system_events.md +++ b/content/engine/reference/commandline/system_events.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_system_events title: docker system events -redirect_from: - - /edge/engine/reference/commandline/system_events/ +aliases: +- /edge/engine/reference/commandline/system_events/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/system_info.md b/content/engine/reference/commandline/system_info.md index a855cc6f3a..69bf76d902 100644 --- a/content/engine/reference/commandline/system_info.md +++ b/content/engine/reference/commandline/system_info.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_system_info title: docker system info -redirect_from: - - /edge/engine/reference/commandline/system_info/ +aliases: +- /edge/engine/reference/commandline/system_info/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/system_prune.md b/content/engine/reference/commandline/system_prune.md index 025b6e7ebf..5e2b58c887 100644 --- a/content/engine/reference/commandline/system_prune.md +++ b/content/engine/reference/commandline/system_prune.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_system_prune title: docker system prune -redirect_from: - - /edge/engine/reference/commandline/system_prune/ +aliases: +- /edge/engine/reference/commandline/system_prune/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/tag.md b/content/engine/reference/commandline/tag.md index e7b0045f57..dbb6b0fe2d 100644 --- a/content/engine/reference/commandline/tag.md +++ b/content/engine/reference/commandline/tag.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_tag title: docker tag -redirect_from: - - /edge/engine/reference/commandline/tag/ +aliases: +- /edge/engine/reference/commandline/tag/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/top.md b/content/engine/reference/commandline/top.md index 372f48b7b9..5c7565c86b 100644 --- a/content/engine/reference/commandline/top.md +++ b/content/engine/reference/commandline/top.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_top title: docker top -redirect_from: - - /edge/engine/reference/commandline/top/ +aliases: +- /edge/engine/reference/commandline/top/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust.md b/content/engine/reference/commandline/trust.md index 43c802236a..16eada7bfc 100644 --- a/content/engine/reference/commandline/trust.md +++ b/content/engine/reference/commandline/trust.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust title: docker trust -redirect_from: - - /edge/engine/reference/commandline/trust/ +aliases: +- /edge/engine/reference/commandline/trust/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_inspect.md b/content/engine/reference/commandline/trust_inspect.md index c454f70ec8..1ee4e597ab 100644 --- a/content/engine/reference/commandline/trust_inspect.md +++ b/content/engine/reference/commandline/trust_inspect.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_inspect title: docker trust inspect -redirect_from: - - /edge/engine/reference/commandline/trust_inspect/ +aliases: +- /edge/engine/reference/commandline/trust_inspect/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_key.md b/content/engine/reference/commandline/trust_key.md index cf60152db2..eb329917cc 100644 --- a/content/engine/reference/commandline/trust_key.md +++ b/content/engine/reference/commandline/trust_key.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_key title: docker trust key -redirect_from: - - /edge/engine/reference/commandline/trust_key/ +aliases: +- /edge/engine/reference/commandline/trust_key/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_key_generate.md b/content/engine/reference/commandline/trust_key_generate.md index cb6277e9fc..eabc825bad 100644 --- a/content/engine/reference/commandline/trust_key_generate.md +++ b/content/engine/reference/commandline/trust_key_generate.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_key_generate title: docker trust key generate -redirect_from: - - /edge/engine/reference/commandline/trust_key_generate/ +aliases: +- /edge/engine/reference/commandline/trust_key_generate/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_key_load.md b/content/engine/reference/commandline/trust_key_load.md index 20c320a50b..2045245918 100644 --- a/content/engine/reference/commandline/trust_key_load.md +++ b/content/engine/reference/commandline/trust_key_load.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_key_load title: docker trust key load -redirect_from: - - /edge/engine/reference/commandline/trust_key_load/ +aliases: +- /edge/engine/reference/commandline/trust_key_load/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_revoke.md b/content/engine/reference/commandline/trust_revoke.md index 8c5db7b81c..93a1c7bf6b 100644 --- a/content/engine/reference/commandline/trust_revoke.md +++ b/content/engine/reference/commandline/trust_revoke.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_revoke title: docker trust revoke -redirect_from: - - /edge/engine/reference/commandline/trust_revoke/ +aliases: +- /edge/engine/reference/commandline/trust_revoke/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_sign.md b/content/engine/reference/commandline/trust_sign.md index da1a1df9da..1041a4332d 100644 --- a/content/engine/reference/commandline/trust_sign.md +++ b/content/engine/reference/commandline/trust_sign.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_sign title: docker trust sign -redirect_from: - - /edge/engine/reference/commandline/trust_sign/ +aliases: +- /edge/engine/reference/commandline/trust_sign/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_signer.md b/content/engine/reference/commandline/trust_signer.md index ea4ace8a3a..3a895d7e15 100644 --- a/content/engine/reference/commandline/trust_signer.md +++ b/content/engine/reference/commandline/trust_signer.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_signer title: docker trust signer -redirect_from: - - /edge/engine/reference/commandline/trust_signer/ +aliases: +- /edge/engine/reference/commandline/trust_signer/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_signer_add.md b/content/engine/reference/commandline/trust_signer_add.md index 0630cb1f91..4728a5e22d 100644 --- a/content/engine/reference/commandline/trust_signer_add.md +++ b/content/engine/reference/commandline/trust_signer_add.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_signer_add title: docker trust signer add -redirect_from: - - /edge/engine/reference/commandline/trust_signer_add/ +aliases: +- /edge/engine/reference/commandline/trust_signer_add/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/trust_signer_remove.md b/content/engine/reference/commandline/trust_signer_remove.md index 2618465fe7..22bcb72d75 100644 --- a/content/engine/reference/commandline/trust_signer_remove.md +++ b/content/engine/reference/commandline/trust_signer_remove.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_trust_signer_remove title: docker trust signer remove -redirect_from: - - /edge/engine/reference/commandline/trust_signer_remove/ +aliases: +- /edge/engine/reference/commandline/trust_signer_remove/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/unpause.md b/content/engine/reference/commandline/unpause.md index c4b150e6f2..62e70dc739 100644 --- a/content/engine/reference/commandline/unpause.md +++ b/content/engine/reference/commandline/unpause.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_unpause title: docker unpause -redirect_from: - - /edge/engine/reference/commandline/unpause/ +aliases: +- /edge/engine/reference/commandline/unpause/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/update.md b/content/engine/reference/commandline/update.md index ddde86c0c8..2c8a714493 100644 --- a/content/engine/reference/commandline/update.md +++ b/content/engine/reference/commandline/update.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_update title: docker update -redirect_from: - - /edge/engine/reference/commandline/update/ +aliases: +- /edge/engine/reference/commandline/update/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/version.md b/content/engine/reference/commandline/version.md index 06b10b5fb1..56fb1b7102 100644 --- a/content/engine/reference/commandline/version.md +++ b/content/engine/reference/commandline/version.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_version title: docker version -redirect_from: - - /edge/engine/reference/commandline/version/ +aliases: +- /edge/engine/reference/commandline/version/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume.md b/content/engine/reference/commandline/volume.md index 2fa7c962f6..a25430630b 100644 --- a/content/engine/reference/commandline/volume.md +++ b/content/engine/reference/commandline/volume.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_volume title: docker volume -redirect_from: - - /edge/engine/reference/commandline/volume/ +aliases: +- /edge/engine/reference/commandline/volume/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume_create.md b/content/engine/reference/commandline/volume_create.md index 5bb6052c2b..9f79f77744 100644 --- a/content/engine/reference/commandline/volume_create.md +++ b/content/engine/reference/commandline/volume_create.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_volume_create title: docker volume create -redirect_from: - - /edge/engine/reference/commandline/volume_create/ +aliases: +- /edge/engine/reference/commandline/volume_create/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume_inspect.md b/content/engine/reference/commandline/volume_inspect.md index 4ce4655fd3..3c2f1cdaed 100644 --- a/content/engine/reference/commandline/volume_inspect.md +++ b/content/engine/reference/commandline/volume_inspect.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_volume_inspect title: docker volume inspect -redirect_from: - - /edge/engine/reference/commandline/volume_inspect/ +aliases: +- /edge/engine/reference/commandline/volume_inspect/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume_ls.md b/content/engine/reference/commandline/volume_ls.md index ab2a961f3e..68c36ff8f1 100644 --- a/content/engine/reference/commandline/volume_ls.md +++ b/content/engine/reference/commandline/volume_ls.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_volume_ls title: docker volume ls -redirect_from: - - /edge/engine/reference/commandline/volume_ls/ +aliases: +- /edge/engine/reference/commandline/volume_ls/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume_prune.md b/content/engine/reference/commandline/volume_prune.md index 8d91c644b9..e51d299b9c 100644 --- a/content/engine/reference/commandline/volume_prune.md +++ b/content/engine/reference/commandline/volume_prune.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_volume_prune title: docker volume prune -redirect_from: - - /edge/engine/reference/commandline/volume_prune/ +aliases: +- /edge/engine/reference/commandline/volume_prune/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume_rm.md b/content/engine/reference/commandline/volume_rm.md index e1b6a410b6..7291700cdd 100644 --- a/content/engine/reference/commandline/volume_rm.md +++ b/content/engine/reference/commandline/volume_rm.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_volume_rm title: docker volume rm -redirect_from: - - /edge/engine/reference/commandline/volume_rm/ +aliases: +- /edge/engine/reference/commandline/volume_rm/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/volume_update.md b/content/engine/reference/commandline/volume_update.md index c8d85b7fe2..6832591951 100644 --- a/content/engine/reference/commandline/volume_update.md +++ b/content/engine/reference/commandline/volume_update.md @@ -2,13 +2,13 @@ datafolder: engine-cli datafile: docker_volume_update title: docker volume update +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/reference/commandline/wait.md b/content/engine/reference/commandline/wait.md index 12349d104e..9ac4b23d45 100644 --- a/content/engine/reference/commandline/wait.md +++ b/content/engine/reference/commandline/wait.md @@ -2,15 +2,15 @@ datafolder: engine-cli datafile: docker_wait title: docker wait -redirect_from: - - /edge/engine/reference/commandline/wait/ +aliases: +- /edge/engine/reference/commandline/wait/ +layout: cli --- + - -{% include cli.md datafolder=page.datafolder datafile=page.datafile %} +--> \ No newline at end of file diff --git a/content/engine/release-notes/17.03.md b/content/engine/release-notes/17.03.md index 63a066a3e5..5af1623c11 100644 --- a/content/engine/release-notes/17.03.md +++ b/content/engine/release-notes/17.03.md @@ -113,5 +113,4 @@ Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk. * Fix extraneous task creations for global services that led to confusing replica counts in `docker service ls` [docker/swarmkit#1957](https://github.com/docker/swarmkit/pull/1957) * Fix problem that made rolling updates slow when `task-history-limit` was set to 1 [docker/swarmkit#1948](https://github.com/docker/swarmkit/pull/1948) * Restart tasks elsewhere, if appropriate, when they are shut down as a result of nodes no longer satisfying constraints [docker/swarmkit#1958](https://github.com/docker/swarmkit/pull/1958) -* (experimental) - +* (experimental) \ No newline at end of file diff --git a/content/engine/release-notes/17.04.md b/content/engine/release-notes/17.04.md index 053ec2b909..fe4963d7bc 100644 --- a/content/engine/release-notes/17.04.md +++ b/content/engine/release-notes/17.04.md @@ -89,4 +89,4 @@ skip_read_time: true ### Windows -* Block pulling Windows images on non-Windows daemons [#29001](https://github.com/docker/docker/pull/29001) +* Block pulling Windows images on non-Windows daemons [#29001](https://github.com/docker/docker/pull/29001) \ No newline at end of file diff --git a/content/engine/release-notes/17.05.md b/content/engine/release-notes/17.05.md index 09869f9286..ad1393f186 100644 --- a/content/engine/release-notes/17.05.md +++ b/content/engine/release-notes/17.05.md @@ -90,4 +90,4 @@ skip_read_time: true ### Deprecation - Deprecate `--api-enable-cors` daemon flag. This flag was marked deprecated in Docker 1.6.0 but not listed in deprecated features [#32352](https://github.com/docker/docker/pull/32352) -- Remove Ubuntu 12.04 (Precise Pangolin) as supported platform. Ubuntu 12.04 is EOL, and no longer receives updates [#32520](https://github.com/docker/docker/pull/32520) +- Remove Ubuntu 12.04 (Precise Pangolin) as supported platform. Ubuntu 12.04 is EOL, and no longer receives updates [#32520](https://github.com/docker/docker/pull/32520) \ No newline at end of file diff --git a/content/engine/release-notes/17.06.md b/content/engine/release-notes/17.06.md index 4432855c1c..a49a736cf0 100644 --- a/content/engine/release-notes/17.06.md +++ b/content/engine/release-notes/17.06.md @@ -180,4 +180,4 @@ skip_read_time: true ### Deprecation -* Disable legacy registry (v1) by default [#33629](https://github.com/moby/moby/pull/33629) +* Disable legacy registry (v1) by default [#33629](https://github.com/moby/moby/pull/33629) \ No newline at end of file diff --git a/content/engine/release-notes/17.07.md b/content/engine/release-notes/17.07.md index 727a1ee715..67b3229954 100644 --- a/content/engine/release-notes/17.07.md +++ b/content/engine/release-notes/17.07.md @@ -66,4 +66,4 @@ skip_read_time: true * Make engine support cluster config event [moby/moby#34032](https://github.com/moby/moby/pull/34032) * Only pass a join address when in the process of joining a cluster [moby/moby#33361](https://github.com/moby/moby/pull/33361) * Fix error during service creation if a network with the same name exists both as "local" and "swarm" scoped network [docker/cli#184](https://github.com/docker/cli/pull/184) -* (experimental) Add support for plugins on swarm [moby/moby#33575](https://github.com/moby/moby/pull/33575) +* (experimental) Add support for plugins on swarm [moby/moby#33575](https://github.com/moby/moby/pull/33575) \ No newline at end of file diff --git a/content/engine/release-notes/17.09.md b/content/engine/release-notes/17.09.md index 517cfcc547..a1bb95c44c 100644 --- a/content/engine/release-notes/17.09.md +++ b/content/engine/release-notes/17.09.md @@ -67,9 +67,9 @@ skip_read_time: true + Add support for update order in compose deployments [docker/cli#360](https://github.com/docker/cli/pull/360) + Add ulimits to unsupported compose fields [docker/cli#482](https://github.com/docker/cli/pull/482) + Add `--format` to `docker-search` [docker/cli#440](https://github.com/docker/cli/pull/440) -* Show images digests when {% raw %}`{{.Digest}}`{% endraw %} is in format [docker/cli#439](https://github.com/docker/cli/pull/439) +* Show images digests when `{{.Digest}}` is in format [docker/cli#439](https://github.com/docker/cli/pull/439) * Print output of `docker stack rm` on `stdout` instead of `stderr` [docker/cli#491](https://github.com/docker/cli/pull/491) -- Fix {% raw %}`docker history --format {{json .}}`{% endraw %} printing human-readable timestamps instead of ISO8601 when `--human=true` [docker/cli#438](https://github.com/docker/cli/pull/438) +- Fix `docker history --format {{json .}}` printing human-readable timestamps instead of ISO8601 when `--human=true` [docker/cli#438](https://github.com/docker/cli/pull/438) - Fix idempotence of `docker stack deploy` when secrets or configs are used [docker/cli#509](https://github.com/docker/cli/pull/509) - Fix presentation of random host ports [docker/cli#404](https://github.com/docker/cli/pull/404) - Fix redundant service restarts when service created with multiple secrets [moby/moby#34746](https://github.com/moby/moby/issues/34746) @@ -112,4 +112,4 @@ skip_read_time: true ### Deprecation -+ Remove deprecated `--enable-api-cors` daemon flag [moby/moby#34821](https://github.com/moby/moby/pull/34821) ++ Remove deprecated `--enable-api-cors` daemon flag [moby/moby#34821](https://github.com/moby/moby/pull/34821) \ No newline at end of file diff --git a/content/engine/release-notes/17.10.md b/content/engine/release-notes/17.10.md index 1857cb22fc..68e0e46154 100644 --- a/content/engine/release-notes/17.10.md +++ b/content/engine/release-notes/17.10.md @@ -11,7 +11,7 @@ skip_read_time: true > **Important**: Starting with this release, `docker service create`, `docker service update`, `docker service scale` and `docker service rollback` use non-detached mode as default, use `--detach` to keep the old behaviour. -{: .important } +{ .important } ### Builder @@ -53,4 +53,4 @@ use `--detach` to keep the old behaviour. + Add support for `.Node.Hostname` templating in swarm services [moby/moby#34686](https://github.com/moby/moby/pull/34686) * Increase gRPC request timeout to 20 seconds for sending snapshots [docker/swarmkit#2391](https://github.com/docker/swarmkit/pull/2391) - Do not filter nodes if logdriver is set to `none` [docker/swarmkit#2396](https://github.com/docker/swarmkit/pull/2396) -+ Adding ipam options to ipam driver requests [docker/swarmkit#2324](https://github.com/docker/swarmkit/pull/2324) ++ Adding ipam options to ipam driver requests [docker/swarmkit#2324](https://github.com/docker/swarmkit/pull/2324) \ No newline at end of file diff --git a/content/engine/release-notes/17.11.md b/content/engine/release-notes/17.11.md index 6129be1ba2..c6db3ab6db 100644 --- a/content/engine/release-notes/17.11.md +++ b/content/engine/release-notes/17.11.md @@ -17,7 +17,7 @@ you must stop all containers before upgrading to Docker CE 17.11. If you don't, any containers started by Docker versions that predate 17.11 aren't recognized by Docker after the upgrade and keep running, un-managed, on the system. -{:.important} +{ .important } ### Builder @@ -76,4 +76,4 @@ running, un-managed, on the system. ### Packaging + Build packages for Debian 10 (Buster) [docker/docker-ce-packaging#50](https://github.com/docker/docker-ce-packaging/pull/50) -+ Build packages for Ubuntu 17.10 (Artful) [docker/docker-ce-packaging#55](https://github.com/docker/docker-ce-packaging/pull/55) ++ Build packages for Ubuntu 17.10 (Artful) [docker/docker-ce-packaging#55](https://github.com/docker/docker-ce-packaging/pull/55) \ No newline at end of file diff --git a/content/engine/release-notes/17.12.md b/content/engine/release-notes/17.12.md index 0346b0ecfc..143f6a92f3 100644 --- a/content/engine/release-notes/17.12.md +++ b/content/engine/release-notes/17.12.md @@ -152,4 +152,4 @@ skip_read_time: true + Add Packaging for Fedora 27 [docker/docker-ce-packaging#59](https://github.com/docker/docker-ce-packaging/pull/59) * Change default versioning scheme to 0.0.0-dev unless specified for packaging [docker/docker-ce-packaging#67](https://github.com/docker/docker-ce-packaging/pull/67) * Pass Version to engine static builds [docker/docker-ce-packaging#70](https://github.com/docker/docker-ce-packaging/pull/70) -+ Added support for aarch64 on Debian (stretch/jessie) and Ubuntu Zesty or newer [docker/docker-ce-packaging#35](https://github.com/docker/docker-ce-packaging/pull/35) ++ Added support for aarch64 on Debian (stretch/jessie) and Ubuntu Zesty or newer [docker/docker-ce-packaging#35](https://github.com/docker/docker-ce-packaging/pull/35) \ No newline at end of file diff --git a/content/engine/release-notes/18.01.md b/content/engine/release-notes/18.01.md index 3fa3e93a3e..02026c5f39 100644 --- a/content/engine/release-notes/18.01.md +++ b/content/engine/release-notes/18.01.md @@ -5,7 +5,6 @@ toc_max: 2 skip_read_time: true --- - ## 18.01.0-ce 2018-01-10 @@ -62,4 +61,4 @@ skip_read_time: true ### Swarm mode - Fix published ports not being updated if a service has the same number of host-mode published ports with Published Port 0 [docker/swarmkit#2376](https://github.com/docker/swarmkit/pull/2376) -* Make the task termination order deterministic [docker/swarmkit#2265](https://github.com/docker/swarmkit/pull/2265) +* Make the task termination order deterministic [docker/swarmkit#2265](https://github.com/docker/swarmkit/pull/2265) \ No newline at end of file diff --git a/content/engine/release-notes/18.02.md b/content/engine/release-notes/18.02.md index 5a906966ac..4c2d0b6082 100644 --- a/content/engine/release-notes/18.02.md +++ b/content/engine/release-notes/18.02.md @@ -5,7 +5,6 @@ toc_max: 2 skip_read_time: true --- - ## 18.02.0-ce 2018-02-07 @@ -70,4 +69,4 @@ skip_read_time: true - Fix `DOCKER_RAMDISK` environment variable not being honoured [moby/moby#35957](https://github.com/moby/moby/pull/35957) * Bump containerd to 1.0.1 (9b55aab90508bd389d7654c4baf173a981477d55) [moby/moby#35986](https://github.com/moby/moby/pull/35986) * Update runc to fix hang during start and exec [moby/moby#36097](https://github.com/moby/moby/pull/36097) -- Fix "--node-generic-resource" singular/plural [moby/moby#36125](https://github.com/moby/moby/pull/36125) +- Fix "--node-generic-resource" singular/plural [moby/moby#36125](https://github.com/moby/moby/pull/36125) \ No newline at end of file diff --git a/content/engine/release-notes/18.03.md b/content/engine/release-notes/18.03.md index 5fccb5dde1..993e78a3d2 100644 --- a/content/engine/release-notes/18.03.md +++ b/content/engine/release-notes/18.03.md @@ -5,7 +5,6 @@ toc_max: 2 skip_read_time: true --- - ## 18.03.1-ce 2018-04-26 diff --git a/content/engine/release-notes/18.04.md b/content/engine/release-notes/18.04.md index 3c5dec7a94..60742a05b2 100644 --- a/content/engine/release-notes/18.04.md +++ b/content/engine/release-notes/18.04.md @@ -5,7 +5,6 @@ toc_max: 2 skip_read_time: true --- - ## 18.04.0-ce 2018-04-10 @@ -86,4 +85,4 @@ skip_read_time: true * Agent: backoff session when no remotes are available. [docker/swarmkit#2570](https://github.com/docker/swarmkit/pull/2570) * [ca/manager] Remove root CA key encryption support entirely. [docker/swarmkit#2573](https://github.com/docker/swarmkit/pull/2573) - Fix agent logging race. [docker/swarmkit#2578](https://github.com/docker/swarmkit/pull/2578) -* Adding logic to restore networks in order. [docker/swarmkit#2571](https://github.com/docker/swarmkit/pull/2571) +* Adding logic to restore networks in order. [docker/swarmkit#2571](https://github.com/docker/swarmkit/pull/2571) \ No newline at end of file diff --git a/content/engine/release-notes/18.05.md b/content/engine/release-notes/18.05.md index 27e28db7f7..9130405bee 100644 --- a/content/engine/release-notes/18.05.md +++ b/content/engine/release-notes/18.05.md @@ -74,4 +74,4 @@ skip_read_time: true * Agent reports FIPS status. [docker/swarmkit#2587](https://github.com/docker/swarmkit/pull/2587) - Fix: timeMutex critical operation outside of critical section. [docker/swarmkit#2603](https://github.com/docker/swarmkit/pull/2603) * Expose swarmkit's Raft tuning parameters in engine config. [moby/moby#36726](https://github.com/moby/moby/pull/36726) -* Make internal/test/daemon.Daemon swarm aware. [moby/moby#36826](https://github.com/moby/moby/pull/36826) +* Make internal/test/daemon.Daemon swarm aware. [moby/moby#36826](https://github.com/moby/moby/pull/36826) \ No newline at end of file diff --git a/content/engine/release-notes/18.06.md b/content/engine/release-notes/18.06.md index b206b75708..5bd9e3ed8c 100644 --- a/content/engine/release-notes/18.06.md +++ b/content/engine/release-notes/18.06.md @@ -220,4 +220,4 @@ skip_read_time: true - Fix broken swarm commands with Kubernetes defined as orchestrator. "--orchestrator" flag is no longer global but local to stack commands and subcommands [docker/cli#1137](https://github.com/docker/cli/pull/1137) [docker/cli#1139](https://github.com/docker/cli/pull/1139) * Bump swarmkit to include task reaper fixes and more metrics. [docker/engine#13](https://github.com/docker/engine/pull/13) - Avoid a leak when a service with unassigned tasks is deleted. [docker/engine#27](https://github.com/docker/engine/pull/27) -- Fix racy batching on the dispatcher. [docker/engine#27](https://github.com/docker/engine/pull/27) +- Fix racy batching on the dispatcher. [docker/engine#27](https://github.com/docker/engine/pull/27) \ No newline at end of file diff --git a/content/engine/release-notes/18.09.md b/content/engine/release-notes/18.09.md index 9f41bde9ec..13cc814abc 100644 --- a/content/engine/release-notes/18.09.md +++ b/content/engine/release-notes/18.09.md @@ -382,4 +382,4 @@ For more information on the list of deprecated flags and APIs, have a look at th ### End of Life Notification In this release, Docker has also removed support for TLS < 1.2 [moby/moby#37660](https://github.com/moby/moby/pull/37660), -Ubuntu 14.04 "Trusty Tahr" [docker-ce-packaging#255](https://github.com/docker/docker-ce-packaging/pull/255) / [docker-ce-packaging#254](https://github.com/docker/docker-ce-packaging/pull/254), and Debian 8 "Jessie" [docker-ce-packaging#255](https://github.com/docker/docker-ce-packaging/pull/255) / [docker-ce-packaging#254](https://github.com/docker/docker-ce-packaging/pull/254). +Ubuntu 14.04 "Trusty Tahr" [docker-ce-packaging#255](https://github.com/docker/docker-ce-packaging/pull/255) / [docker-ce-packaging#254](https://github.com/docker/docker-ce-packaging/pull/254), and Debian 8 "Jessie" [docker-ce-packaging#255](https://github.com/docker/docker-ce-packaging/pull/255) / [docker-ce-packaging#254](https://github.com/docker/docker-ce-packaging/pull/254). \ No newline at end of file diff --git a/content/engine/release-notes/19.03.md b/content/engine/release-notes/19.03.md index 3cb57abcd6..ebc53661b5 100644 --- a/content/engine/release-notes/19.03.md +++ b/content/engine/release-notes/19.03.md @@ -643,4 +643,4 @@ The missing rules are : rules back. Run the script on a cron in regular intervals, for example, every minutes. - Affected versions: 18.09.1, 19.03.0 * [CVE-2018-15664](https://nvd.nist.gov/vuln/detail/CVE-2018-15664) symlink-exchange attack with directory traversal. Workaround until proper fix is available in upcoming patch release: `docker pause` container before doing file operations. [moby/moby#39252](https://github.com/moby/moby/pull/39252) -* `docker cp` regression due to CVE mitigation. An error is produced when the source of `docker cp` is set to `/`. +* `docker cp` regression due to CVE mitigation. An error is produced when the source of `docker cp` is set to `/`. \ No newline at end of file diff --git a/content/engine/release-notes/20.10.md b/content/engine/release-notes/20.10.md index dfb9f0ec3e..0438bf4408 100644 --- a/content/engine/release-notes/20.10.md +++ b/content/engine/release-notes/20.10.md @@ -1,6 +1,7 @@ --- title: Docker Engine 20.10 release notes -description: Learn about the new features, bug fixes, and breaking changes for Docker Engine +description: Learn about the new features, bug fixes, and breaking changes for Docker + Engine keywords: docker, docker engine, ce, whats new, release notes toc_min: 1 toc_max: 2 @@ -11,7 +12,7 @@ This document describes the latest changes, additions, known issues, and fixes for Docker Engine version 20.10. ## 20.10.24 -{% include release-date.html date="2023-04-04" %} +{{< release-date date="2023-04-04" >}} ### Updates @@ -39,24 +40,24 @@ for Docker Engine version 20.10. ## 20.10.23 -{% include release-date.html date="2023-01-19" %} +{{< release-date date="2023-01-19" >}} This release of Docker Engine contains updated versions of Docker Compose, Docker Buildx, containerd, and some minor bug fixes and enhancements. ### Updates -- Update Docker Compose to [v2.15.1](https://github.com/docker/compose/releases/tag/v2.15.1){:target="_blank" rel="noopener"}. -- Update Docker Buildx to [v0.10.0](https://github.com/docker/buildx/releases/tag/v0.10.0){:target="_blank" rel="noopener"}. -- Update containerd (`containerd.io` package) to [v1.6.15](https://github.com/containerd/containerd/releases/tag/v1.6.15){:target="_blank" rel="noopener"}. -- Update the package versioning format for `docker-compose-cli` to allow distro version updates [docker/docker-ce-packaging#822](https://github.com/docker/docker-ce-packaging/pull/822){:target="_blank" rel="noopener"}. -- Update Go runtime to [1.18.10](https://go.dev/doc/devel/release#go1.18.minor){:target="_blank" rel="noopener"}, +- Update Docker Compose to [v2.15.1](https://github.com/docker/compose/releases/tag/v2.15.1). +- Update Docker Buildx to [v0.10.0](https://github.com/docker/buildx/releases/tag/v0.10.0). +- Update containerd (`containerd.io` package) to [v1.6.15](https://github.com/containerd/containerd/releases/tag/v1.6.15). +- Update the package versioning format for `docker-compose-cli` to allow distro version updates [docker/docker-ce-packaging#822](https://github.com/docker/docker-ce-packaging/pull/822). +- Update Go runtime to [1.18.10](https://go.dev/doc/devel/release#go1.18.minor), ### Bug fixes and enhancements - Fix an issue where `docker build` would fail when using `--add-host=host.docker.internal:host-gateway` - with BuildKit enabled [moby/moby#44650](https://github.com/moby/moby/pull/44650){:target="_blank" rel="noopener"}. -- Revert seccomp: block socket calls to `AF_VSOCK` in default profile [moby/moby#44712](https://github.com/moby/moby/pull/44712){:target="_blank" rel="noopener"}. + with BuildKit enabled [moby/moby#44650](https://github.com/moby/moby/pull/44650). +- Revert seccomp: block socket calls to `AF_VSOCK` in default profile [moby/moby#44712](https://github.com/moby/moby/pull/44712). This change, while favorable from a security standpoint, caused a change in behavior for some use-cases. As such, we are reverting it to ensure @@ -72,35 +73,35 @@ Docker Buildx, containerd, and some minor bug fixes and enhancements. confinement or set a custom seccomp profile. ## 20.10.22 -{% include release-date.html date="2022-12-16" %} +{{< release-date date="2022-12-16" >}} This release of Docker Engine contains updated versions of Docker Compose, Docker Scan, containerd, and some minor bug fixes and enhancements. ### Updates -- Update Docker Compose to [v2.14.1](https://github.com/docker/compose/releases/tag/v2.14.1){:target="_blank" rel="noopener"}. -- Update Docker Scan to [v0.23.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.23.0){:target="_blank" rel="noopener"}. -- Update containerd (`containerd.io` package) to [v1.6.13](https://github.com/containerd/containerd/releases/tag/v1.6.13){:target="_blank" rel="noopener"}, - to include a fix for [CVE-2022-23471](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23471){:target="_blank" rel="noopener"}. -- Update Go runtime to [1.18.9](https://go.dev/doc/devel/release#go1.18.minor){:target="_blank" rel="noopener"}, +- Update Docker Compose to [v2.14.1](https://github.com/docker/compose/releases/tag/v2.14.1). +- Update Docker Scan to [v0.23.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.23.0). +- Update containerd (`containerd.io` package) to [v1.6.13](https://github.com/containerd/containerd/releases/tag/v1.6.13), + to include a fix for [CVE-2022-23471](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23471). +- Update Go runtime to [1.18.9](https://go.dev/doc/devel/release#go1.18.minor), to include fixes for - [CVE-2022-41716](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41716){:target="_blank" rel="noopener"}, - [CVE-2022-41717](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41717){:target="_blank" rel="noopener"}, and - [CVE-2022-41720](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41720){:target="_blank" rel="noopener"}. + [CVE-2022-41716](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41716), + [CVE-2022-41717](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41717), and + [CVE-2022-41720](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41720). ### Bug fixes and enhancements - Improve error message when attempting to pull an unsupported image format or OCI artifact - [moby/moby#44413](https://github.com/moby/moby/pull/44413){:target="_blank" rel="noopener"}, - [moby/moby#44569](https://github.com/moby/moby/pull/44569){:target="_blank" rel="noopener"}. -- Fix an issue where the host's ephemeral port-range was ignored when selecting random ports for containers [moby/moby#44476](https://github.com/moby/moby/pull/44476){:target="_blank" rel="noopener"}. -- Fix `ssh: parse error in message type 27` errors during `docker build` on hosts using OpenSSH 8.9 or above [moby/moby#3862](https://github.com/moby/moby/pull/3862){:target="_blank" rel="noopener"}. -- seccomp: block socket calls to `AF_VSOCK` in default profile [moby/moby#44564](https://github.com/moby/moby/pull/44564){:target="_blank" rel="noopener"}. + [moby/moby#44413](https://github.com/moby/moby/pull/44413), + [moby/moby#44569](https://github.com/moby/moby/pull/44569). +- Fix an issue where the host's ephemeral port-range was ignored when selecting random ports for containers [moby/moby#44476](https://github.com/moby/moby/pull/44476). +- Fix `ssh: parse error in message type 27` errors during `docker build` on hosts using OpenSSH 8.9 or above [moby/moby#3862](https://github.com/moby/moby/pull/3862). +- seccomp: block socket calls to `AF_VSOCK` in default profile [moby/moby#44564](https://github.com/moby/moby/pull/44564). ## 20.10.21 -{% include release-date.html date="2022-10-25" %} +{{< release-date date="2022-10-25" >}} This release of Docker Engine contains updated versions of Docker Compose, Docker Scan, containerd, added packages for Ubuntu 22.10, and some minor bug @@ -108,25 +109,25 @@ fixes and enhancements. ### New - Provide packages for Ubuntu 22.10 (Kinetic Kudu). -- Add support for `allow-nondistributable-artifacts` towards Docker Hub [moby/moby#44313](https://github.com/moby/moby/pull/44313){:target="_blank" rel="noopener"}. +- Add support for `allow-nondistributable-artifacts` towards Docker Hub [moby/moby#44313](https://github.com/moby/moby/pull/44313). ### Updates -- Update Docker Compose to [v2.12.2](https://github.com/docker/compose/releases/tag/v2.12.2){:target="_blank" rel="noopener"}. -- Update Docker Scan to [v0.21.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.21.0){:target="_blank" rel="noopener"}. -- Update containerd (`containerd.io` package) to [v1.6.9](https://github.com/containerd/containerd/releases/tag/v1.6.9){:target="_blank" rel="noopener"}. -- Update bundled BuildKit version to to fix `output clipped, log limit 1MiB reached` errors [moby/moby#44339](https://github.com/moby/moby/pull/44339){:target="_blank" rel="noopener"}. +- Update Docker Compose to [v2.12.2](https://github.com/docker/compose/releases/tag/v2.12.2). +- Update Docker Scan to [v0.21.0](https://github.com/docker/scan-cli-plugin/releases/tag/v0.21.0). +- Update containerd (`containerd.io` package) to [v1.6.9](https://github.com/containerd/containerd/releases/tag/v1.6.9). +- Update bundled BuildKit version to to fix `output clipped, log limit 1MiB reached` errors [moby/moby#44339](https://github.com/moby/moby/pull/44339). ### Bug fixes and enhancements -- Remove experimental gate for `--platform` in bash completion [docker/cli#3824](https://github.com/docker/cli/pull/3824){:target="_blank" rel="noopener"}. -- Fix an `Invalid standard handle identifier` panic when registering the Docker Engine as a service from a legacy CLI on Windows [moby/moby#44326](https://github.com/moby/moby/pull/44326){:target="_blank" rel="noopener"}. -- Fix running Git commands in Cygwin on Windows [moby/moby#44332](https://github.com/moby/moby/pull/44332){:target="_blank" rel="noopener"}. +- Remove experimental gate for `--platform` in bash completion [docker/cli#3824](https://github.com/docker/cli/pull/3824). +- Fix an `Invalid standard handle identifier` panic when registering the Docker Engine as a service from a legacy CLI on Windows [moby/moby#44326](https://github.com/moby/moby/pull/44326). +- Fix running Git commands in Cygwin on Windows [moby/moby#44332](https://github.com/moby/moby/pull/44332). ## 20.10.20 -{% include release-date.html date="2022-10-18" %} +{{< release-date date="2022-10-18" >}} This release of Docker Engine contains partial mitigations for a Git vulnerability -([CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253){:target="_blank" rel="noopener"}), +([CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253)), and has updated handling of `image:tag@digest` image references. The Git vulnerability allows a maliciously crafted Git repository, when used as a @@ -139,11 +140,11 @@ are partial and only protect users who build a Git URL context (e.g. `git+protoc As the vulnerability could still be exploited by manually run Git commands that interact with and check out submodules, users should immediately upgrade to a patched version of Git to protect against this vulnerability. Further details are available from the GitHub -blog (["Git security vulnerabilities announced"](https://github.blog/2022-10-18-git-security-vulnerabilities-announced/){:target="_blank" rel="noopener"}). +blog (["Git security vulnerabilities announced"](https://github.blog/2022-10-18-git-security-vulnerabilities-announced/)). ### Updates -- Update Docker Compose to [v2.12.0](https://github.com/docker/compose/releases/tag/v2.12.0){:target="_blank" rel="noopener"}. +- Update Docker Compose to [v2.12.0](https://github.com/docker/compose/releases/tag/v2.12.0). - Updated handling of `image:tag@digest` references. When pulling an image using the `image:tag@digest` ("pull by digest"), image resolution happens through the content-addressable digest and the `image` and `tag` are not used. While @@ -156,35 +157,35 @@ blog (["Git security vulnerabilities announced"](https://github.blog/2022-10-18- ### Bug fixes and enhancements -- Added a mitigation for [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253){:target="_blank" rel="noopener"}, +- Added a mitigation for [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253), when using the classic Builder with a Git URL as the build context. -- Added a mitigation to the classic Builder and updated BuildKit to [v0.8.3-31-gc0149372](https://github.com/moby/buildkit/commit/c014937225cba29cfb1d5161fd134316c0e9bdaa){:target="_blank" rel="noopener"}, - for [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253){:target="_blank" rel="noopener"}. +- Added a mitigation to the classic Builder and updated BuildKit to [v0.8.3-31-gc0149372](https://github.com/moby/buildkit/commit/c014937225cba29cfb1d5161fd134316c0e9bdaa), + for [CVE-2022-39253](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253). ## 20.10.19 -{% include release-date.html date="2022-10-14" %} +{{< release-date date="2022-10-14" >}} This release of Docker Engine comes with some bug-fixes, and an updated version of Docker Compose. ### Updates -- Update Docker Compose to [v2.11.2](https://github.com/docker/compose/releases/tag/v2.11.2){:target="_blank" rel="noopener"}. -- Update Go runtime to [1.18.7](https://go.dev/doc/devel/release#go1.18.minor){:target="_blank" rel="noopener"}, - which contains fixes for [CVE-2022-2879](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2879){:target="_blank" rel="noopener"}, - [CVE-2022-2880](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2880){:target="_blank" rel="noopener"}, - and [CVE-2022-41715](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41715){:target="_blank" rel="noopener"}. +- Update Docker Compose to [v2.11.2](https://github.com/docker/compose/releases/tag/v2.11.2). +- Update Go runtime to [1.18.7](https://go.dev/doc/devel/release#go1.18.minor), + which contains fixes for [CVE-2022-2879](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2879), + [CVE-2022-2880](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2880), + and [CVE-2022-41715](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41715). ### Bug fixes and enhancements - Fix an issue that could result in a panic during `docker builder prune` or - `docker system prune` [moby/moby#44122](https://github.com/moby/moby/pull/44122){:target="_blank" rel="noopener"}. + `docker system prune` [moby/moby#44122](https://github.com/moby/moby/pull/44122). - Fix a bug where using `docker volume prune` would remove volumes that were still in use if the daemon was running with "live restore" and was restarted - [moby/moby#44238](https://github.com/moby/moby/pull/44238){:target="_blank" rel="noopener"}. + [moby/moby#44238](https://github.com/moby/moby/pull/44238). ## 20.10.18 -{% include release-date.html date="2022-09-09" %} +{{< release-date date="2022-09-09" >}} This release of Docker Engine comes with a fix for a low-severity security issue, some minor bug fixes, and updated versions of Docker Compose, Docker Buildx, @@ -192,82 +193,82 @@ some minor bug fixes, and updated versions of Docker Compose, Docker Buildx, ### Updates -- Update Docker Buildx to [v0.9.1](https://github.com/docker/buildx/releases/tag/v0.9.1){:target="_blank" rel="noopener"}. -- Update Docker Compose to [v2.10.2](https://github.com/docker/compose/releases/tag/v2.10.2){:target="_blank" rel="noopener"}. -- Update containerd (`containerd.io` package) to [v1.6.8](https://github.com/containerd/containerd/releases/tag/v1.6.8){:target="_blank" rel="noopener"}. -- Update runc version to [v1.1.4](https://github.com/opencontainers/runc/releases/tag/v1.1.4){:target="_blank" rel="noopener"}. -- Update Go runtime to [1.18.6](https://go.dev/doc/devel/release#go1.18.minor){:target="_blank" rel="noopener"}, - which contains fixes for [CVE-2022-27664](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27664){:target="_blank" rel="noopener"} and - [CVE-2022-32190](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32190){:target="_blank" rel="noopener"}. +- Update Docker Buildx to [v0.9.1](https://github.com/docker/buildx/releases/tag/v0.9.1). +- Update Docker Compose to [v2.10.2](https://github.com/docker/compose/releases/tag/v2.10.2). +- Update containerd (`containerd.io` package) to [v1.6.8](https://github.com/containerd/containerd/releases/tag/v1.6.8). +- Update runc version to [v1.1.4](https://github.com/opencontainers/runc/releases/tag/v1.1.4). +- Update Go runtime to [1.18.6](https://go.dev/doc/devel/release#go1.18.minor), + which contains fixes for [CVE-2022-27664](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27664) and + [CVE-2022-32190](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32190). ### Bug fixes and enhancements -- Add Bash completion for Docker Compose [docker/cli#3752](https://github.com/docker/cli/pull/3752){:target="_blank" rel="noopener"}. +- Add Bash completion for Docker Compose [docker/cli#3752](https://github.com/docker/cli/pull/3752). - Fix an issue where file-capabilities were not preserved during build - [moby/moby#43876](https://github.com/moby/moby/pull/43876){:target="_blank" rel="noopener"}. + [moby/moby#43876](https://github.com/moby/moby/pull/43876). - Fix an issue that could result in a panic caused by a concurrent map read and - map write [moby/moby#44067](https://github.com/moby/moby/pull/44067){:target="_blank" rel="noopener"}. + map write [moby/moby#44067](https://github.com/moby/moby/pull/44067). - Fix a security vulnerability relating to supplementary group permissions, which could allow a container process to bypass primary group restrictions within the - container [CVE-2022-36109](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36109){:target="_blank" rel="noopener"}, - [GHSA-rc4r-wh2q-q6c4](https://github.com/moby/moby/security/advisories/GHSA-rc4r-wh2q-q6c4){:target="_blank" rel="noopener"}. -- seccomp: add support for Landlock syscalls in default policy [moby/moby#43991](https://github.com/moby/moby/pull/43991){:target="_blank" rel="noopener"}. -- seccomp: update default policy to support new syscalls introduced in kernel 5.12 - 5.16 [moby/moby#43991](https://github.com/moby/moby/pull/43991){:target="_blank" rel="noopener"}. + container [CVE-2022-36109](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36109), + [GHSA-rc4r-wh2q-q6c4](https://github.com/moby/moby/security/advisories/GHSA-rc4r-wh2q-q6c4). +- seccomp: add support for Landlock syscalls in default policy [moby/moby#43991](https://github.com/moby/moby/pull/43991). +- seccomp: update default policy to support new syscalls introduced in kernel 5.12 - 5.16 [moby/moby#43991](https://github.com/moby/moby/pull/43991). - Fix an issue where cache lookup for image manifests would fail, resulting - in a redundant round-trip to the image registry [moby/moby#44109](https://github.com/moby/moby/pull/44109){:target="_blank" rel="noopener"}. + in a redundant round-trip to the image registry [moby/moby#44109](https://github.com/moby/moby/pull/44109). - Fix an issue where `exec` processes and healthchecks were not terminated - when they timed out [moby/moby#44018](https://github.com/moby/moby/pull/44018){:target="_blank" rel="noopener"}. + when they timed out [moby/moby#44018](https://github.com/moby/moby/pull/44018). ## 20.10.17 -{% include release-date.html date="2022-06-06" %} +{{< release-date date="2022-06-06" >}} This release of Docker Engine comes with updated versions of Docker Compose and the `containerd`, and `runc` components, as well as some minor bug fixes. ### Updates -- Update Docker Compose to [v2.6.0](https://github.com/docker/compose/releases/tag/v2.6.0){:target="_blank" rel="noopener"}. +- Update Docker Compose to [v2.6.0](https://github.com/docker/compose/releases/tag/v2.6.0). - Update containerd (`containerd.io` package) to [v1.6.6](https://github.com/containerd/containerd/releases/tag/v1.6.6), - which contains a fix for [CVE-2022-31030](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31030){:target="_blank" rel="noopener"} + which contains a fix for [CVE-2022-31030](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31030) - Update runc version to [v1.1.2](https://github.com/opencontainers/runc/releases/tag/v1.1.2), which contains a fix for - [CVE-2022-29162](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29162){:target="_blank" rel="noopener"}. -- Update Go runtime to [1.17.11](https://go.dev/doc/devel/release#go1.17.minor){:target="_blank" rel="noopener"}, - which contains fixes for [CVE-2022-30634](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30634){:target="_blank" rel="noopener"}, - [CVE-2022-30629](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30629){:target="_blank" rel="noopener"}, - [CVE-2022-30580](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30580){:target="_blank" rel="noopener"} and - [CVE-2022-29804](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29804){:target="_blank" rel="noopener"} + [CVE-2022-29162](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29162). +- Update Go runtime to [1.17.11](https://go.dev/doc/devel/release#go1.17.minor), + which contains fixes for [CVE-2022-30634](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30634), + [CVE-2022-30629](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30629), + [CVE-2022-30580](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30580) and + [CVE-2022-29804](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29804) ### Bug fixes and enhancements -- Remove asterisk from docker commands in zsh completion script [docker/cli#3648](https://github.com/docker/cli/pull/3648){:target="_blank" rel="noopener"}. -- Fix Windows port conflict with published ports in host mode for overlay [moby/moby#43644](https://github.com/moby/moby/pull/43644){:target="_blank" rel="noopener"}. -- Ensure performance tuning is always applied to libnetwork sandboxes [moby/moby#43683](https://github.com/moby/moby/pull/43683){:target="_blank" rel="noopener"}. +- Remove asterisk from docker commands in zsh completion script [docker/cli#3648](https://github.com/docker/cli/pull/3648). +- Fix Windows port conflict with published ports in host mode for overlay [moby/moby#43644](https://github.com/moby/moby/pull/43644). +- Ensure performance tuning is always applied to libnetwork sandboxes [moby/moby#43683](https://github.com/moby/moby/pull/43683). ## 20.10.16 -{% include release-date.html date="2022-05-12" %} +{{< release-date date="2022-05-12" >}} This release of Docker Engine fixes a regression in the Docker CLI builds for macOS, fixes an issue with `docker stats` when using containerd 1.5 and up, -and updates the Go runtime to include a fix for [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}. +and updates the Go runtime to include a fix for [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526). ### Updates - Update golang.org/x/sys dependency which contains a fix for - [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}. -- Updated the `golang.org/x/sys` build-time dependency which contains a fix for [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}. -- Updated Go runtime to [1.17.10](https://go.dev/doc/devel/release#go1.17.minor){:target="_blank" rel="noopener"}, - which contains a fix for [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526){:target="_blank" rel="noopener"}. + [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526). +- Updated the `golang.org/x/sys` build-time dependency which contains a fix for [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526). +- Updated Go runtime to [1.17.10](https://go.dev/doc/devel/release#go1.17.minor), + which contains a fix for [CVE-2022-29526](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29526). ### Bug fixes and enhancements - Fixed a regression in binaries for macOS introduced in [20.10.15](#201015), which - resulted in a panic [docker/cli#43426](https://github.com/docker/cli/pull/3592){:target="_blank" rel="noopener"}. + resulted in a panic [docker/cli#43426](https://github.com/docker/cli/pull/3592). - Fixed an issue where `docker stats` was showing empty stats when running with - containerd 1.5.0 or up [moby/moby#43567](https://github.com/moby/moby/pull/43567){:target="_blank" rel="noopener"}. + containerd 1.5.0 or up [moby/moby#43567](https://github.com/moby/moby/pull/43567). - Used "weak" dependencies for the `docker scan` CLI plugin, to prevent a "conflicting requests" error when users performed an off-line installation from - downloaded RPM packages [docker/docker-ce-packaging#659](https://github.com/docker/docker-ce-packaging/pull/659){:target="_blank" rel="noopener"}. + downloaded RPM packages [docker/docker-ce-packaging#659](https://github.com/docker/docker-ce-packaging/pull/659). ## 20.10.15 -{% include release-date.html date="2022-05-05" %} +{{< release-date date="2022-05-05" >}} This release of Docker Engine comes with updated versions of the `compose`, `buildx`, `containerd`, and `runc` components, as well as some minor bug fixes. @@ -286,11 +287,11 @@ This release of Docker Engine comes with updated versions of the `compose`, - Add packages for CentOS 9 stream and Fedora 36. ### Known issues -- We've identified an issue with the [macOS CLI binaries](https://download.docker.com/mac/static/stable/){:target="_blank" rel="noopener" class="_"} +- We've identified an issue with the [macOS CLI binaries](https://download.docker.com/mac/static/stable/) in the 20.10.15 release. This issue has been resolved in the [20.10.16](#201016) release. ## 20.10.14 -{% include release-date.html date="2022-03-23" %} +{{< release-date date="2022-03-23" >}} This release of Docker Engine updates the default inheritable capabilities for containers to address [CVE-2022-24769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24769), @@ -304,7 +305,7 @@ issue. - Update `docker buildx` to [v0.8.1](https://github.com/docker/buildx/releases/tag/v0.8.1). ## 20.10.13 -{% include release-date.html date="2022-03-10" %} +{{< release-date date="2022-03-10" >}} This release of Docker Engine contains some bug-fixes and packaging changes, updates to the `docker scan` and `docker buildx` commands, an updated version of @@ -407,7 +408,7 @@ to learn how to use the `docker scan` command to check if images are vulnerable. > > Refer to the [HTTP/HTTPS proxy section](../../config/daemon/systemd.md#httphttps-proxy) > to learn how to configure the Docker Daemon to use a proxy server. -{: .important } +{ .important } ### Distribution @@ -437,7 +438,7 @@ to learn how to use the `docker scan` command to check if images are vulnerable. > > Refer to the [HTTP/HTTPS proxy section](../../config/daemon/systemd.md#httphttps-proxy) > to learn how to configure the Docker Daemon to use a proxy server. -{: .important } +{ .important } ### Builder @@ -478,7 +479,7 @@ well as updated versions of the containerd.io package. > > Refer to the [HTTP/HTTPS proxy section](../../config/daemon/systemd.md#httphttps-proxy) > to learn how to configure the Docker Daemon to use a proxy server. -{: .important } +{ .important } ### Client @@ -523,7 +524,7 @@ well as updated versions of the containerd.io package. > > Refer to the [HTTP/HTTPS proxy section](../../config/daemon/systemd.md#httphttps-proxy) > to learn how to configure the Docker Daemon to use a proxy server. -{: .important } +{ .important } ### Deprecation @@ -961,4 +962,4 @@ For an overview of all deprecated features, refer to the [Deprecated Engine Feat - Add support for sending down service Running and Desired task counts [moby/moby#39231](https://github.com/moby/moby/pull/39231) - service: support `--mount type=bind,bind-nonrecursive` [moby/moby#38788](https://github.com/moby/moby/pull/38788) - Support ulimits on Swarm services. [moby/moby#41284](https://github.com/moby/moby/pull/41284) [docker/cli#2712](https://github.com/docker/cli/pull/2712) -- Fixed an issue where service logs could leak goroutines on the worker [moby/moby#40426](https://github.com/moby/moby/pull/40426) +- Fixed an issue where service logs could leak goroutines on the worker [moby/moby#40426](https://github.com/moby/moby/pull/40426) \ No newline at end of file diff --git a/content/engine/release-notes/23.0.md b/content/engine/release-notes/23.0.md index 10507a85e4..b8d9c339e3 100644 --- a/content/engine/release-notes/23.0.md +++ b/content/engine/release-notes/23.0.md @@ -1,6 +1,7 @@ --- title: Docker Engine 23.0 release notes -description: Learn about the new features, bug fixes, and breaking changes for Docker Engine +description: Learn about the new features, bug fixes, and breaking changes for Docker + Engine keywords: docker, docker engine, ce, whats new, release notes toc_min: 1 toc_max: 2 @@ -38,7 +39,7 @@ Work continues towards Go module compatibility in a future release. ## 23.0.6 -{% include release-date.html date="2023-05-08" %} +{{< release-date date="2023-05-08" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -59,7 +60,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 23.0.5 -{% include release-date.html date="2023-04-26" %} +{{< release-date date="2023-04-26" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -81,7 +82,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 23.0.4 -{% include release-date.html date="2023-04-17" %} +{{< release-date date="2023-04-17" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -108,7 +109,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 23.0.3 -{% include release-date.html date="2023-04-04" %} +{{< release-date date="2023-04-04" >}} > **Note** > @@ -139,7 +140,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 23.0.2 -{% include release-date.html date="2023-03-28" %} +{{< release-date date="2023-03-28" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -175,7 +176,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 23.0.1 -{% include release-date.html date="2023-02-09" %} +{{< release-date date="2023-02-09" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -202,7 +203,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 23.0.0 -{% include release-date.html date="2023-02-01" %} +{{< release-date date="2023-02-01" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -232,7 +233,7 @@ For a full list of pull requests and changes in this release, refer to the relev - Add support for SwarmKit jobs in `docker stack deploy`. [docker/cli#2907](https://github.com/docker/cli/pull/2907) - Add the `docker stack config` command to output the merged and interpolated config files as utilized by `stack deploy`. [docker/cli#3544](https://github.com/docker/cli/pull/3544) - Add a new `docker context show` command that prints the name of the current context. [docker/cli#3567](https://github.com/docker/cli/pull/3567) -- Add the `--format=json` shorthand variant of {% raw %}`--format="{{ json . }}"`{% endraw %} to all commands supporting the `--format` flag. [docker/cli#2936](https://github.com/docker/cli/pull/2936) +- Add the `--format=json` shorthand variant of `--format="{{ json . }}"` to all commands supporting the `--format` flag. [docker/cli#2936](https://github.com/docker/cli/pull/2936) - Add a `--quiet` option to `docker create` and `docker run` commands to suppress output when pulling an image. [docker/cli#3377](https://github.com/docker/cli/pull/3377) - Add a `--force` option to `docker network rm` subcommand. Causes CLI to return a 0 exit code even if the network doesn't exist. Has no effect on the server-side procedure for removing a network. [docker/cli#3547](https://github.com/docker/cli/pull/3547) - Add a `--signal` option to `docker stop` and `docker restart`. [docker/cli#3614](https://github.com/docker/cli/pull/3614) @@ -497,4 +498,4 @@ The 23.0 branch brings support for alternate containerd shims, such as `io.conta When using the Kata Containers runtime, exiting an `exec` session stops the running container, and hangs the connected CLI if a TTY was opened. There is no mitigation at this time beyond avoiding execing into containers running on the Kata runtime. -The root cause of this issue is a long-standing bug in Moby. This will be resolved in a future release. Be advised that support for alternate OCI runtimes is a new feature and that similar issues may be discovered as more users start exercising this functionality. +The root cause of this issue is a long-standing bug in Moby. This will be resolved in a future release. Be advised that support for alternate OCI runtimes is a new feature and that similar issues may be discovered as more users start exercising this functionality. \ No newline at end of file diff --git a/content/engine/release-notes/24.0.md b/content/engine/release-notes/24.0.md index 165f9546b4..55990c27ea 100644 --- a/content/engine/release-notes/24.0.md +++ b/content/engine/release-notes/24.0.md @@ -1,15 +1,16 @@ --- title: Docker Engine 24.0 release notes -description: Learn about the new features, bug fixes, and breaking changes for Docker Engine +description: Learn about the new features, bug fixes, and breaking changes for Docker + Engine keywords: docker, docker engine, ce, whats new, release notes toc_min: 1 toc_max: 2 skip_read_time: true -redirect_from: - - /engine/release-notes/ - - /engine/release-notes/latest/ - - /release-notes/docker-ce/ - - /release-notes/docker-engine/ +aliases: +- /engine/release-notes/ +- /engine/release-notes/latest/ +- /release-notes/docker-ce/ +- /release-notes/docker-engine/ --- This page describes the latest changes, additions, known issues, and fixes for Docker Engine version 24.0. @@ -21,7 +22,7 @@ For more information about: ## 24.0.5 -{% include release-date.html date="2023-07-24" %} +{{< release-date date="2023-07-24" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -51,7 +52,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 24.0.4 -{% include release-date.html date="2023-07-07" %} +{{< release-date date="2023-07-07" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -65,7 +66,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 24.0.3 -{% include release-date.html date="2023-07-06" %} +{{< release-date date="2023-07-06" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -110,7 +111,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 24.0.2 -{% include release-date.html date="2023-05-26" %} +{{< release-date date="2023-05-26" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -134,7 +135,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 24.0.1 -{% include release-date.html date="2023-05-19" %} +{{< release-date date="2023-05-19" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -161,7 +162,7 @@ For a full list of pull requests and changes in this release, refer to the relev ## 24.0.0 -{% include release-date.html date="2023-05-16" %} +{{< release-date date="2023-05-16" >}} For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones: @@ -211,4 +212,4 @@ For a full list of pull requests and changes in this release, refer to the relev * Update Go to `1.20.4`. [docker/cli#4253](https://github.com/docker/cli/pull/4253), [moby/moby#45456](https://github.com/moby/moby/pull/45456), [docker/docker-ce-packaging#888](https://github.com/docker/docker-ce-packaging/pull/888) * Update `containerd` to [`v1.7.1`](https://github.com/containerd/containerd/releases/tag/v1.7.1). [moby/moby#45537](https://github.com/moby/moby/pull/45537) -* Update `buildkit` to [`v0.11.6`](https://github.com/moby/buildkit/releases/v0.11.6). [moby/moby#45367](https://github.com/moby/moby/pull/45367) +* Update `buildkit` to [`v0.11.6`](https://github.com/moby/buildkit/releases/v0.11.6). [moby/moby#45367](https://github.com/moby/moby/pull/45367) \ No newline at end of file diff --git a/content/engine/release-notes/prior-releases.md b/content/engine/release-notes/prior-releases.md index 3aac1111f6..550b39fb2b 100644 --- a/content/engine/release-notes/prior-releases.md +++ b/content/engine/release-notes/prior-releases.md @@ -3,13 +3,13 @@ title: Docker Engine release notes description: Release notes for Docker CE keywords: release notes, community toc_max: 2 -redirect_from: - - /cs-engine/1.12/release-notes/ - - /cs-engine/1.12/release-notes/release-notes/ - - /cs-engine/1.12/release-notes/prior-release-notes/ - - /cs-engine/1.13/release-notes/ - - /ee/engine/release-notes/ - - /ee/docker-ee/release-notes/ +aliases: +- /cs-engine/1.12/release-notes/ +- /cs-engine/1.12/release-notes/release-notes/ +- /cs-engine/1.12/release-notes/prior-release-notes/ +- /cs-engine/1.13/release-notes/ +- /ee/engine/release-notes/ +- /ee/docker-ee/release-notes/ --- ## 1.13.1 (2017-02-08) @@ -814,7 +814,7 @@ installing docker, make sure to update them accordingly. + Enable syslog logger to have access to env and labels [#21724](https://github.com/docker/docker/pull/21724) + An additional syslog-format option `rfc5424micro` to allow microsecond resolution in syslog timestamp [#21844](https://github.com/docker/docker/pull/21844) * Inherit the daemon log options when creating containers [#21153](https://github.com/docker/docker/pull/21153) -* Remove `docker/` prefix from log messages tag and replace it with `{% raw %}{{.DaemonName}}{% endraw %}` so that users have the option of changing the prefix [#22384](https://github.com/docker/docker/pull/22384) +* Remove `docker/` prefix from log messages tag and replace it with `{{.DaemonName}}` so that users have the option of changing the prefix [#22384](https://github.com/docker/docker/pull/22384) ### Networking @@ -830,7 +830,7 @@ installing docker, make sure to update them accordingly. * Add container's short-id as default network alias [#21901](https://github.com/docker/docker/pull/21901) * `run` options `--dns` and `--net=host` are no longer mutually exclusive [#22408](https://github.com/docker/docker/pull/22408) - Fix DNS issue when renaming containers with generated names [#22716](https://github.com/docker/docker/pull/22716) -- Allow both `{% raw %}network inspect -f {{.Id}}` and `network inspect -f {{.ID}}{% endraw %}` to address inconsistency with inspect output [#23226](https://github.com/docker/docker/pull/23226) +- Allow both `network inspect -f {{.Id}}` and `network inspect -f {{.ID}}` to address inconsistency with inspect output [#23226](https://github.com/docker/docker/pull/23226) ### Plugins (experimental) @@ -1374,7 +1374,7 @@ Engine 1.10 migrator can be found on Docker Hub: https://hub.docker.com/r/docker - Fix `docker login` on windows (#17738) - Fix bug with `docker inspect` output when not connected to daemon (#17715) -- Fix `{% raw %}docker inspect -f {{.HostConfig.Dns}} somecontainer{% endraw %}` (#17680) +- Fix `docker inspect -f {{.HostConfig.Dns}} somecontainer` (#17680) ### Builder @@ -3342,4 +3342,4 @@ Initial public release - Add Vagrant support with Vagrantfile - Add unit tests - Add repository/tags to ease image management -- Improve the layer implementation +- Improve the layer implementation \ No newline at end of file diff --git a/content/engine/sbom/_index.md b/content/engine/sbom/_index.md index c41a65298c..3db56852e7 100644 --- a/content/engine/sbom/_index.md +++ b/content/engine/sbom/_index.md @@ -11,7 +11,7 @@ A Software Bill Of Materials (SBOM) is analogous to a packing list for a shipmen > **Warning** > > The `docker sbom` command is currently experimental. This may change or be removed from future releases. -{: .warning } +{ .warning } The experimental `docker sbom` command allows you to generate the SBOM of a container image. Today, it does this by scanning the layers of the image using the [Syft project](https://github.com/anchore/syft) but in future it may read the SBOM from the image itself or elsewhere. @@ -40,7 +40,7 @@ The output includes both system packages and software libraries used by applicat ## Output formatting and saving outputs -You can view the SBOM output in standard formats like [SPDX](https://spdx.dev){: target="_blank" rel="noopener" class="_"} and [CycloneDX](https://cyclonedx.org){: target="_blank" rel="noopener" class="_"} along with the Syft and GitHub formats using the `--format` option. +You can view the SBOM output in standard formats like [SPDX](https://spdx.dev) and [CycloneDX](https://cyclonedx.org) along with the Syft and GitHub formats using the `--format` option. ```console $ docker sbom --format spdx-json alpine:3.15 @@ -94,4 +94,4 @@ $ cat sbom.json ## Feedback Thanks for trying the Docker SBOM CLI plugin. We’d love to hear from you. You can provide feedback and report any bugs through the Issues tracker in the -[docker/sbom-cli-plugin](https://github.com/docker/sbom-cli-plugin){: target="_blank" rel="noopener" class="_"} GitHub repository. +[docker/sbom-cli-plugin](https://github.com/docker/sbom-cli-plugin) GitHub repository. \ No newline at end of file diff --git a/content/engine/security/_index.md b/content/engine/security/_index.md index 5ecb72bba8..186c68c96b 100644 --- a/content/engine/security/_index.md +++ b/content/engine/security/_index.md @@ -1,12 +1,12 @@ --- description: Review of the Docker Daemon attack surface keywords: Docker, Docker documentation, security -redirect_from: +title: Docker security +aliases: - /articles/security/ - /engine/articles/security/ - /engine/security/security/ - /security/security/ -title: Docker security --- There are four major areas to consider when reviewing Docker security: @@ -281,4 +281,4 @@ pull requests, or comments on the Docker community forums. * [Seccomp security profiles for Docker](seccomp.md) * [AppArmor security profiles for Docker](apparmor.md) * [On the Security of Containers (2014)](https://medium.com/@ewindisch/on-the-security-of-containers-2c60ffe25a9e) -* [Docker swarm mode overlay network security model](../../network/drivers/overlay.md) +* [Docker swarm mode overlay network security model](../../network/drivers/overlay.md) \ No newline at end of file diff --git a/content/engine/security/antivirus.md b/content/engine/security/antivirus.md index 326103fb78..37bf53282b 100644 --- a/content/engine/security/antivirus.md +++ b/content/engine/security/antivirus.md @@ -13,4 +13,4 @@ antivirus's exclusion list. However, this comes with the trade-off that viruses or malware in Docker images, writable layers of containers, or volumes are not detected. If you do choose to exclude Docker's data directory from background virus scanning, you may want to schedule a recurring task that stops Docker, -scans the data directory, and restarts Docker. +scans the data directory, and restarts Docker. \ No newline at end of file diff --git a/content/engine/security/apparmor.md b/content/engine/security/apparmor.md index 496954bee5..218c9f16e5 100644 --- a/content/engine/security/apparmor.md +++ b/content/engine/security/apparmor.md @@ -278,4 +278,4 @@ Advanced users and package managers can find a profile for `/usr/bin/docker` in the Docker Engine source repository. The `docker-default` profile for containers lives in -[profiles/apparmor](https://github.com/moby/moby/tree/master/profiles/apparmor). +[profiles/apparmor](https://github.com/moby/moby/tree/master/profiles/apparmor). \ No newline at end of file diff --git a/content/engine/security/certificates.md b/content/engine/security/certificates.md index eed6aa5be8..34c2f75e97 100644 --- a/content/engine/security/certificates.md +++ b/content/engine/security/certificates.md @@ -1,10 +1,11 @@ --- description: How to set up and use certificates with a registry to verify access -keywords: Usage, registry, repository, client, root, certificate, docker, apache, ssl, tls, documentation, examples, articles, tutorials -redirect_from: +keywords: Usage, registry, repository, client, root, certificate, docker, apache, + ssl, tls, documentation, examples, articles, tutorials +title: Verify repository client with certificates +aliases: - /articles/certificates/ - /engine/articles/certificates/ -title: Verify repository client with certificates --- In [Running Docker with HTTPS](protect-access.md), you learned that, by default, @@ -95,4 +96,4 @@ If the Docker registry is accessed without a port number, do not add the port to ## Related information * [Use trusted images](trust/index.md) -* [Protect the Docker daemon socket](protect-access.md) +* [Protect the Docker daemon socket](protect-access.md) \ No newline at end of file diff --git a/content/engine/security/https/README.md b/content/engine/security/https/README.md index 650c650a0f..bd7cb5e5b7 100644 --- a/content/engine/security/https/README.md +++ b/content/engine/security/https/README.md @@ -26,4 +26,4 @@ Start another terminal: root@boot2docker:/# cd docker/docs/articles/https root@boot2docker:/# make client -The last connects first with `--tls` and then with `--tlsverify`, both should succeed. +The last connects first with `--tls` and then with `--tlsverify`, both should succeed. \ No newline at end of file diff --git a/content/engine/security/protect-access.md b/content/engine/security/protect-access.md index 00a1d5794c..256fa6f19c 100644 --- a/content/engine/security/protect-access.md +++ b/content/engine/security/protect-access.md @@ -1,11 +1,11 @@ --- description: How to setup and run Docker with SSH or HTTPS keywords: docker, docs, article, example, ssh, https, daemon, tls, ca, certificate -redirect_from: +title: Protect the Docker daemon socket +aliases: - /articles/https/ - /engine/articles/https/ - /engine/security/https/ -title: Protect the Docker daemon socket --- By default, Docker runs through a non-networked UNIX socket. It can also @@ -89,7 +89,7 @@ it only connects to servers with a certificate signed by that CA. > > Using TLS and managing a CA is an advanced topic. Please familiarize yourself > with OpenSSL, x509, and TLS before using it in production. -{:.important} +{ .important } ### Create a CA, server and client keys with OpenSSL @@ -271,7 +271,7 @@ $ docker --tlsverify \ > That means anyone with the keys can give any instructions to your Docker > daemon, giving them root access to the machine hosting the daemon. Guard > these keys as you would a root password! -{:.warning} +{ .warning } ### Secure by default @@ -335,4 +335,4 @@ $ curl https://$HOST:2376/images/json \ ## Related information * [Using certificates for repository client verification](certificates.md) -* [Use trusted images](trust/index.md) +* [Use trusted images](trust/index.md) \ No newline at end of file diff --git a/content/engine/security/rootless.md b/content/engine/security/rootless.md index 3dd7cd52e1..d65bcbe517 100644 --- a/content/engine/security/rootless.md +++ b/content/engine/security/rootless.md @@ -161,7 +161,7 @@ $ sudo apt-get install -y docker-ce-rootless-extras {{< tab name="Without packages" >}} If you do not have permission to run package managers like `apt-get` and `dnf`, -consider using the installation script available at [https://get.docker.com/rootless](https://get.docker.com/rootless){: target="_blank" rel="noopener" class="_" }. +consider using the installation script available at [https://get.docker.com/rootless](https://get.docker.com/rootless). Since static packages are not available for `s390x`, hence it is not supported for `s390x`. ```console @@ -601,4 +601,4 @@ See [RootlessKit documentation](https://github.com/rootless-containers/rootlessk The `dockerd-rootless.sh` script executes `dockerd` in its own user, mount, and network namespaces. For debugging, you can enter the namespaces by running -`nsenter -U --preserve-credentials -n -m -t $(cat $XDG_RUNTIME_DIR/docker.pid)`. +`nsenter -U --preserve-credentials -n -m -t $(cat $XDG_RUNTIME_DIR/docker.pid)`. \ No newline at end of file diff --git a/content/engine/security/seccomp.md b/content/engine/security/seccomp.md index f576140c3f..5be2672d11 100644 --- a/content/engine/security/seccomp.md +++ b/content/engine/security/seccomp.md @@ -117,4 +117,4 @@ profile. ```console $ docker run --rm -it --security-opt seccomp=unconfined debian:jessie \ unshare --map-root-user --user sh -c whoami -``` +``` \ No newline at end of file diff --git a/content/engine/security/trust/_index.md b/content/engine/security/trust/_index.md index dd2f33f30c..7a6c563a09 100644 --- a/content/engine/security/trust/_index.md +++ b/content/engine/security/trust/_index.md @@ -2,7 +2,7 @@ description: Enabling content trust in Docker keywords: content, trust, security, docker, documentation title: Content trust in Docker -redirect_from: +aliases: - /engine/security/trust/content_trust/ - /notary/getting_started/ - /notary/advanced_usage/ @@ -99,7 +99,7 @@ The following image depicts the various signing keys and their relationships: > >The root key once lost is not recoverable. If you lose any other key, send an email to [Docker Hub Support](mailto:hub-support@docker.com). This loss also requires manual intervention from every consumer that used a signed tag from this repository prior to the loss. -{:.warning} +{ .warning } You should back up the root key somewhere safe. Given that it is only required to create new repositories, it is a good idea to store it offline in hardware. @@ -110,7 +110,7 @@ read how to [manage keys for DCT](trust_key_mng.md). Within the Docker CLI we can sign and push a container image with the `$ docker trust` command syntax. This is built on top of the Notary feature -set. For more information, see the [Notary GitHub repository](https://github.com/theupdateframework/notary){:target="_blank" rel="noopener" class="_"}. +set. For more information, see the [Notary GitHub repository](https://github.com/theupdateframework/notary). A prerequisite for signing an image is a Docker Registry with a Notary server attached (Such as the Docker Hub ). Instructions for @@ -255,4 +255,4 @@ Status: Downloaded newer image for registry.example.com/user/image@sha256:ee7491 * [Delegations for content trust](trust_delegation.md) * [Automation with content trust](trust_automation.md) * [Manage keys for content trust](trust_key_mng.md) -* [Play in a content trust sandbox](trust_sandbox.md) +* [Play in a content trust sandbox](trust_sandbox.md) \ No newline at end of file diff --git a/content/engine/security/trust/deploying_notary.md b/content/engine/security/trust/deploying_notary.md index 5ed9748cb3..0ebae5aebb 100644 --- a/content/engine/security/trust/deploying_notary.md +++ b/content/engine/security/trust/deploying_notary.md @@ -15,7 +15,7 @@ The easiest way to deploy Notary Server is by using Docker Compose. To follow th docker compose up -d - For more detailed documentation about how to deploy Notary Server, see the [instructions to run a Notary service](https://github.com/theupdateframework/notary/blob/master/docs/running_a_service.md){:target="_blank" rel="noopener" class="_"} as well as [the Notary repository](https://github.com/theupdateframework/notary){:target="_blank" rel="noopener" class="_"} for more information. + For more detailed documentation about how to deploy Notary Server, see the [instructions to run a Notary service](https://github.com/theupdateframework/notary/blob/master/docs/running_a_service.md) as well as [the Notary repository](https://github.com/theupdateframework/notary) for more information. 3. Make sure that your Docker or Notary client trusts Notary Server's certificate before you try to interact with the Notary server. See the instructions for [Docker](../../reference/commandline/cli.md#notary) or @@ -25,4 +25,4 @@ for [Notary](https://github.com/docker/notary#using-notary) depending on which o Check back here for instructions after Notary Server has an official stable release. To get a head start on deploying Notary in production, see -[the Notary repository](https://github.com/theupdateframework/notary). +[the Notary repository](https://github.com/theupdateframework/notary). \ No newline at end of file diff --git a/content/engine/security/trust/trust_automation.md b/content/engine/security/trust/trust_automation.md index 3f59a96047..5e92079436 100644 --- a/content/engine/security/trust/trust_automation.md +++ b/content/engine/security/trust/trust_automation.md @@ -12,7 +12,7 @@ This guide follows the steps as described [here](index.md#signing-images-with-docker-content-trust) so please read that and understand its prerequisites. -When working directly with the Notary client, it uses its [own set of environment variables](https://github.com/theupdateframework/notary/blob/master/docs/reference/client-config.md#environment-variables-optional){:target="_blank" rel="noopener" class="_"}. +When working directly with the Notary client, it uses its [own set of environment variables](https://github.com/theupdateframework/notary/blob/master/docs/reference/client-config.md#environment-variables-optional). ## Add a delegation private key @@ -107,4 +107,4 @@ unable to process Dockerfile: No trust data for notrust * [Delegations for content trust](trust_delegation.md) * [Content trust in Docker](index.md) * [Manage keys for content trust](trust_key_mng.md) -* [Play in a content trust sandbox](trust_sandbox.md) +* [Play in a content trust sandbox](trust_sandbox.md) \ No newline at end of file diff --git a/content/engine/security/trust/trust_delegation.md b/content/engine/security/trust/trust_delegation.md index c8f9adf8e6..3093518c86 100644 --- a/content/engine/security/trust/trust_delegation.md +++ b/content/engine/security/trust/trust_delegation.md @@ -2,7 +2,7 @@ description: Delegations for content trust keywords: trust, security, delegations, keys, repository title: Delegations for content trust -redirect_from: +aliases: - /ee/dtr/user/access-dtr/configure-your-notary-client/ --- @@ -97,7 +97,7 @@ The newly created configuration file contains information about the location of For more detailed information about how to use notary outside of the Docker Content Trust use cases, refer to the Notary CLI documentation -[here](https://github.com/theupdateframework/notary/blob/master/docs/command_reference.md){:target="_blank" rel="noopener" class="_"} +[here](https://github.com/theupdateframework/notary/blob/master/docs/command_reference.md) ## Creating Delegation Keys @@ -369,7 +369,7 @@ $ notary witness registry.example.com/admin/demo targets/releases --publish ``` More information on the `$ notary witness` command can be found -[here](https://github.com/theupdateframework/notary/blob/master/docs/advanced_usage.md#recovering-a-delegation){:target="_blank" rel="noopener" class="_"} +[here](https://github.com/theupdateframework/notary/blob/master/docs/advanced_usage.md#recovering-a-delegation) ### Removing a Contributor's Key from a Delegation @@ -484,4 +484,4 @@ No signatures or cannot access registry.example.com/admin/demo * [Content trust in Docker](index.md) * [Manage keys for content trust](trust_key_mng.md) * [Automation with content trust](trust_automation.md) -* [Play in a content trust sandbox](trust_sandbox.md) +* [Play in a content trust sandbox](trust_sandbox.md) \ No newline at end of file diff --git a/content/engine/security/trust/trust_key_mng.md b/content/engine/security/trust/trust_key_mng.md index 9a06447628..b4d37046f6 100644 --- a/content/engine/security/trust/trust_key_mng.md +++ b/content/engine/security/trust/trust_key_mng.md @@ -31,7 +31,7 @@ workflow. They need to be **Note**: Prior to Docker Engine 1.11, the snapshot key was also generated and stored locally client-side. -Use the Notary CLI to [manage your snapshot key locally again](https://github.com/theupdateframework/notary/blob/master/docs/advanced_usage.md#rotate-keys){:target="_blank" rel="noopener" class="_"} for repositories created with newer versions of Docker. +Use the Notary CLI to [manage your snapshot key locally again](https://github.com/theupdateframework/notary/blob/master/docs/advanced_usage.md#rotate-keys) for repositories created with newer versions of Docker. ## Choose a passphrase @@ -51,7 +51,7 @@ Good practice is to create two encrypted USB keys. > > It is **very important** that you back up your keys to a safe, secure location. The loss of the repository key is recoverable, but the loss of the root key is not. -{:.warning} +{ .warning } The Docker client stores the keys in the `~/.docker/trust/private` directory. Before backing them up, you should `tar` them into an archive: @@ -66,7 +66,7 @@ Docker Content Trust can store and sign with root keys from a Yubikey 4. The Yubikey is prioritized over keys stored in the filesystem. When you initialize a new repository with content trust, Docker Engine looks for a root key locally. If a key is not found and the Yubikey 4 exists, Docker Engine creates a root key in the -Yubikey 4. Consult the [Notary documentation](https://github.com/theupdateframework/notary/blob/master/docs/advanced_usage.md#use-a-yubikey){:target="_blank" rel="noopener" class="_"} +Yubikey 4. Consult the [Notary documentation](https://github.com/theupdateframework/notary/blob/master/docs/advanced_usage.md#use-a-yubikey) for more details. Prior to Docker Engine 1.11, this feature was only in the experimental branch. @@ -78,7 +78,7 @@ Prior to Docker Engine 1.11, this feature was only in the experimental branch. > If a publisher loses keys it means losing the ability to sign images for the repositories in question. If you lose a key, send an email to [Docker Hub Support](mailto:hub-support@docker.com). As a reminder, the loss of a root key is not recoverable. -{:.warning} +{ .warning } This loss also requires **manual intervention** from every consumer that used a signed tag from this repository prior to the loss. @@ -96,4 +96,4 @@ the new key. * [Content trust in Docker](index.md) * [Automation with content trust](trust_automation.md) * [Delegations for content trust](trust_delegation.md) -* [Play in a content trust sandbox](trust_sandbox.md) +* [Play in a content trust sandbox](trust_sandbox.md) \ No newline at end of file diff --git a/content/engine/security/trust/trust_sandbox.md b/content/engine/security/trust/trust_sandbox.md index 96c68c152e..fb4229524e 100644 --- a/content/engine/security/trust/trust_sandbox.md +++ b/content/engine/security/trust/trust_sandbox.md @@ -2,7 +2,7 @@ description: Play in a trust sandbox keywords: trust, security, root, keys, repository, sandbox title: Play in a content trust sandbox -redirect_from: +aliases: - /security/trust/trust_sandbox/ --- @@ -289,4 +289,4 @@ When you are done, and want to clean up all the services you've started and any anonymous volumes that have been created, just run the following command in the directory where you've created your Docker Compose file: - $ docker compose down -v + $ docker compose down -v \ No newline at end of file diff --git a/content/engine/security/userns-remap.md b/content/engine/security/userns-remap.md index 557096ed1c..7be9b20738 100644 --- a/content/engine/security/userns-remap.md +++ b/content/engine/security/userns-remap.md @@ -7,7 +7,7 @@ title: Isolate containers with a user namespace Linux namespaces provide isolation for running processes, limiting their access to system resources without the running process being aware of the limitations. For more information on Linux namespaces, see -[Linux namespaces](https://www.linux.com/news/understanding-and-securing-linux-namespaces){: target="_blank" rel="noopener" class="_" }. +[Linux namespaces](https://www.linux.com/news/understanding-and-securing-linux-namespaces). The best way to prevent privilege-escalation attacks from within a container is to configure your container's applications to run as unprivileged users. For @@ -51,7 +51,7 @@ purpose. > automatically add the new group to the `/etc/subuid` and `/etc/subgid` files. > You are responsible for editing these files and assigning non-overlapping > ranges, in this case. This step is covered in [Prerequisites](#prerequisites). -{: .warning } +{ .warning } It is very important that the ranges do not overlap, so that a process cannot gain access in a different namespace. On most Linux distributions, system utilities @@ -269,4 +269,4 @@ expected privileges of the superuser within the container, the Linux kernel imposes restrictions based on internal knowledge that this is a user-namespaced process. One notable restriction is the inability to use the `mknod` command. Permission is denied for device creation within the container when run by -the `root` user. +the `root` user. \ No newline at end of file diff --git a/content/engine/swarm/_index.md b/content/engine/swarm/_index.md index 4eee0cdf36..43e630b4c0 100644 --- a/content/engine/swarm/_index.md +++ b/content/engine/swarm/_index.md @@ -2,7 +2,7 @@ description: Docker Engine swarm mode overview keywords: docker, container, cluster, swarm title: Swarm mode overview -redirect_from: +aliases: - /api/swarm-api/ - /engine/userguide/networking/overlay-standalone-swarm/ - /network/overlay-standalone.swarm/ @@ -45,7 +45,7 @@ redirect_from: - /swarm/swarm_at_scale/troubleshoot/ --- -{% include swarm-mode.md %} +{{< include "swarm-mode.md" >}} To use Docker in swarm mode, install Docker. See [installation instructions](../../get-docker.md) for all operating systems and platforms. @@ -55,7 +55,7 @@ of Docker Engines called a *swarm*. Use the Docker CLI to create a swarm, deploy application services to a swarm, and manage swarm behavior. Docker Swarm mode is built into the Docker Engine. Do not confuse Docker Swarm mode -with [Docker Classic Swarm](https://github.com/docker/classicswarm){:target="_blank" rel="noopener" class="_"} +with [Docker Classic Swarm](https://github.com/docker/classicswarm) which is no longer actively developed. ## Feature highlights @@ -130,4 +130,4 @@ Explore swarm mode CLI commands * [service rm](../reference/commandline/service_rm.md) * [service scale](../reference/commandline/service_scale.md) * [service ps](../reference/commandline/service_ps.md) -* [service update](../reference/commandline/service_update.md) +* [service update](../reference/commandline/service_update.md) \ No newline at end of file diff --git a/content/engine/swarm/admin_guide.md b/content/engine/swarm/admin_guide.md index 1f7314bdec..194b55a9d9 100644 --- a/content/engine/swarm/admin_guide.md +++ b/content/engine/swarm/admin_guide.md @@ -1,9 +1,9 @@ --- description: Manager administration guide keywords: docker, container, swarm, manager, raft -redirect_from: -- /engine/swarm/manager-administration-guide/ title: Administer and maintain a swarm of Docker Engines +aliases: +- /engine/swarm/manager-administration-guide/ --- When you run a swarm of Docker Engines, **manager nodes** are the key components @@ -160,21 +160,21 @@ for more information. From the command line, run `docker node inspect ` to query the nodes. For instance, to query the reachability of the node as a manager: -{% raw %} + ```console $ docker node inspect manager1 --format "{{ .ManagerStatus.Reachability }}" reachable ``` -{% endraw %} + To query the status of the node as a worker that accept tasks: -{% raw %} + ```console $ docker node inspect manager1 --format "{{ .Status.State }}" ready ``` -{% endraw %} + From those commands, we can see that `manager1` is both at the status `reachable` as a manager and `ready` as a worker. @@ -396,4 +396,4 @@ balance of your service across nodes. See also [`docker service scale`](../reference/commandline/service_scale.md) and -[`docker service ps`](../reference/commandline/service_ps.md). +[`docker service ps`](../reference/commandline/service_ps.md). \ No newline at end of file diff --git a/content/engine/swarm/configs.md b/content/engine/swarm/configs.md index fc2f7dbe9a..a74fc3c945 100644 --- a/content/engine/swarm/configs.md +++ b/content/engine/swarm/configs.md @@ -290,7 +290,7 @@ name as its argument. The template will be rendered when container is created. Hello Docker -

Hello {% raw %}{{ env "HELLO" }}{% endraw %}! I'm service {% raw %}{{ .Service.Name }}{% endraw %}.

+

Hello {{ env "HELLO" }}! I'm service {{ .Service.Name }}.

``` @@ -661,4 +661,4 @@ configuration file. ``` You have now updated your `nginx` service's configuration without the need to -rebuild its image. +rebuild its image. \ No newline at end of file diff --git a/content/engine/swarm/how-swarm-mode-works/nodes.md b/content/engine/swarm/how-swarm-mode-works/nodes.md index 4df1685ff4..662eef9cc4 100644 --- a/content/engine/swarm/how-swarm-mode-works/nodes.md +++ b/content/engine/swarm/how-swarm-mode-works/nodes.md @@ -1,9 +1,9 @@ --- description: How swarm nodes work keywords: docker, container, cluster, swarm mode, node -redirect_from: -- /engine/swarm/how-swarm-mode-works/ title: How nodes work +aliases: +- /engine/swarm/how-swarm-mode-works/ --- Docker Engine 1.12 introduces swarm mode that enables you to create a @@ -81,4 +81,4 @@ You can also demote a manager node to a worker node. See ## Learn more * Read about how swarm mode [services](services.md) work. -* Learn how [PKI](pki.md) works in swarm mode. +* Learn how [PKI](pki.md) works in swarm mode. \ No newline at end of file diff --git a/content/engine/swarm/how-swarm-mode-works/pki.md b/content/engine/swarm/how-swarm-mode-works/pki.md index b077fdff36..927cda4a04 100644 --- a/content/engine/swarm/how-swarm-mode-works/pki.md +++ b/content/engine/swarm/how-swarm-mode-works/pki.md @@ -103,4 +103,4 @@ root CA, and do not contain any intermediates. ## Learn More * Read about how [nodes](nodes.md) work. -* Learn how swarm mode [services](services.md) work. +* Learn how swarm mode [services](services.md) work. \ No newline at end of file diff --git a/content/engine/swarm/how-swarm-mode-works/services.md b/content/engine/swarm/how-swarm-mode-works/services.md index 7365e00451..f86fff4aa9 100644 --- a/content/engine/swarm/how-swarm-mode-works/services.md +++ b/content/engine/swarm/how-swarm-mode-works/services.md @@ -120,4 +120,4 @@ in gray. ## Learn more * Read about how swarm mode [nodes](nodes.md) work. -* Learn how [PKI](pki.md) works in swarm mode. +* Learn how [PKI](pki.md) works in swarm mode. \ No newline at end of file diff --git a/content/engine/swarm/how-swarm-mode-works/swarm-task-states.md b/content/engine/swarm/how-swarm-mode-works/swarm-task-states.md index 3038ab0f73..2bb67c1461 100644 --- a/content/engine/swarm/how-swarm-mode-works/swarm-task-states.md +++ b/content/engine/swarm/how-swarm-mode-works/swarm-task-states.md @@ -2,7 +2,7 @@ title: Swarm task states description: Learn about tasks that are scheduled on your swarm. keywords: swarm, task, service -redirect_from: +aliases: - /datacenter/ucp/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-task-state/ --- @@ -59,4 +59,4 @@ j91iahr8s74p \_ webserver.1 nginx UbuntuVM Shutdown Failed 50 s ## Where to go next -- [Learn about swarm tasks](https://github.com/docker/swarmkit/blob/master/design/task_model.md) +- [Learn about swarm tasks](https://github.com/docker/swarmkit/blob/master/design/task_model.md) \ No newline at end of file diff --git a/content/engine/swarm/ingress.md b/content/engine/swarm/ingress.md index 6024091ad6..2fb886c25e 100644 --- a/content/engine/swarm/ingress.md +++ b/content/engine/swarm/ingress.md @@ -86,13 +86,13 @@ $ docker service update \ You can use `docker service inspect` to view the service's published port. For instance: -{% raw %} + ```console $ docker service inspect --format="{{json .Endpoint.Spec.Ports}}" my-web [{"Protocol":"tcp","TargetPort":80,"PublishedPort":8080}] ``` -{% endraw %} + The output shows the `` (labeled `TargetPort`) from the containers and the `` (labeled `PublishedPort`) where nodes listen for requests for the service. @@ -252,4 +252,4 @@ IP addresses and ports to your load balancer. See ## Learn more -* [Deploy services to a swarm](services.md) +* [Deploy services to a swarm](services.md) \ No newline at end of file diff --git a/content/engine/swarm/join-nodes.md b/content/engine/swarm/join-nodes.md index 225c60f61c..849c0454ad 100644 --- a/content/engine/swarm/join-nodes.md +++ b/content/engine/swarm/join-nodes.md @@ -99,4 +99,4 @@ This node joined a swarm as a manager. ## Learn More * `swarm join` [command line reference](../reference/commandline/swarm_join.md) -* [Swarm mode tutorial](swarm-tutorial/index.md) +* [Swarm mode tutorial](swarm-tutorial/index.md) \ No newline at end of file diff --git a/content/engine/swarm/key-concepts.md b/content/engine/swarm/key-concepts.md index 0942f4fd33..980265bb13 100644 --- a/content/engine/swarm/key-concepts.md +++ b/content/engine/swarm/key-concepts.md @@ -108,4 +108,4 @@ the service. ## What's next? * Read the [Swarm mode overview](index.md). -* Get started with the [Swarm mode tutorial](swarm-tutorial/index.md). +* Get started with the [Swarm mode tutorial](swarm-tutorial/index.md). \ No newline at end of file diff --git a/content/engine/swarm/manage-nodes.md b/content/engine/swarm/manage-nodes.md index 41d4a849d2..1d7c4c3c12 100644 --- a/content/engine/swarm/manage-nodes.md +++ b/content/engine/swarm/manage-nodes.md @@ -240,4 +240,4 @@ $ docker node rm node-2 * [Swarm administration guide](admin_guide.md) * [Docker Engine command line reference](../reference/commandline/docker.md) -* [Swarm mode tutorial](swarm-tutorial/index.md) +* [Swarm mode tutorial](swarm-tutorial/index.md) \ No newline at end of file diff --git a/content/engine/swarm/networking.md b/content/engine/swarm/networking.md index f1ae2f0a1c..3129b794b7 100644 --- a/content/engine/swarm/networking.md +++ b/content/engine/swarm/networking.md @@ -425,4 +425,4 @@ $ docker swarm join \ * [Swarm administration guide](admin_guide.md) * [Swarm mode tutorial](swarm-tutorial/index.md) * [Networking overview](../../network/index.md) -* [Docker CLI reference](../reference/commandline/docker.md) +* [Docker CLI reference](../reference/commandline/docker.md) \ No newline at end of file diff --git a/content/engine/swarm/raft.md b/content/engine/swarm/raft.md index 494e7addc7..ebb6c0f701 100644 --- a/content/engine/swarm/raft.md +++ b/content/engine/swarm/raft.md @@ -35,4 +35,4 @@ the properties inherent to distributed systems: and the [Raft Consensus Algorithm paper](https://www.usenix.org/system/files/conference/atc14/atc14-paper-ongaro.pdf)) - *mutual exclusion* through the leader election process - *cluster membership* management -- *globally consistent object sequencing* and CAS (compare-and-swap) primitives +- *globally consistent object sequencing* and CAS (compare-and-swap) primitives \ No newline at end of file diff --git a/content/engine/swarm/secrets.md b/content/engine/swarm/secrets.md index ed7b422dcb..564b8aee2c 100644 --- a/content/engine/swarm/secrets.md +++ b/content/engine/swarm/secrets.md @@ -1,7 +1,8 @@ --- title: Manage sensitive data with Docker secrets description: How to securely store, retrieve, and use sensitive data with Docker services -keywords: swarm, secrets, credentials, sensitive strings, sensitive data, security, encryption, encryption at rest +keywords: swarm, secrets, credentials, sensitive strings, sensitive data, security, + encryption, encryption at rest --- ## About secrets @@ -1024,4 +1025,4 @@ Each service uses environment variables to specify where the service should look for that secret data. More information on short and long syntax for secrets can be found at -[Compose file version 3 reference](../../compose/compose-file/compose-file-v3.md#secrets). +[Compose file version 3 reference](../../compose/compose-file/compose-file-v3.md#secrets). \ No newline at end of file diff --git a/content/engine/swarm/services.md b/content/engine/swarm/services.md index 4384227bc0..40a13c3e1d 100644 --- a/content/engine/swarm/services.md +++ b/content/engine/swarm/services.md @@ -307,7 +307,7 @@ of the image. > Thus, if you use content trust, the swarm manager receives the request > pre-resolved. In this case, if the client cannot resolve the image to a > digest, the request fails. -{: id="image_resolution_with_trust" } +{ #image_resolution_with_trust } If the manager can't resolve the tag to a digest, each worker node is responsible for resolving the tag to a digest, and different nodes may @@ -1009,13 +1009,13 @@ Valid placeholders for the Go template are: This example sets the template of the created containers based on the service's name and the ID of the node where the container is running: -{% raw %} + ```console $ docker service create --name hosttempl \ --hostname="{{.Node.ID}}-{{.Service.Name}}"\ busybox top ``` -{% endraw %} + To see the result of using the template, use the `docker service ps` and `docker inspect` commands. @@ -1027,14 +1027,14 @@ ID NAME IMAGE wo41w8hg8qan hosttempl.1 busybox:latest@sha256:29f5d56d12684887bdfa50dcd29fc31eea4aaf4ad3bec43daf19026a7ce69912 2e7a8a9c4da2 Running Running about a minute ago ``` -{% raw %} + ```console $ docker inspect --format="{{.Config.Hostname}}" hosttempl.1.wo41w8hg8qanxwjwsg4kxpprj ``` -{% endraw %} + ## Learn More * [Swarm administration guide](admin_guide.md) * [Docker Engine command line reference](../reference/commandline/docker.md) -* [Swarm mode tutorial](swarm-tutorial/index.md) +* [Swarm mode tutorial](swarm-tutorial/index.md) \ No newline at end of file diff --git a/content/engine/swarm/stack-deploy.md b/content/engine/swarm/stack-deploy.md index a618c50e47..f0f8ffed6c 100644 --- a/content/engine/swarm/stack-deploy.md +++ b/content/engine/swarm/stack-deploy.md @@ -8,7 +8,7 @@ When running Docker Engine in swarm mode, you can use `docker stack deploy` to deploy a complete application stack to the swarm. The `deploy` command accepts a stack description in the form of a [Compose file](../../compose/compose-file/compose-file-v3.md). -{% include swarm-compose-compat.md %} +{{< include "swarm-compose-compat.md" >}} The `docker stack deploy` command supports any Compose file of version "3.x". If you have an older version, see the [upgrade guide](../../compose/compose-file/compose-versioning.md#upgrading). @@ -294,4 +294,4 @@ The stack is now ready to be deployed. $ docker swarm leave --force Node left the swarm. - ``` + ``` \ No newline at end of file diff --git a/content/engine/swarm/swarm-mode.md b/content/engine/swarm/swarm-mode.md index d9952bdec0..c3d385180c 100644 --- a/content/engine/swarm/swarm-mode.md +++ b/content/engine/swarm/swarm-mode.md @@ -215,4 +215,4 @@ To add a worker to this swarm, run the following command: * [Join nodes to a swarm](join-nodes.md) * `swarm init` [command line reference](../reference/commandline/swarm_init.md) -* [Swarm mode tutorial](swarm-tutorial/index.md) +* [Swarm mode tutorial](swarm-tutorial/index.md) \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/_index.md b/content/engine/swarm/swarm-tutorial/_index.md index e3a2f4d2f1..fc77c1e078 100644 --- a/content/engine/swarm/swarm-tutorial/_index.md +++ b/content/engine/swarm/swarm-tutorial/_index.md @@ -97,4 +97,4 @@ iptables -I INPUT -m udp —-dport 4789 -m policy --dir in --pol none -j DROP ## What's next? -After you have set up your environment, you are ready to [create a swarm](create-swarm.md). +After you have set up your environment, you are ready to [create a swarm](create-swarm.md). \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/add-nodes.md b/content/engine/swarm/swarm-tutorial/add-nodes.md index ac5555438a..81c56959c2 100644 --- a/content/engine/swarm/swarm-tutorial/add-nodes.md +++ b/content/engine/swarm/swarm-tutorial/add-nodes.md @@ -71,4 +71,4 @@ to add worker nodes. ## What's next? Now your swarm consists of a manager and two worker nodes. In the next step of -the tutorial, you [deploy a service](deploy-service.md) to the swarm. +the tutorial, you [deploy a service](deploy-service.md) to the swarm. \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/create-swarm.md b/content/engine/swarm/swarm-tutorial/create-swarm.md index 6c0b490e18..bafcc1ea65 100644 --- a/content/engine/swarm/swarm-tutorial/create-swarm.md +++ b/content/engine/swarm/swarm-tutorial/create-swarm.md @@ -79,4 +79,4 @@ machines. ## What's next? In the next section of the tutorial, we [add two more nodes](add-nodes.md) to -the cluster. +the cluster. \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/delete-service.md b/content/engine/swarm/swarm-tutorial/delete-service.md index 2b65ef2446..f8336dbcf7 100644 --- a/content/engine/swarm/swarm-tutorial/delete-service.md +++ b/content/engine/swarm/swarm-tutorial/delete-service.md @@ -52,4 +52,4 @@ you can delete the service from the swarm. ## What's next? In the next step of the tutorial, you set up a new service and apply a -[rolling update](rolling-update.md). +[rolling update](rolling-update.md). \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/deploy-service.md b/content/engine/swarm/swarm-tutorial/deploy-service.md index ede843651e..962a0184fd 100644 --- a/content/engine/swarm/swarm-tutorial/deploy-service.md +++ b/content/engine/swarm/swarm-tutorial/deploy-service.md @@ -37,4 +37,4 @@ is not a requirement to deploy a service. ## What's next? -Now you've deployed a service to the swarm, you're ready to [inspect the service](inspect-service.md). +Now you've deployed a service to the swarm, you're ready to [inspect the service](inspect-service.md). \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/drain-node.md b/content/engine/swarm/swarm-tutorial/drain-node.md index 4110435e61..ca27ccd741 100644 --- a/content/engine/swarm/swarm-tutorial/drain-node.md +++ b/content/engine/swarm/swarm-tutorial/drain-node.md @@ -18,7 +18,7 @@ node and launches replica tasks on a node with `ACTIVE` availability. > such as those created with `docker run`, `docker compose up`, or the Docker Engine > API. A node's status, including `DRAIN`, only affects the node's ability to schedule > swarm service workloads. -{:.important} +{ .important } 1. If you haven't already, open a terminal and ssh into the machine where you run your manager node. For example, the tutorial uses a machine named @@ -131,4 +131,4 @@ drained node to an active state: ## What's next? -Learn how to [use a swarm mode routing mesh](../ingress.md). +Learn how to [use a swarm mode routing mesh](../ingress.md). \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/inspect-service.md b/content/engine/swarm/swarm-tutorial/inspect-service.md index 5fc8ea90b4..6351a9e2e4 100644 --- a/content/engine/swarm/swarm-tutorial/inspect-service.md +++ b/content/engine/swarm/swarm-tutorial/inspect-service.md @@ -120,4 +120,4 @@ the Docker CLI to see details about the service running in the swarm. ## What's next? Next, you can [change the scale](scale-service.md) for the service running in -the swarm. +the swarm. \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/rolling-update.md b/content/engine/swarm/swarm-tutorial/rolling-update.md index 867ba1f5fc..94dd74e2e1 100644 --- a/content/engine/swarm/swarm-tutorial/rolling-update.md +++ b/content/engine/swarm/swarm-tutorial/rolling-update.md @@ -148,4 +148,4 @@ Redis 3.0.7 container image using rolling updates. ## What's next? -Next, learn about how to [drain a node](drain-node.md) in the swarm. +Next, learn about how to [drain a node](drain-node.md) in the swarm. \ No newline at end of file diff --git a/content/engine/swarm/swarm-tutorial/scale-service.md b/content/engine/swarm/swarm-tutorial/scale-service.md index 82dc9f9271..66bc4cf1f8 100644 --- a/content/engine/swarm/swarm-tutorial/scale-service.md +++ b/content/engine/swarm/swarm-tutorial/scale-service.md @@ -61,4 +61,4 @@ the service. Containers running in a service are called "tasks." ## What's next? At this point in the tutorial, you're finished with the `helloworld` service. -The next step shows how to [delete the service](delete-service.md). +The next step shows how to [delete the service](delete-service.md). \ No newline at end of file diff --git a/content/engine/swarm/swarm_manager_locking.md b/content/engine/swarm/swarm_manager_locking.md index 2647f43711..d00b07688d 100644 --- a/content/engine/swarm/swarm_manager_locking.md +++ b/content/engine/swarm/swarm_manager_locking.md @@ -154,4 +154,4 @@ will not be able to restart the manager. > When you rotate the unlock key, keep a record of the old key > around for a few minutes, so that if a manager goes down before it gets the new > key, it may still be unlocked with the old one. -{:.warning} +{ .warning } \ No newline at end of file diff --git a/content/engine/tutorials/_index.md b/content/engine/tutorials/_index.md index 0f8f906b68..73920f628a 100644 --- a/content/engine/tutorials/_index.md +++ b/content/engine/tutorials/_index.md @@ -1,9 +1,10 @@ --- description: Explains how to work with containers -keywords: docker, introduction, documentation, about, technology, docker.io, user, guide, user's, manual, platform, framework, home, intro -redirect_from: -- /engine/userguide/containers/ +keywords: docker, introduction, documentation, about, technology, docker.io, user, + guide, user's, manual, platform, framework, home, intro title: Engine tutorials +aliases: +- /engine/userguide/containers/ --- # Learn by example @@ -11,4 +12,4 @@ title: Engine tutorials * [Network containers](networkingcontainers.md) * [Manage data in containers](../../storage/volumes.md) * [Samples](../../samples/index.md) -* [Get Started](../../get-started/index.md) +* [Get Started](../../get-started/index.md) \ No newline at end of file diff --git a/content/engine/tutorials/networkingcontainers.md b/content/engine/tutorials/networkingcontainers.md index d6660e5a3f..9590f28a09 100644 --- a/content/engine/tutorials/networkingcontainers.md +++ b/content/engine/tutorials/networkingcontainers.md @@ -1,10 +1,10 @@ --- description: How to network Docker containers. keywords: Examples, Usage, volume, docker, documentation, user guide, data, volumes -redirect_from: +title: Network containers +aliases: - /engine/userguide/containers/networkigncontainers/ - /engine/userguide/networkigncontainers/ -title: Network containers --- If you are working your way through the user guide, you just built and ran a @@ -143,9 +143,9 @@ Launch a container running a PostgreSQL database and pass it the `--net=my_bridg If you inspect your `my_bridge` you can see it has a container attached. You can also inspect your container to see where it is connected: - {% raw %} + $ docker inspect --format='{{json .NetworkSettings.Networks}}' db - {% endraw %} + {"my_bridge":{"NetworkID":"7d86d31b1478e7cca9ebed7e73aa0fdeec46c5ca29497431d3007d2d9e15ed99", "EndpointID":"508b170d56b2ac9e4ef86694b0a76a22dd3df1983404f7321da5649645bf7043","Gateway":"10.0.0.1","IPAddress":"10.0.0.254","IPPrefixLen":24,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}} @@ -158,18 +158,18 @@ Now, go ahead and start your by now familiar web application. This time don't sp Which network is your `web` application running under? Inspect the application to verify that it is running in the default `bridge` network. - {% raw %} + $ docker inspect --format='{{json .NetworkSettings.Networks}}' web - {% endraw %} + {"bridge":{"NetworkID":"7ea29fc1412292a2d7bba362f9253545fecdfa8ce9a6e37dd10ba8bee7129812", "EndpointID":"508b170d56b2ac9e4ef86694b0a76a22dd3df1983404f7321da5649645bf7043","Gateway":"172.17.0.1","IPAddress":"10.0.0.2","IPPrefixLen":24,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02"}} Then, get the IP address of your `web` - {% raw %} + $ docker inspect --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' web - {% endraw %} + 172.17.0.2 @@ -211,4 +211,4 @@ The `ping` shows it is contacting a different IP address, the address on the `my ## Next steps -Now that you know how to network containers, see [how to manage data in containers](../../storage/volumes.md). +Now that you know how to network containers, see [how to manage data in containers](../../storage/volumes.md). \ No newline at end of file diff --git a/content/faq/_index.md b/content/faq/_index.md index 1eb0bd5059..9c8a52c337 100644 --- a/content/faq/_index.md +++ b/content/faq/_index.md @@ -3,26 +3,26 @@ title: Frequently asked questions description: Landing page to common FAQ topics keywords: faqs, desktop, Hub, Scout, Engine, Build, Extensions grid: - - title: Subscription - icon: contact_page - link: /subscription/faq/ - - title: Billing - icon: credit_score - link: /billing/faqs/ - - title: Docker Hub - icon: lan - link: /docker-hub/general-faqs/ - - title: Enforcing Single Sign-On - icon: key - link: /single-sign-on/enforcement-faqs/ - - title: Single Sign-On and IdPs - icon: checklist - link: /single-sign-on/idp-faqs/ - - title: Docker Desktop - icon: explore - link: /desktop/faqs/general/ +- title: Subscription + icon: contact_page + link: /subscription/faq/ +- title: Billing + icon: credit_score + link: /billing/faqs/ +- title: Docker Hub + icon: lan + link: /docker-hub/general-faqs/ +- title: Enforcing Single Sign-On + icon: key + link: /single-sign-on/enforcement-faqs/ +- title: Single Sign-On and IdPs + icon: checklist + link: /single-sign-on/idp-faqs/ +- title: Docker Desktop + icon: explore + link: /desktop/faqs/general/ --- Explore popular FAQ topics. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/get-docker.md b/content/get-docker.md index f620d01474..c9f6328052 100644 --- a/content/get-docker.md +++ b/content/get-docker.md @@ -1,8 +1,10 @@ --- -description: Download and install Docker on the platform of your choice, including Mac, Linux, or Windows. -keywords: install docker, docker download, download docker, docker installation, how to install docker, get docker, docker locally +description: Download and install Docker on the platform of your choice, including + Mac, Linux, or Windows. +keywords: install docker, docker download, download docker, docker installation, how + to install docker, get docker, docker locally title: Get Docker -redirect_from: +aliases: - /install/ - /install/overview/ - /installation/ @@ -45,4 +47,4 @@ section and choose the best installation path for you. > **Note** > -> If you're looking for information on how to install Docker Engine, see [Docker Engine installation overview](/engine/install/index.md). +> If you're looking for information on how to install Docker Engine, see [Docker Engine installation overview](/engine/install/index.md). \ No newline at end of file diff --git a/content/get-started/02_our_app.md b/content/get-started/02_our_app.md index 1ded810cd0..69532b437d 100644 --- a/content/get-started/02_our_app.md +++ b/content/get-started/02_our_app.md @@ -1,9 +1,12 @@ --- -title: "Containerize an application" -keywords: dockerfile example, Containerize an application, run docker file, running docker file, how to run dockerfile, example dockerfile, how to create a docker container, create dockerfile, simple dockerfile, creating containers -redirect_from: +title: Containerize an application +keywords: dockerfile example, Containerize an application, run docker file, running + docker file, how to run dockerfile, example dockerfile, how to create a docker container, + create dockerfile, simple dockerfile, creating containers +description: Follow this step-by-step guide to learn how to create and run a containerized + application using Docker +aliases: - /get-started/part2/ -description: Follow this step-by-step guide to learn how to create and run a containerized application using Docker --- For the rest of this guide, you'll be working with a simple todo @@ -13,14 +16,14 @@ don't worry. This guide doesn't require any prior experience with JavaScript. ## Prerequisites - You have installed the latest version of [Docker Desktop](../get-docker.md). -- You have installed a [Git client](https://git-scm.com/downloads){:target="_blank" rel="noopener" class="_"}. -- You have an IDE or a text editor to edit files. Docker recommends using [Visual Studio Code](https://code.visualstudio.com/){:target="_blank" rel="noopener" class="_"}. +- You have installed a [Git client](https://git-scm.com/downloads). +- You have an IDE or a text editor to edit files. Docker recommends using [Visual Studio Code](https://code.visualstudio.com/). ## Get the app Before you can run the application, you need to get the application source code onto your machine. -1. Clone the [getting-started-app repository](https://github.com/docker/getting-started-app/tree/main){:target="_blank" rel="noopener" class="_"} using the following command: +1. Clone the [getting-started-app repository](https://github.com/docker/getting-started-app/tree/main) using the following command: ```console $ git clone https://github.com/docker/getting-started-app.git @@ -131,11 +134,11 @@ Now that you have an image, you can run the application in a container using the The command publishes the container's port 3000 to `127.0.0.1:3000` (`localhost:3000`) on the host. Without the port mapping, you wouldn't be able to access the application from the host. -2. After a few seconds, open your web browser to [http://localhost:3000](http://localhost:3000){:target="_blank" rel="noopener" class="_"}. +2. After a few seconds, open your web browser to [http://localhost:3000](http://localhost:3000). You should see your app. - ![Empty todo list](images/todo-list-empty.png){: style="width:450px;margin-top:20px;"} - {: .text-center } + ![Empty todo list](images/todo-list-empty.png) + 3. Add an item or two and see that it works as you expect. You can mark items as complete and remove them. Your frontend is successfully storing items in the backend. @@ -182,4 +185,4 @@ Related information: Next, you're going to make a modification to your app and learn how to update your running application with a new image. Along the way, you'll learn a few other useful commands. -[Update the application](03_updating_app.md){: .button .primary-btn} +{{< button text="Update the application" url="03_updating_app.md" >}} \ No newline at end of file diff --git a/content/get-started/03_updating_app.md b/content/get-started/03_updating_app.md index 1a2da371ea..fc540c4a68 100644 --- a/content/get-started/03_updating_app.md +++ b/content/get-started/03_updating_app.md @@ -1,6 +1,7 @@ --- -title: "Update the application" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop +title: Update the application +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop description: Making changes to your application --- @@ -90,7 +91,7 @@ To remove a container, you first need to stop it. Once it has stopped, you can r $ docker run -dp 127.0.0.1:3000:3000 getting-started ``` -2. Refresh your browser on [http://localhost:3000](http://localhost:3000){:target="_blank" rel="noopener" class="_"} and you should see your updated help text. +2. Refresh your browser on [http://localhost:3000](http://localhost:3000) and you should see your updated help text. ## Summary @@ -103,4 +104,4 @@ Related information: Next, you'll learn how to share images with others. -[Share the application](04_sharing_app.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Share the application" url="04_sharing_app.md" >}} \ No newline at end of file diff --git a/content/get-started/04_sharing_app.md b/content/get-started/04_sharing_app.md index 93ada232c6..a19dcafc72 100644 --- a/content/get-started/04_sharing_app.md +++ b/content/get-started/04_sharing_app.md @@ -1,9 +1,11 @@ --- -title: "Share the application" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop, docker hub, sharing -redirect_from: +title: Share the application +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop, docker hub, sharing +description: Sharing your image you built for your example application so you can + run it else where and other developers can use it +aliases: - /get-started/part3/ -description: Sharing your image you built for your example application so you can run it else where and other developers can use it --- Now that you've built an image, you can share it. To share Docker images, you have to use a Docker @@ -11,13 +13,13 @@ registry. The default registry is Docker Hub and is where all of the images you' > **Docker ID** > -> A Docker ID lets you to access Docker Hub, which is the world's largest library and community for container images. Create a [Docker ID](https://hub.docker.com/signup){:target="_blank" rel="noopener" class="_"} for free if you don't have one. +> A Docker ID lets you to access Docker Hub, which is the world's largest library and community for container images. Create a [Docker ID](https://hub.docker.com/signup) for free if you don't have one. ## Create a repository To push an image, you first need to create a repository on Docker Hub. -1. [Sign up](https://www.docker.com/pricing?utm_source=docker&utm_medium=webreferral&utm_campaign=docs_driven_upgrade){:target="_blank" rel="noopener" class="_"} or Sign in to [Docker Hub](https://hub.docker.com){:target="_blank" rel="noopener" class="_"}. +1. [Sign up](https://www.docker.com/pricing?utm_source=docker&utm_medium=webreferral&utm_campaign=docs_driven_upgrade) or Sign in to [Docker Hub](https://hub.docker.com). 2. Select the **Create Repository** button. @@ -27,8 +29,8 @@ To push an image, you first need to create a repository on Docker Hub. In the following image, you can see an example Docker command from Docker Hub. This command will push to this repository. -![Docker command with push example](images/push-command.png){: style=width:75% } -{: .text-center } +![Docker command with push example](images/push-command.png) + ## Push the image @@ -79,7 +81,7 @@ new instance that has never seen this container image. To do this, you will use > Docker buildx also supports building multi-platform images. To learn more, see [Multi-platform images](../build/building/multi-platform.md). -1. Open your browser to [Play with Docker](https://labs.play-with-docker.com/){:target="_blank" rel="noopener" class="_"}. +1. Open your browser to [Play with Docker](https://labs.play-with-docker.com/). 2. Select **Login** and then select **docker** from the drop-down list. @@ -87,7 +89,7 @@ new instance that has never seen this container image. To do this, you will use 4. Select the **ADD NEW INSTANCE** option on the left side bar. If you don't see it, make your browser a little wider. After a few seconds, a terminal window opens in your browser. - ![Play with Docker add new instance](images/pwd-add-new-instance.png){: style=width:75% } + ![Play with Docker add new instance](images/pwd-add-new-instance.png) 5. In the terminal, start your freshly pushed app. @@ -109,7 +111,7 @@ new instance that has never seen this container image. To do this, you will use > > For more information about how port mapping works, see > [Networking](../network/index.md#published-ports). - {: .tip } + { .tip } 6. Select the 3000 badge when it appears. @@ -133,4 +135,4 @@ Related information: In the next section, you'll learn how to persist data in your containerized application. -[Persist the DB](05_persisting_data.md){: .button .primary-btn} +{{< button text="Persist the DB" url="05_persisting_data.md" >}} \ No newline at end of file diff --git a/content/get-started/05_persisting_data.md b/content/get-started/05_persisting_data.md index 68049134f8..3afee52eb6 100644 --- a/content/get-started/05_persisting_data.md +++ b/content/get-started/05_persisting_data.md @@ -1,6 +1,7 @@ --- -title: "Persist the DB" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop +title: Persist the DB +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop description: Making your DB persistent in your application --- @@ -146,7 +147,7 @@ To start the todo app container with the volume mounted: > **Tip** > > Use the search filter to filter images and only show **Local images**. - {: .tip } + { .tip } 4. Select your image and then select **Run**. 5. Select **Optional settings**. @@ -162,8 +163,8 @@ To start the todo app container with the volume mounted: 1. Once the container starts up, open the app and add a few items to your todo list. - ![Items added to todo list](images/items-added.png){: style="width: 55%; " } - {: .text-center } + ![Items added to todo list](images/items-added.png) + 2. Stop and remove the container for the todo app. Use Docker Desktop or `docker ps` to get the ID and then `docker rm -f ` to remove it. @@ -211,4 +212,4 @@ Related information: Next, you'll learn how you can develop your app more efficiently using bind mounts. -[Use bind mounts](06_bind_mounts.md){: .button .primary-btn} +{{< button text="Use bind mounts" url="06_bind_mounts.md" >}} \ No newline at end of file diff --git a/content/get-started/06_bind_mounts.md b/content/get-started/06_bind_mounts.md index 5cbe283262..f61341134a 100644 --- a/content/get-started/06_bind_mounts.md +++ b/content/get-started/06_bind_mounts.md @@ -1,8 +1,9 @@ --- -title: "Use bind mounts" -keywords: > - get started, setup, orientation, quickstart, intro, concepts, containers, +title: Use bind mounts +keywords: 'get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop + + ' description: Using bind mounts in our application --- @@ -18,8 +19,7 @@ that you can run processes in the container that watch for filesystem changes and respond to them. In this chapter, you'll see how you can use bind mounts and a tool called -[nodemon](https://npmjs.com/package/nodemon){:target="_blank" rel="noopener" -class="_"} to watch for file changes, and then restart the application +[nodemon](https://npmjs.com/package/nodemon) to watch for file changes, and then restart the application automatically. There are equivalent tools in most other languages and frameworks. @@ -256,7 +256,7 @@ Run the image with a bind mount. > **Tip** > > Use the search filter to filter images and only show **Local images**. - {: .tip } + { .tip } 4. Select your image and then select **Run**. 5. Select **Optional settings**. @@ -303,8 +303,7 @@ Update your app on your host machine and see the changes reflected in the contai almost immediately. It might take a few seconds for the Node server to restart. If you get an error, try refreshing after a few seconds. - ![Screenshot of updated label for Add button](images/updated-add-button.png){: - style="width:75%;" .text-center} + ![Screenshot of updated label for Add button](images/updated-add-button.png) 3. Feel free to make any other changes you'd like to make. Each time you make a change and save a file, the `nodemon` process restarts the app inside the @@ -335,5 +334,4 @@ simplicity, you'll keep using a relational database and switch your application to use MySQL. But, how should you run MySQL? How do you allow the containers to talk to each other? You'll learn about that in the next section. -[Multi container apps](07_multi_container.md){: .button .primary-btn} - +{{< button text="Multi container apps" url="07_multi_container.md" >}} \ No newline at end of file diff --git a/content/get-started/07_multi_container.md b/content/get-started/07_multi_container.md index 7eb26329b4..516220d0b8 100644 --- a/content/get-started/07_multi_container.md +++ b/content/get-started/07_multi_container.md @@ -1,6 +1,7 @@ --- -title: "Multi container apps" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop +title: Multi container apps +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop description: Using more than one container in your application --- @@ -17,7 +18,7 @@ container or run it separately?" In general, each container should do one thing And there are more reasons. So, like the following diagram, it's best to run your app in multiple containers. ![Todo App connected to MySQL container](images/multi-app-architecture.png) -{: .text-center } + ## Container networking @@ -76,7 +77,7 @@ In the following steps, you'll create the network first and then attach the MySQ > **Tip** > > You'll notice a volume named `todo-mysql-data` in the above command that is mounted at `/var/lib/mysql`, which is where MySQL stores its data. However, you never ran a `docker volume create` command. Docker recognizes you want to use a named volume and creates one automatically for you. - {: .tip } + { .tip } 3. To confirm you have the database up and running, connect to the database and verify that it connects. @@ -177,7 +178,7 @@ The todo app supports the setting of a few environment variables to specify MySQ > > While using env vars to set connection settings is generally accepted for development, it's highly discouraged > when running applications in production. Diogo Monica, a former lead of security at Docker, -> [wrote a fantastic blog post](https://diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/){:target="_blank" rel="noopener" class="_"} +> [wrote a fantastic blog post](https://diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/) > explaining why. > > A more secure mechanism is to use the secret support provided by your container orchestration framework. In most cases, @@ -280,4 +281,4 @@ ports, and more. That's a lot to remember and it's certainly making things harde In the next section, you'll learn about Docker Compose. With Docker Compose, you can share your application stacks in a much easier way and let others spin them up with a single, simple command. -[Use Docker Compose](08_using_compose.md){: .button .primary-btn} +{{< button text="Use Docker Compose" url="08_using_compose.md" >}} \ No newline at end of file diff --git a/content/get-started/08_using_compose.md b/content/get-started/08_using_compose.md index 999d418d87..c9a05a74c0 100644 --- a/content/get-started/08_using_compose.md +++ b/content/get-started/08_using_compose.md @@ -1,6 +1,7 @@ --- -title: "Use Docker Compose" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop +title: Use Docker Compose +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop description: Using Docker Compose for multi-container applications --- @@ -246,7 +247,7 @@ Now that you have your `compose.yaml` file, you can start your application. view the logs for a specific service, you can add the service name to the end of the logs command (for example, `docker compose logs -f app`). -4. At this point, you should be able to open your app in your browser on [http://localhost:3000](http://localhost:3000){:target="_blank" rel="noopener" class="_"} and see it running. +4. At this point, you should be able to open your app in your browser on [http://localhost:3000](http://localhost:3000) and see it running. ## See the app stack in Docker Dashboard @@ -269,7 +270,7 @@ for the entire app. The containers will stop and the network will be removed. >remove the volumes, you need to add the `--volumes` flag. > >The Docker Dashboard does not remove volumes when you delete the app stack. -{: .warning} +{ .warning } ## Summary @@ -285,4 +286,4 @@ Related information: Next, you'll learn about a few best practices you can use to improve your Dockerfile. -[Image-building best practices](09_image_best.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Image-building best practices" url="09_image_best.md" >}} \ No newline at end of file diff --git a/content/get-started/09_image_best.md b/content/get-started/09_image_best.md index 3f03ed58ea..4c9d811085 100644 --- a/content/get-started/09_image_best.md +++ b/content/get-started/09_image_best.md @@ -1,6 +1,7 @@ --- -title: "Image-building best practices" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop +title: Image-building best practices +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop description: Tips for building images for your application --- @@ -96,7 +97,7 @@ dependencies if there was a change to the `package.json`. it would possibly overwrite files which were created by the command in the `RUN` step. For further details on why this is recommended for Node.js applications and other best practices, have a look at their guide on - [Dockerizing a Node.js web app](https://nodejs.org/en/docs/guides/nodejs-docker-webapp/){:target="_blank" rel="noopener" class="_"}. + [Dockerizing a Node.js web app](https://nodejs.org/en/docs/guides/nodejs-docker-webapp/). 3. Build a new image using `docker build`. @@ -220,4 +221,4 @@ Related information: In the next section, you'll learn about additional resources you can use to continue learning about containers. -[What next](11_what_next.md){: .button .primary-btn} +{{< button text="What next" url="11_what_next.md" >}} \ No newline at end of file diff --git a/content/get-started/11_what_next.md b/content/get-started/11_what_next.md index 8f3860a1f3..2da650229a 100644 --- a/content/get-started/11_what_next.md +++ b/content/get-started/11_what_next.md @@ -1,6 +1,7 @@ --- -title: "What next after getting started" -keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop +title: What next after getting started +keywords: get started, setup, orientation, quickstart, intro, concepts, containers, + docker desktop description: Making sure you have more ideas of what you could do next with your application --- @@ -23,8 +24,8 @@ a container quitting) and then work to make the actual state reflect the expecte ## Cloud Native Computing Foundation projects The CNCF is a vendor-neutral home for various open-source projects, including Kubernetes, Prometheus, -Envoy, Linkerd, NATS, and more. You can view the [graduated and incubated projects here](https://www.cncf.io/projects/){:target="_blank" rel="noopener" class="_"} -and the entire [CNCF Landscape here](https://landscape.cncf.io/){:target="_blank" rel="noopener" class="_"}. There are a lot of projects to help +Envoy, Linkerd, NATS, and more. You can view the [graduated and incubated projects here](https://www.cncf.io/projects/) +and the entire [CNCF Landscape here](https://landscape.cncf.io/). There are a lot of projects to help solve problems around monitoring, logging, security, image registries, messaging, and more. ## Getting started video workshop @@ -48,5 +49,4 @@ If you'd like to see how containers are built from scratch, Liz Rice from Aqua S ## Language-specific guides -If you are looking for information on how to containerize an application using your favorite language, see the [Language-specific guides](../language/index.md). - +If you are looking for information on how to containerize an application using your favorite language, see the [Language-specific guides](../language/index.md). \ No newline at end of file diff --git a/content/get-started/_index.md b/content/get-started/_index.md index bdf3204053..cb96ed3f6c 100644 --- a/content/get-started/_index.md +++ b/content/get-started/_index.md @@ -1,8 +1,11 @@ --- title: Overview of the get started guide -keywords: docker basics, how to start a docker container, container settings, setup docker, how to setup docker, setting up docker, docker container guide, how to get started with docker -description: Get started with the Docker basics in this comprehensive overview, You'll learn about containers, images, and how to containerize your first application. -redirect_from: +keywords: docker basics, how to start a docker container, container settings, setup + docker, how to setup docker, setting up docker, docker container guide, how to get + started with docker +description: Get started with the Docker basics in this comprehensive overview, You'll + learn about containers, images, and how to containerize your first application. +aliases: - /engine/getstarted-voting-app/ - /engine/getstarted-voting-app/cleanup/ - /engine/getstarted-voting-app/create-swarm/ @@ -86,5 +89,4 @@ In this section, you learned about containers and images. Next, you'll containerize a simple application and get hands-on with the concepts. -[Containerize an application](02_our_app.md){: .button .primary-btn} - +{{< button text="Containerize an application" url="02_our_app.md" >}} \ No newline at end of file diff --git a/content/get-started/hands-on-overview.md b/content/get-started/hands-on-overview.md index a4172295ce..ef35b3b8ae 100644 --- a/content/get-started/hands-on-overview.md +++ b/content/get-started/hands-on-overview.md @@ -3,20 +3,20 @@ title: Docker Desktop hands-on guides keywords: get started, setup, orientation, quickstart, intro, concepts description: Overview of Docker Desktop hands-on guides grid: - - title: "What is a container?" - icon: "help" - link: "/get-started/what-is-a-container/" - - title: "How do I run a container?" - icon: "edit_document" - link: "/get-started/run-your-own-container/" - - title: "Run Docker Hub images" - icon: "layers" - link: "/get-started/run-docker-hub-images/" - - title: "Publish your images" - icon: "publish" - link: "/get-started/publish-your-own-image/" +- title: What is a container? + icon: help + link: /get-started/what-is-a-container/ +- title: How do I run a container? + icon: edit_document + link: /get-started/run-your-own-container/ +- title: Run Docker Hub images + icon: layers + link: /get-started/run-docker-hub-images/ +- title: Publish your images + icon: publish + link: /get-started/publish-your-own-image/ --- Use the resources in this section to learn Docker concepts by using Docker Desktop. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/get-started/kube-deploy.md b/content/get-started/kube-deploy.md index 2d0ca3be1f..c84979dd37 100644 --- a/content/get-started/kube-deploy.md +++ b/content/get-started/kube-deploy.md @@ -1,5 +1,5 @@ --- -title: "Deploy to Kubernetes" +title: Deploy to Kubernetes keywords: kubernetes, pods, deployments, kubernetes services description: Learn how to describe and deploy a simple application on Kubernetes. --- @@ -132,4 +132,4 @@ Further documentation for all new Kubernetes objects used in this article are av - [Kubernetes Pods](https://kubernetes.io/docs/concepts/workloads/pods/pod/) - [Kubernetes Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) - - [Kubernetes Services](https://kubernetes.io/docs/concepts/services-networking/service/) + - [Kubernetes Services](https://kubernetes.io/docs/concepts/services-networking/service/) \ No newline at end of file diff --git a/content/get-started/orchestration.md b/content/get-started/orchestration.md index 2c2f179c32..953935872a 100644 --- a/content/get-started/orchestration.md +++ b/content/get-started/orchestration.md @@ -1,5 +1,5 @@ --- -title: "Deployment and orchestration" +title: Deployment and orchestration keywords: orchestration, deploy, kubernetes, swarm, description: Get oriented on some basics of Docker and install Docker Desktop. --- @@ -312,4 +312,4 @@ Further documentation for all CLI commands used in this article are available he - [`kubectl logs`](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs) - [`kubectl delete`](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#delete) - [`docker swarm init`](/engine/reference/commandline/swarm_init/) -- [`docker service *`](/engine/reference/commandline/service/) +- [`docker service *`](/engine/reference/commandline/service/) \ No newline at end of file diff --git a/content/get-started/overview.md b/content/get-started/overview.md index ece6f961e3..dfe4a66518 100644 --- a/content/get-started/overview.md +++ b/content/get-started/overview.md @@ -1,13 +1,16 @@ --- -description: Get an in-depth overview of the Docker platform including what it can be used for, the architecture it employs, and its underlying technology. -keywords: what is a docker, docker daemon, why use docker, docker architecture, what to use docker for, docker client, what is docker for, why docker, uses for docker, what is docker container used for, what are docker containers used for -redirect_from: +description: Get an in-depth overview of the Docker platform including what it can + be used for, the architecture it employs, and its underlying technology. +keywords: what is a docker, docker daemon, why use docker, docker architecture, what + to use docker for, docker client, what is docker for, why docker, uses for docker, + what is docker container used for, what are docker containers used for +title: Docker overview +aliases: - /introduction/understanding-docker/ - /engine/userguide/basics/ - /engine/introduction/understanding-docker/ - /engine/understanding-docker/ - /engine/docker-overview/ -title: Docker overview --- Docker is an open platform for developing, shipping, and running applications. @@ -198,4 +201,4 @@ in a separate namespace and its access is limited to that namespace. ## Next steps - [Install Docker](../get-docker.md) -- [Get started with Docker](index.md) +- [Get started with Docker](index.md) \ No newline at end of file diff --git a/content/get-started/publish-your-own-image.md b/content/get-started/publish-your-own-image.md index 4334fffd4d..c514affbed 100644 --- a/content/get-started/publish-your-own-image.md +++ b/content/get-started/publish-your-own-image.md @@ -12,7 +12,7 @@ Before you publish your image, you need an image to publish. For this guide, use To get the image, use Docker Desktop to search for the `welcome-to-docker` image, and then select **Pull**. -![Pulling the welcome-to-docker image](images/getting-started-pull.gif){:width="500px"} +![Pulling the welcome-to-docker image](images/getting-started-pull.gif) ## Step 2: Sign in to Docker @@ -36,7 +36,7 @@ In Docker Desktop, go to the **Images** tab and find your image. In the **Action ## Step 5: Verify the image is on Docker Hub -That's it! Your image is now shared on Docker Hub. In your browser, go to [Docker Hub](https://hub.docker.com){:target="_blank" rel="noopener" class="_"} and verify that you see the `welcome-to-docker` repository. +That's it! Your image is now shared on Docker Hub. In your browser, go to [Docker Hub](https://hub.docker.com) and verify that you see the `welcome-to-docker` repository. ## What's next @@ -46,4 +46,4 @@ In this guide you learned how to publish your own image to Docker Hub. Continue - [Python](../language/python/index.md) - [Go](../language/golang/index.md) - [Java](../language/java/index.md) - - [C# (.NET)](../language/dotnet/index.md) + - [C# (.NET)](../language/dotnet/index.md) \ No newline at end of file diff --git a/content/get-started/resources.md b/content/get-started/resources.md index 65f35509f2..62f2e69d29 100644 --- a/content/get-started/resources.md +++ b/content/get-started/resources.md @@ -1,6 +1,7 @@ --- -title: "Educational resources" -keywords: get started, setup, orientation, quickstart, intro, concepts, kubernetes, docker desktop +title: Educational resources +keywords: get started, setup, orientation, quickstart, intro, concepts, kubernetes, + docker desktop description: Get started resources learning docker --- @@ -8,9 +9,9 @@ Docker and the broader community of Docker experts have put together many differ ## Hosted labs -These self-paced and hands-on workshops use a free, hosted environment ([Play with Kubernetes](https://labs.play-with-k8s.com/){:target="_blank" rel="noopener" class="_"}) that does not require any installation. Follow along and learn more about Kubernetes. +These self-paced and hands-on workshops use a free, hosted environment ([Play with Kubernetes](https://labs.play-with-k8s.com/)) that does not require any installation. Follow along and learn more about Kubernetes. -* [Kubernetes Workshop](https://training.play-with-kubernetes.com/kubernetes-workshop/){:target="_blank" rel="noopener" class="_"} +* [Kubernetes Workshop](https://training.play-with-kubernetes.com/kubernetes-workshop/) * Labs are free but require registration with a Docker ID. @@ -19,45 +20,45 @@ These self-paced and hands-on workshops use a free, hosted environment ([Play wi Created by experts in the Docker community, these free tutorials provide guided step-by-step workflows for working with the Docker platform. * **Integrating Docker with Your IDE** - * [Java Development: Eclipse](https://training.play-with-docker.com/java-debugging-eclipse/){:target="_blank" rel="noopener" class="_"} - * [Java Development: IntelliJ](https://training.play-with-docker.com/java-debugging-intellij/){:target="_blank" rel="noopener" class="_"} - * [Java Development: Netbeans](https://training.play-with-docker.com/java-debugging-netbeans/){:target="_blank" rel="noopener" class="_"} - * [Live Debugging Node.js with Docker and Visual Studio Code](https://training.play-with-docker.com/nodejs-live-debugging/){:target="_blank" rel="noopener" class="_"} + * [Java Development: Eclipse](https://training.play-with-docker.com/java-debugging-eclipse/) + * [Java Development: IntelliJ](https://training.play-with-docker.com/java-debugging-intellij/) + * [Java Development: Netbeans](https://training.play-with-docker.com/java-debugging-netbeans/) + * [Live Debugging Node.js with Docker and Visual Studio Code](https://training.play-with-docker.com/nodejs-live-debugging/) * **Windows Containers** - * [Windows Container Setup](https://training.play-with-docker.com/windows-containers-setup/){:target="_blank" rel="noopener" class="_"} - * [Windows Container Basics](https://training.play-with-docker.com/windows-containers-basics/){:target="_blank" rel="noopener" class="_"} - * [Windows Containers Multi-Container Applications](https://training.play-with-docker.com/windows-containers-multicontainer/){:target="_blank" rel="noopener" class="_"} + * [Windows Container Setup](https://training.play-with-docker.com/windows-containers-setup/) + * [Windows Container Basics](https://training.play-with-docker.com/windows-containers-basics/) + * [Windows Containers Multi-Container Applications](https://training.play-with-docker.com/windows-containers-multicontainer/) ## Books -If books are your preferred learning style, check out these written by the [Docker Captains](https://www.docker.com/community/captains){:target="_blank" rel="noopener" class="_"}. Docker Captain is a distinction that Docker awards to select members of the community that are both experts in their field and are committed to sharing their Docker knowledge with others. +If books are your preferred learning style, check out these written by the [Docker Captains](https://www.docker.com/community/captains). Docker Captain is a distinction that Docker awards to select members of the community that are both experts in their field and are committed to sharing their Docker knowledge with others. -* [Learn Docker in a Month of Lunches](https://www.manning.com/books/learn-docker-in-a-month-of-lunches){:target="_blank" rel="noopener" class="_"}, Elton Stoneman. Use the code `stonemanpc` for a 40% discount. -* [Docker on Windows: From 101 to Production with Docker on Windows](https://www.amazon.com/Docker-Windows-Elton-Stoneman-ebook/dp/B0711Y4J9K/){:target="_blank" rel="noopener" class="_"}, Elton Stoneman -* [Learn Kubernetes in a Month of Lunches](https://www.manning.com/books/learn-kubernetes-in-a-month-of-lunches){:target="_blank" rel="noopener" class="_"}, Elton Stoneman. Use the code `stonemanpc` for a 40% discount. -* [Docker in Action 2nd Edition](https://www.manning.com/books/docker-in-action-second-edition){:target="_blank" rel="noopener" class="_"} Jeff Nickoloff, Oct 2019 -* [The Kubernetes Book](https://www.amazon.com/Kubernetes-Book-Nigel-Poulton/dp/1521823634/ref=sr_1_3?ie=UTF8&qid=1509660871&sr=8-3&keywords=nigel+poulton){:target="_blank" rel="noopener" class="_"}, Nigel Poulton, Nov 2018 -* [Docker Deep Dive](https://www.amazon.com/Docker-Deep-Dive-Nigel-Poulton/dp/1521822808/ref=sr_1_1?ie=UTF8&qid=1509660871&sr=8-1&keywords=nigel+poulton){:target="_blank" rel="noopener" class="_"}, Nigel Poulton, March 2018 -* [Portuguese] [Docker para desenvolvedores](https://leanpub.com/dockerparadesenvolvedores){:target="_blank" rel="noopener" class="_"} (2017) by Rafael Gomes -* [Spanish] [Érase una vez Docker](https://leanpub.com/erase-una-vez-docker){:target="_blank" rel="noopener" class="_"}, Manuel Morejón, March 2023 -* [Spanish] [Érase una vez Kubernetes](https://leanpub.com/erase-una-vez-kubernetes){:target="_blank" rel="noopener" class="_"}, Manuel Morejón, Jan 2022 +* [Learn Docker in a Month of Lunches](https://www.manning.com/books/learn-docker-in-a-month-of-lunches), Elton Stoneman. Use the code `stonemanpc` for a 40% discount. +* [Docker on Windows: From 101 to Production with Docker on Windows](https://www.amazon.com/Docker-Windows-Elton-Stoneman-ebook/dp/B0711Y4J9K/), Elton Stoneman +* [Learn Kubernetes in a Month of Lunches](https://www.manning.com/books/learn-kubernetes-in-a-month-of-lunches), Elton Stoneman. Use the code `stonemanpc` for a 40% discount. +* [Docker in Action 2nd Edition](https://www.manning.com/books/docker-in-action-second-edition) Jeff Nickoloff, Oct 2019 +* [The Kubernetes Book](https://www.amazon.com/Kubernetes-Book-Nigel-Poulton/dp/1521823634/ref=sr_1_3?ie=UTF8&qid=1509660871&sr=8-3&keywords=nigel+poulton), Nigel Poulton, Nov 2018 +* [Docker Deep Dive](https://www.amazon.com/Docker-Deep-Dive-Nigel-Poulton/dp/1521822808/ref=sr_1_1?ie=UTF8&qid=1509660871&sr=8-1&keywords=nigel+poulton), Nigel Poulton, March 2018 +* [Portuguese] [Docker para desenvolvedores](https://leanpub.com/dockerparadesenvolvedores) (2017) by Rafael Gomes +* [Spanish] [Érase una vez Docker](https://leanpub.com/erase-una-vez-docker), Manuel Morejón, March 2023 +* [Spanish] [Érase una vez Kubernetes](https://leanpub.com/erase-una-vez-kubernetes), Manuel Morejón, Jan 2022 ## CLI cheat sheet -The [Docker CLI cheat sheet](/docker_cheatsheet.pdf){: target="_blank" rel="noopener" class="_"} features the common Docker CLI commands for easy reference. It covers working with Images, Containers, Docker Hub, and other general purpose commands. +The [Docker CLI cheat sheet](/docker_cheatsheet.pdf) features the common Docker CLI commands for easy reference. It covers working with Images, Containers, Docker Hub, and other general purpose commands. ## Self-Paced online learning A number of Docker Captains have also created video courses on Docker and Kubernetes. -* [Bret Fisher](https://www.bretfisher.com/courses/){:target="_blank" rel="noopener" class="_"}: Docker Mastery, Docker Swarm Mastery, Docker Mastery for Node.js Projects -* [Elton Stoneman](https://docker4.net/udemy){:target="_blank" rel="noopener" class="_"}: Docker for .NET Apps - on Linux and Windows. Includes the discount code `644ABCBC33F474541885`. -* [Nick Janetakis](https://nickjanetakis.com/courses/){:target="_blank" rel="noopener" class="_"} Dive into Docker, Docker for DevOps -* [Nigel Poulton](https://nigelpoulton.com/video-courses){:target="_blank" rel="noopener" class="_"}: Kubernetes 101, Getting Started with Kubernetes, Docker and Kubernetes: The Big Picture, Kubernetes Deep Dive, Docker Deep Dive -* [Arun Gupta](https://www.lynda.com/Docker-tutorials/Docker-Java-developers/576584-2.html){:target="_blank" rel="noopener" class="_"}: Docker for Java Developers -* [Ajeet Singh Raina](https://collabnix.com/){:target="_blank" rel="noopener" class="_"}: Docker and Kubernetes Labs -* [French] [Luc Juggery](https://www.udemy.com/user/lucjuggery/){:target="_blank" rel="noopener" class="_"}: Introduction to Kubernetes, The Docker Platform +* [Bret Fisher](https://www.bretfisher.com/courses/): Docker Mastery, Docker Swarm Mastery, Docker Mastery for Node.js Projects +* [Elton Stoneman](https://docker4.net/udemy): Docker for .NET Apps - on Linux and Windows. Includes the discount code `644ABCBC33F474541885`. +* [Nick Janetakis](https://nickjanetakis.com/courses/) Dive into Docker, Docker for DevOps +* [Nigel Poulton](https://nigelpoulton.com/video-courses): Kubernetes 101, Getting Started with Kubernetes, Docker and Kubernetes: The Big Picture, Kubernetes Deep Dive, Docker Deep Dive +* [Arun Gupta](https://www.lynda.com/Docker-tutorials/Docker-Java-developers/576584-2.html): Docker for Java Developers +* [Ajeet Singh Raina](https://collabnix.com/): Docker and Kubernetes Labs +* [French] [Luc Juggery](https://www.udemy.com/user/lucjuggery/): Introduction to Kubernetes, The Docker Platform \* Many of the courses are fee-based @@ -69,4 +70,4 @@ A number of Docker Captains have also created video courses on Docker and Kubern > members. This is not an officially translated version of Docker docs and it may not be up to date. > You must use the community-translated docs at your own discretion. -- [Subset of Docker docs in Japanese](https://docs.docker.jp/index.html){:target="_blank" rel="noopener" class="_"} translated by Docker Captain [Masahito Zembutsu](https://github.com/zembutsu){:target="_blank" rel="noopener" class="_"}. +- [Subset of Docker docs in Japanese](https://docs.docker.jp/index.html) translated by Docker Captain [Masahito Zembutsu](https://github.com/zembutsu). \ No newline at end of file diff --git a/content/get-started/run-docker-hub-images.md b/content/get-started/run-docker-hub-images.md index c60203ab42..1ce1511730 100644 --- a/content/get-started/run-docker-hub-images.md +++ b/content/get-started/run-docker-hub-images.md @@ -4,32 +4,32 @@ keywords: get started, quick start, intro, concepts description: Learn how to run Docker Hub images --- -You can share and store images in Docker Hub ([http://hub.docker.com](http://hub.docker.com){:target="_blank" rel="noopener" class="_"}). Docker hub has over 100,000 images created by developers that you can run locally. You can search for Docker Hub images and run them directly from Docker Desktop. +You can share and store images in Docker Hub ([http://hub.docker.com](http://hub.docker.com)). Docker hub has over 100,000 images created by developers that you can run locally. You can search for Docker Hub images and run them directly from Docker Desktop. ## Step 1: Search for the image You can search for Docker Hub images on Docker Desktop. Use the search bar, or use the shortcut ⌘K on Mac or Ctrl + K on Windows. In the search bar, specify `welcome-to-docker` to find the `docker/welcome-to-docker` image used in this guide. -![Search Docker Desktop for the welcome-to-docker image](images/getting-started-search.png){:width="500px"} +![Search Docker Desktop for the welcome-to-docker image](images/getting-started-search.png) ## Step 2: Run the image To run the `docker/welcome-to-docker` image, select **Run**. When the **Optional settings** appear, specify the **Host port** number `8090` and then select **Run**. -![Running the image in Docker Desktop](images/getting-started-run.gif){:width="500px"} +![Running the image in Docker Desktop](images/getting-started-run.gif) > **Note** > -> Many images hosted on Docker Hub have a description that highlights what settings must be set in order to run them. You can read the description for the image on Docker Hub by selecting **View on Hub** or by searching for the image directly on [https://hub.docker.com](https://hub.docker.com){:target="_blank" rel="noopener" class="_"}. +> Many images hosted on Docker Hub have a description that highlights what settings must be set in order to run them. You can read the description for the image on Docker Hub by selecting **View on Hub** or by searching for the image directly on [https://hub.docker.com](https://hub.docker.com). ## Step 3: Explore the container That's it! The container is ready to use. Go to the **Containers** tab in Docker Desktop to view the container. -![Viewing the Containers tab in Docker Desktop](images/getting-started-view.png){:width="500px"} +![Viewing the Containers tab in Docker Desktop](images/getting-started-view.png) ## What's next In this guide, you ran someone else's image from Docker Hub. Continue to the next guide to learn how you can publish your own image to Docker Hub. -[Publish your images](./publish-your-own-image.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Publish your images" url="./publish-your-own-image.md" >}} \ No newline at end of file diff --git a/content/get-started/run-your-own-container.md b/content/get-started/run-your-own-container.md index e0265fddb6..ddabe44ae9 100644 --- a/content/get-started/run-your-own-container.md +++ b/content/get-started/run-your-own-container.md @@ -24,7 +24,7 @@ $ git clone https://github.com/docker/welcome-to-docker If you don't have Git, download the source and extract it. -[Download the source](https://github.com/docker/welcome-to-docker/archive/refs/heads/main.zip){: .button .primary-btn} +{{< button text="Download the source" url="https://github.com/docker/welcome-to-docker/archive/refs/heads/main.zip" >}} {{< /tab >}} {{< /tabs >}} @@ -47,17 +47,17 @@ Building the image may take some time. After your image is built, you can view y To run your image as a container, go to the **Images** tab, and then select **Run** in the **Actions** column of your image. When the **Optional settings** appear, specify the **Host port** number `8089` and then select **Run**. -![Running an image in Docker Desktop](images/getting-started-run-image.gif){:width="500px"} +![Running an image in Docker Desktop](images/getting-started-run-image.gif) ## Step 5: Verify that your container is running -You can use Docker Desktop to view and access running containers. Go to the **Containers** tab to view your container and select the link in the **Port(s)** column or go to [http://localhost:8089](http://localhost:8089){:target="_blank" rel="noopener" class="_"} to verify that the application is running. +You can use Docker Desktop to view and access running containers. Go to the **Containers** tab to view your container and select the link in the **Port(s)** column or go to [http://localhost:8089](http://localhost:8089) to verify that the application is running. ## What's next In this guide, you built your own image. When running containers on Docker Desktop, you don’t need to build your own image from scratch. You can also run images created by others on Docker Hub. -[Run Docker Hub images](./run-docker-hub-images.md){: .button .primary-btn} +{{< button text="Run Docker Hub images" url="./run-docker-hub-images.md" >}} ## Dive deeper @@ -74,4 +74,4 @@ If you want to learn more about creating images for applications in other langua When you built the image, you used the `docker build` command. Here are what the different parts of the `docker build` command do: - `docker build`: This command builds the image. It needs one argument, the source folder for the Dockerfile that needs to be built. In this case, it’s the Dockerfile in the current folder, `.`. - - `-t welcome-to-docker`: The `-t` flag tags the image with a unique name. In this case, `welcome-to-docker`. + - `-t welcome-to-docker`: The `-t` flag tags the image with a unique name. In this case, `welcome-to-docker`. \ No newline at end of file diff --git a/content/get-started/swarm-deploy.md b/content/get-started/swarm-deploy.md index ec4dde5ee1..a6814d2901 100644 --- a/content/get-started/swarm-deploy.md +++ b/content/get-started/swarm-deploy.md @@ -1,12 +1,12 @@ --- -title: "Deploy to Swarm" +title: Deploy to Swarm keywords: swarm, swarm services, stacks description: Learn how to describe and deploy a simple application on Docker Swarm. -redirect_from: +aliases: - /get-started/part4/ --- -{% include swarm-mode.md %} +{{< include "swarm-mode.md" >}} ## Prerequisites @@ -28,7 +28,7 @@ Swarm never creates individual containers like we did in the previous step of th Let's write a simple stack file to run and manage our Todo app, the container `getting-started` image created in [Part 2](02_our_app.md) of the Quickstart tutorial. Place the following in a file called `bb-stack.yaml`: -{% include swarm-compose-compat.md %} +{{< include "swarm-compose-compat.md" >}} ```yaml version: '3.7' @@ -98,4 +98,4 @@ Further documentation for all new Swarm objects and CLI commands used in this ar - [Swarm Mode Services](../engine/swarm/how-swarm-mode-works/services.md) - [Swarm Stacks](../engine/swarm/stack-deploy.md) - [`docker stack *`](/engine/reference/commandline/stack/) - - [`docker service *`](/engine/reference/commandline/service/) + - [`docker service *`](/engine/reference/commandline/service/) \ No newline at end of file diff --git a/content/get-started/what-is-a-container.md b/content/get-started/what-is-a-container.md index b784b0cc21..87d0d400f4 100644 --- a/content/get-started/what-is-a-container.md +++ b/content/get-started/what-is-a-container.md @@ -20,31 +20,31 @@ $ docker run -p 8088:80 -d --name welcome-to-docker docker/welcome-to-docker You just ran a container! Open Docker Desktop to take a look. This container runs a simple web server that displays HTML text. When working with more complex projects, you'll run different parts in different containers. For example, a different container for the frontend, backend, and database. In this guide, you only have a simple frontend container. -![Docker Desktop with get-started container running](images/getting-started-container.png){:width="500px"} +![Docker Desktop with get-started container running](images/getting-started-container.png) ## Step 3: View the frontend -The frontend is accessible on port 8088 of your local host. Select the link in the **Port(s)** column of your container, or visit [http://localhost:8088](http://localhost:8088){:target="_blank" rel="noopener" class="_"} in your browser to check it out. +The frontend is accessible on port 8088 of your local host. Select the link in the **Port(s)** column of your container, or visit [http://localhost:8088](http://localhost:8088) in your browser to check it out. -![Accessing container frontend from Docker Desktop](images/getting-started-frontend.png){:width="500px"} +![Accessing container frontend from Docker Desktop](images/getting-started-frontend.png) ## Step 4: Explore your container Docker Desktop allows you to easily view and interact with different aspects of your container. Try it out yourself. Select your container and then select **Files** to explore your container's isolated file system. -![Viewing container details in Docker Desktop](images/getting-started-explore-container.gif){:width="500px"} +![Viewing container details in Docker Desktop](images/getting-started-explore-container.gif) ## Step 5: Stop your container The `welcome-to-docker` container continues to run until you stop it. To stop the container in Docker Desktop, go to the **Containers** tab and select the **Stop** icon in the **Actions** column of your container. -![Stopping a container in Docker Desktop](images/getting-started-stop.png){:width="500px"} +![Stopping a container in Docker Desktop](images/getting-started-stop.png) ## What's next In this guide, you explored what a container is. Continue to the next guide to learn what you need to create and run your own container. -[Run your own container](./run-your-own-container.md){: .button .primary-btn} +{{< button text="Run your own container" url="./run-your-own-container.md" >}} ## Dive deeper diff --git a/content/glossary.md b/content/glossary.md index 04cf0224ed..d9c88e2334 100644 --- a/content/glossary.md +++ b/content/glossary.md @@ -1,16 +1,17 @@ --- -title: "Glossary" -description: "Glossary of terms used around Docker" -keywords: "glossary, docker, terms, definitions" +title: Glossary +description: Glossary of terms used around Docker +keywords: glossary, docker, terms, definitions layout: glossary notoc: true skip_feedback: true skip_read_time: true -redirect_from: +aliases: - /engine/reference/glossary/ - /reference/glossary/ --- + +--> \ No newline at end of file diff --git a/content/includes/aci-ecs-eol.md b/content/includes/aci-ecs-eol.md index 45de328b5e..10ab16a360 100644 --- a/content/includes/aci-ecs-eol.md +++ b/content/includes/aci-ecs-eol.md @@ -1,4 +1,4 @@ >**Important** > >Docker Compose's integration for ECS and ACI is retiring in November 2023. -{: .important} +{ .important } \ No newline at end of file diff --git a/content/includes/admin-company-overview.md b/content/includes/admin-company-overview.md index 15923850c4..74dfc31223 100644 --- a/content/includes/admin-company-overview.md +++ b/content/includes/admin-company-overview.md @@ -2,7 +2,7 @@ A company provides a single point of visibility across multiple organizations. T The following diagram depicts the setup of a company and how it relates to associated organizations. -![company-hierarchy](/admin/images/docker-hierarchy-company.svg){: width="700px" } +![company-hierarchy](/admin/images/docker-hierarchy-company.svg) ## Key features diff --git a/content/includes/admin-early-access.md b/content/includes/admin-early-access.md index 6a1d7283e9..b9028ff93f 100644 --- a/content/includes/admin-early-access.md +++ b/content/includes/admin-early-access.md @@ -3,4 +3,4 @@ > Docker Admin is an [early access](/release-lifecycle#early-access-ea) product. > > It's currently available to all company owners and organization owners that have a Docker Business or Docker Team subscription. You can still manage companies and organizations in Docker Hub. For details about managing companies or organizations in Docker Hub, see [Administration and security](/docker-hub/admin-overview/). -{: .restricted} \ No newline at end of file +{ .restricted } \ No newline at end of file diff --git a/content/includes/admin-org-overview.md b/content/includes/admin-org-overview.md index 8901e22a83..7fd61ff439 100644 --- a/content/includes/admin-org-overview.md +++ b/content/includes/admin-org-overview.md @@ -11,4 +11,4 @@ organization. The following diagram depicts the setup of an organization and how it relates to teams. Teams are an optional feature that owners can use to group members and assign permissions. -![organization-hierarchy](/admin/images/docker-hierarchy-org.svg){: width="700px" } \ No newline at end of file +![organization-hierarchy](/admin/images/docker-hierarchy-org.svg) \ No newline at end of file diff --git a/content/includes/api-version-matrix.md b/content/includes/api-version-matrix.md index 92ec0b33c2..560746724e 100644 --- a/content/includes/api-version-matrix.md +++ b/content/includes/api-version-matrix.md @@ -28,4 +28,4 @@ | 1.9 | [1.21](/engine/api/v1.21/) | [changes](/engine/api/version-history/#v121-api-changes) | | 1.8 | [1.20](/engine/api/v1.20/) | [changes](/engine/api/version-history/#v120-api-changes) | | 1.7 | [1.19](/engine/api/v1.19/) | [changes](/engine/api/version-history/#v119-api-changes) | -| 1.6 | [1.18](/engine/api/v1.18/) | [changes](/engine/api/version-history/#v118-api-changes) | +| 1.6 | [1.18](/engine/api/v1.18/) | [changes](/engine/api/version-history/#v118-api-changes) | \ No newline at end of file diff --git a/content/includes/beta.md b/content/includes/beta.md index b65d244466..6b54157cff 100644 --- a/content/includes/beta.md +++ b/content/includes/beta.md @@ -2,6 +2,4 @@ Beta features provide access to future product functionality. These features are intended for testing and feedback only as they may change between releases without warning or remove them entirely from a future release. Beta features must not be used in production environments. -Docker doesn't offer support for beta features. - - +Docker doesn't offer support for beta features. \ No newline at end of file diff --git a/content/includes/build-feature-state.md b/content/includes/build-feature-state.md index 2a1f01e222..91355c3389 100644 --- a/content/includes/build-feature-state.md +++ b/content/includes/build-feature-state.md @@ -1,2 +1,2 @@ > This feature is supported in BuildKit version `{{ include.buildkit_v }}` -> and Buildx version `{{ include.buildx_v }}`. +> and Buildx version `{{ include.buildx_v }}`. \ No newline at end of file diff --git a/content/includes/buildx-v0.10-disclaimer.md b/content/includes/buildx-v0.10-disclaimer.md index 5eac8cb9fc..7c2ebb79cc 100644 --- a/content/includes/buildx-v0.10-disclaimer.md +++ b/content/includes/buildx-v0.10-disclaimer.md @@ -1,8 +1,8 @@ > **Note** > -> Buildx v0.10 enables support for a minimal [SLSA Provenance](https://slsa.dev/provenance/){:target="blank" rel="noopener" class=""} -> attestation, which requires support for [OCI-compliant](https://github.com/opencontainers/image-spec){:target="blank" rel="noopener" class=""} +> Buildx v0.10 enables support for a minimal [SLSA Provenance](https://slsa.dev/provenance/) +> attestation, which requires support for [OCI-compliant](https://github.com/opencontainers/image-spec) > multi-platform images. This may introduce issues with registry and runtime support -> (e.g. [Google Cloud Run and AWS Lambda](https://github.com/docker/buildx/issues/1533){:target="blank" rel="noopener" class=""}). +> (e.g. [Google Cloud Run and AWS Lambda](https://github.com/docker/buildx/issues/1533)). > You can optionally disable the default provenance attestation functionality -> using `--provenance=false`. +> using `--provenance=false`. \ No newline at end of file diff --git a/content/includes/compose-eol.md b/content/includes/compose-eol.md index 62f83ffb5b..80d8c290c3 100644 --- a/content/includes/compose-eol.md +++ b/content/includes/compose-eol.md @@ -6,4 +6,4 @@ > For more information, see [Migrate to Compose V2](/compose/migrate). > > Docker's documentation refers to and describes Compose V2 functionality. -{: .important} +{ .important } \ No newline at end of file diff --git a/content/includes/configure-registry-json.md b/content/includes/configure-registry-json.md index f7602d4236..2b56d37bf3 100644 --- a/content/includes/configure-registry-json.md +++ b/content/includes/configure-registry-json.md @@ -23,7 +23,7 @@ The `registry.json` file must contain the following contents, where `myorg` is r ``` In Docker Hub, you can download the `registry.json` file for your organization or copy the specific commands to create the file for your organization. To download the file or copy the commands from Docker Hub: -1. Log in to [Docker Hub](http://hub.docker.com){: target="_blank" rel="noopener" class="_"} as an organization owner. +1. Log in to [Docker Hub](http://hub.docker.com) as an organization owner. 2. Go to **Organizations** > **_Your Organization_** > **Settings**. 3. Select **Enforce Sign-in** and continue with the on-screen instructions for Windows, Mac, or Linux. @@ -162,4 +162,4 @@ $ sudo ls -l /usr/share/docker-desktop/registry/registry.json ``` {{< /tab >}} -{{< /tabs >}} +{{< /tabs >}} \ No newline at end of file diff --git a/content/includes/content/compose-extfields-sub.md b/content/includes/content/compose-extfields-sub.md index c7adc8b276..3f7f04f8e7 100644 --- a/content/includes/content/compose-extfields-sub.md +++ b/content/includes/content/compose-extfields-sub.md @@ -9,7 +9,7 @@ your Compose file and their name start with the `x-` character sequence. > of service, volume, network, config and secret definitions. ```yaml -version: "{{ site.compose_file_v3 }}" +version: "{{% param "compose_file_v3" %}}" x-custom: items: - a @@ -35,7 +35,7 @@ logging: You may write your Compose file as follows: ```yaml -version: "{{ site.compose_file_v3 }}" +version: "{{% param "compose_file_v3" %}}" x-logging: &default-logging options: @@ -56,7 +56,7 @@ It is also possible to partially override values in extension fields using the [YAML merge type](https://yaml.org/type/merge.html). For example: ```yaml -version: "{{ site.compose_file_v3 }}" +version: "{{% param "compose_file_v3" %}}" x-volumes: &default-volume driver: foobar-storage @@ -74,4 +74,4 @@ volumes: << : *default-volume driver: default name: volume-local -``` +``` \ No newline at end of file diff --git a/content/includes/content/compose-matrix.md b/content/includes/content/compose-matrix.md index 9eec23afe2..def6b1aba3 100644 --- a/content/includes/content/compose-matrix.md +++ b/content/includes/content/compose-matrix.md @@ -26,4 +26,4 @@ do not necessarily increment with each release. For example, Compose file format 1.10.0](https://github.com/docker/compose/releases/tag/1.10.0), and versioned gradually in subsequent releases. -The latest Compose file format is defined by the [Compose Specification](https://github.com/compose-spec/compose-spec/blob/master/spec.md){:target="_blank" rel="noopener" class="_"} and is implemented by Docker Compose **1.27.0+**. +The latest Compose file format is defined by the [Compose Specification](https://github.com/compose-spec/compose-spec/blob/master/spec.md) and is implemented by Docker Compose **1.27.0+**. \ No newline at end of file diff --git a/content/includes/content/compose-var-sub.md b/content/includes/content/compose-var-sub.md index 5f2aa0a0f0..6c92478279 100644 --- a/content/includes/content/compose-var-sub.md +++ b/content/includes/content/compose-var-sub.md @@ -26,7 +26,7 @@ Values set in the shell environment override those set in the `.env` file. > > The `.env file` feature only works when you use the `docker compose up` command > and does not work with `docker stack deploy`. -{: .important } +{ .important } Both `$VARIABLE` and `${VARIABLE}` syntax are supported. Additionally when using the [2.1 file format](/compose/compose-file/compose-versioning/#version-21), it is possible to @@ -63,4 +63,4 @@ as an environment variable and warns you: ```console The VAR_NOT_INTERPOLATED_BY_COMPOSE is not set. Substituting an empty string. -``` +``` \ No newline at end of file diff --git a/content/includes/deploy.md b/content/includes/deploy.md index f99e98b527..12bd9fdda1 100644 --- a/content/includes/deploy.md +++ b/content/includes/deploy.md @@ -25,4 +25,4 @@ To enable Kubernetes: This starts a Kubernetes single-node cluster when Docker Desktop starts. -For detailed information, see [Deploy on Kubernetes](/desktop/kubernetes/) and [Describing apps using Kubernetes YAML](/get-started/kube-deploy/#describing-apps-using-kubernetes-yaml). +For detailed information, see [Deploy on Kubernetes](/desktop/kubernetes/) and [Describing apps using Kubernetes YAML](/get-started/kube-deploy/#describing-apps-using-kubernetes-yaml). \ No newline at end of file diff --git a/content/includes/desktop-builders-setting.md b/content/includes/desktop-builders-setting.md index 15ad8944c8..6ffdbc6e6f 100644 --- a/content/includes/desktop-builders-setting.md +++ b/content/includes/desktop-builders-setting.md @@ -59,4 +59,4 @@ You can start and stop the BuildKit container using the drop-down menu. Running a build automatically starts the container if it's stopped. -You can only start and stop builders using the `docker-container` driver. +You can only start and stop builders using the `docker-container` driver. \ No newline at end of file diff --git a/content/includes/desktop-experimental.md b/content/includes/desktop-experimental.md index f2f772bfe6..cf7955a21f 100644 --- a/content/includes/desktop-experimental.md +++ b/content/includes/desktop-experimental.md @@ -1,3 +1,3 @@ On the **Experimental features** tab, you have the option to allow feature flags. These are features that Docker is currently experimenting with. This is switched on by default. -These features are intended for testing and feedback only as they may change between releases without warning or remove them entirely from a future release. Docker doesn't offer support for experimental features. +These features are intended for testing and feedback only as they may change between releases without warning or remove them entirely from a future release. Docker doesn't offer support for experimental features. \ No newline at end of file diff --git a/content/includes/desktop-license-update.md b/content/includes/desktop-license-update.md index 35af70f61e..96dfd4834d 100644 --- a/content/includes/desktop-license-update.md +++ b/content/includes/desktop-license-update.md @@ -3,4 +3,4 @@ Here’s a summary of the key points: - Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open source projects. - Otherwise, it requires a paid subscription for professional use. - Paid subscriptions are also required for government entities. -- The Docker Pro, Team, and Business subscriptions include commercial use of Docker Desktop. +- The Docker Pro, Team, and Business subscriptions include commercial use of Docker Desktop. \ No newline at end of file diff --git a/content/includes/desktop-linux-launch.md b/content/includes/desktop-linux-launch.md index df0949ce60..2049689e33 100644 --- a/content/includes/desktop-linux-launch.md +++ b/content/includes/desktop-linux-launch.md @@ -53,4 +53,4 @@ Alternatively, open a terminal and run: ```console $ systemctl --user stop docker-desktop -``` +``` \ No newline at end of file diff --git a/content/includes/dev-envs-changing.md b/content/includes/dev-envs-changing.md index 823d42faf6..d48135834c 100644 --- a/content/includes/dev-envs-changing.md +++ b/content/includes/dev-envs-changing.md @@ -3,4 +3,4 @@ >We’re working hard to make Dev Environments work even better for you and your teams. In the coming months, we’ll be introducing a new vision for Dev Environments. > >In the mean time, it may take us longer to respond to requests for support. -{: .important} \ No newline at end of file +{ .important } \ No newline at end of file diff --git a/content/includes/dockerfile-labs-channel.md b/content/includes/dockerfile-labs-channel.md index df9686341b..b311f14cde 100644 --- a/content/includes/dockerfile-labs-channel.md +++ b/content/includes/dockerfile-labs-channel.md @@ -2,4 +2,4 @@ > > The "labs" channel provides early access to Dockerfile features that are not > yet available in the stable channel. -{: .experimental } +{ .experimental } \ No newline at end of file diff --git a/content/includes/experimental.md b/content/includes/experimental.md index 86cebbd3f9..ed9afdbb7b 100644 --- a/content/includes/experimental.md +++ b/content/includes/experimental.md @@ -4,4 +4,4 @@ between releases without warning or can be removed entirely from a future release. Experimental features must not be used in production environments. Docker does not offer support for experimental features. -For a list of current experimental features in the Docker CLI, see [Docker CLI Experimental features](https://github.com/docker/cli/blob/master/experimental/README.md). +For a list of current experimental features in the Docker CLI, see [Docker CLI Experimental features](https://github.com/docker/cli/blob/master/experimental/README.md). \ No newline at end of file diff --git a/content/includes/gha-tutorial.md b/content/includes/gha-tutorial.md index 452f920d77..25eab5093f 100644 --- a/content/includes/gha-tutorial.md +++ b/content/includes/gha-tutorial.md @@ -65,14 +65,13 @@ Hub. the job should run on. For more information about the YAML syntax used here, see -[Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions){: -target="blank" rel="noopener"}. +[Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions). ### Step three: Define the workflow steps Now the essentials: what steps to run, and in what order to run them. -{% raw %} + ```yaml jobs: build: @@ -99,20 +98,17 @@ jobs: push: true tags: ${{ secrets.DOCKERHUB_USERNAME }}/clockbox:latest ``` -{% endraw %} + The previous YAML snippet contains a sequence of steps that: 1. Checks out the repository on the build machine. 2. Signs in to Docker Hub, using the - [Docker Login](https://github.com/marketplace/actions/docker-login){: - target="blank" rel="noopener"} action and your Docker Hub credentials. + [Docker Login](https://github.com/marketplace/actions/docker-login) action and your Docker Hub credentials. 3. Creates a BuildKit builder instance using the - [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx){: - target="blank" rel="noopener"} action. + [Docker Setup Buildx](https://github.com/marketplace/actions/docker-setup-buildx) action. 4. Builds the container image and pushes it to the Docker Hub repository, using - [Build and push Docker images](https://github.com/marketplace/actions/build-and-push-docker-images){: - target="blank" rel="noopener"}. + [Build and push Docker images](https://github.com/marketplace/actions/build-and-push-docker-images). The `with` key lists a number of input parameters that configures the step: @@ -125,7 +121,7 @@ The previous YAML snippet contains a sequence of steps that: Add these steps to your workflow file. The full workflow configuration should look as follows: -{% raw %} + ```yaml name: ci @@ -159,7 +155,7 @@ jobs: push: true tags: ${{ secrets.DOCKERHUB_USERNAME }}/clockbox:latest ``` -{% endraw %} + ### Run the workflow @@ -174,8 +170,7 @@ Save the workflow file and run the job. Selecting the workflow shows you the breakdown of all the steps. 3. When the workflow is complete, go to your - [repositories on Docker Hub](https://hub.docker.com/repositories){: - target="blank" rel="noopener"}. + [repositories on Docker Hub](https://hub.docker.com/repositories). If you see the new repository in that list, it means the GitHub Actions - successfully pushed the image to Docker Hub! + successfully pushed the image to Docker Hub! \ No newline at end of file diff --git a/content/includes/github_issue.md b/content/includes/github_issue.md index bf42e1e1f7..54ef44f9f9 100644 --- a/content/includes/github_issue.md +++ b/content/includes/github_issue.md @@ -1 +1 @@ -[{{ include.repo }}#{{ include.number }}](https://github.com/{{ include.repo }}/issues/{{ include.number }}){:target="_blank" rel="noopener" class="_"} \ No newline at end of file +[{{ include.repo }}#{{ include.number }}](https://github.com/{{ include.repo }}/issues/{{ include.number }}) \ No newline at end of file diff --git a/content/includes/index.md b/content/includes/index.md index ca03031f1e..e69de29bb2 100644 --- a/content/includes/index.md +++ b/content/includes/index.md @@ -1,3 +0,0 @@ ---- -headless: true ---- diff --git a/content/includes/install-script.md b/content/includes/install-script.md index 8fd80ff7e3..cab0a9f052 100644 --- a/content/includes/install-script.md +++ b/content/includes/install-script.md @@ -8,14 +8,13 @@ provisioning script tailored to your needs. Also refer to the [install using the repository](#install-using-the-repository) steps to learn about installation steps to install using the package repository. The source code for the script is open source, and you can find it in the -[`docker-install` repository on GitHub](https://github.com/docker/docker-install){:target="_blank" -rel="noopener" class="_"}. +[`docker-install` repository on GitHub](https://github.com/docker/docker-install). Always examine scripts downloaded from the internet before running them locally. Before installing, make yourself familiar with potential risks and limitations of the convenience script: -{:.warning} +{ .warning } - The script requires `root` or `sudo` privileges to run. - The script attempts to detect your Linux distribution and version and @@ -91,4 +90,4 @@ $ sudo sh test-docker.sh If you installed Docker using the convenience script, you should upgrade Docker using your package manager directly. There's no advantage to re-running the convenience script. Re-running it can cause issues if it attempts to re-install -repositories which already exist on the host machine. +repositories which already exist on the host machine. \ No newline at end of file diff --git a/content/includes/registry.md b/content/includes/registry.md index deb4372beb..8ee10e0765 100644 --- a/content/includes/registry.md +++ b/content/includes/registry.md @@ -1,6 +1,6 @@ > > This page contains information about hosting your own registry using the -> [open source Docker Registry](https://github.com/distribution/distribution){: target="_blank" rel="noopener" class="_"}. For information about Docker Hub, which offers a +> [open source Docker Registry](https://github.com/distribution/distribution). For information about Docker Hub, which offers a > hosted registry with additional features such as teams, organizations, web > hooks, automated builds, etc, see [Docker Hub](/docker-hub/). -{: .important } +{ .important } \ No newline at end of file diff --git a/content/includes/root-errors.md b/content/includes/root-errors.md index d37cb4084e..f8f12c11a2 100644 --- a/content/includes/root-errors.md +++ b/content/includes/root-errors.md @@ -5,4 +5,4 @@ > The `docker` user group exists but contains no users, which is why you’re required > to use `sudo` to run Docker commands. Continue to [Linux postinstall](/engine/install/linux-postinstall) > to allow non-privileged users to run Docker commands and for other optional configuration steps. -{: .tip} \ No newline at end of file +{ .tip } \ No newline at end of file diff --git a/content/includes/scout-early-access.md b/content/includes/scout-early-access.md index bccc6930d5..5010d4deaa 100644 --- a/content/includes/scout-early-access.md +++ b/content/includes/scout-early-access.md @@ -1,5 +1,5 @@ > **Early Access** > > Advanced image analysis is provided by Docker Scout and in [early access](/release-lifecycle/#early-access-ea). -> [Learn more on the Docker Scout product page](https://docker.com/products/docker-scout){: target="_blank" rel="noopener" }. -{: .restricted} \ No newline at end of file +> [Learn more on the Docker Scout product page](https://docker.com/products/docker-scout). +{ .restricted } \ No newline at end of file diff --git a/content/includes/swarm-compose-compat.md b/content/includes/swarm-compose-compat.md index d9c41f0bc7..2868f11bb4 100644 --- a/content/includes/swarm-compose-compat.md +++ b/content/includes/swarm-compose-compat.md @@ -7,4 +7,4 @@ > isn't compatible with the `docker stack deploy` command. > > For more information about the evolution of Compose, see -> [History of Compose](/compose/history/). +> [History of Compose](/compose/history/). \ No newline at end of file diff --git a/content/includes/swarm-mode.md b/content/includes/swarm-mode.md index c1485d4c8c..e1eb88cd26 100644 --- a/content/includes/swarm-mode.md +++ b/content/includes/swarm-mode.md @@ -7,4 +7,4 @@ > If you're not planning on deploying with Swarm, use > [Docker Compose](/compose/) instead. > If you're developing for a Kubernetes deployment, consider using the -> [integrated Kubernetes feature](/desktop/kubernetes/) in Docker Desktop. +> [integrated Kubernetes feature](/desktop/kubernetes/) in Docker Desktop. \ No newline at end of file diff --git a/content/language/_index.md b/content/language/_index.md index 8522177d4c..584533f833 100644 --- a/content/language/_index.md +++ b/content/language/_index.md @@ -39,5 +39,4 @@ Learn how to set up your Docker environment and start containerizing your applic
Develop with Rust
- - + \ No newline at end of file diff --git a/content/language/dotnet/_index.md b/content/language/dotnet/_index.md index 2d13f6cdb6..14176c73e4 100644 --- a/content/language/dotnet/_index.md +++ b/content/language/dotnet/_index.md @@ -21,4 +21,4 @@ After completing the .NET getting started modules, you should be able to contain Let's get started! -[Build your first .NET image](build-images.md){: .button .primary-btn} +{{< button text="Build your first .NET image" url="build-images.md" >}} \ No newline at end of file diff --git a/content/language/dotnet/build-images.md b/content/language/dotnet/build-images.md index c60a5f6452..cafb2cf9d7 100644 --- a/content/language/dotnet/build-images.md +++ b/content/language/dotnet/build-images.md @@ -1,5 +1,5 @@ --- -title: "Build your .NET image" +title: Build your .NET image keywords: .net, build, images, dockerfile description: Learn how to build your first Docker image by writing a Dockerfile --- @@ -16,9 +16,9 @@ Now that we have a good overview of containers and the Docker platform, let’s To complete this tutorial, you need the following: -- .NET SDK version 6.0 or later. [Download .NET SDK](https://dotnet.microsoft.com/download){: target="_blank" rel="noopener" class="_"}. +- .NET SDK version 6.0 or later. [Download .NET SDK](https://dotnet.microsoft.com/download). - Docker running locally. Follow the instructions to [download and install Docker](../../get-docker.md). -- An IDE or a text editor to edit files. We recommend using [Visual Studio Code](https://code.visualstudio.com/){: target="_blank" rel="noopener" class="_"}. +- An IDE or a text editor to edit files. We recommend using [Visual Studio Code](https://code.visualstudio.com/). ## Sample application @@ -290,8 +290,8 @@ Our image that was tagged with `:v1.0.0` has been removed, but we still have the In this module, we took a look at setting up our example .NET application that we will use for the rest of the tutorial. We also created a Dockerfile that we used to build our Docker image. Then, we took a look at tagging our images and removing images. In the next module we’ll take a look at how to: -[Run your image as a container](run-containers.md){: .button .primary-btn} +{{< button text="Run your image as a container" url="run-containers.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]) GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/dotnet/configure-ci-cd.md b/content/language/dotnet/configure-ci-cd.md index 0e9467c049..020519f00c 100644 --- a/content/language/dotnet/configure-ci-cd.md +++ b/content/language/dotnet/configure-ci-cd.md @@ -1,5 +1,5 @@ --- -title: "Configure CI/CD for your application" +title: Configure CI/CD for your application keywords: .net, CI/CD, local, development description: Learn how to Configure CI/CD for your application --- @@ -8,7 +8,7 @@ description: Learn how to Configure CI/CD for your application ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Next steps @@ -16,8 +16,8 @@ In this module, you have learnt how to set up GitHub Actions workflow to an exis You can also consider deploying your application. For detailed instructions, see: -[Deploy your app](deploy.md){: .button .primary-btn} +{{< button text="Deploy your app" url="deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]) GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/dotnet/deploy.md b/content/language/dotnet/deploy.md index 3180d4dfec..d202a97c95 100644 --- a/content/language/dotnet/deploy.md +++ b/content/language/dotnet/deploy.md @@ -1,13 +1,13 @@ --- -title: "Deploy your app" +title: Deploy your app keywords: deploy, ACI, ECS, .net, local, development description: Learn how to deploy your application --- {% include_relative nav.html selected="6" %} -{% include deploy.md %} +{{< include "deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]) GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/dotnet/develop.md b/content/language/dotnet/develop.md index 1a3d7a207c..97f3bad9dd 100644 --- a/content/language/dotnet/develop.md +++ b/content/language/dotnet/develop.md @@ -1,5 +1,5 @@ --- -title: "Use containers for development" +title: Use containers for development keywords: .net, local, development, run, description: Learn how to develop your application locally. --- @@ -453,8 +453,8 @@ Now let’s test our application. Using a web browser, access `http://localhost: In the next module, we’ll take a look at how to write containerized tests in Docker. See: -[Run your tests](run-tests.md){: .button .primary-btn} +{{< button text="Run your tests" url="run-tests.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. \ No newline at end of file +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]) GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/dotnet/run-containers.md b/content/language/dotnet/run-containers.md index d3c913bf7f..43be3486c4 100644 --- a/content/language/dotnet/run-containers.md +++ b/content/language/dotnet/run-containers.md @@ -1,5 +1,5 @@ --- -title: "Run your image as a container" +title: Run your image as a container keywords: .net, run, image, container, description: Learn how to run the image as a container. --- @@ -163,8 +163,8 @@ That’s better! We can now easily identify our container based on the name. In this module, we took a look at running containers, publishing ports, and running containers in detached mode. We also took a look at managing containers by starting, stopping, and, restarting them. We also looked at naming our containers so they are more easily identifiable. In the next module, we’ll learn how to run a database in a container and connect it to our application. See: -[How to develop your application](develop.md){: .button .primary-btn} +{{< button text="How to develop your application" url="develop.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]) GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/dotnet/run-tests.md b/content/language/dotnet/run-tests.md index 2ea00b91d3..85545df47b 100644 --- a/content/language/dotnet/run-tests.md +++ b/content/language/dotnet/run-tests.md @@ -1,5 +1,5 @@ --- -title: "Run your tests" +title: Run your tests keywords: .NET, build, test description: How to build and run your tests --- @@ -137,8 +137,8 @@ Passed! - Failed: 0, Passed: 1, Skipped: 0, Total: 1, Duration: In the next module, we’ll take a look at how to set up a CI/CD pipeline using GitHub Actions. See: -[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn} +{{< button text="Configure CI/CD" url="configure-ci-cd.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. \ No newline at end of file +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs](https://github.com/docker/docker.github.io/issues/new?title=[dotnet%20docs%20feedback]) GitHub repository. Alternatively, [create a PR](https://github.com/docker/docker.github.io/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/golang/_index.md b/content/language/golang/_index.md index 49be14d494..1eb2e52dbb 100644 --- a/content/language/golang/_index.md +++ b/content/language/golang/_index.md @@ -10,7 +10,7 @@ This guide will show you how to create, test, and deploy containerized Go applic > **Acknowledgment** > -> We'd like to thank [Oliver Frolovs](https://www.linkedin.com/in/ofr/){:target="_blank" rel="noopener" class="_"} for his contribution to this guide. +> We'd like to thank [Oliver Frolovs](https://www.linkedin.com/in/ofr/) for his contribution to this guide. ## What will you learn? @@ -20,13 +20,13 @@ In this guide, you’ll learn how to: * Run the image as a container in your local Docker instance and manage the container's lifecycle. * Use multi-stage builds for building small images efficiently while keeping your *Dockerfiles* easy to read and maintain. * Use Docker Compose to orchestrate running of multiple related containers together in a development environment. -* Configure a CI/CD pipeline for your application using [GitHub Actions](https://docs.github.com/en/actions){:target="_blank" rel="noopener" class="_"} -* Deploy your containerized Go application to Google [Cloud Run](https://cloud.google.com/run/docs/overview/what-is-cloud-run){:target="_blank" rel="noopener" class="_"} serverless platform. +* Configure a CI/CD pipeline for your application using [GitHub Actions](https://docs.github.com/en/actions) +* Deploy your containerized Go application to Google [Cloud Run](https://cloud.google.com/run/docs/overview/what-is-cloud-run) serverless platform. ## Prerequisites Some basic understanding of Go and its toolchain is assumed. This is not a Go tutorial. If you are new to the language, -the [Go website](https://golang.org/){: target="_blank" rel="noopener" class="_"} is a great place to explore, +the [Go website](https://golang.org/) is a great place to explore, so *go* (pun intended) check it out! You also must know some basic [Docker concepts](../../get-started/overview.md) as well as to @@ -44,4 +44,4 @@ The aim of this guide is to provide enough examples and instructions for you to Let's get started! -[Build your Go image](build-images.md){: .button .primary-btn} +{{< button text="Build your Go image" url="build-images.md" >}} \ No newline at end of file diff --git a/content/language/golang/build-images.md b/content/language/golang/build-images.md index 46005bd0df..2d1447a25e 100644 --- a/content/language/golang/build-images.md +++ b/content/language/golang/build-images.md @@ -1,8 +1,8 @@ --- -title: "Build your Go image" +title: Build your Go image keywords: containers, images, go, golang, dockerfiles, coding, build, push, run description: Learn how to build your first Docker image by writing a Dockerfile -redirect_from: +aliases: - /get-started/golang/build-images/ --- @@ -18,9 +18,9 @@ all other resources required by your application. To complete this tutorial, you need the following: -- Go version 1.19 or later. Visit the [download page for Go](https://golang.org/dl/){:target="_blank" rel="noopener" class="_"} first and install the toolchain. +- Go version 1.19 or later. Visit the [download page for Go](https://golang.org/dl/) first and install the toolchain. - Docker running locally. Follow the [instructions to download and install Docker](../../desktop/index.md). -- An IDE or a text editor to edit files. [Visual Studio Code](https://code.visualstudio.com/){: target="_blank" rel="noopener" class="_"} is a free and popular choice but you can use anything you feel comfortable with. +- An IDE or a text editor to edit files. [Visual Studio Code](https://code.visualstudio.com/) is a free and popular choice but you can use anything you feel comfortable with. - A Git client. We'll use a command-line based `git` client throughout this module, but you are free to use whatever works for you. - A command-line terminal application. The examples shown in this module are from the Linux shell, but they should work in PowerShell, Windows Command Prompt, or OS X Terminal with minimal, if any, modifications. @@ -39,7 +39,7 @@ The application listens on a TCP port defined by the value of environment variab The application is *stateless*. -The complete source code for the application is on GitHub: [github.com/docker/docker-gs-ping](https://github.com/docker/docker-gs-ping){: target="_blank" rel="noopener" class="_"}. You are encouraged to fork it and experiment with it as much as you like. +The complete source code for the application is on GitHub: [github.com/docker/docker-gs-ping](https://github.com/docker/docker-gs-ping). You are encouraged to fork it and experiment with it as much as you like. To continue, we clone the application repository to our local machine: @@ -49,7 +49,7 @@ $ git clone https://github.com/docker/docker-gs-ping The application's `main.go` file is fairly straightforward, if you are familiar with Go: -{% raw %} + ```go package main @@ -93,7 +93,7 @@ func IntMin(a, b int) int { return b } ``` -{% endraw %} + ## Smoke test the application @@ -456,7 +456,7 @@ is very lean and does not include the Go toolchain or other optional components. The `Dockerfile.multistage` in the sample application's repo has the following content: -{% raw %} + ```dockerfile # syntax=docker/dockerfile:1 @@ -489,7 +489,7 @@ USER nonroot:nonroot ENTRYPOINT ["/docker-gs-ping"] ``` -{% endraw %} + Since we have two Dockerfiles now, we have to tell Docker what Dockerfile we'd like to use to build the image. Let's tag the new image with `multistage`. This tag (like any other, @@ -508,7 +508,7 @@ docker-gs-ping multistage e3fdde09f172 About a minute ago 28.1MB docker-gs-ping latest 336a3f164d0f About an hour ago 1.11GB ``` -This is so because the ["distroless"](https://github.com/GoogleContainerTools/distroless){:target="_blank" rel="noopener" class="_"} +This is so because the ["distroless"](https://github.com/GoogleContainerTools/distroless) base image that we have used in the second stage of the build is very barebones and is designed for lean deployments of static binaries. There's much more to multi-stage builds, including the possibility of multi-architecture builds, @@ -522,11 +522,11 @@ In this module, we met our example application and built and container image for In the next module, we’ll take a look at how to: -[Run your image as a container](run-containers.md){: .button .primary-btn} +{{< button text="Run your image as a container" url="run-containers.md" >}} ## Feedback Help us improve this topic by providing your feedback. Let us know what you -think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} -GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} -to suggest updates. +think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Golang%20docs%20feedback]) +GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) +to suggest updates. \ No newline at end of file diff --git a/content/language/golang/configure-ci-cd.md b/content/language/golang/configure-ci-cd.md index 79c204cc50..c40aea3418 100644 --- a/content/language/golang/configure-ci-cd.md +++ b/content/language/golang/configure-ci-cd.md @@ -1,8 +1,9 @@ --- -title: "Configure CI/CD for your application" -keywords: ci, cd, ci/cd, continuous integration, continuous deployment, deployment, github, github actions, go, golang, development +title: Configure CI/CD for your application +keywords: ci, cd, ci/cd, continuous integration, continuous deployment, deployment, + github, github actions, go, golang, development description: Learn how to set up CI/CD pipeline for your application. -redirect_from: +aliases: - /get-started/golang/configure-ci-cd/ --- @@ -10,7 +11,7 @@ redirect_from: ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Next steps @@ -20,8 +21,8 @@ You can also consider deploying your application to a public Cloud provider, suc In the next module, we’ll look into some options for doing so: -[Deploy your app](deploy.md){: .button .primary-btn} +{{< button text="Deploy your app" url="deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Golang%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/golang/deploy.md b/content/language/golang/deploy.md index f1ce0335d3..fd28393b1a 100644 --- a/content/language/golang/deploy.md +++ b/content/language/golang/deploy.md @@ -1,13 +1,13 @@ --- -title: "Deploy your app" +title: Deploy your app keywords: deploy, ACI, ECS, local, development, Go, Golang, cloud, deployment description: Learn how to deploy your application --- {% include_relative nav.html selected="6" %} -{% include deploy.md %} +{{< include "deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Golang%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/golang/develop.md b/content/language/golang/develop.md index 70b0aa9197..5c359ccc18 100644 --- a/content/language/golang/develop.md +++ b/content/language/golang/develop.md @@ -1,8 +1,8 @@ --- -title: "Use containers for development" +title: Use containers for development keywords: get started, go, golang, local, development description: Learn how to develop your application locally. -redirect_from: +aliases: - /get-started/golang/develop/ --- @@ -131,7 +131,7 @@ $ docker exec -it roach ./cockroach sql --insecure An example of interaction with the SQL shell is presented below. -{% raw %} + ```console $ sudo docker exec -it roach ./cockroach sql --insecure # @@ -162,7 +162,7 @@ Time: 14.217559ms root@:26257/defaultdb> quit oliver@hki:~$ ``` -{% endraw %} + ### Meet the example application @@ -196,7 +196,7 @@ And _now_ it's going to be: The full source code listing of `main.go` follows. -{% raw %} + ```go package main @@ -337,7 +337,7 @@ func countRecords(db *sql.DB) (int, error) { return count, nil } ``` -{% endraw %} + The repository also includes the `Dockerfile`, which is almost exactly the same as the multi-stage `Dockerfile` introduced in the previous modules. It uses the official Docker Go image to build the application and then builds the final image by placing the compiled binary into the much slimmer, "distroless" image. @@ -527,7 +527,7 @@ In this section, we’ll create a Docker Compose file to start our `docker-gs-pi In our application's directory, create a new text file named `docker-compose.yml` with the following content. -{% raw %} + ```yaml version: '3.8' @@ -572,7 +572,7 @@ networks: mynet: driver: bridge ``` -{% endraw %} + This Docker Compose configuration is super convenient as we do not have to type all the parameters to pass to the `docker run` command. We can declaratively do that in the Docker Compose file. The [Docker Compose documentation pages](../../compose/index.md) are quite extensive and include a full reference for the Docker Compose file format. @@ -740,8 +740,8 @@ In this module, we set up a containerised development environment with our appli In the next module, we’ll take a look at one possible approach to running functional tests in Docker. See: -[Run your tests](run-tests.md){: .button .primary-btn} +{{< button text="Run your tests" url="run-tests.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Golang%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/golang/run-containers.md b/content/language/golang/run-containers.md index 6f3835e6ba..78cab0b21a 100644 --- a/content/language/golang/run-containers.md +++ b/content/language/golang/run-containers.md @@ -1,8 +1,8 @@ --- -title: "Run your image as a container" +title: Run your image as a container keywords: get started, go, golang, run, container description: Learn how to run the image as a container. -redirect_from: +aliases: - /get-started/golang/run-containers/ --- @@ -198,8 +198,8 @@ Now, we can easily identify our container based on the name. In this module, we learned how to run containers and publish ports. We also learned to manage the lifecycle of containers. We then discussed the importance of naming our containers so that they are more easily identifiable. In the next module, we’ll learn how to run a database in a container and connect it to our application. See: -[How to develop your application](develop.md){: .button .primary-btn} +{{< button text="How to develop your application" url="develop.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Golang %20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Golang %20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/golang/run-tests.md b/content/language/golang/run-tests.md index 13fc54c944..ec596c4714 100644 --- a/content/language/golang/run-tests.md +++ b/content/language/golang/run-tests.md @@ -1,8 +1,8 @@ --- -title: "Run your tests using Go test" +title: Run your tests using Go test keywords: build, go, golang, test description: How to build and run your Go tests in a container -redirect_from: +aliases: - /get-started/golang/run-tests/ --- @@ -14,7 +14,7 @@ Testing is an essential part of modern software development. Yet, testing can me Each test is meant to verify a single business requirement for our example application. The following test is an excerpt from `main_test.go` test suite in our example application. -{% raw %} + ```go func TestRespondsWithLove(t *testing.T) { @@ -50,7 +50,7 @@ func TestRespondsWithLove(t *testing.T) { require.Contains(t, string(body), "<3", "does not respond with love?") } ``` -{% endraw %} + As you can see, this is a high-level test, unconcerned with the implementation details of our example application. @@ -102,8 +102,8 @@ In this module, we've seen an example of using Docker for isolated functional te In the next module, we’ll take a look at how to set up a CI/CD pipeline using GitHub Actions. See: -[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn} +{{< button text="Configure CI/CD" url="configure-ci-cd.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Golang%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Golang%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/java/_index.md b/content/language/java/_index.md index f08dbb83e3..64f28bf3b4 100644 --- a/content/language/java/_index.md +++ b/content/language/java/_index.md @@ -20,4 +20,4 @@ After completing the Java getting started modules, you should be able to contain Let’s get started! -[Build your first Java image](build-images.md){: .button .primary-btn} +{{< button text="Build your first Java image" url="build-images.md" >}} \ No newline at end of file diff --git a/content/language/java/build-images.md b/content/language/java/build-images.md index 9e5f8f1c8b..943ee1b8ff 100644 --- a/content/language/java/build-images.md +++ b/content/language/java/build-images.md @@ -1,5 +1,5 @@ --- -title: "Build your Java image" +title: Build your Java image keywords: Java, build, images, dockerfile description: Learn how to build your first Docker image by writing a Dockerfile --- @@ -21,7 +21,7 @@ To complete this tutorial, you need the following: - Docker running locally. Follow the instructions to [download and install Docker](../../get-docker.md) - A Git client -- An IDE or a text editor to edit files. We recommend using [IntelliJ Community Edition](https://www.jetbrains.com/idea/download/){: target="_blank" rel="noopener" class="_"}. +- An IDE or a text editor to edit files. We recommend using [IntelliJ Community Edition](https://www.jetbrains.com/idea/download/). ## Sample application @@ -38,7 +38,7 @@ $ cd spring-petclinic In this step, we will test the application locally without Docker, before we continue with building and running the application with Docker. This section requires you to have Java OpenJDK version 15 or later installed on your machine. -[Download and install Java](https://jdk.java.net/){: target="_blank" rel="noopener" class="_"} +[Download and install Java](https://jdk.java.net/) If you prefer to not install Java on your machine, you can skip this step, and continue straight to the next section, in which we explain how to build and run @@ -242,8 +242,8 @@ Our image that was tagged with `:v1.0.0` has been removed, but we still have the In this module, we took a look at setting up our example Java application that we'll use for the rest of the tutorial. We also created a Dockerfile that we used to build our Docker image. Then, we took a look at tagging our images and removing images. In the next module, we’ll take a look at how to: -[Run your image as a container](run-containers.md){: .button .primary-btn} +{{< button text="Run your image as a container" url="run-containers.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Java%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/java/configure-ci-cd.md b/content/language/java/configure-ci-cd.md index f0419438c8..de93112c0f 100644 --- a/content/language/java/configure-ci-cd.md +++ b/content/language/java/configure-ci-cd.md @@ -1,5 +1,5 @@ --- -title: "Configure CI/CD for your application" +title: Configure CI/CD for your application keywords: Java, CI/CD, local, development description: Learn how to Configure CI/CD for your application --- @@ -8,7 +8,7 @@ description: Learn how to Configure CI/CD for your application ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Next steps @@ -16,8 +16,8 @@ In this module, you have learnt how to set up GitHub Actions workflow to an exis You can also consider deploying your application. For detailed instructions, see: -[Deploy your application](deploy.md){: .button .primary-btn} +{{< button text="Deploy your application" url="deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Java%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/java/deploy.md b/content/language/java/deploy.md index fca8bb279d..bf10da969b 100644 --- a/content/language/java/deploy.md +++ b/content/language/java/deploy.md @@ -1,13 +1,13 @@ --- -title: "Deploy your app" +title: Deploy your app keywords: deploy, ACI, ECS, Java, local, development description: Learn how to deploy your application --- {% include_relative nav.html selected="6" %} -{% include deploy.md %} +{{< include "deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Java%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/java/develop.md b/content/language/java/develop.md index 580c1394d9..19c7ba4a94 100644 --- a/content/language/java/develop.md +++ b/content/language/java/develop.md @@ -1,5 +1,5 @@ --- -title: "Use containers for development" +title: Use containers for development keywords: Java, local, development, run, description: Learn how to develop your application locally. --- @@ -217,7 +217,7 @@ You should have seen the code break on the marked line and now you are able to u ![Debugger code breakpoint](images/debugger-breakpoint.png) -You can also activate the live reload option provided by SpringBoot Dev Tools. Check out the [SpringBoot documentation](https://docs.spring.io/spring-boot/docs/current/reference/html/using-spring-boot.html#using-boot-devtools-remote){:target="_blank" rel="noopener" class="_"} for information on how to connect to a remote application. +You can also activate the live reload option provided by SpringBoot Dev Tools. Check out the [SpringBoot documentation](https://docs.spring.io/spring-boot/docs/current/reference/html/using-spring-boot.html#using-boot-devtools-remote) for information on how to connect to a remote application. ## Next steps @@ -225,8 +225,8 @@ In this module, we took a look at creating a general development image that we c In the next module, we’ll take a look at how to run unit tests in Docker. See -[Run your tests](run-tests.md){: .button .primary-btn} +{{< button text="Run your tests" url="run-tests.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Java%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/java/run-containers.md b/content/language/java/run-containers.md index b91b8a00d0..25c8fce0c2 100644 --- a/content/language/java/run-containers.md +++ b/content/language/java/run-containers.md @@ -1,5 +1,5 @@ --- -title: "Run your image as a container" +title: Run your image as a container keywords: Java, run, image, container, description: Learn how to run the image as a container. --- @@ -176,8 +176,8 @@ In this module, we took a look at running containers, publishing ports, and runn In the next module, we’ll learn how to run a database in a container and connect it to our application. See: -[Use containers for development](develop.md){: .button .primary-btn} +{{< button text="Use containers for development" url="develop.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Java%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/java/run-tests.md b/content/language/java/run-tests.md index 59152e91b2..16a337d187 100644 --- a/content/language/java/run-tests.md +++ b/content/language/java/run-tests.md @@ -1,5 +1,5 @@ --- -title: "Run your tests" +title: Run your tests keywords: Java, build, test description: How to build and run your Tests --- @@ -171,8 +171,8 @@ In this module, we took a look at running tests as part of our Docker image buil In the next module, we’ll take a look at how to set up a CI/CD pipeline using GitHub Actions. See: -[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn} +{{< button text="Configure CI/CD" url="configure-ci-cd.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Java%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Java%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/nodejs/_index.md b/content/language/nodejs/_index.md index 5348d22aaf..7036e7104d 100644 --- a/content/language/nodejs/_index.md +++ b/content/language/nodejs/_index.md @@ -19,4 +19,4 @@ After completing the Node.js getting started modules, you should be able to cont Let's get started! -[Build your Node.js image](build-images.md){: .button .primary-btn} +{{< button text="Build your Node.js image" url="build-images.md" >}} \ No newline at end of file diff --git a/content/language/nodejs/build-images.md b/content/language/nodejs/build-images.md index eb24988bcc..d8d395b6d1 100644 --- a/content/language/nodejs/build-images.md +++ b/content/language/nodejs/build-images.md @@ -1,9 +1,10 @@ --- -title: "Build your Node image" -keywords: containers, images, node.js, node, dockerfiles, node, coding, build, push, run +title: Build your Node image +keywords: containers, images, node.js, node, dockerfiles, node, coding, build, push, + run description: Learn how to build your first Docker image by writing a Dockerfile -redirect_from: - - /get-started/nodejs/build-images/ +aliases: +- /get-started/nodejs/build-images/ --- {% include_relative nav.html selected="1" %} @@ -21,7 +22,7 @@ Now that we have a good overview of containers and the Docker platform, let’s To complete this tutorial, you need the following: -- Node.js version 18 or later. [Download Node.js](https://nodejs.org/en/){: target="_blank" rel="noopener" class="_"} +- Node.js version 18 or later. [Download Node.js](https://nodejs.org/en/) - Docker running locally: Follow the instructions to [download and install Docker](../../desktop/index.md). - An IDE or a text editor to edit files. We recommend using Visual Studio Code. @@ -301,8 +302,8 @@ Our image that was tagged with `:v1.0.0` has been removed but we still have the In this module, we took a look at setting up our example Node application that we will use for the rest of the tutorial. We also created a Dockerfile that we used to build our Docker image. Then, we took a look at tagging our images and removing images. In the next module, we’ll take a look at how to: -[Run your image as a container](run-containers.md){: .button .primary-btn} +{{< button text="Run your image as a container" url="run-containers.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Node.js%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/nodejs/configure-ci-cd.md b/content/language/nodejs/configure-ci-cd.md index 938f9727af..365e1eb802 100644 --- a/content/language/nodejs/configure-ci-cd.md +++ b/content/language/nodejs/configure-ci-cd.md @@ -1,5 +1,5 @@ --- -title: "Configure CI/CD for your application" +title: Configure CI/CD for your application keywords: CI/CD, GitHub Actions, NodeJS, local, development description: Learn how to develop your application locally. --- @@ -8,7 +8,7 @@ description: Learn how to develop your application locally. ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Next steps @@ -16,8 +16,8 @@ In this module, you have learnt how to set up GitHub Actions workflow to an exis You can also consider deploying your application. For detailed instructions, see: -[Deploy your app](./deploy.md){: .button .primary-btn} +{{< button text="Deploy your app" url="./deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Node.js%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/nodejs/deploy.md b/content/language/nodejs/deploy.md index 08524a7d6f..368729b619 100644 --- a/content/language/nodejs/deploy.md +++ b/content/language/nodejs/deploy.md @@ -1,13 +1,13 @@ --- -title: "Deploy your app" +title: Deploy your app keywords: deploy, cloud, ACI, ECS, NodeJS, local, development description: Learn how to deploy your application --- {% include_relative nav.html selected="6" %} -{% include deploy.md %} +{{< include "deploy.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Node.js%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/nodejs/develop.md b/content/language/nodejs/develop.md index cf1b58e929..245ac35056 100644 --- a/content/language/nodejs/develop.md +++ b/content/language/nodejs/develop.md @@ -1,8 +1,8 @@ --- -title: "Use containers for development" +title: Use containers for development keywords: get started, NodeJS, local, development description: Learn how to develop your application locally. -redirect_from: +aliases: - /get-started/nodejs/develop/ --- @@ -185,7 +185,7 @@ We pass the `--build` flag so Docker compiles our image and then starts it. If all goes well, you should see something similar: - ![Screenshot of image being compiled](images/node-compile.png){:width="800px"} + ![Screenshot of image being compiled](images/node-compile.png) Now let’s test our API endpoint. Run the following curl command: @@ -207,7 +207,7 @@ We’ll use the debugger that comes with the Chrome browser. Open Chrome on your It opens the following screen. - ![Imaging showing Chrome inspect with DevTools](images/chrome-inspect.png){:width="800px"} + ![Imaging showing Chrome inspect with DevTools](images/chrome-inspect.png) Select **Configure**. This opens the **Target discovery settings**. Specify the target `127.0.0.1:9229` if it does not exist and then select **Done**. @@ -225,7 +225,7 @@ Add the following code above the existing `server.use()` statement, and save the If you take a look at the terminal where our Compose application is running, you’ll see that nodemon noticed the changes and reloaded our application. - ![Image of terminal noticing change and reloading](images/nodemon.png){:width="800px"} + ![Image of terminal noticing change and reloading](images/nodemon.png) Navigate back to the Chrome DevTools and set a breakpoint on the line containing the `return res.json({ "foo": "bar" })` statement, and then run the following curl command to trigger the breakpoint. @@ -241,8 +241,8 @@ In this module, we took a look at creating a general development image that we c In the next module, we’ll take a look at how to run unit tests in Docker. See: -[Run your tests](run-tests.md){: .button .primary-btn} +{{< button text="Run your tests" url="run-tests.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Node.js%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/nodejs/run-containers.md b/content/language/nodejs/run-containers.md index da01200044..5076bffaaa 100644 --- a/content/language/nodejs/run-containers.md +++ b/content/language/nodejs/run-containers.md @@ -1,8 +1,8 @@ --- -title: "Run your image as a container" +title: Run your image as a container keywords: get started, Node JS, run, container, description: Learn how to run the image as a container. -redirect_from: +aliases: - /get-started/nodejs/run-containers/ --- @@ -193,8 +193,8 @@ Now, we can easily identify our container based on the name. In this module, we took a look at running containers, publishing ports, and running containers in detached mode. We also took a look at managing containers by starting, stopping, and restarting them. We also looked at naming our containers so they are more easily identifiable. In the next module, we’ll learn how to run a database in a container and connect it to our application. See: -[How to develop your application](develop.md){: .button .primary-btn} +{{< button text="How to develop your application" url="develop.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Node.js%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/nodejs/run-tests.md b/content/language/nodejs/run-tests.md index 91ab5b2ada..febd45d65b 100644 --- a/content/language/nodejs/run-tests.md +++ b/content/language/nodejs/run-tests.md @@ -1,5 +1,5 @@ --- -title: "Run your Tests using Node.js and Mocha frameworks" +title: Run your Tests using Node.js and Mocha frameworks keywords: Node.js, build, Mocha, test description: How to Build and Run your Tests using Node.js and Mocha frameworks --- @@ -320,8 +320,8 @@ In this module, we took a look at running tests as part of our Docker image buil In the next module, we’ll take a look at how to set up a CI/CD pipeline using GitHub Actions. See: -[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn} +{{< button text="Configure CI/CD" url="configure-ci-cd.md" >}} ## Feedback -Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{ site.repo }}/issues/new?title=[Node.js%20docs%20feedback]){:target="_blank" rel="noopener" class="_"} GitHub repository. Alternatively, [create a PR]({{ site.repo }}/pulls){:target="_blank" rel="noopener" class="_"} to suggest updates. +Help us improve this topic by providing your feedback. Let us know what you think by creating an issue in the [Docker Docs]({{% param "repo" %}}/issues/new?title=[Node.js%20docs%20feedback]) GitHub repository. Alternatively, [create a PR]({{% param "repo" %}}/pulls) to suggest updates. \ No newline at end of file diff --git a/content/language/python/_index.md b/content/language/python/_index.md index 191daa1cdb..1ded742ffa 100644 --- a/content/language/python/_index.md +++ b/content/language/python/_index.md @@ -20,4 +20,4 @@ After completing the Python getting started modules, you should be able to conta Let's get started! -[Build your first Python image](build-images.md){: .button .primary-btn} +{{< button text="Build your first Python image" url="build-images.md" >}} \ No newline at end of file diff --git a/content/language/python/build-images.md b/content/language/python/build-images.md index 0f9129dafc..97e200b5c9 100644 --- a/content/language/python/build-images.md +++ b/content/language/python/build-images.md @@ -1,5 +1,5 @@ --- -title: "Build your Python image" +title: Build your Python image keywords: python, build, images, dockerfile description: Learn how to build an image of your Python application --- @@ -20,7 +20,7 @@ dependencies, and any other file system objects required. ## Sample application -The sample application uses the popular [Flask](https://flask.palletsprojects.com/){: target="_blank" rel="noopener" class="_"} framework. +The sample application uses the popular [Flask](https://flask.palletsprojects.com/) framework. Clone the sample application to use with this guide. Open a terminal, change directory to a directory that you want to work in, and run the following command to clone the repository: @@ -30,7 +30,7 @@ $ git clone https://github.com/docker/python-docker ## Test the application without Docker (optional) -You can test the application locally without Docker before you continue building and running the application with Docker. This section requires you to have Python 3.11 or later installed on your machine. Download and install [Python](https://www.python.org/downloads/){: target="_blank" rel="noopener" class="_"}. +You can test the application locally without Docker before you continue building and running the application with Docker. This section requires you to have Python 3.11 or later installed on your machine. Download and install [Python](https://www.python.org/downloads/). Open your terminal and navigate to the working directory you created. Create an environment, install the dependencies, and start the application to make sure it’s running. @@ -194,4 +194,4 @@ Related information: In the next section learn how to run your image as a container. -[Run the image as a container](run-containers.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Run the image as a container" url="run-containers.md" >}} \ No newline at end of file diff --git a/content/language/python/configure-ci-cd.md b/content/language/python/configure-ci-cd.md index bd007caed3..b375ff5922 100644 --- a/content/language/python/configure-ci-cd.md +++ b/content/language/python/configure-ci-cd.md @@ -1,5 +1,5 @@ --- -title: "Configure CI/CD for your application" +title: Configure CI/CD for your application keywords: python, CI/CD, local, development description: Learn how to Configure CI/CD for your application --- @@ -8,7 +8,7 @@ description: Learn how to Configure CI/CD for your application ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Summary @@ -18,4 +18,4 @@ In this section, you have learned how to set up GitHub Actions workflow to an ex Next, learn how you can deploy your application. -[Deploy your app](deploy.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Deploy your app" url="deploy.md" >}} \ No newline at end of file diff --git a/content/language/python/deploy.md b/content/language/python/deploy.md index 80bad796db..98165b4874 100644 --- a/content/language/python/deploy.md +++ b/content/language/python/deploy.md @@ -1,9 +1,9 @@ --- -title: "Deploy your app" +title: Deploy your app keywords: deploy, ACI, ECS, Python, local, development description: Learn how to deploy your application --- {% include_relative nav.html selected="5" %} -{% include deploy.md %} \ No newline at end of file +{{< include "deploy.md" >}} \ No newline at end of file diff --git a/content/language/python/develop.md b/content/language/python/develop.md index 0864965de8..b8837d9b3a 100644 --- a/content/language/python/develop.md +++ b/content/language/python/develop.md @@ -1,5 +1,5 @@ --- -title: "Use containers for development" +title: Use containers for development keywords: python, local, development, run, description: Learn how to develop your application locally. --- @@ -239,4 +239,4 @@ Related information: In the next section, you'll take a look at how to set up a CI/CD pipeline using GitHub Actions. -[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn} +{{< button text="Configure CI/CD" url="configure-ci-cd.md" >}} \ No newline at end of file diff --git a/content/language/python/run-containers.md b/content/language/python/run-containers.md index 270f7f49f4..0270871d62 100644 --- a/content/language/python/run-containers.md +++ b/content/language/python/run-containers.md @@ -1,5 +1,5 @@ --- -title: "Run your image as a container" +title: Run your image as a container keywords: Python, run, image, container, description: Learn how to run the image as a container. --- @@ -187,4 +187,4 @@ Related information: In the next section, you’ll learn how to run a database in a container and connect it to a Rust application. -[How to develop your application](develop.md){: .button .primary-btn} \ No newline at end of file +{{< button text="How to develop your application" url="develop.md" >}} \ No newline at end of file diff --git a/content/language/rust/_index.md b/content/language/rust/_index.md index 5d2818f8df..a1d0180fec 100644 --- a/content/language/rust/_index.md +++ b/content/language/rust/_index.md @@ -21,4 +21,4 @@ After completing the Rust modules, you should be able to containerize your own R Start with building your first Rust image. -[Build your first Rust image](build-images.md){: .button .primary-btn} +{{< button text="Build your first Rust image" url="build-images.md" >}} \ No newline at end of file diff --git a/content/language/rust/build-images.md b/content/language/rust/build-images.md index 769e6eed2e..2ca4b413ee 100644 --- a/content/language/rust/build-images.md +++ b/content/language/rust/build-images.md @@ -204,4 +204,4 @@ Related information: In the next section learn how to run your image as a container. -[Run the image as a container](run-containers.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Run the image as a container" url="run-containers.md" >}} \ No newline at end of file diff --git a/content/language/rust/configure-ci-cd.md b/content/language/rust/configure-ci-cd.md index 70f2b93bb9..1ea699b93b 100644 --- a/content/language/rust/configure-ci-cd.md +++ b/content/language/rust/configure-ci-cd.md @@ -1,5 +1,5 @@ --- -title: "Configure CI/CD for your application" +title: Configure CI/CD for your application keywords: rust, CI/CD, local, development description: Learn how to Configure CI/CD for your application --- @@ -8,7 +8,7 @@ description: Learn how to Configure CI/CD for your application ## Get started with GitHub Actions -{% include gha-tutorial.md %} +{{< include "gha-tutorial.md" >}} ## Summary @@ -18,4 +18,4 @@ In this section, you have learned how to set up GitHub Actions workflow to an ex Next, learn how you can deploy your application. -[Deploy your app](deploy.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Deploy your app" url="deploy.md" >}} \ No newline at end of file diff --git a/content/language/rust/deploy.md b/content/language/rust/deploy.md index a5cfe22e28..55a148c149 100644 --- a/content/language/rust/deploy.md +++ b/content/language/rust/deploy.md @@ -1,9 +1,9 @@ --- -title: "Deploy your app" +title: Deploy your app keywords: deploy, ACI, ECS, rust, local, development description: Learn how to deploy your application --- {% include_relative nav.html selected="5" %} -{% include deploy.md %} +{{< include "deploy.md" >}} \ No newline at end of file diff --git a/content/language/rust/develop.md b/content/language/rust/develop.md index 095e66082c..a0f69da231 100644 --- a/content/language/rust/develop.md +++ b/content/language/rust/develop.md @@ -322,4 +322,4 @@ Related information: In the next section, you'll take a look at how to set up a CI/CD pipeline using GitHub Actions. -[Configure CI/CD](configure-ci-cd.md){: .button .primary-btn} \ No newline at end of file +{{< button text="Configure CI/CD" url="configure-ci-cd.md" >}} \ No newline at end of file diff --git a/content/language/rust/run-containers.md b/content/language/rust/run-containers.md index b459ef505d..8fef16de29 100644 --- a/content/language/rust/run-containers.md +++ b/content/language/rust/run-containers.md @@ -1,5 +1,5 @@ --- -title: "Run your Rust image as a container" +title: Run your Rust image as a container keywords: rust, run, image, container, description: Learn how to run your Rust image as a container. --- @@ -200,4 +200,4 @@ Related information: In the next section, you’ll learn how to run a database in a container and connect it to a Rust application. -[How to develop your application](develop.md){: .button .primary-btn} \ No newline at end of file +{{< button text="How to develop your application" url="develop.md" >}} \ No newline at end of file diff --git a/content/network/_index.md b/content/network/_index.md index bd1638870f..01bd4ad009 100644 --- a/content/network/_index.md +++ b/content/network/_index.md @@ -2,15 +2,15 @@ title: Networking overview description: How networking works from the container's point of view keywords: networking, container, standalone -redirect_from: - - /articles/networking/ - - /config/containers/container-networking/ - - /engine/userguide/networking/ - - /engine/userguide/networking/configure-dns/ - - /engine/userguide/networking/default_network/binding/ - - /engine/userguide/networking/default_network/configure-dns/ - - /engine/userguide/networking/default_network/container-communication/ - - /engine/userguide/networking/dockernetworks/ +aliases: +- /articles/networking/ +- /config/containers/container-networking/ +- /engine/userguide/networking/ +- /engine/userguide/networking/configure-dns/ +- /engine/userguide/networking/default_network/binding/ +- /engine/userguide/networking/default_network/configure-dns/ +- /engine/userguide/networking/default_network/container-communication/ +- /engine/userguide/networking/dockernetworks/ --- Container networking refers to the ability for containers to connect to and @@ -64,8 +64,8 @@ Here are some examples: > > network switch) can reach ports published to localhost. > > For more information, see > > [moby/moby#45610](https://github.com/moby/moby/issues/45610) -> {: .warning } -{: .important } +> { .warning } +{ .important } If you want to make a container accessible to other containers, it isn't necessary to publish the container's ports. @@ -141,4 +141,4 @@ in the `docker run` reference documentation. ## Proxy server If your container needs to use a proxy server, see -[Use a proxy server](proxy.md). +[Use a proxy server](proxy.md). \ No newline at end of file diff --git a/content/network/drivers/_index.md b/content/network/drivers/_index.md index 2f86a8298c..f574b55fcf 100644 --- a/content/network/drivers/_index.md +++ b/content/network/drivers/_index.md @@ -73,4 +73,4 @@ understanding using the following tutorials: - [Standalone networking tutorial](../network-tutorial-standalone.md) - [Host networking tutorial](../network-tutorial-host.md) - [Overlay networking tutorial](../network-tutorial-overlay.md) -- [Macvlan networking tutorial](../network-tutorial-macvlan.md) +- [Macvlan networking tutorial](../network-tutorial-macvlan.md) \ No newline at end of file diff --git a/content/network/drivers/bridge.md b/content/network/drivers/bridge.md index d12e52ee56..3c07afedd5 100644 --- a/content/network/drivers/bridge.md +++ b/content/network/drivers/bridge.md @@ -2,13 +2,13 @@ title: Bridge network driver description: All about using user-defined bridge networks and the default bridge keywords: network, bridge, user-defined, standalone -redirect_from: - - /config/containers/bridges/ - - /engine/userguide/networking/default_network/build-bridges/ - - /engine/userguide/networking/default_network/custom-docker0/ - - /engine/userguide/networking/default_network/dockerlinks/ - - /engine/userguide/networking/work-with-networks/ - - /network/bridge/ +aliases: +- /config/containers/bridges/ +- /engine/userguide/networking/default_network/build-bridges/ +- /engine/userguide/networking/default_network/custom-docker0/ +- /engine/userguide/networking/default_network/dockerlinks/ +- /engine/userguide/networking/work-with-networks/ +- /network/bridge/ --- In terms of networking, a bridge network is a Link Layer device @@ -255,11 +255,11 @@ inter-container communications may break when 1000 containers or more connect to a single network. For more information about this limitation, see -[moby/moby#44973](https://github.com/moby/moby/issues/44973#issuecomment-1543747718){: target="_blank" rel="noopener"}. +[moby/moby#44973](https://github.com/moby/moby/issues/44973#issuecomment-1543747718). ## Next steps - Go through the [standalone networking tutorial](../network-tutorial-standalone.md) - Learn about [networking from the container's point of view](../index.md) - Learn about [overlay networks](overlay.md) -- Learn about [Macvlan networks](macvlan.md) +- Learn about [Macvlan networks](macvlan.md) \ No newline at end of file diff --git a/content/network/drivers/host.md b/content/network/drivers/host.md index 8b1679ba84..7ede367e6e 100644 --- a/content/network/drivers/host.md +++ b/content/network/drivers/host.md @@ -2,8 +2,8 @@ title: Host network driver description: All about exposing containers on the Docker host's network keywords: network, host, standalone -redirect_from: - - /network/host/ +aliases: +- /network/host/ --- If you use the `host` network mode for a container, that container's network @@ -45,4 +45,4 @@ given swarm node. - Learn about [networking from the container's point of view](../index.md) - Learn about [bridge networks](bridge.md) - Learn about [overlay networks](overlay.md) -- Learn about [Macvlan networks](macvlan.md) +- Learn about [Macvlan networks](macvlan.md) \ No newline at end of file diff --git a/content/network/drivers/ipvlan.md b/content/network/drivers/ipvlan.md index 42d9da0b79..d44253c60f 100644 --- a/content/network/drivers/ipvlan.md +++ b/content/network/drivers/ipvlan.md @@ -1,9 +1,10 @@ --- title: IPvlan network driver -description: All about using IPvlan to make your containers appear like physical machines on the network +description: All about using IPvlan to make your containers appear like physical machines + on the network keywords: network, ipvlan, l2, l3, standalone -redirect_from: - - /network/ipvlan/ +aliases: +- /network/ipvlan/ --- The IPvlan driver gives users total control over both IPv4 and IPv6 addressing. @@ -639,4 +640,4 @@ $ ip link del foo As with all of the Libnetwork drivers, they can be mixed and matched, even as far as running 3rd party ecosystem drivers in parallel for maximum flexibility -to the Docker user. +to the Docker user. \ No newline at end of file diff --git a/content/network/drivers/macvlan.md b/content/network/drivers/macvlan.md index 1eb26b76f1..3eb96b98d1 100644 --- a/content/network/drivers/macvlan.md +++ b/content/network/drivers/macvlan.md @@ -3,10 +3,10 @@ title: Macvlan network driver description: All about using Macvlan to make your containers appear like physical machines on the network keywords: network, macvlan, standalone -redirect_from: - - /config/containers/macvlan/ - - /engine/userguide/networking/get-started-macvlan/ - - /network/macvlan/ +aliases: +- /config/containers/macvlan/ +- /engine/userguide/networking/get-started-macvlan/ +- /network/macvlan/ --- Some applications, especially legacy applications or applications which monitor @@ -122,4 +122,4 @@ $ docker network create -d macvlan \ ## Next steps Learn how to use the Macvlan driver in the -[Macvlan networking tutorial](../network-tutorial-macvlan.md) +[Macvlan networking tutorial](../network-tutorial-macvlan.md) \ No newline at end of file diff --git a/content/network/drivers/none.md b/content/network/drivers/none.md index 354925eefc..16e24e62df 100644 --- a/content/network/drivers/none.md +++ b/content/network/drivers/none.md @@ -2,8 +2,8 @@ title: None network driver description: How to isolate the networking stack of a container using the none driver keywords: network, none, standalone -redirect_from: - - /network/none/ +aliases: +- /network/none/ --- If you want to completely isolate the networking stack of a container, you can @@ -35,4 +35,4 @@ $ docker run --rm --network none --name no-net-alpine alpine:latest ip addr show - Learn about [networking from the container's point of view](../index.md) - Learn about [bridge networks](bridge.md) - Learn about [overlay networks](overlay.md) -- Learn about [Macvlan networks](macvlan.md) +- Learn about [Macvlan networks](macvlan.md) \ No newline at end of file diff --git a/content/network/drivers/overlay.md b/content/network/drivers/overlay.md index 9f82f79a38..d4dbd7b182 100644 --- a/content/network/drivers/overlay.md +++ b/content/network/drivers/overlay.md @@ -2,10 +2,10 @@ title: Overlay network driver description: All about using overlay networks keywords: network, overlay, user-defined, swarm, service -redirect_from: - - /config/containers/overlay/ - - /engine/userguide/networking/overlay-security-model/ - - /network/overlay/ +aliases: +- /config/containers/overlay/ +- /engine/userguide/networking/overlay-security-model/ +- /network/overlay/ --- The `overlay` network driver creates a distributed network among multiple @@ -98,7 +98,7 @@ automatically rotate the keys every 12 hours. > Overlay network encryption is not supported on Windows. If a Windows node > attempts to connect to an encrypted overlay network, no error is detected but > the node cannot communicate. -{: .warning } +{ .warning } #### Swarm mode overlay networks and standalone containers @@ -292,11 +292,11 @@ inter-container communications may break when 1000 containers are co-located on the same host. For more information about this limitation, see -[moby/moby#44973](https://github.com/moby/moby/issues/44973#issuecomment-1543747718){: target="_blank" rel="noopener"}. +[moby/moby#44973](https://github.com/moby/moby/issues/44973#issuecomment-1543747718). ## Next steps - Go through the [overlay networking tutorial](../network-tutorial-overlay.md) - Learn about [networking from the container's point of view](../index.md) - Learn about [standalone bridge networks](bridge.md) -- Learn about [Macvlan networks](macvlan.md) +- Learn about [Macvlan networks](macvlan.md) \ No newline at end of file diff --git a/content/network/links.md b/content/network/links.md index 49c07e45b3..14f3b313df 100644 --- a/content/network/links.md +++ b/content/network/links.md @@ -1,10 +1,11 @@ --- description: Learn how to connect Docker containers together. -keywords: Examples, Usage, user guide, links, linking, docker, documentation, examples, names, name, container naming, port, map, network port, network -redirect_from: +keywords: Examples, Usage, user guide, links, linking, docker, documentation, examples, + names, name, container naming, port, map, network port, network +title: Legacy container links +aliases: - /userguide/dockerlinks/ - /engine/userguide/networking/default_network/dockerlinks/ -title: Legacy container links --- >**Warning** @@ -19,7 +20,7 @@ between containers in a more controlled way. > > See [Differences between user-defined bridges and the default bridge](drivers/bridge.md#differences-between-user-defined-bridges-and-the-default-bridge) > for some alternatives to using `--link`. -{:.warning} +{ .warning } The information in this section explains legacy container links within the Docker default `bridge` network which is created automatically when you install @@ -225,13 +226,13 @@ $ docker run -d -P --name web --link db training/webapp python app.py Next, inspect your linked containers with `docker inspect`: -{% raw %} + ```console $ docker inspect -f "{{ .HostConfig.Links }}" web [/db:/web/db] ``` -{% endraw %} + You can see that the `web` container is now linked to the `db` container `web/db`. Which allows it to access information about the `db` container. @@ -270,7 +271,7 @@ target container of information related to the source container. > from Docker within a container are made available to *any* container > that links to it. This could have serious security implications if sensitive > data is stored in them. -{:.warning} +{ .warning } Docker sets an `_NAME` environment variable for each target container listed in the `--link` parameter. For example, if a new container called @@ -409,4 +410,4 @@ root@aed84ee21bde:/opt/webapp# cat /etc/hosts 172.17.0.7 aed84ee21bde <...> 172.17.0.9 db -``` +``` \ No newline at end of file diff --git a/content/network/network-tutorial-host.md b/content/network/network-tutorial-host.md index ac8714ecce..df4c57017e 100644 --- a/content/network/network-tutorial-host.md +++ b/content/network/network-tutorial-host.md @@ -66,5 +66,4 @@ you might want to run through these other networking tutorials: - [Standalone networking tutorial](network-tutorial-standalone.md) - [Overlay networking tutorial](network-tutorial-overlay.md) -- [Macvlan networking tutorial](network-tutorial-macvlan.md) - +- [Macvlan networking tutorial](network-tutorial-macvlan.md) \ No newline at end of file diff --git a/content/network/network-tutorial-macvlan.md b/content/network/network-tutorial-macvlan.md index 16a379794d..cab208bac6 100644 --- a/content/network/network-tutorial-macvlan.md +++ b/content/network/network-tutorial-macvlan.md @@ -1,6 +1,7 @@ --- title: Networking using a macvlan network -description: Tutorials for networking using a macvlan bridge network and 802.1Q trunk bridge network +description: Tutorials for networking using a macvlan bridge network and 802.1Q trunk + bridge network keywords: networking, macvlan, 802.1Q, standalone --- @@ -220,5 +221,4 @@ you might want to run through these other networking tutorials: - [Standalone networking tutorial](network-tutorial-standalone.md) - [Overlay networking tutorial](network-tutorial-overlay.md) -- [Host networking tutorial](network-tutorial-host.md) - +- [Host networking tutorial](network-tutorial-host.md) \ No newline at end of file diff --git a/content/network/network-tutorial-overlay.md b/content/network/network-tutorial-overlay.md index 4f4dba9cdf..5d5c684587 100644 --- a/content/network/network-tutorial-overlay.md +++ b/content/network/network-tutorial-overlay.md @@ -1,8 +1,9 @@ --- title: Networking with overlay networks -description: Tutorials for networking with swarm services and standalone containers on multiple Docker daemons +description: Tutorials for networking with swarm services and standalone containers + on multiple Docker daemons keywords: networking, bridge, routing, ports, swarm, overlay -redirect_from: +aliases: - /engine/userguide/networking/get-started-overlay/ --- @@ -638,4 +639,4 @@ you might want to run through these other networking tutorials: - [Host networking tutorial](network-tutorial-host.md) - [Standalone networking tutorial](network-tutorial-standalone.md) -- [Macvlan networking tutorial](network-tutorial-macvlan.md) +- [Macvlan networking tutorial](network-tutorial-macvlan.md) \ No newline at end of file diff --git a/content/network/network-tutorial-standalone.md b/content/network/network-tutorial-standalone.md index db9279689d..1b4f4dc450 100644 --- a/content/network/network-tutorial-standalone.md +++ b/content/network/network-tutorial-standalone.md @@ -620,5 +620,4 @@ you might want to run through these other networking tutorials: - [Host networking tutorial](network-tutorial-host.md) - [Overlay networking tutorial](network-tutorial-overlay.md) -- [Macvlan networking tutorial](network-tutorial-macvlan.md) - +- [Macvlan networking tutorial](network-tutorial-macvlan.md) \ No newline at end of file diff --git a/content/network/packet-filtering-firewalls.md b/content/network/packet-filtering-firewalls.md index 52c68cbfb9..16c27e5ff0 100644 --- a/content/network/packet-filtering-firewalls.md +++ b/content/network/packet-filtering-firewalls.md @@ -2,8 +2,8 @@ title: Packet filtering and firewalls description: How Docker works with packet filtering, iptables, and firewalls keywords: network, iptables, firewall -redirect_from: - - /network/iptables/ +aliases: +- /network/iptables/ --- On Linux, Docker manipulates `iptables` rules to provide network isolation. @@ -55,7 +55,7 @@ $ sudo iptables -I DOCKER-USER -p tcp -m conntrack --ctorigsrc 1.2.3.4 --ctorigd > **Important** > > Using the `conntrack` extension may result in degraded performance. -{: .important } +{ .important } ### Restrict connections to the Docker host @@ -155,7 +155,7 @@ $ docker network create mybridge \ ## Integration with Firewalld -If you are running Docker with [firewalld](https://firewalld.org){: target="blank" rel="noopener" class=“”} +If you are running Docker with [firewalld](https://firewalld.org) on your system with `--iptables` enabled, Docker automatically creates a `firewalld` zone called `docker` and inserts all the network interfaces it creates (for example, `docker0`) into the `docker` zone to allow seamless networking. @@ -172,7 +172,7 @@ Restarting `dockerd` daemon inserts the interface into the `docker` zone. ## Docker and ufw -[Uncomplicated Firewall](https://launchpad.net/ufw){: target="_blank" rel="noopener"} +[Uncomplicated Firewall](https://launchpad.net/ufw) (ufw) is a frontend that ships with Debian and Ubuntu, and it lets you manage firewall rules. Docker and ufw use iptables in ways that make them incompatible with each other. @@ -182,4 +182,4 @@ container gets diverted before it goes through the ufw firewall settings. Docker routes container traffic in the `nat` table, which means that packets are diverted before it reaches the `INPUT` and `OUTPUT` chains that ufw uses. Packets are routed before the firewall rules can be applied, -effectively ignoring your firewall configuration. +effectively ignoring your firewall configuration. \ No newline at end of file diff --git a/content/network/proxy.md b/content/network/proxy.md index 73a76b1e69..157cf2d7e4 100644 --- a/content/network/proxy.md +++ b/content/network/proxy.md @@ -30,7 +30,7 @@ configure it in different ways: > > If you're interested in the history of these variables, check out this blog > post on the subject, by the GitLab team: -> [We need to talk: Can we standardize NO_PROXY?](https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/){: target="_blank" rel="noopener"}. +> [We need to talk: Can we standardize NO_PROXY?](https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/). ## Configure the Docker client @@ -59,7 +59,7 @@ Builds and containers use the configuration specified in this file. > Environment variables are stored as plain text in the container's configuration, > and as such can be inspected through the remote API or committed to an image > when using `docker commit`. -{: .warning } +{ .warning } The configuration becomes active after saving the file, you don't need to restart Docker. However, the configuration only applies to new containers and @@ -188,5 +188,4 @@ If the proxy is an internal proxy, it might not be accessible for containers created from that image. Embedding proxy settings in images also poses a security risk, as the values -may include sensitive information. - +may include sensitive information. \ No newline at end of file diff --git a/content/reference.md b/content/reference.md index 59d2a57a22..44783b8784 100644 --- a/content/reference.md +++ b/content/reference.md @@ -1,81 +1,83 @@ --- title: Reference documentation -description: This section includes the reference documentation for the Docker platform’s various APIs, CLIs, and file formats. +description: This section includes the reference documentation for the Docker platform’s + various APIs, CLIs, and file formats. notoc: true skip_read_time: true -redirect_from: - - /app/working-with-app/ - - /engine/reference/commandline/app/ - - /engine/reference/commandline/app_bundle/ - - /engine/reference/commandline/app_completion/ - - /engine/reference/commandline/app_init/ - - /engine/reference/commandline/app_inspect/ - - /engine/reference/commandline/app_install/ - - /engine/reference/commandline/app_list/ - - /engine/reference/commandline/app_merge/ - - /engine/reference/commandline/app_pull/ - - /engine/reference/commandline/app_push/ - - /engine/reference/commandline/app_render/ - - /engine/reference/commandline/app_split/ - - /engine/reference/commandline/app_status/ - - /engine/reference/commandline/app_uninstall/ - - /engine/reference/commandline/app_upgrade/ - - /engine/reference/commandline/app_validate/ - - /engine/reference/commandline/app_validate/ - - /engine/reference/commandline/app_version/ grid_files: - - title: Dockerfile - description: - Defines the contents and startup behavior of a single container. - icon: edit_document - link: /engine/reference/builder/ - - title: Compose file - description: Defines a multi-container application. - icon: polyline - link: /compose/compose-file/ +- title: Dockerfile + description: Defines the contents and startup behavior of a single container. + icon: edit_document + link: /engine/reference/builder/ +- title: Compose file + description: Defines a multi-container application. + icon: polyline + link: /compose/compose-file/ grid_clis: - - title: Docker CLI - description: The main Docker CLI, includes all `docker` commands. - icon: terminal - link: /engine/reference/commandline/cli/ - - title: Compose CLI - description: The CLI for Docker Compose, for building and running multi-container applications. - icon: subtitles - link: /compose/reference/ - - title: Daemon CLI (dockerd) - description: Persistent process that manages containers. - icon: developer_board - link: /engine/reference/commandline/dockerd/ +- title: Docker CLI + description: The main Docker CLI, includes all `docker` commands. + icon: terminal + link: /engine/reference/commandline/cli/ +- title: Compose CLI + description: The CLI for Docker Compose, for building and running multi-container + applications. + icon: subtitles + link: /compose/reference/ +- title: Daemon CLI (dockerd) + description: Persistent process that manages containers. + icon: developer_board + link: /engine/reference/commandline/dockerd/ grid_apis: - - title: Engine API - description: The main API for Docker, provides programmatic access to a daemon. - icon: api - link: /engine/api/ - - title: Registry API - description: Facilitates distribution of images to the engine. - icon: storage - link: /registry/spec/api/ - - title: Docker Hub API - description: API to interact with Docker Hub. - icon: communities - link: /docker-hub/api/latest/ - - title: DVP Data API - description: API for Docker Verified Publishers to fetch analytics data. - icon: auto_graph - link: /docker-hub/api/dvp/ +- title: Engine API + description: The main API for Docker, provides programmatic access to a daemon. + icon: api + link: /engine/api/ +- title: Registry API + description: Facilitates distribution of images to the engine. + icon: storage + link: /registry/spec/api/ +- title: Docker Hub API + description: API to interact with Docker Hub. + icon: communities + link: /docker-hub/api/latest/ +- title: DVP Data API + description: API for Docker Verified Publishers to fetch analytics data. + icon: auto_graph + link: /docker-hub/api/dvp/ grid_specs: - - title: Image specification - description: Describes the various components of a Docker image. - icon: contract - link: /registry/spec/manifest-v2-2/ - - title: Registry token authentication - description: Outlines the Docker Registry authentication schemes. - icon: key - link: /registry/spec/auth/ - - title: Registry storage drivers - description: Enables support for given cloud providers when storing images with Registry. - icon: shelves - link: /registry/storage-drivers/ +- title: Image specification + description: Describes the various components of a Docker image. + icon: contract + link: /registry/spec/manifest-v2-2/ +- title: Registry token authentication + description: Outlines the Docker Registry authentication schemes. + icon: key + link: /registry/spec/auth/ +- title: Registry storage drivers + description: Enables support for given cloud providers when storing images with + Registry. + icon: shelves + link: /registry/storage-drivers/ +aliases: +- /app/working-with-app/ +- /engine/reference/commandline/app/ +- /engine/reference/commandline/app_bundle/ +- /engine/reference/commandline/app_completion/ +- /engine/reference/commandline/app_init/ +- /engine/reference/commandline/app_inspect/ +- /engine/reference/commandline/app_install/ +- /engine/reference/commandline/app_list/ +- /engine/reference/commandline/app_merge/ +- /engine/reference/commandline/app_pull/ +- /engine/reference/commandline/app_push/ +- /engine/reference/commandline/app_render/ +- /engine/reference/commandline/app_split/ +- /engine/reference/commandline/app_status/ +- /engine/reference/commandline/app_uninstall/ +- /engine/reference/commandline/app_upgrade/ +- /engine/reference/commandline/app_validate/ +- /engine/reference/commandline/app_validate/ +- /engine/reference/commandline/app_version/ --- This section includes the reference documentation for the Docker platform's @@ -95,4 +97,4 @@ various APIs, CLIs, drivers and specifications, and file formats. ## Drivers and specifications -{{< grid grid_specs >}} +{{< grid grid_specs >}} \ No newline at end of file diff --git a/content/registry/_index.md b/content/registry/_index.md index 03ed942fcf..f19ee175a2 100644 --- a/content/registry/_index.md +++ b/content/registry/_index.md @@ -1,12 +1,12 @@ --- description: High-level overview of the Registry keywords: registry, on-prem, images, tags, repository, distribution -redirect_from: -- /registry/overview/ title: Docker Registry +aliases: +- /registry/overview/ --- -{% include registry.md %} +{{< include "registry.md" >}} ## What it is @@ -14,7 +14,7 @@ The Registry is a stateless, highly scalable server side application that stores and lets you distribute Docker images. The Registry is open-source, under the permissive [Apache license](https://en.wikipedia.org/wiki/Apache_License). You can find the source code on -[GitHub](https://github.com/distribution/distribution){: target="blank" rel="noopener" class=""}. +[GitHub](https://github.com/distribution/distribution). ## Why use it @@ -64,4 +64,4 @@ Now stop your registry and remove all data ## Next You should now read the [detailed introduction about the registry](introduction.md), -or jump directly to [deployment instructions](deploying.md). +or jump directly to [deployment instructions](deploying.md). \ No newline at end of file diff --git a/content/registry/compatibility.md b/content/registry/compatibility.md index d162d8d4ff..e2dc41eef6 100644 --- a/content/registry/compatibility.md +++ b/content/registry/compatibility.md @@ -4,7 +4,7 @@ keywords: registry, manifest, images, tags, repository, distribution, digest title: Registry compatibility --- -{% include registry.md %} +{{< include "registry.md" >}} ## Synopsis If a manifest is pulled by _digest_ from a registry 2.3 with Docker Engine 1.9 @@ -76,5 +76,4 @@ The Docker Engine constructs a _Schema 1_ manifest which the registry persists to disk. When the manifest is pulled by digest or tag with any Docker version, a -_Schema 1_ manifest is returned. - +_Schema 1_ manifest is returned. \ No newline at end of file diff --git a/content/registry/deploying.md b/content/registry/deploying.md index a8b1664c48..19630ac783 100644 --- a/content/registry/deploying.md +++ b/content/registry/deploying.md @@ -4,7 +4,7 @@ keywords: registry, on-prem, images, tags, repository, distribution, deployment title: Deploy a registry server --- -{% include registry.md %} +{{< include "registry.md" >}} Before you can deploy a registry, you need to install Docker on the host. A registry is an instance of the `registry` image, and runs within Docker. @@ -33,7 +33,7 @@ The registry is now ready to use. > TLS and should ideally use an access-control mechanism. Keep reading and then > continue to the [configuration guide](configuration.md) to deploy a > production-ready registry. -{: .important} +{ .important } ## Copy an image from Docker Hub to your registry @@ -403,7 +403,7 @@ secrets. > credentials as clear text. You must > [configure TLS first](deploying.md#run-an-externally-accessible-registry) for > authentication to work. -{:.warning} +{ .warning } 1. Create a password file with one entry for the user `testuser`, with password `testpassword`: @@ -503,7 +503,7 @@ registry: Replace `/path` with the directory which contains the `certs/` and `auth/` directories. -{:.warning} +{ .warning } Start your registry by issuing the following command in the directory containing the `docker-compose.yml` file: @@ -573,4 +573,4 @@ More specific and advanced information is available in the following sections: - [Advanced "recipes"](recipes/index.md) - [Registry API](spec/api.md) - [Storage driver model](storage-drivers/index.md) - - [Token authentication](spec/auth/token.md) + - [Token authentication](spec/auth/token.md) \ No newline at end of file diff --git a/content/registry/deprecated.md b/content/registry/deprecated.md index a46b2c1fdc..af69e5c317 100644 --- a/content/registry/deprecated.md +++ b/content/registry/deprecated.md @@ -4,7 +4,7 @@ keywords: registry, manifest, images, signatures, repository, distribution, dige title: Docker Registry deprecation --- -{% include registry.md %} +{{< include "registry.md" >}} This document details functionality or components which are deprecated within the registry. diff --git a/content/registry/garbage-collection.md b/content/registry/garbage-collection.md index 8732c761eb..53048eda31 100644 --- a/content/registry/garbage-collection.md +++ b/content/registry/garbage-collection.md @@ -4,7 +4,7 @@ keywords: registry, garbage, images, tags, repository, distribution title: Garbage collection --- -{% include registry.md %} +{{< include "registry.md" >}} As of v2.4.0 a garbage collector command is included within the registry binary. This document describes what this command does and how and why it should be used. @@ -123,4 +123,4 @@ blob eligible for deletion: sha256:7e15ce58ccb2181a8fced7709e9893206f0937cc9543b blob eligible for deletion: sha256:87192bdbe00f8f2a62527f36bb4c7c7f4eaf9307e4b87e8334fb6abec1765bcb blob eligible for deletion: sha256:b549a9959a664038fc35c155a95742cf12297672ca0ae35735ec027d55bf4e97 blob eligible for deletion: sha256:f251d679a7c61455f06d793e43c06786d7766c88b8c24edf242b2c08e3c3f599 -``` +``` \ No newline at end of file diff --git a/content/registry/glossary.md b/content/registry/glossary.md index b07cfc0c36..a40398f9ed 100644 --- a/content/registry/glossary.md +++ b/content/registry/glossary.md @@ -65,4 +65,4 @@ This page contains definitions for distribution related terms. - + \ No newline at end of file diff --git a/content/registry/help.md b/content/registry/help.md index a0a908572d..a560811056 100644 --- a/content/registry/help.md +++ b/content/registry/help.md @@ -4,12 +4,11 @@ keywords: registry, on-prem, images, tags, repository, distribution, help, 101, title: Get help --- -{% include registry.md %} +{{< include "registry.md" >}} If you need help, or just want to chat about development, you can reach us on the #distribution channel in the CNCF Slack. If you want to report a bug: - be sure to first read about [how to contribute](https://github.com/distribution/distribution/blob/master/CONTRIBUTING.md). -- you can then do so on the [GitHub project bugtracker](https://github.com/distribution/distribution/issues). - +- you can then do so on the [GitHub project bugtracker](https://github.com/distribution/distribution/issues). \ No newline at end of file diff --git a/content/registry/insecure.md b/content/registry/insecure.md index e411e27341..d9333731b2 100644 --- a/content/registry/insecure.md +++ b/content/registry/insecure.md @@ -4,7 +4,7 @@ keywords: registry, on-prem, images, tags, repository, distribution, insecure title: Test an insecure registry --- -{% include registry.md %} +{{< include "registry.md" >}} While it's highly recommended to secure your registry using a TLS certificate issued by a known CA, you can choose to use self-signed certificates, or use @@ -15,7 +15,7 @@ involves security trade-offs and additional configuration steps. > **Warning**: > It's not possible to use an insecure registry with basic authentication. -{:.warning} +{ .warning } This procedure configures Docker to entirely disregard security for your registry. This is **very** insecure and is not recommended. It exposes your @@ -57,7 +57,7 @@ Repeat these steps on every Engine host that wants to access your registry. > **Warning**: > Using this along with basic authentication requires to **also** trust the certificate into the OS cert store for some versions of docker (see below) -{:.warning} +{ .warning } This is more secure than the insecure registry solution. @@ -97,11 +97,11 @@ This is more secure than the insecure registry solution. 3. Click **Finish**. Restart Docker. - **Docker Desktop for Mac**: Follow the instructions in - [Adding custom CA certificates](../desktop/faqs/macfaqs.md#add-custom-ca-certificates-server-side){: target="_blank" rel="noopener" class="_"}. + [Adding custom CA certificates](../desktop/faqs/macfaqs.md#add-custom-ca-certificates-server-side). Restart Docker. - **Docker Desktop for Windows**: Follow the instructions in - [Adding custom CA certificates](../desktop/faqs/windowsfaqs.md#how-do-i-add-custom-ca-certificates){: target="_blank" rel="noopener" class="_"}. + [Adding custom CA certificates](../desktop/faqs/windowsfaqs.md#how-do-i-add-custom-ca-certificates). Restart Docker. @@ -164,4 +164,4 @@ Then, select the following options: [Learn more about managing TLS certificates](https://technet.microsoft.com/en-us/library/cc754841(v=ws.11).aspx#BKMK_addlocal). -After adding the CA certificate to Windows, restart Docker Desktop for Windows. +After adding the CA certificate to Windows, restart Docker Desktop for Windows. \ No newline at end of file diff --git a/content/registry/introduction.md b/content/registry/introduction.md index bb634861ad..e790541888 100644 --- a/content/registry/introduction.md +++ b/content/registry/introduction.md @@ -4,7 +4,7 @@ keywords: registry, on-prem, images, tags, repository, distribution, use cases, title: About Registry --- -{% include registry.md %} +{{< include "registry.md" >}} A registry is a storage and content delivery system, holding named Docker images, available in different tagged versions. @@ -72,4 +72,4 @@ golang are certainly useful as well for advanced operations or hacking. ## Next -Dive into [deploying your registry](deploying.md) +Dive into [deploying your registry](deploying.md) \ No newline at end of file diff --git a/content/registry/migration.md b/content/registry/migration.md index e46441cb0a..30a2df180b 100644 --- a/content/registry/migration.md +++ b/content/registry/migration.md @@ -25,4 +25,4 @@ The Docker Registry 2.0 is backward compatible with images created by the earlie 3. Stop your existing registry service. -4. Restart your registry with your tested 2.0 image. +4. Restart your registry with your tested 2.0 image. \ No newline at end of file diff --git a/content/registry/notifications.md b/content/registry/notifications.md index 6f44c8a251..d3c5b652de 100644 --- a/content/registry/notifications.md +++ b/content/registry/notifications.md @@ -1,10 +1,11 @@ --- description: Explains how to work with registry notifications -keywords: registry, on-prem, images, tags, repository, distribution, notifications, advanced +keywords: registry, on-prem, images, tags, repository, distribution, notifications, + advanced title: Work with notifications --- -{% include registry.md %} +{{< include "registry.md" >}} The Registry supports sending webhook notifications in response to events happening within the registry. Notifications are sent in response to manifest @@ -347,4 +348,4 @@ provide acceptable guarantees, adding a transactional `Sink` to the registry is a possibility, although it may have an effect on request service time. See the [godoc](https://godoc.org/github.com/docker/distribution/notifications#Sink) -for more information. +for more information. \ No newline at end of file diff --git a/content/registry/recipes/_index.md b/content/registry/recipes/_index.md index c7c0cae326..ace9964bec 100644 --- a/content/registry/recipes/_index.md +++ b/content/registry/recipes/_index.md @@ -4,7 +4,7 @@ keywords: registry, on-prem, images, tags, repository, distribution, recipes, ad title: Recipes overview --- -{% include registry.md %} +{{< include "registry.md" >}} This list of "recipes" provides end-to-end scenarios for exotic or otherwise advanced use-cases. These recipes are not useful for most standard set-ups. @@ -26,4 +26,4 @@ At this point, it's assumed that: * [using Apache as an authenticating proxy](apache.md) * [using Nginx as an authenticating proxy](nginx.md) * [running a Registry on macOS](osx-setup-guide.md) - * [mirror the Docker Hub](mirror.md) + * [mirror the Docker Hub](mirror.md) \ No newline at end of file diff --git a/content/registry/recipes/apache.md b/content/registry/recipes/apache.md index 5721703036..f3d3f15cc0 100644 --- a/content/registry/recipes/apache.md +++ b/content/registry/recipes/apache.md @@ -1,10 +1,11 @@ --- description: Restricting access to your registry using an apache proxy -keywords: registry, on-prem, images, tags, repository, distribution, authentication, proxy, apache, httpd, TLS, recipe, advanced +keywords: registry, on-prem, images, tags, repository, distribution, authentication, + proxy, apache, httpd, TLS, recipe, advanced title: Authenticate proxy with apache --- -{% include registry.md %} +{{< include "registry.md" >}} ## Use-case @@ -208,4 +209,4 @@ Now, log in with a "pull-only" user (using `testuser` and `testpassword`), then Verify that the "pull-only" can NOT push: - docker push myregistrydomain.com:5043/test + docker push myregistrydomain.com:5043/test \ No newline at end of file diff --git a/content/registry/recipes/mirror.md b/content/registry/recipes/mirror.md index facc500b3b..744eaea783 100644 --- a/content/registry/recipes/mirror.md +++ b/content/registry/recipes/mirror.md @@ -1,12 +1,13 @@ --- description: Setting-up a local mirror for Docker Hub images -keywords: registry, on-prem, images, tags, repository, distribution, mirror, Hub, recipe, advanced +keywords: registry, on-prem, images, tags, repository, distribution, mirror, Hub, + recipe, advanced title: Registry as a pull through cache -redirect_from: +aliases: - /engine/admin/registry_mirror/ --- -{% include registry.md %} +{{< include "registry.md" >}} ## Use-case @@ -35,7 +36,7 @@ Hub can be mirrored. > **Note** > -> Mirrors of Docker Hub are still subject to Docker's [fair usage policy](https://www.docker.com/pricing/resource-consumption-updates){: target="blank" rel="noopener" class=“”}. +> Mirrors of Docker Hub are still subject to Docker's [fair usage policy](https://www.docker.com/pricing/resource-consumption-updates). ### Solution @@ -129,4 +130,4 @@ Save the file and reload Docker for the change to take effect. > ``` > > It's telling you that the file doesn't exist yet in the local cache and is -> being pulled from upstream. +> being pulled from upstream. \ No newline at end of file diff --git a/content/registry/recipes/nginx.md b/content/registry/recipes/nginx.md index a46bf9046c..045bce2209 100644 --- a/content/registry/recipes/nginx.md +++ b/content/registry/recipes/nginx.md @@ -1,12 +1,13 @@ --- description: Restricting access to your registry using a nginx proxy -keywords: registry, on-prem, images, tags, repository, distribution, nginx, proxy, authentication, TLS, recipe, advanced +keywords: registry, on-prem, images, tags, repository, distribution, nginx, proxy, + authentication, TLS, recipe, advanced title: Authenticate proxy with nginx -redirect_from: +aliases: - /registry/nginx/ --- -{% include registry.md %} +{{< include "registry.md" >}} ## Use-case @@ -201,4 +202,4 @@ tag and push your first image: docker login -u=testuser -p=testpassword -e=root@example.ch myregistrydomain.com:5043 docker tag ubuntu myregistrydomain.com:5043/test docker push myregistrydomain.com:5043/test - docker pull myregistrydomain.com:5043/test + docker pull myregistrydomain.com:5043/test \ No newline at end of file diff --git a/content/registry/recipes/osx-setup-guide.md b/content/registry/recipes/osx-setup-guide.md index 4de1c5570b..1d13cb82eb 100644 --- a/content/registry/recipes/osx-setup-guide.md +++ b/content/registry/recipes/osx-setup-guide.md @@ -1,10 +1,11 @@ --- description: Explains how to run a registry on macOS -keywords: registry, on-prem, images, tags, repository, distribution, macOS, recipe, advanced +keywords: registry, on-prem, images, tags, repository, distribution, macOS, recipe, + advanced title: macOS setup guide --- -{% include registry.md %} +{{< include "registry.md" >}} ## Use-case @@ -73,4 +74,4 @@ Start the Docker registry: ### Unload the docker registry service - launchctl unload ~/Library/LaunchAgents/com.docker.registry.plist + launchctl unload ~/Library/LaunchAgents/com.docker.registry.plist \ No newline at end of file diff --git a/content/registry/storage-drivers/_index.md b/content/registry/storage-drivers/_index.md index 750791bb1c..32abb16da9 100644 --- a/content/registry/storage-drivers/_index.md +++ b/content/registry/storage-drivers/_index.md @@ -1,12 +1,13 @@ --- description: Explains how to use storage drivers -keywords: registry, on-prem, images, tags, repository, distribution, storage drivers, advanced -redirect_from: -- /registry/storagedrivers/ +keywords: registry, on-prem, images, tags, repository, distribution, storage drivers, + advanced title: Docker Registry storage driver +aliases: +- /registry/storagedrivers/ --- -{% include registry.md %} +{{< include "registry.md" >}} This document describes the registry storage driver model, implementation, and explains how to contribute new storage drivers. @@ -57,4 +58,4 @@ Storage drivers should call `factory.Register` with their driver name in an `ini Storage driver test suites are provided in `storagedriver/testsuites/testsuites.go` and may be used for any storage driver written in Go. Tests can be registered using the `RegisterSuite` -function, which run the same set of tests for any registered drivers. +function, which run the same set of tests for any registered drivers. \ No newline at end of file diff --git a/content/registry/storage-drivers/azure.md b/content/registry/storage-drivers/azure.md index 6043750a80..fe2b2f093e 100644 --- a/content/registry/storage-drivers/azure.md +++ b/content/registry/storage-drivers/azure.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, azure title: Microsoft Azure storage driver --- -{% include registry.md %} +{{< include "registry.md" >}} An implementation of the `storagedriver.StorageDriver` interface which uses [Microsoft Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/) for object storage. @@ -23,4 +23,4 @@ An implementation of the `storagedriver.StorageDriver` interface which uses [Mic * To get information about [azure-blob-storage](https://azure.microsoft.com/en-us/services/storage/), visit the Microsoft website. -* You can use Microsoft's [Blob Service REST API](https://docs.microsoft.com/en-us/rest/api/storageservices/Blob-Service-REST-API) to [create a storage container](https://docs.microsoft.com/en-us/rest/api/storageservices/Create-Container). +* You can use Microsoft's [Blob Service REST API](https://docs.microsoft.com/en-us/rest/api/storageservices/Blob-Service-REST-API) to [create a storage container](https://docs.microsoft.com/en-us/rest/api/storageservices/Create-Container). \ No newline at end of file diff --git a/content/registry/storage-drivers/filesystem.md b/content/registry/storage-drivers/filesystem.md index f921673191..6274157203 100644 --- a/content/registry/storage-drivers/filesystem.md +++ b/content/registry/storage-drivers/filesystem.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, filesystem title: Filesystem storage driver --- -{% include registry.md %} +{{< include "registry.md" >}} An implementation of the `storagedriver.StorageDriver` interface which uses the local filesystem. @@ -18,4 +18,4 @@ bits. If `umask` bits are not set, the resulting permission will be `0777`. * `maxthreads`: (optional) The maximum number of simultaneous blocking filesystem operations permitted within the registry. Each operation spawns a new thread and may cause thread exhaustion issues if many are done in parallel. Defaults to -`100`, and cannot be lower than `25`. +`100`, and cannot be lower than `25`. \ No newline at end of file diff --git a/content/registry/storage-drivers/gcs.md b/content/registry/storage-drivers/gcs.md index d91842548d..f2af289829 100644 --- a/content/registry/storage-drivers/gcs.md +++ b/content/registry/storage-drivers/gcs.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, gcs, google, cloud title: Google Cloud Storage driver --- -{% include registry.md %} +{{< include "registry.md" >}} An implementation of the `storagedriver.StorageDriver` interface which uses Google Cloud for object storage. @@ -17,5 +17,4 @@ An implementation of the `storagedriver.StorageDriver` interface which uses Goog | `rootdirectory` | no | The root directory tree in which all registry files are stored. Defaults to the empty string (bucket root). If a prefix is used, the path `bucketname/` has to be pre-created before starting the registry. The prefix is applied to all Google Cloud Storage keys to allow you to segment data in your bucket if necessary.| | `chunksize` | no (default 5242880) | This is the chunk size used for uploading large blobs, must be a multiple of 256*1024. | -**Note:** Instead of a key file you can use [Google Application Default Credentials](https://developers.google.com/identity/protocols/application-default-credentials). - +**Note:** Instead of a key file you can use [Google Application Default Credentials](https://developers.google.com/identity/protocols/application-default-credentials). \ No newline at end of file diff --git a/content/registry/storage-drivers/inmemory.md b/content/registry/storage-drivers/inmemory.md index 6e91304542..3768127c91 100644 --- a/content/registry/storage-drivers/inmemory.md +++ b/content/registry/storage-drivers/inmemory.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, in-memory title: In-memory storage driver (testing only) --- -{% include registry.md %} +{{< include "registry.md" >}} For purely tests purposes, you can use the `inmemory` storage driver. This driver is an implementation of the `storagedriver.StorageDriver` interface which @@ -15,4 +15,4 @@ volatile memory, use the [`filesystem` driver](filesystem.md) on a ramdisk. ## Parameters -None +None \ No newline at end of file diff --git a/content/registry/storage-drivers/oss.md b/content/registry/storage-drivers/oss.md index 4a18c1f52c..d2b0ce65f1 100644 --- a/content/registry/storage-drivers/oss.md +++ b/content/registry/storage-drivers/oss.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, OSS, aliyun title: Aliyun OSS storage driver --- -{% include registry.md %} +{{< include "registry.md" >}} An implementation of the `storagedriver.StorageDriver` interface which uses [Aliyun OSS](https://www.alibabacloud.com/product/oss) for object storage. @@ -22,4 +22,4 @@ An implementation of the `storagedriver.StorageDriver` interface which uses | `encrypt` | no | Specifies whether you would like your data encrypted on the server side. Defaults to false if not specified. | | `secure` | no | Specifies whether to transfer data to the bucket over ssl or not. If you omit this value, `true` is used. | | `chunksize` | no | The default part size for multipart uploads (performed by WriteStream) to OSS. The default is 10 MB. Keep in mind that the minimum part size for OSS is 5MB. You might experience better performance for larger chunk sizes depending on the speed of your connection to OSS. | -| `rootdirectory` | no | The root directory tree in which to store all registry files. Defaults to an empty string (bucket root). | +| `rootdirectory` | no | The root directory tree in which to store all registry files. Defaults to an empty string (bucket root). | \ No newline at end of file diff --git a/content/registry/storage-drivers/s3.md b/content/registry/storage-drivers/s3.md index 81038d7f40..a71c3f2dbc 100644 --- a/content/registry/storage-drivers/s3.md +++ b/content/registry/storage-drivers/s3.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, S3 title: S3 storage driver --- -{% include registry.md %} +{{< include "registry.md" >}} An implementation of the `storagedriver.StorageDriver` interface which uses Amazon S3 or S3 compatible services for object storage. @@ -158,4 +158,4 @@ middleware: A CloudFront key-pair is required for all AWS accounts needing access to your CloudFront distribution. You must have access to your AWS account's root credentials to create the required Cloudfront keypair. For information, see [Creating CloudFront Key -Pairs](http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-trusted-signers.html#private-content-creating-cloudfront-key-pairs). +Pairs](http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-trusted-signers.html#private-content-creating-cloudfront-key-pairs). \ No newline at end of file diff --git a/content/registry/storage-drivers/swift.md b/content/registry/storage-drivers/swift.md index f0027ee84d..6d52213460 100644 --- a/content/registry/storage-drivers/swift.md +++ b/content/registry/storage-drivers/swift.md @@ -4,7 +4,7 @@ keywords: registry, service, driver, images, storage, swift title: OpenStack Swift storage driver --- -{% include registry.md %} +{{< include "registry.md" >}} An implementation of the `storagedriver.StorageDriver` interface that uses [OpenStack Swift](http://docs.openstack.org/developer/swift/) for object @@ -39,4 +39,4 @@ configuration file can specify the following optional parameters : | Optional parameter | Description | |:--------------|:---------| | `tempurlcontainerkey` | Specify whether to use container secret key to generate temporary URL when set to true, or the account secret key otherwise. | -| `tempurlmethods` | Array of HTTP methods that are supported by the TempURL middleware of the Swift server. For example: `["GET", "PUT", "HEAD", "POST", "DELETE"]` | +| `tempurlmethods` | Array of HTTP methods that are supported by the TempURL middleware of the Swift server. For example: `["GET", "PUT", "HEAD", "POST", "DELETE"]` | \ No newline at end of file diff --git a/content/release-lifecycle.md b/content/release-lifecycle.md index dfb745177f..a8f1797493 100644 --- a/content/release-lifecycle.md +++ b/content/release-lifecycle.md @@ -1,7 +1,8 @@ --- title: Product release lifecycle -description: describes to users the various stages of feature lifecycle from beta to GA. -keywords: beta, GA, Early Access, +description: describes to users the various stages of feature lifecycle from beta + to GA. +keywords: beta, GA, Early Access, --- This page details Docker's product release lifecycle and how Docker defines each stage. It also provides information on the product retirement process. Features and products may progress through some or all of these phases. @@ -82,6 +83,4 @@ We may need to accelerate the timeline for retirement of functionality in extenu Similarly, integrated third party software or services may need to be retired due to the third-party decision to change or retire their solution. In these situations, the pace of retirement will be out of our control. -However, even under these circumstances, we will provide as much advance notice as possible. - - +However, even under these circumstances, we will provide as much advance notice as possible. \ No newline at end of file diff --git a/content/release-notes.md b/content/release-notes.md index e742cb6648..0557608084 100644 --- a/content/release-notes.md +++ b/content/release-notes.md @@ -3,21 +3,21 @@ description: Release notes for Docker keywords: docker, documentation, about, technology, understanding, release title: Docker release notes grid: - - title: Docker Desktop - icon: web_asset - link: /desktop/release-notes/ - - title: Docker Engine - icon: settings_suggest - link: /desktop/release-notes/ - - title: Docker Compose - icon: storage - link: /compose/release-notes/ - - title: Docker Build - icon: construction - link: /build/release-notes/ - - title: Docker Hub - icon: widgets - link: /docker-hub/release-notes/ +- title: Docker Desktop + icon: web_asset + link: /desktop/release-notes/ +- title: Docker Engine + icon: settings_suggest + link: /desktop/release-notes/ +- title: Docker Compose + icon: storage + link: /compose/release-notes/ +- title: Docker Build + icon: construction + link: /build/release-notes/ +- title: Docker Hub + icon: widgets + link: /docker-hub/release-notes/ --- Find out what's new in Docker. Release notes contain information about new @@ -25,4 +25,4 @@ features, improvements, known issues, and bug fixes in each release. You can find release notes for each component in the Manuals section. We suggest that you regularly visit the release notes to learn about updates. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/samples/_index.md b/content/samples/_index.md index e54a866fb6..8b09cca684 100644 --- a/content/samples/_index.md +++ b/content/samples/_index.md @@ -1,9 +1,10 @@ --- title: Samples overview -description: Learn how to containerize different types of services by walking through Official Docker samples. +description: Learn how to containerize different types of services by walking through + Official Docker samples. cascade: layout: samples -redirect_from: +aliases: - /en/latest/examples/ - /engine/examples/ - /examples/ @@ -26,4 +27,4 @@ Learn how to containerize different types of services by walking through Officia [Gitea](../samples/gitea.md) \| [Nextcloud](../samples/nextcloud.md) \| [Portainer](../samples/portainer.md) \| [Prometheus](../samples/prometheus.md) \| [WordPress](../samples/wordpress.md) ## Other services -[Cloudflared](../samples/cloudflared.md) \| [Elasticsearch / Logstash / Kibana](../samples/elasticsearch.md) \| [Minecraft](../samples/minecraft.md) \| [NGINX](../samples/nginx.md) \| [Pi-hole](../samples/pi-hole.md) \| [Plex](../samples/plex.md) \| [Traefik](../samples/traefik.md) \| [WireGuard](../samples/wireguard.md) +[Cloudflared](../samples/cloudflared.md) \| [Elasticsearch / Logstash / Kibana](../samples/elasticsearch.md) \| [Minecraft](../samples/minecraft.md) \| [NGINX](../samples/nginx.md) \| [Pi-hole](../samples/pi-hole.md) \| [Plex](../samples/plex.md) \| [Traefik](../samples/traefik.md) \| [WireGuard](../samples/wireguard.md) \ No newline at end of file diff --git a/content/samples/django.md b/content/samples/django.md index ebba317818..b5ed354ed5 100644 --- a/content/samples/django.md +++ b/content/samples/django.md @@ -2,8 +2,8 @@ title: Django samples description: Docker samples for Django. service: django -redirect_from: - - /compose/django/ +aliases: +- /compose/django/ --- {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/dotnet.md b/content/samples/dotnet.md index b275e2cd54..7ba97d285d 100644 --- a/content/samples/dotnet.md +++ b/content/samples/dotnet.md @@ -2,10 +2,10 @@ title: .NET samples description: Docker samples for .NET. service: .net -redirect_from: - - /samples/dotnetcore/ - - /compose/aspnet-mssql-compose/ - - /samples/aspnet-mssql-compose/ +aliases: +- /samples/dotnetcore/ +- /compose/aspnet-mssql-compose/ +- /samples/aspnet-mssql-compose/ --- {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/java.md b/content/samples/java.md index f24580fcc3..f8c0ad5f7d 100644 --- a/content/samples/java.md +++ b/content/samples/java.md @@ -4,5 +4,4 @@ description: Docker samples for Java. service: java --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/javascript.md b/content/samples/javascript.md index b654e336b7..289d967c23 100644 --- a/content/samples/javascript.md +++ b/content/samples/javascript.md @@ -4,5 +4,4 @@ description: Docker samples for JavaScript. service: javascript --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/mariadb.md b/content/samples/mariadb.md index b8e21662dd..7b2a8e1a1c 100644 --- a/content/samples/mariadb.md +++ b/content/samples/mariadb.md @@ -4,5 +4,4 @@ description: Docker samples for MariaDB. service: mariadb --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/minecraft.md b/content/samples/minecraft.md index a07f76904e..cf0f65d1c9 100644 --- a/content/samples/minecraft.md +++ b/content/samples/minecraft.md @@ -4,5 +4,4 @@ description: Docker samples for Minecraft. service: minecraft --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/mongodb.md b/content/samples/mongodb.md index 6a8a0c3f93..6e56a099ef 100644 --- a/content/samples/mongodb.md +++ b/content/samples/mongodb.md @@ -4,5 +4,4 @@ description: Docker samples for MongoDB. service: mongodb --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/ms-sql.md b/content/samples/ms-sql.md index 71835348aa..f941c7d307 100644 --- a/content/samples/ms-sql.md +++ b/content/samples/ms-sql.md @@ -4,6 +4,4 @@ description: Docker samples for MS-SQL. service: ms-sql --- - - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/mysql.md b/content/samples/mysql.md index a8bb67e39b..2dbd23bbc3 100644 --- a/content/samples/mysql.md +++ b/content/samples/mysql.md @@ -4,5 +4,4 @@ description: Docker samples for MySQL. service: mysql --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/nextcloud.md b/content/samples/nextcloud.md index c9368038d8..c3995d05be 100644 --- a/content/samples/nextcloud.md +++ b/content/samples/nextcloud.md @@ -4,5 +4,4 @@ description: Docker samples for Nextcloud. service: nextcloud --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/nginx.md b/content/samples/nginx.md index 3e6b60b15b..dc547db266 100644 --- a/content/samples/nginx.md +++ b/content/samples/nginx.md @@ -4,5 +4,4 @@ description: Docker samples for NGINX. service: nginx --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/nodejs.md b/content/samples/nodejs.md index 0f783a2f20..c5e4c36bf3 100644 --- a/content/samples/nodejs.md +++ b/content/samples/nodejs.md @@ -4,5 +4,4 @@ description: Docker samples for Node.js. service: nodejs --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/php.md b/content/samples/php.md index a97b7db373..a32b3decd7 100644 --- a/content/samples/php.md +++ b/content/samples/php.md @@ -4,5 +4,4 @@ description: Docker samples for PHP. service: php --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/pi-hole.md b/content/samples/pi-hole.md index ef63693ef3..123a321dd8 100644 --- a/content/samples/pi-hole.md +++ b/content/samples/pi-hole.md @@ -4,5 +4,4 @@ description: Docker samples for Pi-hole. service: pi-hole --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/plex.md b/content/samples/plex.md index 462e5a3c9a..c370f245de 100644 --- a/content/samples/plex.md +++ b/content/samples/plex.md @@ -4,5 +4,4 @@ description: Docker samples for Plex. service: plex --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/portainer.md b/content/samples/portainer.md index 476a568527..586a4e77ca 100644 --- a/content/samples/portainer.md +++ b/content/samples/portainer.md @@ -4,5 +4,4 @@ description: Docker samples for Portainer. service: portainer --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/postgres.md b/content/samples/postgres.md index 0051fe785b..f14579a392 100644 --- a/content/samples/postgres.md +++ b/content/samples/postgres.md @@ -2,10 +2,9 @@ title: PostgreSQL samples description: Docker samples for PostgreSQL. service: postgresql -redirect_from: - - /engine/examples/postgresql_service/ - - /samples/postgresql_service/ +aliases: +- /engine/examples/postgresql_service/ +- /samples/postgresql_service/ --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/prometheus.md b/content/samples/prometheus.md index dfd3822b44..d35c65d500 100644 --- a/content/samples/prometheus.md +++ b/content/samples/prometheus.md @@ -4,5 +4,4 @@ description: Docker samples for Prometheus. service: prometheus --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/python.md b/content/samples/python.md index 1bdb7398b3..6824aae8c7 100644 --- a/content/samples/python.md +++ b/content/samples/python.md @@ -4,5 +4,4 @@ description: Docker samples for Python. service: python --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/rails.md b/content/samples/rails.md index 2c387d4f7c..de04d094aa 100644 --- a/content/samples/rails.md +++ b/content/samples/rails.md @@ -4,5 +4,4 @@ description: Docker samples for Rails. service: rails --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/react.md b/content/samples/react.md index 4ff32946e9..1f0683fb28 100644 --- a/content/samples/react.md +++ b/content/samples/react.md @@ -4,5 +4,4 @@ description: Docker samples for React. service: react --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/redis.md b/content/samples/redis.md index b5a53a863a..0e2f14b211 100644 --- a/content/samples/redis.md +++ b/content/samples/redis.md @@ -4,5 +4,4 @@ description: Docker samples for Redis. service: redis --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/ruby.md b/content/samples/ruby.md index a58c5c8ae6..0f6680dbd8 100644 --- a/content/samples/ruby.md +++ b/content/samples/ruby.md @@ -4,5 +4,4 @@ description: Docker samples for Ruby. service: ruby --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/rust.md b/content/samples/rust.md index 42e611fad8..ff3aea94ab 100644 --- a/content/samples/rust.md +++ b/content/samples/rust.md @@ -4,5 +4,4 @@ description: Docker samples for Rust. service: rust --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/spark.md b/content/samples/spark.md index d515acc35b..fd2b66ef8f 100644 --- a/content/samples/spark.md +++ b/content/samples/spark.md @@ -4,5 +4,4 @@ description: Docker samples for Spark. service: spark --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/spring.md b/content/samples/spring.md index 1c6b68b08d..cbeca3f418 100644 --- a/content/samples/spring.md +++ b/content/samples/spring.md @@ -4,5 +4,4 @@ description: Docker samples for Spring Boot. service: spring --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/traefik.md b/content/samples/traefik.md index 71bfd3cd6c..5ccd205aa5 100644 --- a/content/samples/traefik.md +++ b/content/samples/traefik.md @@ -4,5 +4,4 @@ description: Docker samples for Traefik. service: traefik --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/typescript.md b/content/samples/typescript.md index 2240fcd936..31cdf12966 100644 --- a/content/samples/typescript.md +++ b/content/samples/typescript.md @@ -4,5 +4,4 @@ description: Docker samples for TypeScript. service: typescript --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/vuejs.md b/content/samples/vuejs.md index dbf85f96a5..9cdaabb328 100644 --- a/content/samples/vuejs.md +++ b/content/samples/vuejs.md @@ -4,5 +4,4 @@ description: Docker samples for Vue.js. service: vuejs --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/wireguard.md b/content/samples/wireguard.md index bfe1cf6bc9..5400b3e145 100644 --- a/content/samples/wireguard.md +++ b/content/samples/wireguard.md @@ -4,5 +4,4 @@ description: Docker samples for WireGuard. service: wireguard --- - {% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/samples/wordpress.md b/content/samples/wordpress.md index d8a223a734..43fe2750c3 100644 --- a/content/samples/wordpress.md +++ b/content/samples/wordpress.md @@ -2,9 +2,8 @@ title: WordPress samples description: Docker samples for WordPress. service: wordpress -redirect_from: - - /compose/wordpress/ +aliases: +- /compose/wordpress/ --- - -{% include_relative samples-body.md %} +{% include_relative samples-body.md %} \ No newline at end of file diff --git a/content/scout/_index.md b/content/scout/_index.md index 5a0e2d0364..3a935880fc 100644 --- a/content/scout/_index.md +++ b/content/scout/_index.md @@ -1,19 +1,21 @@ --- title: Docker Scout keywords: scout, supply chain, vulnerabilities, packages, cves, scan, analysis, analyze -description: > - Docker Scout analyzes your images to help you understand their dependencies and potential vulnerabilities -redirect_from: - - /atomist/ - - /atomist/try-atomist/ - - /atomist/configure/settings/ - - /atomist/configure/advisories/ - - /atomist/integrate/github/ - - /atomist/integrate/deploys/ - - /engine/scan/ +description: 'Docker Scout analyzes your images to help you understand their dependencies + and potential vulnerabilities + + ' +aliases: +- /atomist/ +- /atomist/try-atomist/ +- /atomist/configure/settings/ +- /atomist/configure/advisories/ +- /atomist/integrate/github/ +- /atomist/integrate/deploys/ +- /engine/scan/ --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Container images are often built from layers of other container images and software packages. These layers and packages can contain vulnerabilities that @@ -29,7 +31,7 @@ You can use Docker Scout in [Docker Desktop](#docker-desktop), [Docker Hub](#doc and in the [Docker Scout Dashboard](./dashboard.md). Docker Scout also supports integrations with third-party systems, refer to [Integrating Docker Scout](./integrations/index.md) for more information. -{% include scout-plans.md %} +{{< include "scout-plans.md" >}} ## Quickstart @@ -40,7 +42,7 @@ _The following video shows an end-to-end workflow of using Docker Scout to remed > **Quickstart with Docker Scout** > > For a self-guided quickstart that shows you how to use Docker Scout to identify and remediate vulnerabilities in your images, read the [quickstart](./quickstart.md). -{: .tip } +{ .tip } ## Enabling Docker Scout @@ -109,9 +111,9 @@ and as [a GitHub action](https://github.com/docker/scout-action). ### Docker Scout Dashboard -The [Docker Scout Dashboard](https://scout.docker.com){: target="\_blank" rel="noopener" } +The [Docker Scout Dashboard](https://scout.docker.com) helps you share the analysis and security status of images in an organization with your team. You can also use the dashboard settings to enable Docker Scout on multiple images from Docker Hub at once. -For more information, read the [Docker Scout Dashboard guide](./dashboard.md). +For more information, read the [Docker Scout Dashboard guide](./dashboard.md). \ No newline at end of file diff --git a/content/scout/advanced-image-analysis.md b/content/scout/advanced-image-analysis.md index e47df3df07..e94c42d651 100644 --- a/content/scout/advanced-image-analysis.md +++ b/content/scout/advanced-image-analysis.md @@ -4,7 +4,7 @@ keywords: scanning, vulnerabilities, Hub, supply chain, security title: Advanced image analysis --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Advanced image analysis is a Docker Scout feature for Docker Hub. @@ -44,7 +44,7 @@ To activate Advanced image analysis: > > You can enable Advanced image analysis on repositories in bulk from > the [Docker Scout Dashboard settings](./dashboard.md#repository-settings). -{: .tip } +{ .tip } ## Analyze an image @@ -113,5 +113,4 @@ To deactivate Advanced image analysis: Thank you for trying out the Advanced image analysis feature. Give feedback or report any bugs you may find through the issues tracker on the -[hub-feedback](https://github.com/docker/hub-feedback/issues){: target="_blank" -rel="noopener" class="_"} GitHub repository. +[hub-feedback](https://github.com/docker/hub-feedback/issues) GitHub repository. \ No newline at end of file diff --git a/content/scout/advisory-db-sources.md b/content/scout/advisory-db-sources.md index cb91e6e8d5..0f3d0ab81d 100644 --- a/content/scout/advisory-db-sources.md +++ b/content/scout/advisory-db-sources.md @@ -1,10 +1,11 @@ --- -description: More details on the Advisory Database and CVE-to-package matching service behind Docker Scout analysis. +description: More details on the Advisory Database and CVE-to-package matching service + behind Docker Scout analysis. keywords: scanning, analysis, vulnerabilities, Hub, supply chain, security title: Advisory Database sources and matching service --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Docker Scout is a service that helps developers and security teams build and maintain a secure software supply chain. A key component of this is the ability @@ -117,4 +118,4 @@ By sourcing vulnerability data from the providers above, Docker Scout is able to - Ruby - `alpm` (Arch Linux) - `apk` (Alpine Linux) -- `deb` (Debian Linux and derivatives) +- `deb` (Debian Linux and derivatives) \ No newline at end of file diff --git a/content/scout/artifactory.md b/content/scout/artifactory.md index 213c54ab94..c52264d5f6 100644 --- a/content/scout/artifactory.md +++ b/content/scout/artifactory.md @@ -1,13 +1,16 @@ --- -description: > - Integrate JFrog Artifactory and JFrog Container Registry with Docker Scout -keywords: > - docker scout, jfrog, artifactory, jcr, integration, image analysis, security, +description: 'Integrate JFrog Artifactory and JFrog Container Registry with Docker + Scout + + ' +keywords: 'docker scout, jfrog, artifactory, jcr, integration, image analysis, security, cves + + ' title: Artifactory integration --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Integrating Docker Scout with JFrog Artifactory lets you run image analysis automatically on images in Artifactory registries. @@ -24,21 +27,19 @@ docker login {URL} > > For cloud-hosted Artifactory you can find the credentials for your Artifactory repository by > selecting it in the Artifactory UI and then the **Set Me Up** button. -{: .tip } +{ .tip } ## Remote image analysis To automatically analyze images running in remote environments you need to deploy the Docker Scout Artifactory agent. The agent is a standalone service that analyzes images and uploads the result to Docker Scout. You can view the results using the -[Docker Scout Dashboard](https://scout.docker.com/){: target="\_blank" rel="noopener" -}. +[Docker Scout Dashboard](https://scout.docker.com/). ### How the agent works The Docker Scout Artifactory agent is available as an -[image on Docker Hub](https://hub.docker.com/r/docker/artifactory-agent){: -target="\_blank" rel="noopener" }. The agent works by continuously polling +[image on Docker Hub](https://hub.docker.com/r/docker/artifactory-agent). The agent works by continuously polling Artifactory for new images. When it finds a new image, it performs the following steps: @@ -152,7 +153,7 @@ the container. Make sure the mount path you use is the directory containing the > > Use the `v1` tag of the Artifactory agent image. Don't use the `latest` tag as > doing so may incur breaking changes. -{: .important } +{ .important } ```console $ docker run \ @@ -197,4 +198,4 @@ You can view the image analysis results in the Docker Scout Dashboard. When you have selected a tag, you're taken to the vulnerability report for that tag. Here, you can select if you want to view all vulnerabilities in the image, or vulnerabilities introduced in a specific layer. You can also filter -vulnerabilities by severity, and whether or not there's a fix version available. +vulnerabilities by severity, and whether or not there's a fix version available. \ No newline at end of file diff --git a/content/scout/dashboard.md b/content/scout/dashboard.md index becd5c1fd8..be0143c720 100644 --- a/content/scout/dashboard.md +++ b/content/scout/dashboard.md @@ -1,13 +1,14 @@ --- description: The Docker Scout Dashboard helps review and share the analysis of images. -keywords: scanning, analysis, vulnerabilities, Hub, supply chain, security, report, reports, dashboard +keywords: scanning, analysis, vulnerabilities, Hub, supply chain, security, report, + reports, dashboard title: Dashboard -redirect_from: - - /scout/reports/ - - /scout/web-app/ +aliases: +- /scout/reports/ +- /scout/web-app/ --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} The Docker Scout Dashboard helps you share the analysis of images in an organization with your team. Developers can now see an overview of their security status across all their images from both Docker Hub and Artifactory, and get remediation advice at their fingertips. It helps team members in roles such as security, compliance, and operations to know what vulnerabilities and issues they need to focus on. @@ -65,7 +66,7 @@ Each entry in the list shows the following details: > **Tip** > > Compare two image tags by selecting the checkboxes next to them and selecting the **Compare images** button at the top of the list. - {: .tip } + { .tip } - The tag version. Clicking the link for version opens [the image layer view](#image-layer-view). - The operating system and architecture of the image. diff --git a/content/scout/data-handling.md b/content/scout/data-handling.md index e3a15ee2ac..64b7b8bc7f 100644 --- a/content/scout/data-handling.md +++ b/content/scout/data-handling.md @@ -4,7 +4,7 @@ keywords: scanning, supply chain, security, data, metadata title: Data collection and storage in Docker Scout --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Docker Scout image analysis works by collecting metadata from the container images that you analyze. This metadata is stored on the Docker Scout platform. @@ -58,4 +58,4 @@ For the purposes of providing the Docker Scout service, data is stored using: Data is used according to the processes described at [docker.com/legal](https://www.docker.com/legal/) to provide the key -capabilities of Docker Scout. +capabilities of Docker Scout. \ No newline at end of file diff --git a/content/scout/image-details-view.md b/content/scout/image-details-view.md index 60cab1fe21..9643abb2c8 100644 --- a/content/scout/image-details-view.md +++ b/content/scout/image-details-view.md @@ -1,10 +1,12 @@ --- title: Image details view -keywords: scout, supply chain, vulnerabilities, packages, cves, image, tag, scan, analysis, analyze -description: The Docker Scout image detail view analyzes images to show their heirachy, layers, packages, and vulnerabilities +keywords: scout, supply chain, vulnerabilities, packages, cves, image, tag, scan, + analysis, analyze +description: The Docker Scout image detail view analyzes images to show their heirachy, + layers, packages, and vulnerabilities --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} The image details view shows a breakdown of the Docker Scout analysis. You can access the image view from within Docker Desktop and from the image tag @@ -16,10 +18,10 @@ perspectives. The view displays vulnerabilities and packages that an image contains. You can choose whether you want to see data for the image as a whole, or for a specific base image or layer. -![The image details view in Docker Desktop](./images/dd-image-view.png){:width="700px"} +![The image details view in Docker Desktop](./images/dd-image-view.png) Docker Desktop first analyzes images locally, where it generates a software bill of materials (SBOM). -Docker Desktop, Docker Hub, and the Docker Scout Dashboard and CLI all use the [package URL (PURL) links](https://github.com/package-url/purl-spec){: target="_blank" rel="noopener" } +Docker Desktop, Docker Hub, and the Docker Scout Dashboard and CLI all use the [package URL (PURL) links](https://github.com/package-url/purl-spec) in this SBOM to query for matching Common Vulnerabilities and Exposures (CVEs) in [Docker Scout's advisory database](./advisory-db-sources.md). ## Image hierarchy @@ -149,8 +151,8 @@ of `debian` to use. By providing more than one alternative to choose from, you can see for yourself how the options compare with each other, and decide which one to use. -![Base image recommendations](./images/change-base-image.png){:width="700px"} +![Base image recommendations](./images/change-base-image.png) Select a tag recommendation to see further details of the recommendation. It shows the benefits and potential disadvantages of the tag, why it's a -recommended, and how to update your Dockerfile to use this version. +recommended, and how to update your Dockerfile to use this version. \ No newline at end of file diff --git a/content/scout/integrations/_index.md b/content/scout/integrations/_index.md index 7c98fe12b2..719ca9fca6 100644 --- a/content/scout/integrations/_index.md +++ b/content/scout/integrations/_index.md @@ -4,7 +4,7 @@ keywords: supply chain, security, integrations, registries, ci, environments title: Integrating Docker Scout with other systems --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} By default, Docker Scout integrates with your Docker organization and your Docker Scout-enabled repositories on Docker Hub. You can integrate Docker Scout @@ -52,4 +52,4 @@ Integrating with environments lets you compare production workloads to other versions, in your image repositories or in your other environments. For more information about environmet integrations, see -[Environments](./environment/index.md). +[Environments](./environment/index.md). \ No newline at end of file diff --git a/content/scout/integrations/ci/_index.md b/content/scout/integrations/ci/_index.md index 79193ec150..f20dbac3e7 100644 --- a/content/scout/integrations/ci/_index.md +++ b/content/scout/integrations/ci/_index.md @@ -1,12 +1,13 @@ --- description: How to setup Docker Scout in continuous integration pipelines -keywords: scanning, vulnerabilities, Hub, supply chain, security, ci, continuous integration, github actions, gitlab +keywords: scanning, vulnerabilities, Hub, supply chain, security, ci, continuous integration, + github actions, gitlab title: Using Docker Scout in continuous integration -redirect_from: - - /scout/ci/ +aliases: +- /scout/ci/ --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} You can analyze Docker images in continuous integration pipelines as you build them using a GitHub action or the Docker Scout CLI plugin. @@ -17,4 +18,4 @@ Available integrations: - [GitLab](gitlab.md) - [Microsoft Azure DevOps Pipelines](azure.md) - [Circle CI](circle-ci.md) -- [Jenkins](jenkins.md) +- [Jenkins](jenkins.md) \ No newline at end of file diff --git a/content/scout/integrations/ci/azure.md b/content/scout/integrations/ci/azure.md index 2d29a423dd..06fcff2054 100644 --- a/content/scout/integrations/ci/azure.md +++ b/content/scout/integrations/ci/azure.md @@ -4,7 +4,7 @@ keywords: supply chain, security, ci, continuous integration, azure, devops title: Integrate Docker Scout with Microsoft Azure DevOps Pipelines --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} The following examples runs in an Azure DevOps-connected repository containing a Docker image's definition and contents. Triggered by a commit to the main @@ -64,5 +64,4 @@ stages: This creates the flow mentioned previously. It builds and tags the image using the checked-out Dockerfile, downloads the Docker Scout CLI, and then runs the `cves` command against the new tag to generate a CVE report. It only shows -critical or high-severity vulnerabilities. - +critical or high-severity vulnerabilities. \ No newline at end of file diff --git a/content/scout/integrations/ci/circle-ci.md b/content/scout/integrations/ci/circle-ci.md index e740517a88..d3e15e4e3b 100644 --- a/content/scout/integrations/ci/circle-ci.md +++ b/content/scout/integrations/ci/circle-ci.md @@ -4,7 +4,7 @@ keywords: supply chain, security, ci, continuous integration, circle ci title: Integrate Docker Scout with Circle CI --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} The following examples runs when triggered in CircleCI. When triggered, it checks out the "docker/scout-demo-service:latest" image and tag and then uses @@ -73,5 +73,4 @@ workflows: build-docker-image: jobs: - build -``` - +``` \ No newline at end of file diff --git a/content/scout/integrations/ci/gha.md b/content/scout/integrations/ci/gha.md index faef4288a2..f0fc6f2827 100644 --- a/content/scout/integrations/ci/gha.md +++ b/content/scout/integrations/ci/gha.md @@ -4,7 +4,7 @@ keywords: supply chain, security, ci, continuous integration, github actions title: Integrate Docker Scout with GitHub Actions --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} You can use [the Docker Scout GitHub action](https://github.com/docker/scout-action) to run Docker Scout CLI commands as part of a workflow. @@ -20,7 +20,7 @@ those actions and using GitHub Actions with Docker in general, see [the GitHub A Add the following to a GitHub Actions YAML file: -{% raw %} + ```yaml name: Docker @@ -45,7 +45,7 @@ jobs: contents: read packages: write ``` -{% endraw %} + This sets up the workflow to run on pull requests and pushes to the `main` branch, and sets up environment variables available to all workflow steps. It @@ -54,7 +54,7 @@ the permissions available to the job. Add the following to the YAML file: -{% raw %} + ```yaml steps: - name: Checkout repository @@ -88,7 +88,7 @@ steps: type=semver,pattern=v{{version}} type=sha,prefix=,suffix=,format=short ``` -{% endraw %} + This creates workflow steps to checkout the repository, set up Docker buildx, log into the Docker registry, and extract metadata from Git reference and GitHub @@ -96,7 +96,7 @@ events to use in later steps. Add the following to the YAML file: -{% raw %} + ```yaml # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action @@ -111,7 +111,7 @@ Add the following to the YAML file: cache-from: type=gha cache-to: type=gha,mode=max ``` -{% endraw %} + This uses the extracted metadata from the previous step to build and push the Docker image to Docker Hub. GitHub Actions skips this step on pull requests and @@ -119,7 +119,7 @@ only runs when a pull request is merged. Add the following to the YAML file: -{% raw %} + ```yaml - name: Docker Scout id: docker-scout @@ -133,7 +133,7 @@ Add the following to the YAML file: only-severities: critical,high token: ${{ secrets.DOCKER_PAT }} ``` -{% endraw %} + This final step uses the Docker Scout CLI to run [the `compare` command](../../../engine/reference/commandline/scout_compare.md), comparing the new image to the published one. It only shows critical or high-severity @@ -143,4 +143,4 @@ analysis. The GitHub Action outputs the comparison results as a table and a summary in the action output. -![A screenshot showing the results of Docker Scout output in a GitHub Action](../../images/gha-output.png) +![A screenshot showing the results of Docker Scout output in a GitHub Action](../../images/gha-output.png) \ No newline at end of file diff --git a/content/scout/integrations/ci/gitlab.md b/content/scout/integrations/ci/gitlab.md index d224f71fec..43f6516316 100644 --- a/content/scout/integrations/ci/gitlab.md +++ b/content/scout/integrations/ci/gitlab.md @@ -4,7 +4,7 @@ keywords: supply chain, security, ci, continuous integration, gitlab title: Integrate Docker Scout with GitLab CI --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} The following examples runs in GitLab CI in a repository containing a Docker image's definition and contents. Triggered by a commit, the pipeline builds the @@ -45,7 +45,7 @@ settings. Add the following to the YAML file: -{% raw %} + ```yaml script: - | @@ -68,7 +68,7 @@ script: - docker push "$CI_REGISTRY_IMAGE${tag}" ``` -{% endraw %} + This creates the flow mentioned previously. If the commit was to the default branch, Docker Scout generates a CVE report. If the commit was to a different @@ -90,4 +90,4 @@ Dockerfile and if the commit was to the CI branch. _The following is a video walkthrough of the process of setting up the workflow with GitLab._ -
+
\ No newline at end of file diff --git a/content/scout/integrations/ci/jenkins.md b/content/scout/integrations/ci/jenkins.md index 5f7865caf9..48d2107ffd 100644 --- a/content/scout/integrations/ci/jenkins.md +++ b/content/scout/integrations/ci/jenkins.md @@ -4,7 +4,7 @@ keywords: supply chain, security, ci, continuous integration, jenkins title: Integrate Docker Scout with Jenkins --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} You can add the following stage and steps definition to a `Jenkinsfile` to run Docker Scout as part of a Jenkins pipeline. The pipeline needs two secrets @@ -29,4 +29,4 @@ stage('Analyze image') { This installs Docker Scout, logs into Docker Hub, and then runs Docker Scout to generate a CVE report for an image and tag. It only shows critical or -high-severity vulnerabilities. +high-severity vulnerabilities. \ No newline at end of file diff --git a/content/scout/integrations/environment/_index.md b/content/scout/integrations/environment/_index.md index 452e9d1702..4547cb397b 100644 --- a/content/scout/integrations/environment/_index.md +++ b/content/scout/integrations/environment/_index.md @@ -1,12 +1,14 @@ --- -description: | - Docker Scout can integrate with runtime environments to give you realtime +description: 'Docker Scout can integrate with runtime environments to give you realtime + insights about your software supply chain. + + ' keywords: supply chain, security, streams, environments, workloads, deployments title: Integrating Docker Scout with environments --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} You can integrate Docker Scout with your runtime environments, and get insights for your running workloads. This gives you a realtime view of your security @@ -76,4 +78,4 @@ When you've selected an environment on the **Images** tab, tags in the list represent the tag that was used to deploy the image. Tags are mutable, meaning that you can change the image digest that a tag refers to. If Docker Scout detects that a tag refers to an outdated digest, a warning icon displays next -to the image name. +to the image name. \ No newline at end of file diff --git a/content/scout/integrations/registry/artifactory.md b/content/scout/integrations/registry/artifactory.md index 213c54ab94..c52264d5f6 100644 --- a/content/scout/integrations/registry/artifactory.md +++ b/content/scout/integrations/registry/artifactory.md @@ -1,13 +1,16 @@ --- -description: > - Integrate JFrog Artifactory and JFrog Container Registry with Docker Scout -keywords: > - docker scout, jfrog, artifactory, jcr, integration, image analysis, security, +description: 'Integrate JFrog Artifactory and JFrog Container Registry with Docker + Scout + + ' +keywords: 'docker scout, jfrog, artifactory, jcr, integration, image analysis, security, cves + + ' title: Artifactory integration --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Integrating Docker Scout with JFrog Artifactory lets you run image analysis automatically on images in Artifactory registries. @@ -24,21 +27,19 @@ docker login {URL} > > For cloud-hosted Artifactory you can find the credentials for your Artifactory repository by > selecting it in the Artifactory UI and then the **Set Me Up** button. -{: .tip } +{ .tip } ## Remote image analysis To automatically analyze images running in remote environments you need to deploy the Docker Scout Artifactory agent. The agent is a standalone service that analyzes images and uploads the result to Docker Scout. You can view the results using the -[Docker Scout Dashboard](https://scout.docker.com/){: target="\_blank" rel="noopener" -}. +[Docker Scout Dashboard](https://scout.docker.com/). ### How the agent works The Docker Scout Artifactory agent is available as an -[image on Docker Hub](https://hub.docker.com/r/docker/artifactory-agent){: -target="\_blank" rel="noopener" }. The agent works by continuously polling +[image on Docker Hub](https://hub.docker.com/r/docker/artifactory-agent). The agent works by continuously polling Artifactory for new images. When it finds a new image, it performs the following steps: @@ -152,7 +153,7 @@ the container. Make sure the mount path you use is the directory containing the > > Use the `v1` tag of the Artifactory agent image. Don't use the `latest` tag as > doing so may incur breaking changes. -{: .important } +{ .important } ```console $ docker run \ @@ -197,4 +198,4 @@ You can view the image analysis results in the Docker Scout Dashboard. When you have selected a tag, you're taken to the vulnerability report for that tag. Here, you can select if you want to view all vulnerabilities in the image, or vulnerabilities introduced in a specific layer. You can also filter -vulnerabilities by severity, and whether or not there's a fix version available. +vulnerabilities by severity, and whether or not there's a fix version available. \ No newline at end of file diff --git a/content/scout/quickstart.md b/content/scout/quickstart.md index a202d0c7ca..b99e316b5a 100644 --- a/content/scout/quickstart.md +++ b/content/scout/quickstart.md @@ -1,13 +1,15 @@ --- title: Docker Scout quickstart keywords: scout, supply chain, vulnerabilities, packages, cves, scan, analysis, analyze -description: > - Learn how to get started with Docker Scout to analyze images and fix vulnerabilities -redirect_from: - - /atomist/get-started/ +description: 'Learn how to get started with Docker Scout to analyze images and fix + vulnerabilities + + ' +aliases: +- /atomist/get-started/ --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} Docker Scout analyzes image contents and generates a detailed report of packages and vulnerabilities that it detects. It can provide you with @@ -50,7 +52,7 @@ a vulnerable Node.js application that you can use to follow along. > **Important** > > Make sure you log in to the Docker CLI or Docker Desktop before pushing. - {: .important} + { .important } ## Enable Docker Scout @@ -86,7 +88,7 @@ to see vulnerabilities detected by Docker Scout. $ docker scout cves /scout-demo:v1 ``` -![Screenshot showing highlighting a CVE in Docker Desktop](./images/scout-onboarding-dd-v1-cvve-focus.png){:width="650px"} +![Screenshot showing highlighting a CVE in Docker Desktop](./images/scout-onboarding-dd-v1-cvve-focus.png) Docker Scout creates and maintains its vulnerability database by ingesting and collating vulnerability data from multiple sources continuously. These sources @@ -96,7 +98,7 @@ You can find more details in the [Advisory Database sources](./advisory-db-sourc > **Tip** > > Find out how to filter results using the CLI command [`scout cves`](/engine/reference/commandline/scout_cves). -{: .tip } +{ .tip } ## Fix application vulnerabilities @@ -180,8 +182,8 @@ security, compliance, and operations to know what vulnerabilities and issues to > > If you are a member of multiple organizations, make sure you select the > correct organization from the drop-down in the top right. -> ![Screenshot showing organization picker in the Docker Scout dashboard](./images/scout-onboarding-org-picker.png){:width="250px"} -{: .tip } +> ![Screenshot showing organization picker in the Docker Scout dashboard](./images/scout-onboarding-org-picker.png) +{ .tip } ## Comparing image tags @@ -215,4 +217,4 @@ different tags of the same image. - Explore the [Docker Scout Dashboard](/scout/dashboard) to see how you can collaborate with your team on vulnerabilities. - [Learn how to integrate Docker Scout with other systems](./integrations/index.md). -- [Find out where Docker Scout gets its vulnerability data](/scout/advisory-db-sources). +- [Find out where Docker Scout gets its vulnerability data](/scout/advisory-db-sources). \ No newline at end of file diff --git a/content/scout/web-app.md b/content/scout/web-app.md index fca61c42da..2df922a399 100644 --- a/content/scout/web-app.md +++ b/content/scout/web-app.md @@ -1,13 +1,14 @@ --- description: The Docker Scout Dashboard helps review and share the analysis of images. -keywords: scanning, analysis, vulnerabilities, Hub, supply chain, security, report, reports, dashboard +keywords: scanning, analysis, vulnerabilities, Hub, supply chain, security, report, + reports, dashboard title: Dashboard -redirect_from: - - /scout/reports/ - - /scout/web-app/ +aliases: +- /scout/reports/ +- /scout/web-app/ --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} The Docker Scout Dashboard helps you share the analysis of images in an organization with your team. Developers can now see an overview of their security status across all their images from both Docker Hub and Artifactory, and get remediation advice at their fingertips. It helps team members in roles such as security, compliance, and operations to know what vulnerabilities and issues they need to focus on. @@ -98,4 +99,4 @@ Each entry in the list shows the following details: - The package name and version affected by this CVE. - The Common Vulnerability Scoring System (CVSS) score for the vulnerability. Docker Scout shows the highest CVSS score from multiple sources. - The number of images in the organization that use the package affected by this CVE. -- If Docker Scout knows of a fix for the vulnerability, and if so, the package version of the fix. +- If Docker Scout knows of a fix for the vulnerability, and if so, the package version of the fix. \ No newline at end of file diff --git a/content/security.md b/content/security.md index 9ea3a62e87..9266f3113e 100644 --- a/content/security.md +++ b/content/security.md @@ -8,9 +8,9 @@ toc_max: 2 ## Text4Shell CVE-2022-42889 -[CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889){:target="_blank" rel="noopener" class="_"} has been discovered in the popular Apache Commons Text library. Versions of this library up to but not including 1.10.0 are affected by this vulnerability. +[CVE-2022-42889](https://nvd.nist.gov/vuln/detail/CVE-2022-42889) has been discovered in the popular Apache Commons Text library. Versions of this library up to but not including 1.10.0 are affected by this vulnerability. -We strongly encourage you to update to the latest version of [Apache Commons Text](https://commons.apache.org/proper/commons-text/download_text.cgi){:target="_blank" rel="noopener" class="_"}. +We strongly encourage you to update to the latest version of [Apache Commons Text](https://commons.apache.org/proper/commons-text/download_text.cgi). ### Scan images on Docker Hub @@ -27,7 +27,7 @@ the Text4Shell CVE in the vulnerability report. For detailed instructions, see [ > We will be updating this section with the latest information. We recommend > that you revisit this section to view the list of affected images and update > images to the patched version as soon as possible to remediate the issue. -{: .important} +{ .important } A number of [Docker Official Images](../docker-hub/official_images.md) contain the vulnerable versions of Apache Commons Text. The following table lists Docker Official Images that @@ -51,7 +51,7 @@ vulnerable for other reasons. We recommend that you also review the guidelines p Docker Desktop versions 4.3.0 and 4.3.1 have a bug that may log sensitive information (access token or password) on the user's machine during login. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the user’s local files. This vulnerability has been fixed in version 4.3.2 or higher. Users should update to version 4.3.2 and may want to update their password. Users should not send local log files to anyone. Users can manually delete their log files, they can be located in the following folder: `~/Library/Containers/com.docker.docker/Data/log/host/` on Mac, and in `C:\Users\\AppData\Roaming\Docker\log\host\` on Windows. When a user installs 4.3.2 or higher, we will delete their local log files, so there is no risk of leakage after an update. Additionally, these logs may be included when users upload diagnostics, meaning access tokens and passwords might have been shared with Docker. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1, and the user has logged in while on 4.3.0, 4.3.1 and have gone through the process of submitting diagnostics to Docker. Only Docker support Engineers working on an active support case could have access to the diagnostic files, minimizing leakage risk from these files. We have deleted all potentially sensitive diagnostic files from our data storage and will continue to delete diagnostics reported from the affected versions on an ongoing basis. -For detailed information, see [CVE-2021-45449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45449){: target="_blank" rel="noopener" class="_"}. +For detailed information, see [CVE-2021-45449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45449). ### References @@ -61,8 +61,7 @@ For detailed information, see [CVE-2021-45449](https://cve.mitre.org/cgi-bin/cve ## Log4j 2 CVE-2021-44228 -The [Log4j 2 CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228){: -target="_blank" rel="noopener" class="_"} vulnerability in Log4j 2, a very common Java logging library, allows remote code execution, often from a context that is easily available to an attacker. For example, it was found in Minecraft servers which allowed the commands to be typed into chat logs as these were then sent to the logger. This makes it a very serious vulnerability, as the logging library is used so widely and it may be simple to exploit. Many open source maintainers are working hard with fixes and updates to the software ecosystem. +The [Log4j 2 CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) vulnerability in Log4j 2, a very common Java logging library, allows remote code execution, often from a context that is easily available to an attacker. For example, it was found in Minecraft servers which allowed the commands to be typed into chat logs as these were then sent to the logger. This makes it a very serious vulnerability, as the logging library is used so widely and it may be simple to exploit. Many open source maintainers are working hard with fixes and updates to the software ecosystem. The vulnerable versions of Log4j 2 are versions 2.0 to version 2.14.1 inclusive. The first fixed version is 2.15.0. We strongly encourage you to update to the [latest version](https://logging.apache.org/log4j/2.x/download.html) if you can. If you are using a version before 2.0, you are also not vulnerable. @@ -76,13 +75,12 @@ vulnerable versions. > CVE-2021-45046 > > As an update to -> [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228){: -target="_blank" rel="noopener" class="_"}, the fix made in version 2.15.0 was +> [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228), the fix made in version 2.15.0 was > incomplete. Additional issues have been identified and are tracked with -> [CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046){: target="_blank" rel="noopener" class="_"} and -> [CVE-2021-45105](https://nvd.nist.gov/vuln/detail/CVE-2021-45105){: target="_blank" rel="noopener" class="_"}. +> [CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046) and +> [CVE-2021-45105](https://nvd.nist.gov/vuln/detail/CVE-2021-45105). > For a more complete fix to this vulnerability, we recommended that you update to 2.17.0 where possible. -{: .important} +{ .important } ### Scan images on Docker Hub @@ -99,7 +97,7 @@ Log4j 2 CVE in the vulnerability report. For detailed instructions, see [Scan im > We will be updating this section with the latest information. We recommend > that you revisit this section to view the list of affected images and update > images to the patched version as soon as possible to remediate the issue. -{: .important} +{ .important } A number of [Docker Official Images](../docker-hub/official_images.md) contain the vulnerable versions of Log4j 2 CVE-2021-44228. The following table lists Docker Official Images that @@ -122,9 +120,8 @@ vulnerable for other reasons. We recommend that you also review the guidelines p > **Note** > -> Although [xwiki](https://hub.docker.com/_/xwiki){: -target="_blank" rel="noopener" class="_"} images may be detected as vulnerable +> Although [xwiki](https://hub.docker.com/_/xwiki) images may be detected as vulnerable by some scanners, the authors believe the images are not vulnerable by Log4j 2 CVE as the API jars do not contain the vulnerability. -> The [Nuxeo](https://hub.docker.com/_/nuxeo){: target="_blank" rel="noopener" class="_"} -> image is deprecated and will not be updated. +> The [Nuxeo](https://hub.docker.com/_/nuxeo) +> image is deprecated and will not be updated. \ No newline at end of file diff --git a/content/single-sign-on/_index.md b/content/single-sign-on/_index.md index 68d88321e5..4974cc8344 100644 --- a/content/single-sign-on/_index.md +++ b/content/single-sign-on/_index.md @@ -4,4 +4,4 @@ keywords: Single Sign-on, SSO, sign-on title: Overview --- -{% include admin-sso.md product="hub" %} \ No newline at end of file +{{% admin-sso product="hub" %}} \ No newline at end of file diff --git a/content/single-sign-on/configure/_index.md b/content/single-sign-on/configure/_index.md index 4fe37dc5fa..b78f4d76ed 100644 --- a/content/single-sign-on/configure/_index.md +++ b/content/single-sign-on/configure/_index.md @@ -2,7 +2,7 @@ description: SSO configuration keywords: configure, sso, docker hub, hub title: Configure -redirect_from: +aliases: - /docker-hub/domains/ - /docker-hub/sso-connection/ - /docker-hub/enforcing-sso/ @@ -12,6 +12,6 @@ Follow the steps on this page to configure SSO for your organization or company. ## Step one: Add and verify your domain -{% include admin-domains.md product="hub" %} +{{% admin-domains product="hub" %}} -{% include admin-sso-config.md product="hub" %} \ No newline at end of file +{{% admin-sso-config product="hub" %}} \ No newline at end of file diff --git a/content/single-sign-on/domain-faqs.md b/content/single-sign-on/domain-faqs.md index 9f57c766c7..f734c5c7b7 100644 --- a/content/single-sign-on/domain-faqs.md +++ b/content/single-sign-on/domain-faqs.md @@ -26,5 +26,4 @@ Runtime for Docker Desktop if they configure Docker Desktop to require authentic ### Do you support IdP-initiated authentication (e.g., Okta tile support)? -We don't support IdP-initiated authentication. Users must initiate login through Docker Desktop or Hub. - +We don't support IdP-initiated authentication. Users must initiate login through Docker Desktop or Hub. \ No newline at end of file diff --git a/content/single-sign-on/faqs.md b/content/single-sign-on/faqs.md index ee2342a6ca..bc4418d421 100644 --- a/content/single-sign-on/faqs.md +++ b/content/single-sign-on/faqs.md @@ -30,5 +30,4 @@ Yes, all users in your organization must upgrade to Docker Desktop version 4.4.2 ### Can I retain my Docker ID when using SSO? -For a personal Docker ID, a user is the account owner, it’s associated with access to the user's repositories, images, assets. An end user can choose to have a company domain email on the Docker account, when enforcing SSO, the account is connected to the organization account. When enforcing SSO for an organization(s) or company, any user logging in without an existing account using verified company domain email will automatically have an account provisioned, and a new Docker ID created. - +For a personal Docker ID, a user is the account owner, it’s associated with access to the user's repositories, images, assets. An end user can choose to have a company domain email on the Docker account, when enforcing SSO, the account is connected to the organization account. When enforcing SSO for an organization(s) or company, any user logging in without an existing account using verified company domain email will automatically have an account provisioned, and a new Docker ID created. \ No newline at end of file diff --git a/content/single-sign-on/idp-faqs.md b/content/single-sign-on/idp-faqs.md index 48ae0eef71..fc06763484 100644 --- a/content/single-sign-on/idp-faqs.md +++ b/content/single-sign-on/idp-faqs.md @@ -50,4 +50,4 @@ Yes, bot accounts needs a seat, similar to a regular end user, having a non-alia ### Is it possible to connect Docker Hub directly with a Microsoft Azure Active Directory Group? -Yes, Azure AD is supported with SSO for Docker Business, both through a direct integration and through SAML. +Yes, Azure AD is supported with SSO for Docker Business, both through a direct integration and through SAML. \ No newline at end of file diff --git a/content/single-sign-on/manage/_index.md b/content/single-sign-on/manage/_index.md index 52e148fa8f..f169dc11ee 100644 --- a/content/single-sign-on/manage/_index.md +++ b/content/single-sign-on/manage/_index.md @@ -10,7 +10,6 @@ title: Manage SSO > > You must have a [company](/docker-hub/creating-companies/) to manage more than one organization. -{% include admin-sso-management-orgs.md product="hub" %} - -{% include admin-sso-management.md product="hub"%} +{{% admin-sso-management-orgs product="hub" %}} +{% include admin-sso-management.md product="hub"%} \ No newline at end of file diff --git a/content/single-sign-on/saml-faqs.md b/content/single-sign-on/saml-faqs.md index 591d032530..75df68bca7 100644 --- a/content/single-sign-on/saml-faqs.md +++ b/content/single-sign-on/saml-faqs.md @@ -18,4 +18,4 @@ At runtime for Docker Desktop if it’s configured to require authentication to ### Do you have any information on how to use the Docker Desktop application in accordance with the SSO users we provide? How can we verify that we're handling the licensing correctly? -Verify that your users have downloaded the latest version of Docker Desktop. An enhancement in user management observability and capabilities will become available in the future. +Verify that your users have downloaded the latest version of Docker Desktop. An enhancement in user management observability and capabilities will become available in the future. \ No newline at end of file diff --git a/content/single-sign-on/users-faqs.md b/content/single-sign-on/users-faqs.md index 6f611e01c4..01d4880a8b 100644 --- a/content/single-sign-on/users-faqs.md +++ b/content/single-sign-on/users-faqs.md @@ -85,5 +85,4 @@ They can go to the invitee list in the org view and remove them. ### How's the flow for service account authentication different from a UI user account? -It isn't; we don't differentiate the two in product. - +It isn't; we don't differentiate the two in product. \ No newline at end of file diff --git a/content/storage/_index.md b/content/storage/_index.md index 4f5526e3eb..25de327a54 100644 --- a/content/storage/_index.md +++ b/content/storage/_index.md @@ -2,7 +2,7 @@ description: Overview of persisting data in containers title: Manage data in Docker keywords: storage, persistence, data persistence, volumes, mounts, bind mounts -redirect_from: +aliases: - engine/admin/volumes/ --- @@ -96,7 +96,7 @@ mounts is to think about where the data lives on the Docker host. > **container**, including creating, modifying, or deleting important system > files or directories. This is a powerful ability which can have security > implications, including impacting non-Docker processes on the host system. - {: .important } + { .important } - **[tmpfs mounts](tmpfs.md)**: A `tmpfs` mount is not persisted on disk, either on the Docker host or within a container. It can be used by a container during @@ -200,4 +200,4 @@ If you use either bind mounts or volumes, keep the following in mind: - Learn more about [tmpfs mounts](tmpfs.md). - Learn more about [storage drivers](/storage/storagedriver/), which are not related to bind mounts or volumes, but allow you to store data in a - container's writable layer. + container's writable layer. \ No newline at end of file diff --git a/content/storage/bind-mounts.md b/content/storage/bind-mounts.md index 6ebb391c4a..1eb2ebe7fe 100644 --- a/content/storage/bind-mounts.md +++ b/content/storage/bind-mounts.md @@ -2,7 +2,7 @@ description: Using bind mounts title: Bind mounts keywords: storage, persistence, data persistence, mounts, bind mounts -redirect_from: +aliases: - /engine/admin/volumes/bind-mounts/ --- @@ -282,7 +282,7 @@ control whether `/mnt/a` and/or `/tmp/a` would exist. > Warning > > Mount propagation doesn't work with Docker Desktop. -{: .warning } +{ .warning } | Propagation setting | Description | |:--------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -297,7 +297,7 @@ Before you can set bind propagation on a mount point, the host filesystem needs to already support bind propagation. For more information about bind propagation, see the -[Linux kernel documentation for shared subtree](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt){: target="_blank" rel="noopener" class="_"}. +[Linux kernel documentation for shared subtree](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt). The following example mounts the `target/` directory into the container twice, and the second mount sets both the `ro` option and the `rslave` bind propagation @@ -352,7 +352,7 @@ inoperable and you may need to relabel the host machine files by hand. > **Important**: When using bind mounts with services, selinux labels > (`:Z` and `:z`), as well as `:ro` are ignored. See > [moby/moby #32579](https://github.com/moby/moby/issues/32579) for details. -{:.important} +{ .important } This example sets the `z` option to specify that multiple containers can share the bind mount's contents: @@ -393,4 +393,4 @@ and - Learn about [volumes](volumes.md). - Learn about [tmpfs mounts](tmpfs.md). -- Learn about [storage drivers](/storage/storagedriver/). +- Learn about [storage drivers](/storage/storagedriver/). \ No newline at end of file diff --git a/content/storage/containerd.md b/content/storage/containerd.md index e9c6bbf85a..60a154aff6 100644 --- a/content/storage/containerd.md +++ b/content/storage/containerd.md @@ -48,11 +48,11 @@ The following steps explain how to enable the containerd snapshotters feature. After restarting the daemon, running `docker info` shows that you're using containerd snapshotter storage drivers. -{% raw %} + ```console $ docker info -f '{{ .DriverStatus }}' [[driver-type io.containerd.snapshotter.v1]] ``` -{% endraw %} -Docker Engine uses the `overlayfs` containerd snapshotter by default. + +Docker Engine uses the `overlayfs` containerd snapshotter by default. \ No newline at end of file diff --git a/content/storage/storagedriver/_index.md b/content/storage/storagedriver/_index.md index cb0a450e95..547b5ffc5c 100644 --- a/content/storage/storagedriver/_index.md +++ b/content/storage/storagedriver/_index.md @@ -2,7 +2,7 @@ description: Learn the technologies that support storage drivers. keywords: container, storage, driver, btrfs, devicemapper, overlayfs, vfs, zfs title: About storage drivers -redirect_from: +aliases: - /en/latest/terms/layer/ - /engine/installation/userguide/storagedriver/ - /engine/userguide/storagedriver/imagesandcontainers/ @@ -339,7 +339,7 @@ layers are the same. Use the `docker image inspect` command to view the cryptographic IDs of the layers in each image: - {% raw %} + ```console $ docker image inspect --format "{{json .RootFS.Layers}}" acme/my-base-image:1.0 [ @@ -347,9 +347,9 @@ layers are the same. "sha256:07b4a9068b6af337e8b8f1f1dae3dd14185b2c0003a9a1f0a6fd2587495b204a" ] ``` - {% endraw %} + - {% raw %} + ```console $ docker image inspect --format "{{json .RootFS.Layers}}" acme/my-final-image:1.0 [ @@ -359,7 +359,7 @@ layers are the same. "sha256:e84fb818852626e89a09f5143dbc31fe7f0e0a6a24cd8d2eb68062b904337af4" ] ``` - {% endraw %} + Notice that the first two layers are identical in both images. The second image adds two additional layers. Shared image layers are only stored once @@ -376,7 +376,7 @@ layers are the same. > additional tools such as `awk` or `sed`. To learn more about formatting > the output of docker commands using the `--format` flag, refer to the > [format command and log output section](../../config/formatting.md). - > We also pretty-printed the JSON output using the [`jq` utility](https://stedolan.github.io/jq/){: target="_blank" rel="noopener" class="_" } + > We also pretty-printed the JSON output using the [`jq` utility](https://stedolan.github.io/jq/) > for readability. ### Copying makes containers efficient @@ -450,7 +450,7 @@ examines how much room they take up. 2. Run the `docker ps` command with the `--size` option to verify the 5 containers are running, and to see each container's size. - {% raw %} + ```console $ docker ps --size --format "table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Size}}" @@ -461,7 +461,7 @@ examines how much room they take up. a5ff32e2b551 acme/my-final-image:1.0 my_container_2 0B (virtual 7.75MB) 40ebdd763416 acme/my-final-image:1.0 my_container_1 0B (virtual 7.75MB) ``` - {% endraw %} + The output above shows that all containers share the image's read-only layers (7.75MB), but no data was written to the container's filesystem, so no additional @@ -507,7 +507,7 @@ examines how much room they take up. shared. The read-only layers of the containers are not affected, and are still shared by all containers. - {% raw %} + ```console $ docker ps --size --format "table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Size}}" @@ -518,7 +518,7 @@ examines how much room they take up. a5ff32e2b551 acme/my-final-image:1.0 my_container_2 5B (virtual 7.75MB) 40ebdd763416 acme/my-final-image:1.0 my_container_1 5B (virtual 7.75MB) ``` - {% endraw %} + The examples above illustrate how copy-on-write filesystems help making containers efficient. Not only does copy-on-write save space, but it also reduces container @@ -535,4 +535,4 @@ driver, a full copy of the image's data is created for each container. ## Related information * [Volumes](../volumes.md) -* [Select a storage driver](select-storage-driver.md) +* [Select a storage driver](select-storage-driver.md) \ No newline at end of file diff --git a/content/storage/storagedriver/aufs-driver.md b/content/storage/storagedriver/aufs-driver.md index 7c80a020b1..2ae447dbb8 100644 --- a/content/storage/storagedriver/aufs-driver.md +++ b/content/storage/storagedriver/aufs-driver.md @@ -3,24 +3,23 @@ description: Learn how to optimize your use of AUFS driver. keywords: 'container, storage, driver, AUFS ' title: Use the AUFS storage driver sitemap: false -redirect_from: +aliases: - /engine/userguide/storagedriver/aufs-driver/ --- - > **Deprecated** > > The AuFS storage driver has been deprecated, and is removed in Docker Engine > v24.0. If you are using AufS, you must migrate to a supported storage driver > before upgrading to Docker Engine v24.0. Read the [Docker storage drivers](select-storage-driver.md) > page for supported storage drivers. -{:.warning} +{ .warning } AUFS is a *union filesystem*. The `aufs` storage driver was previously the default storage driver used for managing images and layers on Docker for Ubuntu, and for Debian versions prior to Stretch. If your Linux kernel is version 4.0 or higher, and you use Docker Engine - Community, consider using the newer -[overlay2](overlayfs-driver.md){: target="_blank" rel="noopener" class="_" }, which has +[overlay2](overlayfs-driver.md), which has potential performance advantages over the `aufs` storage driver. ## Prerequisites @@ -231,4 +230,4 @@ The following generic performance best practices also apply to AUFS. - [Volumes](../volumes.md) - [Understand images, containers, and storage drivers](index.md) -- [Select a storage driver](select-storage-driver.md) +- [Select a storage driver](select-storage-driver.md) \ No newline at end of file diff --git a/content/storage/storagedriver/btrfs-driver.md b/content/storage/storagedriver/btrfs-driver.md index ed687c3344..2f117264b9 100644 --- a/content/storage/storagedriver/btrfs-driver.md +++ b/content/storage/storagedriver/btrfs-driver.md @@ -2,7 +2,7 @@ description: Learn how to optimize your use of Btrfs driver. keywords: 'container, storage, driver, Btrfs ' title: Use the BTRFS storage driver -redirect_from: +aliases: - /engine/userguide/storagedriver/btrfs-driver/ --- @@ -307,4 +307,4 @@ storage driver. - [Volumes](../volumes.md) - [Understand images, containers, and storage drivers](index.md) -- [Select a storage driver](select-storage-driver.md) +- [Select a storage driver](select-storage-driver.md) \ No newline at end of file diff --git a/content/storage/storagedriver/device-mapper-driver.md b/content/storage/storagedriver/device-mapper-driver.md index 6632086ece..16f685e05b 100644 --- a/content/storage/storagedriver/device-mapper-driver.md +++ b/content/storage/storagedriver/device-mapper-driver.md @@ -2,7 +2,7 @@ description: Learn how to optimize your use of device mapper driver. keywords: container, storage, driver, device mapper title: Use the Device Mapper storage driver -redirect_from: +aliases: - /engine/userguide/storagedriver/device-mapper-driver/ --- @@ -431,7 +431,7 @@ If you run into repeated problems with thin pool, you can set the storage option `/etc/docker/daemon.json`. For instance, setting it to `10` ensures that operations fail with a warning when the free space is at or near 10%. See the -[storage driver options in the Engine daemon reference](/engine/reference/commandline/dockerd/#daemon-storage-driver){: target="_blank" rel="noopener" class="_"}. +[storage driver options in the Engine daemon reference](/engine/reference/commandline/dockerd/#daemon-storage-driver). ### Increase capacity on a running device @@ -834,4 +834,4 @@ storage driver. - [Volumes](../volumes.md) - [Understand images, containers, and storage drivers](index.md) -- [Select a storage driver](select-storage-driver.md) +- [Select a storage driver](select-storage-driver.md) \ No newline at end of file diff --git a/content/storage/storagedriver/overlayfs-driver.md b/content/storage/storagedriver/overlayfs-driver.md index d76820b0ed..665a860264 100644 --- a/content/storage/storagedriver/overlayfs-driver.md +++ b/content/storage/storagedriver/overlayfs-driver.md @@ -2,7 +2,7 @@ description: Learn how to optimize your use of OverlayFS driver. keywords: container, storage, driver, OverlayFS, overlay2, overlay title: Use the OverlayFS storage driver -redirect_from: +aliases: - /engine/userguide/storagedriver/overlayfs-driver/ --- @@ -446,4 +446,4 @@ filesystems: - **rename(2)**: OverlayFS does not fully support the `rename(2)` system call. Your application needs to detect its failure and fall back to a "copy and - unlink" strategy. + unlink" strategy. \ No newline at end of file diff --git a/content/storage/storagedriver/select-storage-driver.md b/content/storage/storagedriver/select-storage-driver.md index 95547a6eda..d517184b6d 100644 --- a/content/storage/storagedriver/select-storage-driver.md +++ b/content/storage/storagedriver/select-storage-driver.md @@ -2,7 +2,7 @@ title: Docker storage drivers description: Learn how to select the proper storage driver for your container. keywords: container, storage, driver, btrfs, devicemapper, zfs, overlay, overlay2 -redirect_from: +aliases: - /engine/userguide/storagedriver/ - /engine/userguide/storagedriver/selectadriver/ - /storage/storagedriver/selectadriver/ @@ -32,8 +32,8 @@ The Docker Engine provides the following storage drivers on Linux: The Docker Engine has a prioritized list of which storage driver to use if no storage driver is explicitly configured, assuming that the storage driver meets the prerequisites, and automatically selects a compatible storage driver. You -can see the order in the [source code for Docker Engine {{ site.docker_ce_version }}](https://github.com/moby/moby/blob/{{ site.docker_ce_version }}/daemon/graphdriver/driver_linux.go#L52-L53). -{: id="storage-driver-order" } +can see the order in the [source code for Docker Engine {{% param "docker_ce_version" %}}](https://github.com/moby/moby/blob/{{% param "docker_ce_version" %}}/daemon/graphdriver/driver_linux.go#L52-L53). +{ #storage-driver-order } Some storage drivers require you to use a specific format for the backing filesystem. If you have external requirements to use a specific backing filesystem, this may @@ -188,7 +188,7 @@ to physical or logical disks on the Docker host. > driver. If you revert your changes, you can access the old images and containers > again, but any that you pulled or created using the new driver are then > inaccessible. -{:.important} +{ .important } ## Related information @@ -196,4 +196,4 @@ to physical or logical disks on the Docker host. * [`devicemapper` storage driver in practice](device-mapper-driver.md) * [`overlay2` storage driver in practice](overlayfs-driver.md) * [`btrfs` storage driver in practice](btrfs-driver.md) -* [`zfs` storage driver in practice](zfs-driver.md) +* [`zfs` storage driver in practice](zfs-driver.md) \ No newline at end of file diff --git a/content/storage/storagedriver/vfs-driver.md b/content/storage/storagedriver/vfs-driver.md index 9b3f5160fb..0be424acab 100644 --- a/content/storage/storagedriver/vfs-driver.md +++ b/content/storage/storagedriver/vfs-driver.md @@ -1,8 +1,8 @@ --- description: Learn how to optimize your use of VFS driver. -keywords: 'container, storage, driver, vfs' +keywords: container, storage, driver, vfs title: Use the VFS storage driver -redirect_from: +aliases: - /engine/userguide/storagedriver/vfs-driver/ --- @@ -130,5 +130,4 @@ same amount of room on disk. This is one of the disadvantages of using the ## Related information - [Understand images, containers, and storage drivers](index.md) -- [Select a storage driver](select-storage-driver.md) - +- [Select a storage driver](select-storage-driver.md) \ No newline at end of file diff --git a/content/storage/storagedriver/zfs-driver.md b/content/storage/storagedriver/zfs-driver.md index e8ec3497bd..d161fe054a 100644 --- a/content/storage/storagedriver/zfs-driver.md +++ b/content/storage/storagedriver/zfs-driver.md @@ -2,7 +2,7 @@ description: Learn how to optimize your use of ZFS driver. keywords: 'container, storage, driver, ZFS ' title: Use the ZFS storage driver -redirect_from: +aliases: - /engine/userguide/storagedriver/zfs-driver/ --- @@ -271,5 +271,4 @@ There are several factors that influence the performance of Docker using the the storage driver and do not incur any of the potential overheads introduced by thin provisioning and copy-on-write. Volumes have other benefits, such as allowing you to share data among containers and persisting even when no - running container is using them. - + running container is using them. \ No newline at end of file diff --git a/content/storage/tmpfs.md b/content/storage/tmpfs.md index b0fdac2260..e269d00583 100644 --- a/content/storage/tmpfs.md +++ b/content/storage/tmpfs.md @@ -2,7 +2,7 @@ description: Using tmpfs mounts title: tmpfs mounts keywords: storage, persistence, data persistence, tmpfs -redirect_from: +aliases: - /engine/admin/volumes/tmpfs/ --- @@ -132,4 +132,4 @@ docker run -d \ - Learn about [volumes](volumes.md) - Learn about [bind mounts](bind-mounts.md) -- Learn about [storage drivers](/storage/storagedriver/) +- Learn about [storage drivers](/storage/storagedriver/) \ No newline at end of file diff --git a/content/storage/troubleshooting_volume_errors.md b/content/storage/troubleshooting_volume_errors.md index e6b3f4c512..ccc7fb8973 100644 --- a/content/storage/troubleshooting_volume_errors.md +++ b/content/storage/troubleshooting_volume_errors.md @@ -2,7 +2,7 @@ description: Troubleshooting volume errors keywords: cadvisor, troubleshooting, volumes, bind-mounts title: Troubleshoot volume errors -redirect_from: +aliases: - /engine/admin/troubleshooting_volume_errors/ --- @@ -58,4 +58,4 @@ $ sudo lsof /var/lib/docker/containers/74bef250361c7817bee19349c93139621b272bc8f ``` To work around this problem, stop the container which bind-mounts -`/var/lib/docker` and try again to remove the other container. +`/var/lib/docker` and try again to remove the other container. \ No newline at end of file diff --git a/content/storage/volumes.md b/content/storage/volumes.md index 15154436f4..3e9c92f355 100644 --- a/content/storage/volumes.md +++ b/content/storage/volumes.md @@ -1,12 +1,14 @@ --- -description: Learn how to create, manage, and use volumes instead of bind mounts for persisting data generated and used by Docker. +description: Learn how to create, manage, and use volumes instead of bind mounts for + persisting data generated and used by Docker. title: Volumes -keywords: docker compose volumes, docker volumes, docker compose volume, docker volume mount, docker mount volume, docker volume create, docker volume location -redirect_from: - - /userguide/dockervolumes/ - - /engine/tutorials/dockervolumes/ - - /engine/userguide/dockervolumes/ - - /engine/admin/volumes/volumes/ +keywords: docker compose volumes, docker volumes, docker compose volume, docker volume + mount, docker mount volume, docker volume create, docker volume location +aliases: +- /userguide/dockervolumes/ +- /engine/tutorials/dockervolumes/ +- /engine/userguide/dockervolumes/ +- /engine/admin/volumes/volumes/ --- Volumes are the preferred mechanism for persisting data generated by and used @@ -92,7 +94,7 @@ If you need to specify volume driver options, you must use `--mount`. > --name myservice \ > > -> {: .warning} +> { .warning } The examples below show both the `--mount` and `-v` syntax where possible, with `--mount` first. @@ -520,7 +522,7 @@ and how to mount the block device as a container volume. > The following procedure is only an example. > The solution illustrated here isn't recommended as a general practice. > Don't attempt this approach unless you're confident about what you're doing. -{: .important } +{ .important } #### How mounting block devices works @@ -686,4 +688,4 @@ $ docker volume prune - Learn about [bind mounts](bind-mounts.md). - Learn about [tmpfs mounts](tmpfs.md). - Learn about [storage drivers](/storage/storagedriver/). -- Learn about [third-party volume driver plugins](/engine/extend/legacy_plugins/). +- Learn about [third-party volume driver plugins](/engine/extend/legacy_plugins/). \ No newline at end of file diff --git a/content/subscription/_index.md b/content/subscription/_index.md index 4dc35923e5..9ff182cc53 100644 --- a/content/subscription/_index.md +++ b/content/subscription/_index.md @@ -2,24 +2,24 @@ description: Docker subscription overview keywords: Docker, pricing, billing, Pro, Team, business, subscription, tier, plan title: Docker subscription overview -redirect_from: - - /docker-hub/billing/ - - /docker-hub/billing/faq/ grid: - - title: Understand Docker subscriptions and features - link: /subscription/details/ - icon: shop_two - - title: Upgrade your subscription - link: /subscription/upgrade/ - icon: upgrade - - title: Add more seats to your subscription - link: /subscription/add-seats/ - icon: contact - - title: Explore common FAQs - link: /subscription/faq/ - icon: help +- title: Understand Docker subscriptions and features + link: /subscription/details/ + icon: shop_two +- title: Upgrade your subscription + link: /subscription/upgrade/ + icon: upgrade +- title: Add more seats to your subscription + link: /subscription/add-seats/ + icon: contact +- title: Explore common FAQs + link: /subscription/faq/ + icon: help +aliases: +- /docker-hub/billing/ +- /docker-hub/billing/faq/ --- Use the resources in this section to manage your Docker subscription. -{{< grid >}} +{{< grid >}} \ No newline at end of file diff --git a/content/subscription/add-seats.md b/content/subscription/add-seats.md index 2066fcf7f6..7a53e66eb6 100644 --- a/content/subscription/add-seats.md +++ b/content/subscription/add-seats.md @@ -2,7 +2,7 @@ description: Add seats to your subscription keywords: Docker, Docker Hub, subscription, update, add, seats title: Add seats to your subscription -redirect_from: +aliases: - /docker-hub/billing/add-seats/ --- @@ -13,9 +13,9 @@ When you add seats to your subscription in the middle of your billing cycle, you >**Important** > >If you have a [sales-assisted Docker Business subscription](details.md#sales-assisted), contact your account manager to add seats to your subscription. -{: .important} +{ .important } -1. Log into your [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} account. +1. Log into your [Docker Hub](https://hub.docker.com) account. 2. Select **Organizations** and then choose your organization. @@ -27,4 +27,4 @@ When you add seats to your subscription in the middle of your billing cycle, you 5. Select **Purchase** to confirm. The **Billing** tab displays the new number of seats. -6. Navigate to the **Members** tab to add new members. For more information, see [Add a member to a team](../docker-hub/members.md). +6. Navigate to the **Members** tab to add new members. For more information, see [Add a member to a team](../docker-hub/members.md). \ No newline at end of file diff --git a/content/subscription/desktop-license.md b/content/subscription/desktop-license.md index debeae40bf..e3b896e486 100644 --- a/content/subscription/desktop-license.md +++ b/content/subscription/desktop-license.md @@ -6,20 +6,20 @@ keywords: license agreement, docker desktop, subscription Docker Desktop is licensed under the Docker Subscription Service Agreement. When you download and install Docker Desktop, you will be asked to agree to the updated terms. -Our [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"} states: +Our [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) states: - Docker Desktop is free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open source projects. - Otherwise, it requires a paid subscription for professional use. - Paid subscriptions are also required for government entities. - The Docker Pro, Team, and Business subscriptions include commercial use of Docker Desktop. -Read the [Blog](https://www.docker.com/blog/updating-product-subscriptions/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"} and [Docker subscription FAQs](https://www.docker.com/pricing/faq){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"} to learn how companies using Docker Desktop may be affected. +Read the [Blog](https://www.docker.com/blog/updating-product-subscriptions/) and [Docker subscription FAQs](https://www.docker.com/pricing/faq) to learn how companies using Docker Desktop may be affected. > **Note** > > The licensing and distribution terms for Docker and Moby open-source projects, such as Docker Engine, aren't changing. -Docker Desktop is built using open-source software. For information about the licensing of open-source components in Docker Desktop, select ![whale menu](../desktop/mac/images/whale-x.svg){: .inline} > **About Docker Desktop** > **Acknowledgements**. +Docker Desktop is built using open-source software. For information about the licensing of open-source components in Docker Desktop, select {{< inline-image src="../desktop/mac/images/whale-x.svg" alt="whale menu" >}} > **About Docker Desktop** > **Acknowledgements**. Docker Desktop distributes some components that are licensed under the GNU General Public License. Select [here](https://download.docker.com/opensource/License.tar.gz) to download the source for these components. \ No newline at end of file diff --git a/content/subscription/details.md b/content/subscription/details.md index bcfdc295bf..35c517ff6b 100644 --- a/content/subscription/details.md +++ b/content/subscription/details.md @@ -1,10 +1,10 @@ --- title: Docker subscriptions and features -description: Understand +description: Understand keywords: subscription, personal, pro, team, business, features --- -This page provides an overview of each tier. To compare features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"}. +This page provides an overview of each tier. To compare features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/). ## Docker Personal @@ -18,7 +18,7 @@ Docker Personal includes: Additionally, anonymous users get 100 pulls every 6 hours and users that sign in to Docker get 200 pulls every 6 hours. -For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"}. +For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/). ## Docker Pro @@ -32,7 +32,7 @@ Docker Pro includes: - 300 [Vulnerability Scans](../docker-hub/vulnerability-scanning.md) - Unlimited [Scoped Access Tokens](../docker-hub/access-tokens.md), and more. -For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"}. +For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/). ## Docker Team @@ -47,7 +47,7 @@ Docker Team includes: There are also advanced collaboration and management tools, including organization and team management with Role Based Access Control (RBAC) for the whole team, [audit logs](../docker-hub/audit-log.md), and more. -For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"}. +For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/). ## Docker Business @@ -62,7 +62,7 @@ Docker Business includes: - [Single Sign-On](../single-sign-on/index.md) - [System for Cross-domain Identity Management](../docker-hub/scim.md) and more. -For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/){: target="_blank" rel="noopener" class="_" id="dkr_docs_subscription_btl"}. +For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/). ### Self-serve @@ -75,4 +75,4 @@ A self-serve Docker Business subscription is where everything is set up by you. ### Sales-assisted -A sales-assisted Docker Business subscription where everything is set up and managed by a dedicated Docker account manager. +A sales-assisted Docker Business subscription where everything is set up and managed by a dedicated Docker account manager. \ No newline at end of file diff --git a/content/subscription/downgrade.md b/content/subscription/downgrade.md index f3949f6c15..413093a120 100644 --- a/content/subscription/downgrade.md +++ b/content/subscription/downgrade.md @@ -2,7 +2,7 @@ description: Downgrade your Docker subscription keywords: Docker Hub, downgrade, subscription, Pro, Team, Free, pricing plan, title: Downgrade your subscription -redirect_from: +aliases: - /docker-hub/cancel-downgrade/ - /docker-hub/billing/downgrade/ --- @@ -11,16 +11,16 @@ You can downgrade your Docker subscription at anytime before the renewal date. T When you downgrade your subscription, changes are applied immediately and you no longer have access to prior services. -Before you downgrade to a free subscription, you may need to reduce the number of team members and convert any private repositories to public repositories or delete them. For information, see [Docker Pricing](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"}. +Before you downgrade to a free subscription, you may need to reduce the number of team members and convert any private repositories to public repositories or delete them. For information, see [Docker Pricing](https://www.docker.com/pricing). ## Downgrade your Docker subscription >**Important** > >If you have a [sales-assisted Docker Business subscription](details.md#sales-assisted), contact your account manager to downgrade your subscription. -{: .important} +{ .important } -1. Log in to your [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} account. +1. Log in to your [Docker Hub](https://hub.docker.com) account. 2. Select your username in the top-right corner and from the drop-down menu select **Billing**. @@ -35,4 +35,4 @@ Before you downgrade to a free subscription, you may need to reduce the number o 7. Optional: Select a reason for your downgrade from the list and select **Send**. The **Billing** page displays a confirmation of the downgrade with details on when the downgrade changes take effect. -If you want to cancel the downgrade, select **Cancel the downgrade** on the **Plan** tab. +If you want to cancel the downgrade, select **Cancel the downgrade** on the **Plan** tab. \ No newline at end of file diff --git a/content/subscription/faq.md b/content/subscription/faq.md index 49d313e7cb..43a3e39398 100644 --- a/content/subscription/faq.md +++ b/content/subscription/faq.md @@ -6,7 +6,7 @@ title: Subscription FAQs ### I want to buy a large number of Docker Business subscription seats. How do I do this? Can I get a discount? -Docker offers volume pricing for Docker Business subscriptions starting at 25 seats. Contact the [Docker Sales Team](https://www.docker.com/pricing/contact-sales/){:target="blank" rel="noopener" class=""} for more information. +Docker offers volume pricing for Docker Business subscriptions starting at 25 seats. Contact the [Docker Sales Team](https://www.docker.com/pricing/contact-sales/) for more information. ### How do I access support? What level of support do I get for my subscription? @@ -14,7 +14,7 @@ All Docker Pro, Team, and Business subscribers receive email support for their s ### Does Docker offer academic pricing? -Contact the [Docker Sales Team](https://www.docker.com/company/contact){:target="blank" rel="noopener" class=""}. +Contact the [Docker Sales Team](https://www.docker.com/company/contact). ### What ways can I contribute to Docker content? @@ -36,7 +36,7 @@ Personal subscriptions do not include collaborators for private repositories. If ### How do I know what new features are in planning for my Docker Pro or Docker Team subscription? -Docker maintains a [public roadmap](https://github.com/docker/roadmap){:target="blank" rel="noopener" class=""} so subscribers can see what new features are in development, as well as request new capabilities. +Docker maintains a [public roadmap](https://github.com/docker/roadmap) so subscribers can see what new features are in development, as well as request new capabilities. ### Can I pause or delay my Docker Hub subscription? @@ -48,6 +48,4 @@ Subscriptions are non-transferable. ### I have more questions regarding the new pricing, who can I reach out to? -If you have any questions that are not covered in the FAQ, [please reach out](https://www.docker.com/company/contact){:target="blank" rel="noopener" class=""} and a member of the Docker team will get back to you. - - +If you have any questions that are not covered in the FAQ, [please reach out](https://www.docker.com/company/contact) and a member of the Docker team will get back to you. \ No newline at end of file diff --git a/content/subscription/remove-seats.md b/content/subscription/remove-seats.md index b2bd9b4889..ce6524f94e 100644 --- a/content/subscription/remove-seats.md +++ b/content/subscription/remove-seats.md @@ -2,7 +2,7 @@ description: Remove seats from your subscription keywords: Docker, Docker Hub, subscription, update, remove, seats title: Remove seats from your subscription -redirect_from: +aliases: - /docker-hub/billing/remove-seats/ --- @@ -17,9 +17,9 @@ For example, if you receive your billing on the 8th of every month for 10 seats >**Important** > >If you have a [sales-assisted Docker Business subscription](details.md#sales-assisted), contact your account manager to remove seats from your subscription. -{: .important} +{ .important } -1. Log into your [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} account. +1. Log into your [Docker Hub](https://hub.docker.com) account. 2. Select **Organizations** and then choose your organization. @@ -29,4 +29,4 @@ For example, if you receive your billing on the 8th of every month for 10 seats 5. The **Billing** tab confirms the seat removal and the details on when the changes take effect. -To cancel the removal of seats, select **Cancel seats downgrade**. +To cancel the removal of seats, select **Cancel seats downgrade**. \ No newline at end of file diff --git a/content/subscription/scout-details.md b/content/subscription/scout-details.md index e5e0c59e1e..a6caf39e4d 100644 --- a/content/subscription/scout-details.md +++ b/content/subscription/scout-details.md @@ -4,9 +4,9 @@ description: Learn about the Docker Scout subscriptions plans and features keywords: subscription, free, team, business, features --- -{% include scout-early-access.md %} +{{< include "scout-early-access.md" >}} -This page provides an overview of the subscription plans for Docker Scout. To compare features available for each plan, see [Docker Scout Pricing](https://docker.com/products/docker-scout){: target="_blank" rel="noopener" class="_"}. +This page provides an overview of the subscription plans for Docker Scout. To compare features available for each plan, see [Docker Scout Pricing](https://docker.com/products/docker-scout). ## Docker Scout Free @@ -40,4 +40,4 @@ Docker Scout Business includes: - All the features available in Docker Scout Team - Unlimited Docker Scout-enabled repositories -You can [contact sales](https://www.docker.com/products/docker-scout/){: target="_blank" rel="noopener" class="_"} to buy Docker Scout Business. \ No newline at end of file +You can [contact sales](https://www.docker.com/products/docker-scout/) to buy Docker Scout Business. \ No newline at end of file diff --git a/content/subscription/upgrade.md b/content/subscription/upgrade.md index 683d9140e8..e1f04ff239 100644 --- a/content/subscription/upgrade.md +++ b/content/subscription/upgrade.md @@ -2,16 +2,16 @@ description: Upgrading your Docker subscription keywords: Docker Hub, upgrade, subscription, Pro, Team, business, pricing plan, title: Upgrade your subscription -redirect_from: +aliases: - /docker-hub/upgrade/ - /docker-hub/billing/upgrade/ --- -When you upgrade to a paid subscription, you immediately have access to all the features and entitlements available in your new chosen subscription. For detailed information on features available in each subscription, see [Docker Pricing](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"}. +When you upgrade to a paid subscription, you immediately have access to all the features and entitlements available in your new chosen subscription. For detailed information on features available in each subscription, see [Docker Pricing](https://www.docker.com/pricing). ## Upgrade your subscription -1. Log in to your [Docker Hub](https://hub.docker.com){: target="_blank" rel="noopener" class="_"} account. +1. Log in to your [Docker Hub](https://hub.docker.com) account. 2. Optional: If you are upgrading from a free user account to a Team or Business subscription and want to keep your account name, [convert your user account into an organization](../docker-hub/convert-account.md). @@ -27,4 +27,4 @@ When you upgrade to a paid subscription, you immediately have access to all the 5. Follow the on-screen instructions. - If you have a [coupon](../billing/faqs.md#how-do-i-redeem-a-coupon) to use, you can enter it during this step. + If you have a [coupon](../billing/faqs.md#how-do-i-redeem-a-coupon) to use, you can enter it during this step. \ No newline at end of file diff --git a/content/support.md b/content/support.md index 2109ab52e6..6a2a9eb19e 100644 --- a/content/support.md +++ b/content/support.md @@ -2,7 +2,7 @@ description: Get support keywords: Support, Docker Desktop, Docker Hub, Hub, Linux, Mac, Windows title: Get support -redirect_from: +aliases: - /desktop/support/ --- @@ -10,14 +10,14 @@ Find information on how to get support, and the scope of Docker support. ## How do I get support? -If you have a paid Docker subscription, raise a ticket through [Docker support](https://hub.docker.com/support/contact/){:target="_blank" rel="noopener" class="_"}. +If you have a paid Docker subscription, raise a ticket through [Docker support](https://hub.docker.com/support/contact/). All Docker users can seek support through the following resources, where Docker or the community respond on a best effort basis. - - [Docker Desktop for Windows GitHub repo](https://github.com/docker/for-win){:target="_blank" rel="noopener" class="_"} - - [Docker Desktop for Mac GitHub repo](https://github.com/docker/for-mac){:target="_blank" rel="noopener" class="_"} - - [Docker Desktop for Linux GitHub repo](https://github.com/docker/desktop-linux){:target="_blank" rel="noopener" class="_"} - - [Docker Community Forums](https://forums.docker.com/){:target="_blank" rel="noopener" class="_"} - - [Docker Community Slack](https://dockercommunity.slack.com/){:target="_blank" rel="noopener" class="_"} + - [Docker Desktop for Windows GitHub repo](https://github.com/docker/for-win) + - [Docker Desktop for Mac GitHub repo](https://github.com/docker/for-mac) + - [Docker Desktop for Linux GitHub repo](https://github.com/docker/desktop-linux) + - [Docker Community Forums](https://forums.docker.com/) + - [Docker Community Slack](https://dockercommunity.slack.com/) ## What support can I get? @@ -91,7 +91,7 @@ employees who are directly involved in diagnosing Docker Desktop issues. By default, Docker, Inc. will delete uploaded diagnostics bundles after 30 days. You may also request the removal of a diagnostics bundle by either specifying the diagnostics ID or via your GitHub ID (if the diagnostics ID is mentioned in a GitHub issue). Docker, Inc. will only use the data in the diagnostics bundle to investigate specific user issues but may derive high-level (non personal) metrics such as the rate of issues from it. -For more information, see [Docker Data Processing Agreement](https://www.docker.com/legal/data-processing-agreement){: target="_blank" rel="noopener" class="_"}. +For more information, see [Docker Data Processing Agreement](https://www.docker.com/legal/data-processing-agreement). ## What can I do before seeking support? @@ -103,4 +103,4 @@ You can also see if an answer already exists in the following FAQs: - [Docker Desktop for Linux](../desktop/faqs/linuxfaqs.md) - [Docker Desktop for Mac](../desktop/faqs/macfaqs.md) - [Docker Desktop for Windows](../desktop/faqs/windowsfaqs.md) -- [Single Sign-on](../single-sign-on/faqs.md) +- [Single Sign-on](../single-sign-on/faqs.md) \ No newline at end of file