Skip to content
This repository has been archived by the owner on Oct 29, 2024. It is now read-only.

Since the extension backend is executing inside the VM, no need to go through the socket on the host, use the engine socket directly #146

Merged
merged 1 commit into from
Jul 4, 2024

Conversation

gtardif
Copy link
Contributor

@gtardif gtardif commented Jul 4, 2024

Tested export of local image, and export to registry / import from registry

…he socket on the host, use the engine socket directly

Signed-off-by: Guillaume Tardif <guillaume.tardif@gmail.com>
@gtardif gtardif requested a review from a team as a code owner July 4, 2024 16:54
@gtardif gtardif merged commit 3d35ee1 into docker:main Jul 4, 2024
3 checks passed
Copy link
Member

@maxcleme maxcleme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this work with resource saver? IMO it will hang since it won't poke the VM 😅

EDIT: nevermind, if the extension container is running there is no mean the resource saver kicks in! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants