search

brikis98 / docker-osx-dev

A productive development environment with Docker on OS X
http://www.ybrikman.com/writing/2015/05/19/docker-osx-dev/
MIT License
1.43k stars 106 forks source link

Error when trying to init docker-osx-dev #202

Open xmarston opened 7 years ago

xmarston commented 7 years ago

I have installed it successfully following the installation steps but now when I want to initialize it in the folder I want to sync with my docker container I get this error:

2017-04-14 12:31:23 [INFO] Complete list of paths to sync: 
2017-04-14 12:31:23 [INFO] Using default exclude paths: .git
2017-04-14 12:31:23 [INFO] Complete list of paths to exclude: .git
2017-04-14 12:31:23 [INFO] Complete list of paths to include: 
2017-04-14 12:31:23 [INFO] Starting docker-osx-dev file syncing
2017-04-14 12:31:24 [INFO] Installing rsync in the Docker Host image
2017-04-14 12:31:24 [INFO] Performing initial sync of paths: 
2017-04-14 12:31:24 [DEBUG] Creating parent directories in Docker VM: sudo mkdir -p  && sudo chown -R docker 
BusyBox v1.24.2 (2016-05-16 13:28:30 UTC) multi-call binary.

Usage: mkdir [OPTIONS] DIRECTORY...

Create DIRECTORY

    -m MODE Mode
    -p  No error if exists; make parent directories as needed
error in run: exit status 1

Is there anything I can do to fix this?

brikis98 commented 7 years ago

Why does it say BusyBox? It seems like the wrong binary is being called...

What command(s) did you run?

Also, can you set the log level to DEBUG so we can see more info?

docker-osx-dev --log-level DEBUG
merongivian commented 7 years ago

having the same error, i get this when i run the DEBUG option:

2017-05-11 13:53:41 [DEBUG] Creating parent directories in Docker VM: sudo mkdir -p && sudo chown -R docker

slightlytyler commented 7 years ago

I ran into this issue when installing while I had Docker for mac running. Shut it down, re-installed, and it worked. Not sure if it's just a problem with the daemon or something totally not related

victorpedrocs commented 6 years ago

I'm having this same issue. I believe it has something to do with the script that loads the paths to sync.

As you can see, on the first line of the log:

2017-04-14 12:31:23 [INFO] Complete list of paths to sync:

The list of paths to sync is empty. In my case, it's not reading the list of paths to sync from the docker-compose.yml file.

mre commented 4 years ago

Linking #147 with a possible fix.