Closed royfrancis closed 1 year ago
Are you sure that you are not running out of disk space?
As far as I can see, there is plenty of disk space. Even if it was the disk space, the regular install.packages()
command works immediately after.
Pak uses more disk space because it has a cache and it creates a binary package first.
It's a new laptop and there is more than a TB of space. I am hoping the docker container I am running has access to all that. I haven't defined any restrictions.
What OS do you have on the host? Ie on the laptop itself?
It's a MacBook Pro M2.
aarch64-apple-darwin20.0.0 (64-bit)
macOS Ventura 13.4.1
Then Docket does not have access to that space. You can see the amount of empty space and you can also make it bigger in the Docker dashboard. And/or you can run 'docker system prune' to remove unused images and containers.
If this does not work then can you please share your Dockerfile?
Interesting! So, I looked into disk usage and it was by default set to 64GB. But only 43GB of 64GB was used. So, it probably shouldn't be limiting. Anyhow, I increased it to 200GB. Restarted docker and the container and tried the installation again. Same error! I will put together a Dockerfile that I can share.
Tried again with a new Dockerfile, image and container and it works!
It would be good to know why the first file didn't work. Do you think you can share that?
Getting this error with some packages. As an example;
It works with
install.packages()
.Running in RStudio Server in a docker container.
RStudio Server 2023.03.0 Build 386