Using ./?/.ivy2 when given working directory parameter

[aladagemre]

I ran into an strange issue, I don't have time to replicate with a minimal example but I wanted to drop a line.

When given -w="..." working directory parameter, it's using $WORKING_DIRECTORY/?/.ivy2, not the mounted /home/user/.ivy2:/root/.ivy2 volume.

By the way, ? is real question mark. I don't know whether this is a Docker bug or a sbt bug.

It seems that using bash -c "cd $WORKING_DIRECTORY; sbt dist" doesn't work either.

Instead, providing ivy2 path manually works:

sbt -ivy /root/.ivy2 dist

[santtu]

I ran into this, and thought to provide pointers here for anyone finding this issue.

This is caused by not having an entry in passwd for the UID that SBT is running under. SBT apparently looks for "~" directory via getent and not from $HOME environmental variable. Thus the solution is to make sure the container where SBT is being run has an user entry (e.g. useradd).

Since passwd will by default have entry for UID 0 (root), this problem does not usually show up. It is only manifested when the docker run -u option is used to explicitly define the uid, and that uid does not exist in the container's passwd file.