-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qemu driver failed to load image from local filesystem #518
Comments
Thanks for the report. I'm curious if this is a side effect of running with Vagrant because the file is mounted from the host rather than copied, so there is an extra level of indirection. I have had difficulty with linking to files like this in the past. My guess:
The other possibility is that this is weird because of a double-link problem (maybe trying to hardlink a symlink) where:
I think to fix this we should link directly to the file on disk instead of using the alloc dir indirection. |
@cbednarski Unfortunately, it doesn't work even if I put image to the # Job stderr
qemu-system-x86_64: -drive file=/tmp/NomadClient719297766/ccef0b8f-86a0-31b6-5254-fd7bd683c682/debian-image/local/debian-hurd-20150320.img: could not open disk image /tmp/NomadClient719297766/ccef0b8f-86a0-31b6-5254-fd7bd683c682/debian-image/local/debian-hurd-20150320.img: Could not open '/tmp/NomadClient719297766/ccef0b8f-86a0-31b6-5254-fd7bd683c682/debian-image/local/debian-hurd-20150320.img': No such file or directory However, this file exists and it is accessible from chroot:
|
The file is being linked into the chroot, so I wonder if the Qemu driver is On Fri, Dec 4, 2015 at 12:57 PM, Mikhail Zholobov [email protected]
|
Same here on bare metal. job stderr:
|
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version: 0.2.1
OS: Ubuntu 14.04 x64 (running as Vagrant VM in Parallels Desktop on OS X 10.11 host)
Symptoms
Nomad fails to run qemu job if "artifact_source" is pointing to the local file. Symlink is created, but seems like it is not available for nomad job running in chroot.
Job configuration:
Nomad run output:
Nomad agent output:
Job stderr
Actually, image file exists, but it is a symlink:
The text was updated successfully, but these errors were encountered: