moby: mountpoint not found when building docker

Hi

I cloned docker master and run make command, error “mountpoint not found” came up. What should I do the pass the building. Here are the logs

docker$ git branch
* master

and docker daemon output

~$ sudo docker -d
2014/06/10 16:13:15 WARNING: You are running linux kernel version 3.2.0-4-amd64, which might be unstable running docker. Please upgrade your kernel to 3.8.0.
2014/06/10 16:13:15 docker daemon: 0.11.1 fb99f99; execdriver: native; graphdriver:
[59d5d416] +job serveapi(unix:///var/run/docker.sock)
[59d5d416] +job initserver()
[59d5d416.initserver()] Creating server
2014/06/10 16:13:15 Listening for HTTP on unix (/var/run/docker.sock)
[59d5d416] +job init_networkdriver()
[59d5d416] -job init_networkdriver() = OK (0)
2014/06/10 16:13:15 WARNING: mountpoint not found
Loading containers: ..............: done.
[59d5d416.initserver()] Creating pidfile
[59d5d416.initserver()] Setting up signal traps
[59d5d416] -job initserver() = OK (0)
[59d5d416] +job acceptconnections()
[59d5d416] -job acceptconnections() = OK (0)
2014/06/10 16:13:22 POST /build?rm=1&t=docker%3Amaster
[59d5d416] +job build()
[59d5d416] +job allocate_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b)
[59d5d416] -job allocate_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b) = OK (0)
[error] container.go:455 Error running container: mountpoint not found
[59d5d416] +job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b)
[59d5d416] -job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b) = OK (0)
[59d5d416] +job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b)
[59d5d416] -job release_interface(f47543c8ad8786747c5ac51a6248ade060ddea65db155341e3a89cb262ea944b) = OK (0)
mountpoint not found
[59d5d416] -job build() = ERR (1)

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 20 (6 by maintainers)

Most upvoted comments

Came across the same issue, Reboot fixed them