-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rawrr::buildRawrrExe() fails #71
Comments
Hi @SamThilmany, I am unfortunately not to familiar with building docker containers. Does the location Have you ever tried to install rawrr in a bioc docker container? https://www.bioconductor.org/help/docker/ Does it show the same behaviour? Sorry for the many question. Best, |
The mono project homepage shows some basic tests for the mono compiler https://www.mono-project.com/docs/getting-started/mono-basics/ |
I think it would be nice to develop a recipe for |
Hi @tobiasko, Given that In this updated environment, |
Maybe it would even make sense to publish your docker image on docker hub? A container image based on Debian Bookworm might be interesting for people that don't like the bioconductor containers for some reason. |
The bioc containers incl. stuff like RStudio server, which is of course a cool thing for people that depend on an IDE, but there is for sure also people how prefer a stripped down minimal image. |
I have created a Docker container based on
rocker/r2u
for my statistical analyses. Unfortunately,rawrr
is not included in the pool ofr2u
packages and therefore has to be installed manually.I have attempted to do so both in the Dockerfile and in the terminal of the finished container and failed in both cases. The
rawrr
package can be installed, but therawrr::buildRawrrExe()
process fails. According to the error message, a log file was stored under/root/.cache/R/rawrr/rawrrassembly/rawrr_build.log.*
, but this file does not exist.Here is the full error message:
Do you know what the problem might be?
Dockerfile
docker-compose.yml
The text was updated successfully, but these errors were encountered: