Great work! This looks really useful, and I'm very glad to see an example to learn from.
I hit an error building the Dev Container in a local VSCode (M1 Mac, in case it matters... I know there are issues with rocker for M1); the build failed at installing tidyverse (somewhere in the dependency chain, possibly systemfonts) due to a missing libfontconfig1-dev. Adding that, on the next build I found I also needed libharfbuzz-dev and libfribidi-dev (for textshaping); plus nloptr needs cmake. Then libfreetype6-dev, libpng-dev, libtiff5-dev, and libjpeg-dv were required. I added those but it failed without a specific error, perhaps at installing some of the custom packages (?). I tried removing a lot more and it built successfully (albeit I can't run the notebook), but I haven't pinpointed which particular inclusion breaks the build. I'll try both on a linux machine later to see if I can reproduce it. In the meantime, I thought this report might help someone else looking to get started.
The use-case here of running a specific tutorial is excellent, but I wonder if there's an even more minimal R+tidyverse+python config that could be a more flexible starting point for others to expand on?
Just for my own understanding - do I understand correctly that devcontainers doesn't address reproducibility or system configuration issues, except in the sense that if it builds successfully on a remote server, it will work the same for everyone using that server at a given point in time (e.g. codespaces). If package versions were strictly managed and the built container was pushed to a container registry, then perhaps those issues would be addressed.
Great work! This looks really useful, and I'm very glad to see an example to learn from.
I hit an error building the Dev Container in a local VSCode (M1 Mac, in case it matters... I know there are issues with rocker for M1); the build failed at installing
tidyverse(somewhere in the dependency chain, possiblysystemfonts) due to a missinglibfontconfig1-dev. Adding that, on the next build I found I also neededlibharfbuzz-devandlibfribidi-dev(fortextshaping); plusnloptrneedscmake. Thenlibfreetype6-dev,libpng-dev,libtiff5-dev, andlibjpeg-dvwere required. I added those but it failed without a specific error, perhaps at installing some of the custom packages (?). I tried removing a lot more and it built successfully (albeit I can't run the notebook), but I haven't pinpointed which particular inclusion breaks the build. I'll try both on a linux machine later to see if I can reproduce it. In the meantime, I thought this report might help someone else looking to get started.The use-case here of running a specific tutorial is excellent, but I wonder if there's an even more minimal R+tidyverse+python config that could be a more flexible starting point for others to expand on?
Just for my own understanding - do I understand correctly that devcontainers doesn't address reproducibility or system configuration issues, except in the sense that if it builds successfully on a remote server, it will work the same for everyone using that server at a given point in time (e.g. codespaces). If package versions were strictly managed and the built container was pushed to a container registry, then perhaps those issues would be addressed.