Skip to content

[v0.6] container-driver: fix volume destination for cache#752

Merged
tonistiigi merged 2 commits intodocker:v0.6from
tonistiigi:v0.6-mount-path-fix
Aug 28, 2021
Merged

[v0.6] container-driver: fix volume destination for cache#752
tonistiigi merged 2 commits intodocker:v0.6from
tonistiigi:v0.6-mount-path-fix

Conversation

@tonistiigi
Copy link
Member

@tonistiigi tonistiigi commented Aug 28, 2021

pick #751

The container-driver creates a Linux container (as there currently isn't a
Windows version of buildkitd). However, the defaults are platform specific.

Buildx was using the defaults from the buildkit `util/appdefault' package,
which resulted in Buildx running on a Windows client to create a Linux
container that used the Windows location, which causes it to fail:

invalid mount config for type "volume": invalid mount path: 'C:/ProgramData/buildkitd/.buildstate' mount path must be absolute

This patch hard-codes the destination to the default Linux path.

Signed-off-by: Sebastiaan van Stijn github@gone.nl
(cherry picked from commit 93867d0)

thaJeztah and others added 2 commits August 27, 2021 21:03
The container-driver creates a Linux container (as there currently isn't a
Windows version of buildkitd). However, the defaults are platform specific.

Buildx was using the defaults from the buildkit `util/appdefault' package,
which resulted in Buildx running on a Windows client to create a Linux
container that used the Windows location, which causes it to fail:

    invalid mount config for type "volume": invalid mount path: 'C:/ProgramData/buildkitd/.buildstate' mount path must be absolute

This patch hard-codes the destination to the default Linux path.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit 93867d0)
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
(cherry picked from commit 9833420)
@tonistiigi tonistiigi force-pushed the v0.6-mount-path-fix branch from 94fe941 to 0b320fa Compare August 28, 2021 04:20
@thaJeztah
Copy link
Member

ah! didn't realize we started a branch (thought we still did 0.6 from master)

I should probably have a look if we need to get some of the docs changes into the branch (but that can wait)

v0.6...master

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

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

LGTM

@tonistiigi tonistiigi merged commit 266c0ea into docker:v0.6 Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants