similar to: Issues with Ubuntu 22.04 and Installing the Latest Version of R (R 4.4.1) to Docker Image

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

Thanks! ?"jammy" made it work. ? For some reason, ?lsb_release -cs is returning "victoria" rather than "jammy", and $> sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:2 http://packages.linuxmint.com victoria InRelease Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Hit:4 http://packages.linuxmint.com victoria

I just upgraded from Linux Mint 20 to 21 and am no longer able to add the CRAN Ubuntu repository to my list of repositories. ?I am getting: $> sudo /usr/bin/add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" $> sudo apt update Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy

On Mon, 04 Dec 2023 13:41:47 -0500 Steve Gutreuter <sgutreuter at gmail.com> wrote: > $> sudo /usr/bin/add-apt-repository "deb > https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release > -cs)-cran40/" Looks like `lsb_release -cs` returns a Mint codename for you. Thankfully, since we know that Linux Mint 21 is based on Ubuntu 22.04 "Jammy Jellyfish", it

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

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, 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

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 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,

05.12.2023 17:21, Joachim Lindenberg via samba: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > Dec 05 12:48:39 cobra samba[749]:

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

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

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

Hi, I apologise for the naiveness of this question, but I experienced an error when running apt-get update on Debian 9. It’s telling me that it can’t update the xiph repository. Not sure if I should be asking for help about this here, but if not… please let me know where I should take this issue. Any help is appreciated. Damian Get:1 http://security.debian.org/debian-security stretch/updates

Over a week ago (on r-help, my bad!) I raised a question of why the ubuntu install instructions https://cran.r-project.org/bin/linux/ubuntu/README.html instruct users with a xenial-based system to use deb https://cloud.r-project.org/bin/linux/ubuntu xenial-cran40/ Looking at https://cloud.r-project.org/bin/linux/ubuntu/ there is no xenial-cran40 directory. However,

I'm running Debian/Jessie on a server which is used as an AD DC. I'm getting errors like this: Hit http://ftp.ca.debian.org jessie InRelease Hit http://ftp.ca.debian.org jessie/main Sources Hit http://ftp.ca.debian.org jessie/main amd64 Packages Hit http://ftp.ca.debian.org jessie/main Translation-en Err http://ftp3.nrc.ca jessie InRelease Err http://ftp3.nrc.ca jessie-updates InRelease

Still something wrong. I've uncommented the deb-src lines in sources.list as you suggested (and I thought it couldn't hurt to try --allow-unauthenticated as well) and: root at limpet:/etc/apt# apt-get update --allow-unauthenticated Hit:1 http://nz.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://repo.steampowered.com/steam precise InRelease Hit:3

Dear Robin and Tomas, By changing the CC, I'm hereby trying to move this to R-SIG-Debian (Ubuntu a flavor of Debian) where it belongs ... Martin >>>>> robin hankin >>>>> on Fri, 1 Mar 2019 21:43:07 +1300 writes: > Still something wrong. I've uncommented the deb-src lines in > sources.list as you suggested (and I thought it

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