Golang：可以肯定地说，如果一个结构体实现一个方法，那么它会满足所有定义该方法签名的接口？

In the docker source repo, there exists an interface in image/backend.go:

type imageBackend interface {
    ....
    ImagesPrune(pruneFilters filters.Args) (*types.ImagesPruneReport, error)
}

and, there is an implementation in daemon/prune.go:

func (daemon *Daemon) ImagesPrune(pruneFilters filters.Args) (*types.ImagesPruneReport, error) {
    ... implementation details ...
}

Does this mean it's correct to say that Daemon implements the imageBackend interface?

Background: I'm trying to understand how calling docker system prune cmd invokes the ImagesPrune function in daemon.go. I could trace the code flow as:

cli/../system/prune.go -> cli/../prune/prune.go -> cli/../image/prune.go -> client/image_prune.go -> api/server/..image/image_routes.go -> api/server/../image/backend.go -----> ??? ----> daemon/prune.go

I don't know what comes in the ??? section above.

Yes, Daemon does implement the imageBackend interface (as pointed out in the comments, it's actually the *Daemon type that implements the interface). All of imageBackend's methods are implemented in various source code files inside the daemon package (mostly the image_*.go ones).

In the image_routes.go the postImagesPrune method is called, which in turn calls the ImagesPrune method of s.backend. s is a pointer to the instance of imageRouter.

type imageRouter struct {
    backend Backend
    decoder httputils.ContainerDecoder
    routes  []router.Route
}

This imageRouter instance is initialized with backend set to an instance of Daemon in cmd/dockerd/daemon.go here.

So when s.backend.ImagesPrune is called, it is running the ImagesPrune method of the Docker Daemon, which as you point out above is in daemon/prune.go.