Skip to content
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

Cannot run: share includes invalid characters #651

Open
mbrodala opened this issue Mar 2, 2018 · 1 comment
Open

Cannot run: share includes invalid characters #651

mbrodala opened this issue Mar 2, 2018 · 1 comment

Comments

@mbrodala
Copy link
Contributor

mbrodala commented Mar 2, 2018

Given this repository I get an error with nanobox run php test.php on Shippable:

nanobox run php test.php 20s  
Preparing environment :

--------------------------------------------------------------------------------
+ HEADS UP:
+ This is the first build for this project and will take longer than usual.
+ Future builds will pull from the cache and will be much faster.
--------------------------------------------------------------------------------


Building runtime :
  Pulling nanobox/build image :
    
     
     Downloading layer  1/1: 0 B/0 B  0% 
     ...
     Downloading layer  3/3: 100.34 MB/102.89 MB 97% 
     Extracting layer  3/3:  0%
     ...
     Extracting layer  3/3: 100%  Starting docker container :

Error   : Error response from daemon: create ~/.nanobox/share/b9a6246fcf1a1521794c00040328cf77/engine: "~/.nanobox/share/b9a6246fcf1a1521794c00040328cf77/engine" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path
Context : failed to build the code -> failed to start docker container

If you look at the Job node info of the linked build you'll see that this is Docker 17.06.0-ce on a Ubuntu 14.04.5 LTS.

Any idea what's wrong?

(And yes, technically it is possible now to use Nanobox on Shippable, see Shippable/support#3696)

@danhunsaker
Copy link
Contributor

Looks like it's not expanding ~ into /home/user correctly. Not sure where that's being set (output of pwd?), but that'll need fixing to get this working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants