similar to: Update on docker Python:3 and adding R:4.x

My dockerfile: FROM python:3 WORKDIR /usr/src/app COPY requirements.txt ./ COPY languageserver-master ./ COPY radian-master ./ RUN pip3 install --no-cache-dir -r requirements.txt EXPOSE 8080 RUN apt-key adv --keyserver keys.gnupg.net --recv-key 'E19F5F87128899B192B1A2C2AD5F960A256A04AF' RUN echo "deb http://cloud.r-project.org/bin/linux/debian buster-cran40/" >>

Am Donnerstag, 25. Juni 2020, 04:52:37 CEST schrieb Dave Lange: > My dockerfile: > ... > RUN apt update \ > && apt-get install -y --no-install-recommends \ > ca-certificates \ > wget \ > && rm -rf /var/lib/apt/lists/* Any reason why you remove the contents of /var/lib/apt/lists? On my system, this directory holds PGP signed information about each

On 24 June 2020 at 15:15, Dave Lange wrote: | I continue to receive an error installing R via dockerfile on a buster | image python:3. | E: The value 'buster-cran40' is invalid for APT::Default-Release as such a | release is not available in the sources Do you have the Dockerfile in public repo we can look at? | My starting point is the debian buster based Python:3 image adding a couple

Count me as a docker newbie building a debian python and R mytools container. My first post. This was working a couple of weeks ago. My last successful build was a R 4.01 release when the R:base docker hub project used to list a number of base images and I used sections of a posted docker file in that area. Then the install directions at Cran:R listed buster:4.01 instructions that I also added to

I want to build a couple of containers by function instead of replicating even slim images for every single package. My current base image provides an updated debian and python3 image. Dave Lange Kenmore, WA On Wed, Jun 24, 2020 at 3:18 PM Sean Southard <sean.m.southard at gmail.com> wrote: > Dave is there a specific reason you want to install both in one container? > > It is

Hi Dave and Dirk, sorry, I do not understand half of this, as I do not use docker myself. Buf if Dirk does not use Debian buster as the basis for his Rocker container, then you should probably not try to install the backport to buster. Shouldn't these docker containers be there to avoid the need to install R? Johannes Am Montag, 22. Juni 2020, 19:15:56 CEST schrieb Dirk Eddelbuettel:

Hi: I have a Dockerfile, which builds an image which installed R 3.3.2 in Ubuntu 14.04, but building using that Dockerfile seems to have stopped working and I am unclear why. I believe the relevant error is: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet

On 22 June 2020 at 19:37, Johannes Ranke wrote: | sorry, I do not understand half of this, as I do not use docker myself. Buf if | Dirk does not use Debian buster as the basis for his Rocker container, then | you should probably not try to install the backport to buster. Shouldn't these | docker containers be there to avoid the need to install R? That is what they do, and do well! After I

On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net> wrote: > Winston, > I had a similar experience to you tracking down an insanely difficult bug > in my R code that "disappeared" whenever slight changes were made to the > script (e.g. like adding cat() statements). In my case, it coincided with > my over-eager compilation of R and its

On 28 March 2020 at 14:04, Robin Lovelace wrote: | To the list this time... | | On Sat, Mar 28, 2020 at 2:03 PM Robin Lovelace <rob00x at gmail.com> wrote: | | > Hi Dirk, | > | > Thanks for the quick response. | > | > I've updated the draft post following your suggestions, see the updated | > version, in nice .md format, here: | >

Dear list, I've drafted an article on installing geographic R packages on Linux computers and would appreciate any feedback. Is the following text correct, useful and future-proof?: R?s spatial packages can be installed from source on recent (since Ubuntu 19.04) versions of this popular operating system, once the appropriate repository has been set-up, meaning faster install times (only a

On 3/28/20 10:04 AM, Robin Lovelace wrote: > To the list this time... > > On Sat, Mar 28, 2020 at 2:03 PM Robin Lovelace <rob00x at gmail.com> wrote: > >> Hi Dirk, >> >> Thanks for the quick response. >> >> I've updated the draft post following your suggestions, see the updated >> version, in nice .md format, here: >>

On 5 June 2020 at 08:52, Johannes Ranke wrote: | Hi Mark, | | Am Freitag, 5. Juni 2020, 00:31:34 CEST schrieb Mark van der Loo: | > Hi all, | > | > I just spun up a fresh Debian Buster instance, then I added: | > | > deb http://cloud.r-project.org/bin/linux/debian buster-cran40/ | > | > to /etc/apt/sources.list. I also ran the apt-key command as described here: | >

Hi all, I just spun up a fresh Debian Buster instance, then I added: deb http://cloud.r-project.org/bin/linux/debian buster-cran40/ to /etc/apt/sources.list. I also ran the apt-key command as described here: https://cran.r-project.org/bin/linux/debian/#secure-apt So far so good, now when I do the following, I get no joy: $ sudo apt-get install r-base Reading package lists... Done Building

One of my packages is slated to be archived from CRAN due to failures when the ATLAS BLAS is used. I am unable to replicate the error on my machine under R 3.6.1 using the atlas library from ubuntu (seems to be 3.10.2-9, while the good professor is using 3.10.3 per https://www.stats.ox.ac.uk/pub/bdr/Rblas/README.txt ). I also tried the rocker/r-base with R 3.6.2 and

I have a R script that I call from python using rpy2. It uses dplyr, doBy, and ggplot2. The script has install.packages commands for these 3 packages. Even thought the packages are already installed it still downloads, builds, and installs them, which is very time consuming. Is there a way to have it only do the install if the package is not already installed? Also, I run in a docker container,

Hello, I have tried to upgrade R to 4.0. I have added `deb http://cloud.r-project.org/bin/linux/debian buster-cran40/` to `/etc/apt/sources.list` (but I removed cran35). Btu when I run `apt-get update; apt-get install r-base r-base-dev` I get an error. I think it depends on r-base-core, since it depends on these obsolete libraries: ``` $ sudo apt-get install r-base-core Reading package lists...

I have to support a legacy build that runs on CentOS 6. I?m new to Docker and would like to use the official CentOS 6.10 image (https://github.com/CentOS/sig-cloud-instance-images/blob/da050e2fc6c28d8d72d8bf78c49537247b5ddf76/docker/Dockerfile <https://github.com/CentOS/sig-cloud-instance-images/blob/da050e2fc6c28d8d72d8bf78c49537247b5ddf76/docker/Dockerfile>) as a Docker container on

I am working in a Dockerfile but there is a "secure" MariaDB server script I need to run which is interactive and I don't know how to deal with this. Basically this is the flow I have follow on the script at test environment and is the same I want to achieve in the Dockerfile without user interaction by just answering as you seen on the flow below: #

>>>>> Jan Gorecki writes: > So the unique.default is from the R tools package during checks. > I don't see those issues on CRAN checks. I cannot reproduce this locally (and have no clues about docker). Perhaps you can try to debug this on your end? And see what env_list is when the error occurs? Best -k > Exact environment where I am reproducing this issue is a