APP_CODE_PATH_HOST is not populating workspace.

[spaceSquid]

Info:

• Docker version ($ docker --version): 18.03.0-ce
• Laradock commit ($ git rev-parse HEAD): a6ed9e3b4e78f8a12c1f32f8841ce018957ce8aa
• System info (Mac, PC, Linux): PC
• System info disto/version: Windows 10 Pro

Issue:

APP_CODE_PATH_HOST is not populating workspace.

---

[spaceSquid]

workspace_1            | *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
workspace_1            | *** Running /etc/my_init.d/10_syslog-ng.init...
workspace_1            | Apr 24 08:40:08 bf76a3954b5e syslog-ng[9]: syslog-ng starting up; version='3.5.6'
workspace_1            | Apr 24 08:40:08 bf76a3954b5e syslog-ng[9]: WARNING: you are using the pipe driver, underlying file is not a FIFO, it should be used by file(); filename='/dev/stdout'
workspace_1            | *** Running /etc/rc.local...

[Dryr]

Do you mean that the volume is not properly set up between the host and the container?

If you run docker-compose exec workspace ls, do you see the files that are contained in the folder pointed by APP_CODE_PATH_HOST?

[Dolaned]

having the same issue

[bcdennis]

Downgrading docker appears to be the solution.

[bradmccormack]

Same here.

$ docker --version
Docker version 18.03.1-ce, build 9ee9f40

[bradmccormack]

For me this was due to the APP_CODE_PATH_HOST having a relative path to the docker-compose file (parent directory). After I updated it to use an absolute path, no more problems.

[mattogodoy]

Same here!
I'm using docker-compose un WSL under Windows 10 Pro
Docker version 18.06.0-ce, build 0ffa825

I tried using absolute paths and no luck either.
Did you solve it, @Sinden ?

[kneipp]

After wasting my time in the last two days, i have found a solution:

In .env file set this PATH:
APP_CODE_PATH_HOST=/d/your-workspace-path/your-project

**
Running Windows 10 18.03?
Create and modify the new WSL configuration file:

sudo vim /etc/wsl.conf
[automount]
root = /
options = "metadata"

Restart your computer and profit!

** Credit: https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly

[pgvctoken]

Old thread but... When this happens to me it is because Docker cannot access the Shared Drives. I fix it by
right clicking Docker,
Click Settings,
Click Shared Drives,
Uncheck C Drive,
Click Apply,
Check C Drive,
Click Apply,
provide credentials,

bring up the container and workspace is populated. Of course, I forget this every time and spend hours figuring it out again.

[Ablegang]

I also have this problem

[stale]

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

[stale]

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.