Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[23.0 backport] Fix pruning anon volume created from image config #45159

Merged

Conversation

thaJeztah
Copy link
Member


Volumes created from the image config were not being pruned because the volume service did not think they were anonymous since the code to create passes along a generated name instead of letting the volume service generate it.

This changes the code path to have the volume service generate the name instead of doing it ahead of time.

@thaJeztah thaJeztah added this to the v-next milestone Mar 14, 2023
@thaJeztah thaJeztah marked this pull request as draft March 14, 2023 13:13
@thaJeztah thaJeztah modified the milestones: v-next, 23.0.2 Mar 14, 2023
Volumes created from the image config were not being pruned because the
volume service did not think they were anonymous since the code to
create passes along a generated name instead of letting the volume
service generate it.

This changes the code path to have the volume service generate the name
instead of doing it ahead of time.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
(cherry picked from commit 146df5f)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah force-pushed the 23.0_backport_fix_volume_anon_from_image branch from f7f0a39 to fd80ca6 Compare March 14, 2023 15:11
@thaJeztah thaJeztah marked this pull request as ready for review March 14, 2023 15:11
@cpuguy83 cpuguy83 merged commit 9740b68 into moby:23.0 Mar 14, 2023
87 checks passed
@thaJeztah thaJeztah deleted the 23.0_backport_fix_volume_anon_from_image branch March 14, 2023 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants