We probably need to split things up here; part of the volume/ package is related to the volume "service" used by the daemon, but part is a public API, which at least is used for the volume-plugins (we still need to move that repository to the moby org); https://github.com/docker/go-plugins-helpers/blob/45e2431495c83b9ca1c2a669987d6e1afad07774/volume/shim/shim.go#L4

Looks like the volume/mounts package also has at least 1 external consumer; I somewhat doubt they're using the correct thing there, but we need to check if we have alternatives for what they're doing; I know some of the parsing has been non-trivial, so we should check if we have proper utilities for those (somewhere in the client or elsewhere) https://github.com/buildpacks/pack/blob/fb0563f4cdb51ae32463088fccefe5c961bbdd07/pkg/client/process_volumes.go#L10-L16

Looks like the volume/mounts package also has at least 1 external consumer;

This is not going to internal, importers can use the new package location, it will also not be considered stable. They can continue to use the 28 tag in the existing location. After we move this, we can decide of moving any package that is used externally to a more stable location, that would either be under github.com/moby/moby/api, github.com/moby/moby/client or other repo moby repo not under github.com/moby/moby.

We can get this one before we make those decisions, we can track those cases somewhere if that is easier.