make import-osm fails with Docker Toolbox for Windows

[zstadler]

make import-osm fails with Docker Toolbox for Windows.

Failure log:

...
docker-compose run --rm -u $(id -u ${USER}):$(id -g ${USER}) import-osm
Importing in normal mode
[Apr  9 09:09:44] IO error: /cache/coords: Invalid argument
Makefile:108: recipe for target 'import-osm' failed
make: *** [import-osm] Error 1

To reproduce:

make download-geofabrik area=northamptonshire
rm -fr cache
make import-osm

Workaround:

The following changes need to be reverted.

1. Restore the run of import-osm as root.

   diff --git a/Makefile b/Makefile
   index 729b04c..d9bee7e 100644
   --- a/Makefile
   +++ b/Makefile
   @@ -105,7 +105,7 @@ psql: db-start
   
    .PHONY: import-osm
    import-osm: db-start all
   -       docker-compose run $(DC_OPTS) import-osm
   +       docker-compose run import-osm
   
    .PHONY: import-sql
    import-sql: db-start all

2. Restore the use of an anonymous volume for cache.

   diff --git a/docker-compose.yml b/docker-compose.yml
   index 41087d4..176a15e 100644
   --- a/docker-compose.yml
   +++ b/docker-compose.yml
   @@ -1,6 +1,7 @@
    version: "2"
    volumes:
      pgdata:
   +  cache:
    services:
      postgres:
    image: "openmaptiles/postgis:${TOOLS_VERSION}"
   @@ -36,7 +37,7 @@ services:
    volumes:
      - ./data:/import
      - ./build:/mapping
   -      - ./cache:/cache
   +      - cache:/cache
      import-osm-diff:
    image: "openmaptiles/import-osm:${TOOLS_VERSION}"
    env_file: .env
   @@ -48,7 +49,7 @@ services:
    volumes:
      - ./data:/import
      - ./build:/mapping
   -      - ./cache:/cache
   +      - cache:/cache
      update-osm:
    image: "openmaptiles/import-osm:${TOOLS_VERSION}"
    env_file: .env
   @@ -60,7 +61,7 @@ services:
    volumes:
      - ./data:/import
      - ./build:/mapping
   -      - ./cache:/cache
   +      - cache:/cache
      openmaptiles-tools:
    image: "openmaptiles/openmaptiles-tools:${TOOLS_VERSION}"
    env_file: .env

[nyurik]

@zstadler we specifically made sure that all docker images can run without the root access. Running as root creates all local files as root as well, requiring sudo to delete them. Lets try to figure out how it can run safely on Windows too without requiring sudo for everyone.

[zstadler]

@nyurik, The above is my capture of the issue and the only solution I have found.
How would you like to proceed?

[nyurik]

So there are two changes you have here -- using volumes instead of local dirs, and removing -u param. Are you sure you need both? Would sharing the local dir instead of a full volume work?

[zstadler]

The problem is that imposm fails to write to the mounted directory in either user mode or as root.
imposm succeeds only when (1) a Docker named volume is used for the imposm cache and (2) the imposm tasks are run as root.