a2b8d3a9e8
dm_task_deferred_remove is not supported by all distributions, due to out-dated versions of devicemapper. However, in the case where the devicemapper library was updated without rebuilding Docker (which can happen in some distributions) then we should attempt to dynamically load the relevant object rather than try to link to it. This can only be done if Docker was built dynamically, for obvious reasons. In order to avoid having issues arise when dlsym(3) was unnecessary, gate the whole dlsym(3) logic behind a buildflag that we disable by default (libdm_dlsym_deferred_remove). Signed-off-by: Aleksa Sarai <asarai@suse.de> Upstream-commit: 98fe4bd8f1e35f8e498e268f653a43cbfa31e751 Component: engine
18 lines
494 B
Go
18 lines
494 B
Go
// +build linux,cgo
|
|
// +build !libdm_dlsym_deferred_remove,libdm_no_deferred_remove
|
|
|
|
package devicemapper // import "github.com/docker/docker/pkg/devicemapper"
|
|
|
|
// LibraryDeferredRemovalSupport tells if the feature is supported by the
|
|
// current Docker invocation.
|
|
const LibraryDeferredRemovalSupport = false
|
|
|
|
func dmTaskDeferredRemoveFct(task *cdmTask) int {
|
|
// Error. Nobody should be calling it.
|
|
return -1
|
|
}
|
|
|
|
func dmTaskGetInfoWithDeferredFct(task *cdmTask, info *Info) int {
|
|
return -1
|
|
}
|