`DOCKER_BUILDKIT=1` is only needed for some older versions of Docker.
The Dockerfile knows two build time arguments (`--build-arg`), `MMCIF_USER_ID` and `ADD_DEV`. The latter is only used for developing the app. `MMCIF_USER_ID` sets the ID of the user running the translation script inside the Docker container. So files written by the Docker container belong to the user ID of the internal user. When you run into file permission issues with the produced ModelCIF files, build the Docker container using your own user ID:
<aname="builduserid"></a>The Dockerfile knows two build time arguments (`--build-arg`), `MMCIF_USER_ID` and `ADD_DEV`. The latter is only used for developing the app. `MMCIF_USER_ID` sets the ID of the user running the translation script inside the Docker container. So files written by the Docker container belong to the user ID of the internal user. When you run into file permission issues with the produced ModelCIF files, build the Docker container using your own user ID:
```terminal
$DOCKER_BUILDKIT=1 docker build --build-argMMCIF_USER_ID=<YOUR USER ID> -t registry.scicore.unibas.ch/schwede/ma-wilkins-import/converter:latest .
...
...
@@ -153,13 +153,11 @@ If `--rank` is omitted, all models in the project's directory are converted.
## Troubleshooting
<!--
- file permissions
- build with your user ID
-->
### File permission problems
Depending on your local user/ permissions setup, it may happen that either the Docker container cannot read or write the project directories. Otherwise, it can happen that files written by the app, are not readable for you on your local file system. This can be solved by building the Docker container with the same user ID as the local user executing the app. This is described [here](#builduserid)