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

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 My starting point is the debian buster based Python:3 image adding a couple of python specific configurations and then using the commands in the R project documentation for installing R on

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

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

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/" >>

Lauren, here?s my Dockerfile I use to build r-base from the repos, it builds on both Arm64 (Mac with Apple M2 chip) and Amd64 (AWS m5.4xlarge instance running Ubuntu 24.04). I rebuilt the docker image this morning and it builds fine with R 4.4.1 The last RUN is for installing a bit of custom configuration as well as the base of Bio Conductor. Hope this helps (I also have a Dockerfile for

Hi Marco, Thank you for the follow up email. In the line below, do I replace $(lsb-release -cs) with jammy (Ubuntu 22.04) or leave it alone: Add-apt-repository ?deb https://cloud.r-project.org/bin/linux/ubuntu jammy-cran40/? It?s good to know about installations for Bioconductor. I am not currently using it, but I may need it in the future for other projects. Br, Lauren -- Lauren J. Gerber

Lauren, little oversight from my Dockerfile, if you want to follow the CRAN steps and get the R from the cloud.r-project.org server, you want to replace && add-apt-repository -y "ppa:marutter/rrutter4.0" With && add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" The ppa repo is Michael Rutter personal repo

Yes, keep the $(lsb-release -cs) there. This allows you to change the version of the OS without having to change anything else (for instance we are migrating all of our docker to 24.04 LTS right now, so we only have to modify the FROM entry and all of our Dockerfile will still work). From: Gerber, Lauren J <lauren.gerber at helsinki.fi> Date: Thursday, July 11, 2024 at 2:21?AM To:

Lauren, I am now back home where looking into these things is a little easier. From your first email to me, I started off with the selenium container you mentioned as your starting point. And that basically is your issue. It is a 'high-level' container, and it sets a user. (Essentially) all other Dockerfiles you have seen and been pointed at are 'lower-level' and operate as root

Hi Dirk, Thank you so much for looking into this when you got home. I greatly appreciate it. I was actually in the midst of writing to everyone the following message: ?. ?. ?. Hi All, I have some good news. ? My docker image is now up-to-date with R version 4.4.1. I first had to clear a bunch of unused data using docker system prune ?force. Apparently, it cleared over 32.53 gigs of data, and

Hi All, I am building a Docker image that uses Ubuntu 22.04 and am having issues installing the latest version of R (R 4.4.1). The current R version is 4.1.2: :/# apt-cache policy r-base-core r-base-core: Installed: 4.1.2-1ubuntu2 Candidate: 4.1.2-1ubuntu2 Version table: *** 4.1.2-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100

Hi Dirk and Marco, I need to test some of the suggested solutions and circle back here. Thank you so much for your help. Br, Lauren -- Lauren J. Gerber Bioinformatician Precision Systems Medicine (Kallioniemi) Research Group iCAN ? Digital Precision Cancer Medicine Flagship Institute for Molecular Medicine Finland (FIMM) Nordic EMBL Partnership for Molecular Medicine Biomedicum Helsinki 2U,

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

No sure why you?re doubting me but if one would like the minimal Dockerfile following the CRAN recommendations at https://cloud.r-project.org/bin/linux/ubuntu/, one would simply do FROM ubuntu:22.04 USER root ENV DEBIAN_FRONTEND noninteractive ## Configure Ubuntu for R install RUN apt update \ && apt install -y --no-install-recommends \ software-properties-common \ gnupg2 \

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

On 8 July 2024 at 19:32, marcoblanchette at icloud.com wrote: | Oh, again, sorry for the spam but the problem Lauren is seeing is when she is | trying to sign the key. Installing gnugpg usually takes care of that problem. I am not sure about that. For jammy, my current (and used) rocker/r2u:jammy Dockerfile is https://github.com/rocker-org/r2u/blob/master/jammy/Dockerfile and it does what

Oh, again, sorry for the spam but the problem Lauren is seeing is when she is trying to sign the key. Installing gnugpg usually takes care of that problem. From: marcoblanchette at icloud.com <marcoblanchette at icloud.com> Date: Monday, July 8, 2024 at 12:26?PM To: Dirk Eddelbuettel <edd at debian.org> Cc: Gerber, Lauren J <lauren.gerber at helsinki.fi>, r-sig-debian at

Am Freitag, 5. Juni 2020, 20:04:48 CEST schrieb Dirk Eddelbuettel: > 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

On Wed, 4 Mar 2020 16:56:02 -0500 Alfred von Campe <alfred at von-campe.com> wrote: > 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 >