Closed scarf005 closed 2 weeks ago
the Docker stuff came in some years ago as an external contribution. not sure who we have internally who is able to troubleshoot, possibly @hamzaremmal could help or has an idea of who else we could ask?
Mmh, I remember using docker-compose a few weeks ago (or maybe it was for docs.scala-lang 😅) but I remember it working fine. I will take a look at this on my flight back tomorrow.
While not related to the failure, it seems removing the version
statement at the beginning of the compose file would remove one of the warnings and probably avoid a future failure.
Whole not related to the failure, it seems removing the
version
statement at the beginning of the compose file would remove one of the warnings and probably avoid a future failure.
created https://github.com/scala/scala-lang/pull/1679 for this
Whole not related to the failure, it seems removing the
version
statement at the beginning of the compose file would remove one of the warnings and probably avoid a future failure.
The version
field is obsolete for quite some time now, @Philippus thanks for the PR.
I've tried to run the docker-compose command locally after rebuilding the image and removing all the previous containers and images and everything works fine. I will play around a little bit with it to attempt to reproduce the observed behaviour. Since it's a permission issue, @scarf005 does you user have anything special configured ?
not sure but maybe the docker compose
command i ran and docker-compose
from README might behave differently (i think docker-compose is outdated)
interesting, completely removing all references to UID and GID fixed it. it works in both rootless mode and regular docker. both generated output aren't created as root but as host user.
rootless | root |
---|---|
will open a PR.
To reproduce
https://github.com/scala/scala-lang/blob/decdf224af060f9e89350be909146d73d1f7f4e1/README.md?plain=1#L30-L32
Log
despite following the exact step from README, I got:
System info