2018-03-22 17:11:03 -04:00
|
|
|
package service // import "github.com/docker/docker/volume/service"
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
API: add "prune" events
This patch adds a new "prune" event type to indicate that pruning of a resource
type completed.
This event-type can be used on systems that want to perform actions after
resources have been cleaned up. For example, Docker Desktop performs an fstrim
after resources are deleted (https://github.com/linuxkit/linuxkit/tree/v0.7/pkg/trim-after-delete).
While the current (remove, destroy) events can provide information on _most_
resources, there is currently no event triggered after the BuildKit build-cache
is cleaned.
Prune events have a `reclaimed` attribute, indicating the amount of space that
was reclaimed (in bytes). The attribute can be used, for example, to use as a
threshold for performing fstrim actions. Reclaimed space for `network` events
will always be 0, but the field is added to be consistent with prune events for
other resources.
To test this patch:
Create some resources:
for i in foo bar baz; do \
docker network create network_$i \
&& docker volume create volume_$i \
&& docker run -d --name container_$i -v volume_$i:/volume busybox sh -c 'truncate -s 5M somefile; truncate -s 5M /volume/file' \
&& docker tag busybox:latest image_$i; \
done;
docker pull alpine
docker pull nginx:alpine
echo -e "FROM busybox\nRUN truncate -s 50M bigfile" | DOCKER_BUILDKIT=1 docker build -
Start listening for "prune" events in another shell:
docker events --filter event=prune
Prune containers, networks, volumes, and build-cache:
docker system prune -af --volumes
See the events that are returned:
docker events --filter event=prune
2020-07-25T12:12:09.268491000Z container prune (reclaimed=15728640)
2020-07-25T12:12:09.447890400Z network prune (reclaimed=0)
2020-07-25T12:12:09.452323000Z volume prune (reclaimed=15728640)
2020-07-25T12:12:09.517236200Z image prune (reclaimed=21568540)
2020-07-25T12:12:09.566662600Z builder prune (reclaimed=52428841)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-07-25 08:14:38 -04:00
|
|
|
"strconv"
|
2018-03-22 17:11:03 -04:00
|
|
|
"sync/atomic"
|
|
|
|
|
|
|
|
"github.com/docker/docker/api/types"
|
|
|
|
"github.com/docker/docker/api/types/filters"
|
2022-03-18 11:33:43 -04:00
|
|
|
volumetypes "github.com/docker/docker/api/types/volume"
|
2018-03-22 17:11:03 -04:00
|
|
|
"github.com/docker/docker/errdefs"
|
|
|
|
"github.com/docker/docker/pkg/directory"
|
|
|
|
"github.com/docker/docker/pkg/idtools"
|
|
|
|
"github.com/docker/docker/pkg/plugingetter"
|
|
|
|
"github.com/docker/docker/pkg/stringid"
|
|
|
|
"github.com/docker/docker/volume"
|
|
|
|
"github.com/docker/docker/volume/drivers"
|
|
|
|
"github.com/docker/docker/volume/service/opts"
|
|
|
|
"github.com/pkg/errors"
|
|
|
|
"github.com/sirupsen/logrus"
|
2021-06-24 13:06:17 -04:00
|
|
|
"golang.org/x/sync/singleflight"
|
2018-03-22 17:11:03 -04:00
|
|
|
)
|
|
|
|
|
|
|
|
type ds interface {
|
|
|
|
GetDriverList() []string
|
|
|
|
}
|
|
|
|
|
volumes: only send "create" event when actually creating volume
The VolumesService did not have information wether or not a volume
was _created_ or if a volume already existed in the driver, and
the existing volume was used.
As a result, multiple "create" events could be generated for the
same volume. For example:
1. Run `docker events` in a shell to start listening for events
2. Create a volume:
docker volume create myvolume
3. Start a container that uses that volume:
docker run -dit -v myvolume:/foo busybox
4. Check the events that were generated:
2021-02-15T18:49:55.874621004+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.442759052+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.487104176+01:00 container create 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
2021-02-15T18:50:11.519288102+01:00 network connect a19f6bb8d44ff84d478670fa4e34c5bf5305f42786294d3d90e790ac74b6d3e0 (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, name=bridge, type=bridge)
2021-02-15T18:50:11.526407799+01:00 volume mount myvolume (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, destination=/foo, driver=local, propagation=, read/write=true)
2021-02-15T18:50:11.864134043+01:00 container start 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
5. Notice that a "volume create" event is created twice;
- once when `docker volume create` was ran
- once when `docker run ...` was ran
This patch moves the generation of (most) events to the volume _store_, and only
generates an event if the volume did not yet exist.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-02-15 12:45:15 -05:00
|
|
|
// VolumeEventLogger interface provides methods to log volume-related events
|
|
|
|
type VolumeEventLogger interface {
|
|
|
|
// LogVolumeEvent generates an event related to a volume.
|
2018-03-22 17:11:03 -04:00
|
|
|
LogVolumeEvent(volumeID, action string, attributes map[string]string)
|
|
|
|
}
|
|
|
|
|
|
|
|
// VolumesService manages access to volumes
|
2018-10-31 14:50:24 -04:00
|
|
|
// This is used as the main access point for volumes to higher level services and the API.
|
2018-03-22 17:11:03 -04:00
|
|
|
type VolumesService struct {
|
|
|
|
vs *VolumeStore
|
|
|
|
ds ds
|
|
|
|
pruneRunning int32
|
volumes: only send "create" event when actually creating volume
The VolumesService did not have information wether or not a volume
was _created_ or if a volume already existed in the driver, and
the existing volume was used.
As a result, multiple "create" events could be generated for the
same volume. For example:
1. Run `docker events` in a shell to start listening for events
2. Create a volume:
docker volume create myvolume
3. Start a container that uses that volume:
docker run -dit -v myvolume:/foo busybox
4. Check the events that were generated:
2021-02-15T18:49:55.874621004+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.442759052+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.487104176+01:00 container create 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
2021-02-15T18:50:11.519288102+01:00 network connect a19f6bb8d44ff84d478670fa4e34c5bf5305f42786294d3d90e790ac74b6d3e0 (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, name=bridge, type=bridge)
2021-02-15T18:50:11.526407799+01:00 volume mount myvolume (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, destination=/foo, driver=local, propagation=, read/write=true)
2021-02-15T18:50:11.864134043+01:00 container start 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
5. Notice that a "volume create" event is created twice;
- once when `docker volume create` was ran
- once when `docker run ...` was ran
This patch moves the generation of (most) events to the volume _store_, and only
generates an event if the volume did not yet exist.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-02-15 12:45:15 -05:00
|
|
|
eventLogger VolumeEventLogger
|
2021-06-24 13:06:17 -04:00
|
|
|
usage singleflight.Group
|
2018-03-22 17:11:03 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// NewVolumeService creates a new volume service
|
volumes: only send "create" event when actually creating volume
The VolumesService did not have information wether or not a volume
was _created_ or if a volume already existed in the driver, and
the existing volume was used.
As a result, multiple "create" events could be generated for the
same volume. For example:
1. Run `docker events` in a shell to start listening for events
2. Create a volume:
docker volume create myvolume
3. Start a container that uses that volume:
docker run -dit -v myvolume:/foo busybox
4. Check the events that were generated:
2021-02-15T18:49:55.874621004+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.442759052+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.487104176+01:00 container create 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
2021-02-15T18:50:11.519288102+01:00 network connect a19f6bb8d44ff84d478670fa4e34c5bf5305f42786294d3d90e790ac74b6d3e0 (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, name=bridge, type=bridge)
2021-02-15T18:50:11.526407799+01:00 volume mount myvolume (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, destination=/foo, driver=local, propagation=, read/write=true)
2021-02-15T18:50:11.864134043+01:00 container start 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
5. Notice that a "volume create" event is created twice;
- once when `docker volume create` was ran
- once when `docker run ...` was ran
This patch moves the generation of (most) events to the volume _store_, and only
generates an event if the volume did not yet exist.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-02-15 12:45:15 -05:00
|
|
|
func NewVolumeService(root string, pg plugingetter.PluginGetter, rootIDs idtools.Identity, logger VolumeEventLogger) (*VolumesService, error) {
|
2018-03-22 17:11:03 -04:00
|
|
|
ds := drivers.NewStore(pg)
|
|
|
|
if err := setupDefaultDriver(ds, root, rootIDs); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
volumes: only send "create" event when actually creating volume
The VolumesService did not have information wether or not a volume
was _created_ or if a volume already existed in the driver, and
the existing volume was used.
As a result, multiple "create" events could be generated for the
same volume. For example:
1. Run `docker events` in a shell to start listening for events
2. Create a volume:
docker volume create myvolume
3. Start a container that uses that volume:
docker run -dit -v myvolume:/foo busybox
4. Check the events that were generated:
2021-02-15T18:49:55.874621004+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.442759052+01:00 volume create myvolume (driver=local)
2021-02-15T18:50:11.487104176+01:00 container create 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
2021-02-15T18:50:11.519288102+01:00 network connect a19f6bb8d44ff84d478670fa4e34c5bf5305f42786294d3d90e790ac74b6d3e0 (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, name=bridge, type=bridge)
2021-02-15T18:50:11.526407799+01:00 volume mount myvolume (container=45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1, destination=/foo, driver=local, propagation=, read/write=true)
2021-02-15T18:50:11.864134043+01:00 container start 45112157c8b1382626bf5e01ef18445a4c680f3846c5e32d01775dddee8ca6d1 (image=busybox, name=gracious_hypatia)
5. Notice that a "volume create" event is created twice;
- once when `docker volume create` was ran
- once when `docker run ...` was ran
This patch moves the generation of (most) events to the volume _store_, and only
generates an event if the volume did not yet exist.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2021-02-15 12:45:15 -05:00
|
|
|
vs, err := NewStore(root, ds, WithEventLogger(logger))
|
2018-03-22 17:11:03 -04:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return &VolumesService{vs: vs, ds: ds, eventLogger: logger}, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// GetDriverList gets the list of registered volume drivers
|
|
|
|
func (s *VolumesService) GetDriverList() []string {
|
|
|
|
return s.ds.GetDriverList()
|
|
|
|
}
|
|
|
|
|
|
|
|
// Create creates a volume
|
2018-10-31 14:50:24 -04:00
|
|
|
// If the caller is creating this volume to be consumed immediately, it is
|
|
|
|
// expected that the caller specifies a reference ID.
|
|
|
|
// This reference ID will protect this volume from removal.
|
|
|
|
//
|
|
|
|
// A good example for a reference ID is a container's ID.
|
|
|
|
// When whatever is going to reference this volume is removed the caller should defeference the volume by calling `Release`.
|
2022-03-18 11:33:43 -04:00
|
|
|
func (s *VolumesService) Create(ctx context.Context, name, driverName string, opts ...opts.CreateOption) (*volumetypes.Volume, error) {
|
2018-03-22 17:11:03 -04:00
|
|
|
if name == "" {
|
2019-06-07 06:21:18 -04:00
|
|
|
name = stringid.GenerateRandomID()
|
2018-03-22 17:11:03 -04:00
|
|
|
}
|
|
|
|
v, err := s.vs.Create(ctx, name, driverName, opts...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
apiV := volumeToAPIType(v)
|
|
|
|
return &apiV, nil
|
|
|
|
}
|
|
|
|
|
2018-10-31 14:50:24 -04:00
|
|
|
// Get returns details about a volume
|
2022-03-18 11:33:43 -04:00
|
|
|
func (s *VolumesService) Get(ctx context.Context, name string, getOpts ...opts.GetOption) (*volumetypes.Volume, error) {
|
2018-03-22 17:11:03 -04:00
|
|
|
v, err := s.vs.Get(ctx, name, getOpts...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
vol := volumeToAPIType(v)
|
|
|
|
|
|
|
|
var cfg opts.GetConfig
|
|
|
|
for _, o := range getOpts {
|
|
|
|
o(&cfg)
|
|
|
|
}
|
|
|
|
|
|
|
|
if cfg.ResolveStatus {
|
|
|
|
vol.Status = v.Status()
|
|
|
|
}
|
|
|
|
return &vol, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Mount mounts the volume
|
2018-10-31 14:50:24 -04:00
|
|
|
// Callers should specify a uniqe reference for each Mount/Unmount pair.
|
|
|
|
//
|
|
|
|
// Example:
|
|
|
|
// ```go
|
|
|
|
// mountID := "randomString"
|
|
|
|
// s.Mount(ctx, vol, mountID)
|
|
|
|
// s.Unmount(ctx, vol, mountID)
|
|
|
|
// ```
|
2022-03-18 11:33:43 -04:00
|
|
|
func (s *VolumesService) Mount(ctx context.Context, vol *volumetypes.Volume, ref string) (string, error) {
|
2018-03-22 17:11:03 -04:00
|
|
|
v, err := s.vs.Get(ctx, vol.Name, opts.WithGetDriver(vol.Driver))
|
|
|
|
if err != nil {
|
|
|
|
if IsNotExist(err) {
|
|
|
|
err = errdefs.NotFound(err)
|
|
|
|
}
|
|
|
|
return "", err
|
|
|
|
}
|
|
|
|
return v.Mount(ref)
|
|
|
|
}
|
|
|
|
|
|
|
|
// Unmount unmounts the volume.
|
|
|
|
// Note that depending on the implementation, the volume may still be mounted due to other resources using it.
|
2018-10-31 14:50:24 -04:00
|
|
|
//
|
|
|
|
// The reference specified here should be the same reference specified during `Mount` and should be
|
|
|
|
// unique for each mount/unmount pair.
|
|
|
|
// See `Mount` documentation for an example.
|
2022-03-18 11:33:43 -04:00
|
|
|
func (s *VolumesService) Unmount(ctx context.Context, vol *volumetypes.Volume, ref string) error {
|
2018-03-22 17:11:03 -04:00
|
|
|
v, err := s.vs.Get(ctx, vol.Name, opts.WithGetDriver(vol.Driver))
|
|
|
|
if err != nil {
|
|
|
|
if IsNotExist(err) {
|
|
|
|
err = errdefs.NotFound(err)
|
|
|
|
}
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
return v.Unmount(ref)
|
|
|
|
}
|
|
|
|
|
|
|
|
// Release releases a volume reference
|
|
|
|
func (s *VolumesService) Release(ctx context.Context, name string, ref string) error {
|
|
|
|
return s.vs.Release(ctx, name, ref)
|
|
|
|
}
|
|
|
|
|
|
|
|
// Remove removes a volume
|
2018-10-31 14:50:24 -04:00
|
|
|
// An error is returned if the volume is still referenced.
|
2018-03-22 17:11:03 -04:00
|
|
|
func (s *VolumesService) Remove(ctx context.Context, name string, rmOpts ...opts.RemoveOption) error {
|
|
|
|
var cfg opts.RemoveConfig
|
|
|
|
for _, o := range rmOpts {
|
|
|
|
o(&cfg)
|
|
|
|
}
|
|
|
|
|
|
|
|
v, err := s.vs.Get(ctx, name)
|
|
|
|
if err != nil {
|
|
|
|
if IsNotExist(err) && cfg.PurgeOnError {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
err = s.vs.Remove(ctx, v, rmOpts...)
|
|
|
|
if IsNotExist(err) {
|
|
|
|
err = nil
|
|
|
|
} else if IsInUse(err) {
|
|
|
|
err = errdefs.Conflict(err)
|
|
|
|
} else if IsNotExist(err) && cfg.PurgeOnError {
|
|
|
|
err = nil
|
|
|
|
}
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
var acceptedPruneFilters = map[string]bool{
|
|
|
|
"label": true,
|
|
|
|
"label!": true,
|
|
|
|
}
|
|
|
|
|
|
|
|
var acceptedListFilters = map[string]bool{
|
|
|
|
"dangling": true,
|
|
|
|
"name": true,
|
|
|
|
"driver": true,
|
|
|
|
"label": true,
|
|
|
|
}
|
|
|
|
|
|
|
|
// LocalVolumesSize gets all local volumes and fetches their size on disk
|
|
|
|
// Note that this intentionally skips volumes which have mount options. Typically
|
|
|
|
// volumes with mount options are not really local even if they are using the
|
|
|
|
// local driver.
|
2022-03-18 11:33:43 -04:00
|
|
|
func (s *VolumesService) LocalVolumesSize(ctx context.Context) ([]*volumetypes.Volume, error) {
|
2021-06-24 13:06:17 -04:00
|
|
|
ch := s.usage.DoChan("LocalVolumesSize", func() (interface{}, error) {
|
|
|
|
ls, _, err := s.vs.Find(ctx, And(ByDriver(volume.DefaultDriverName), CustomFilter(func(v volume.Volume) bool {
|
|
|
|
dv, ok := v.(volume.DetailedVolume)
|
|
|
|
return ok && len(dv.Options()) == 0
|
|
|
|
})))
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return s.volumesToAPI(ctx, ls, calcSize(true)), nil
|
|
|
|
})
|
|
|
|
select {
|
|
|
|
case <-ctx.Done():
|
|
|
|
return nil, ctx.Err()
|
|
|
|
case res := <-ch:
|
|
|
|
if res.Err != nil {
|
|
|
|
return nil, res.Err
|
|
|
|
}
|
2022-03-18 11:33:43 -04:00
|
|
|
return res.Val.([]*volumetypes.Volume), nil
|
2018-03-22 17:11:03 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Prune removes (local) volumes which match the past in filter arguments.
|
|
|
|
// Note that this intentionally skips volumes with mount options as there would
|
|
|
|
// be no space reclaimed in this case.
|
|
|
|
func (s *VolumesService) Prune(ctx context.Context, filter filters.Args) (*types.VolumesPruneReport, error) {
|
|
|
|
if !atomic.CompareAndSwapInt32(&s.pruneRunning, 0, 1) {
|
|
|
|
return nil, errdefs.Conflict(errors.New("a prune operation is already running"))
|
|
|
|
}
|
|
|
|
defer atomic.StoreInt32(&s.pruneRunning, 0)
|
|
|
|
|
|
|
|
by, err := filtersToBy(filter, acceptedPruneFilters)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
ls, _, err := s.vs.Find(ctx, And(ByDriver(volume.DefaultDriverName), ByReferenced(false), by, CustomFilter(func(v volume.Volume) bool {
|
|
|
|
dv, ok := v.(volume.DetailedVolume)
|
|
|
|
return ok && len(dv.Options()) == 0
|
|
|
|
})))
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
rep := &types.VolumesPruneReport{VolumesDeleted: make([]string, 0, len(ls))}
|
|
|
|
for _, v := range ls {
|
|
|
|
select {
|
|
|
|
case <-ctx.Done():
|
|
|
|
err := ctx.Err()
|
|
|
|
if err == context.Canceled {
|
|
|
|
err = nil
|
|
|
|
}
|
|
|
|
return rep, err
|
|
|
|
default:
|
|
|
|
}
|
|
|
|
|
|
|
|
vSize, err := directory.Size(ctx, v.Path())
|
|
|
|
if err != nil {
|
|
|
|
logrus.WithField("volume", v.Name()).WithError(err).Warn("could not determine size of volume")
|
|
|
|
}
|
|
|
|
if err := s.vs.Remove(ctx, v); err != nil {
|
|
|
|
logrus.WithError(err).WithField("volume", v.Name()).Warnf("Could not determine size of volume")
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
rep.SpaceReclaimed += uint64(vSize)
|
|
|
|
rep.VolumesDeleted = append(rep.VolumesDeleted, v.Name())
|
|
|
|
}
|
API: add "prune" events
This patch adds a new "prune" event type to indicate that pruning of a resource
type completed.
This event-type can be used on systems that want to perform actions after
resources have been cleaned up. For example, Docker Desktop performs an fstrim
after resources are deleted (https://github.com/linuxkit/linuxkit/tree/v0.7/pkg/trim-after-delete).
While the current (remove, destroy) events can provide information on _most_
resources, there is currently no event triggered after the BuildKit build-cache
is cleaned.
Prune events have a `reclaimed` attribute, indicating the amount of space that
was reclaimed (in bytes). The attribute can be used, for example, to use as a
threshold for performing fstrim actions. Reclaimed space for `network` events
will always be 0, but the field is added to be consistent with prune events for
other resources.
To test this patch:
Create some resources:
for i in foo bar baz; do \
docker network create network_$i \
&& docker volume create volume_$i \
&& docker run -d --name container_$i -v volume_$i:/volume busybox sh -c 'truncate -s 5M somefile; truncate -s 5M /volume/file' \
&& docker tag busybox:latest image_$i; \
done;
docker pull alpine
docker pull nginx:alpine
echo -e "FROM busybox\nRUN truncate -s 50M bigfile" | DOCKER_BUILDKIT=1 docker build -
Start listening for "prune" events in another shell:
docker events --filter event=prune
Prune containers, networks, volumes, and build-cache:
docker system prune -af --volumes
See the events that are returned:
docker events --filter event=prune
2020-07-25T12:12:09.268491000Z container prune (reclaimed=15728640)
2020-07-25T12:12:09.447890400Z network prune (reclaimed=0)
2020-07-25T12:12:09.452323000Z volume prune (reclaimed=15728640)
2020-07-25T12:12:09.517236200Z image prune (reclaimed=21568540)
2020-07-25T12:12:09.566662600Z builder prune (reclaimed=52428841)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2020-07-25 08:14:38 -04:00
|
|
|
s.eventLogger.LogVolumeEvent("", "prune", map[string]string{
|
|
|
|
"reclaimed": strconv.FormatInt(int64(rep.SpaceReclaimed), 10),
|
|
|
|
})
|
2018-03-22 17:11:03 -04:00
|
|
|
return rep, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// List gets the list of volumes which match the past in filters
|
|
|
|
// If filters is nil or empty all volumes are returned.
|
2022-03-18 11:33:43 -04:00
|
|
|
func (s *VolumesService) List(ctx context.Context, filter filters.Args) (volumesOut []*volumetypes.Volume, warnings []string, err error) {
|
2018-03-22 17:11:03 -04:00
|
|
|
by, err := filtersToBy(filter, acceptedListFilters)
|
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
volumes, warnings, err := s.vs.Find(ctx, by)
|
|
|
|
if err != nil {
|
|
|
|
return nil, nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
return s.volumesToAPI(ctx, volumes, useCachedPath(true)), warnings, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Shutdown shuts down the image service and dependencies
|
|
|
|
func (s *VolumesService) Shutdown() error {
|
|
|
|
return s.vs.Shutdown()
|
|
|
|
}
|