Closed denhartog closed 5 years ago
What is the engine
set to in your boxfile.yml
?
engine: pythong; which of course is invalid. I thought it was curious nanobox even tried to proceed with a non-existent engine. Regardless, "cloning" should be "clone" and is a nanobox thing rather than a particular engine.
@denhartog Engines can be pulled from anywhere, not just from the Nanobox engine repos. However, if a single-word engine name is provided, it assumes nanobox-io/nanobox-engine-<name>
on github. But you can also use a local engine:
run.config:
engine: ../some-local-dir
or a custom engine on github:
run.config:
engine: ghuser/custom-repo
In regards to the wording of the error message, FAILED TO
is generic text for all messages CLONING ...
is the step that failed. So while the verbiage of the error message sounds incorrect, the context may explain why.
All the same; thanks for the explanation. Excited to explore nanobox.io more!
"FAILED TO CLONING" should be singular "CLONE"
ON failure: nanobox run
Setting up directories and permissions... - Cloning engine :
! FAILED TO CLONING HTTPS://GITHUB.COM/NANOBOX-IO/NANOBOX-ENGINE-PYTHONG.GIT !