Docker App Mount Mac And Often

Sometimes the whole build piped work fine, sometimes itd fail on the last step. 50,000 ft view, the process looks like docker build -v (coderoot):containerpath:delegated.

The shell doesnt have timestamps but this log is over a period of 2mins.

RUN apk -U add --no-cache tzdata git curl wget perl perl-dev libressl libressl-dev make gcc libc-dev zlib-dev.

Ill keep poking it at my end and see if I can make it reliably break but for me just by creating a new container and working for a while.

As with the example, even sitting at the shell will eventually trigger it.

In our case, calls to Pythons os.path.abspath() fail with OSError: Errno 2 No such file or directory.

That method calls os.getcwdu() internally, which is basically a pwd call.) But if we put that call in a loop, sleeping for a second and retrying each time, it suddenly starts working after 30 seconds or so.

The loop isnt starting until the container has already been running for 15-30 seconds, so it seems like its sometimes taking about a minute after container startup for pwd to start working in mounted volumes.

Even recreating the directory will not allow the shell to recover and so may cause this strange situation where the pwd of the shell exists but the shells actual working directory does not.

I believe this is the case regardless of file system or configuration (i.e.

If youre having this difficulty with a shell, you can try cd pwd.

If that fixes the issue, its almost certainly due to a behind-the-scenes removal and recreation.

If youre seeing this issue with other software, it may be due to removalrecreation and a race between different processesthreads.

If youre interested in debugging it in situ, I recommend looking for places where directory removal or recursive removal occurs.

I can imagine scenarios like make clean all where this could happen consistently and sometimes development containers could be unaware.

I went quite a while without it occurring after making those changes, but it just happened again this morning, and I needed to restart macOS as usual to get it working again.

I am running multiple containers, and when it occurs in any container, there is a a chance where next command i execute in any other container throws the same error.

Stale issues will be closed after an additional 30d of inactivity.

Think Ive seen comments you shouldnt do that as it can lead to unpredictable results.

Sometimes it will even create the.aws in the directory in your source code directory on the host (e.g.

I couldnt say w 100 confidence, just because I work in some containers that have that fix and some that dont.

Think Im doing it this way just based on posts I read or official language Dockerfiles that did it that mount it to when I set it up way back.

I assume that once you start using the COMPOSEPROJECTNAME environment variable you have to keep using it or you would run into this issue.

Docker App Mount Mac And Often

This getcwd issue happened only on Mac and often hindered out development experience.

Sometimes the whole build piped work fine, sometimes itd fail on the last step.

Docker For Mac App Mount