Importing from different directory than where import file in causes server name to include all folder names

[dolan-a]

If I import in the following manner: machine-import home/myfiles/machine1.zip, in .docker/machine/machines, the folders home/myfiles/machine1 are created.

I initially thought the problem was as described in #6 since this was a server with no docker machines yet, but I used the mkdir command mentioned there, and still got an error about config.json not existing. But in my case, it was saying it didn't exist in ".docker/machine/machines/home".

The workaround was to just cd to the directory (e.g. home/myfiles) before running machine-import.

[burnedikt]

Faced the exact same problem today. Fix should be easy enough by just taking the actual filename (without the preceding path) in https://github.com/bhurlow/machine-share/blob/master/import.js#L29