Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

(windows) nanobox fails to 'run' complaining about a missing boxfile which is actually there #550

Open
shie-erlich opened this issue Aug 26, 2017 · 2 comments

Comments

@shie-erlich
Copy link

i'm running 'nanobox run' on windows (virtualbox). here is my folder content:

C:\Users\XXX\src\graymatter>dir
Volume in drive C has no label.
Volume Serial Number is B05D-D93E

Directory of C:\Users\XXX\src\

08/26/2017 11:30 AM

.
08/26/2017 11:30 AM ..
08/26/2017 11:13 AM 1,265 .gitignore
08/26/2017 11:13 AM .idea
08/26/2017 11:13 AM 2,435 application.py
08/26/2017 11:13 AM 238 boxfile.yml
08/26/2017 11:13 AM brain
08/26/2017 11:13 AM etc
08/26/2017 11:13 AM 12 README.md
08/26/2017 11:13 AM 68 requirements.txt

however, nanobox complains:

Building runtime :
Starting docker container :
Preparing environment for build :
- Copying ssh keys into the build environment...
- Setting up directories and permissions...

:::::::::::::::::::::::::::::::::::::::::::::::::::::::: MISSING BOXFILE.YML !!!

Nanobox is looking for a boxfile.yml config file. You might want to
check out our getting-started guide on configuring your app:

https://guides.nanobox.io/

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Error : failed to execute hook (fetch) on c36d97eea87ed81d5bb2cf513c595f45a7b0360151e81010d7647a3ae1b0e546: util:Exec:/opt/nanobox/hooks/fetch: bad exit code(1):
Context : failed to build the code -> failed to run the (build)fetch hook

@glinton
Copy link
Contributor

glinton commented Aug 29, 2017

I've seen this before when there were mount issues. It failed to properly mount the code in. If this is still happening, can you provide information requested in this comment.

Also, for sanity, can you please paste the output of nanobox version and nanobox config ls.

If this is still an issue, you could try nanobox config set mount-type native and run again. As obvious from that linked issue, we have had little support debugging this issue.

@glinton
Copy link
Contributor

glinton commented Aug 29, 2017

Duplicate of /issues/423

@glinton glinton marked this as a duplicate of #423 Aug 29, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants