[go: up one dir, main page]
{ const container = $el; // The div with overflow const item = document.getElementById('sidebar-current-page') if (item) { const containerTop = container.scrollTop; const containerBottom = containerTop + container.clientHeight; const itemTop = item.offsetTop - container.offsetTop; const itemBottom = itemTop + item.offsetHeight; // Scroll only if the item is out of view if (itemBottom > containerBottom - 200) { container.scrollTop = itemTop - (container.clientHeight / 2 - item.offsetHeight / 2); } } })" class="bg-background-toc dark:bg-background-toc fixed top-0 z-40 hidden h-screen w-full flex-none overflow-x-hidden overflow-y-auto md:sticky md:top-16 md:z-auto md:block md:h-[calc(100vh-64px)] md:w-[320px]" :class="{ 'hidden': ! $store.showSidebar }">
Contact support
Reference

docker buildx rm

DescriptionRemove one or more builder instances
Usagedocker buildx rm [OPTIONS] [NAME...]

Description

Removes the specified or current builder. It is a no-op attempting to remove the default builder.

Options

OptionDefaultDescription
--all-inactiveRemove all inactive builders
-f, --forceDo not prompt for confirmation
--keep-daemonKeep the BuildKit daemon running
--keep-stateKeep BuildKit state

Examples

Remove all inactive builders (--all-inactive)

Remove builders that are not in running state.

$ docker buildx rm --all-inactive
WARNING! This will remove all builders that are not in running state. Are you sure you want to continue? [y/N] y

Override the configured builder instance (--builder)

Same as buildx --builder.

Do not prompt for confirmation (--force)

Do not prompt for confirmation before removing inactive builders.

$ docker buildx rm --all-inactive --force

Keep the BuildKit daemon running (--keep-daemon)

Keep the BuildKit daemon running after the buildx context is removed. This is useful when you manage BuildKit daemons and buildx contexts independently. Only supported by the docker-container and kubernetes drivers.

Keep BuildKit state (--keep-state)

Keep BuildKit state, so it can be reused by a new builder with the same name. Currently, only supported by the docker-container driver.