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

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

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

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 >

On 09/03/2018 11:05 AM, Stefan G. Weichinger via samba wrote: > Am 03.09.18 um 15:12 schrieb Robert Marcano via samba: >> On 09/03/2018 04:10 AM, Stefan G. Weichinger via samba wrote: >>> >>> As I am learning docker lately I came to the idea of using a docker >>> container as a "fallback" DC at sites where there is no budget (or >>>

Am 03.09.18 um 17:21 schrieb Robert Marcano: > On 09/03/2018 11:05 AM, Stefan G. Weichinger via samba wrote: >> great, thanks! Which docker image do you use as base image? > > Sent to you a copy of this email with an attachment of the Dockerfile > needed to build the container image. There are two Dockerfile there, one > for Fedora (extremely experimental Samba package there,

Hi, In the samba 4.18.5 source, while installing pre-requisite packages using boothstrap.sh file, in the same folder, I saw the Dockerfile. Can I safely assume that the Samba AD can actually run in Docker? -- Thanks & Regards, Raghav DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to Exzatech Consulting And Services Pvt. Ltd., Bangalore,

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

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

Hello, It seems the official Docker images are missing some important security updates [1][2]. Does anyone have any insight in how these packages get built and when? Their Dockerfile seems to come from here: https://github.com/docker-library/official-images/blob/master/library/centos (commit for "latest" says "update CentOS-7 - 20160331 - monthly build"). In the official

On Mon, Sep 11, 2017 at 10:56:10PM +0000, Guillermo Bisheimer wrote: > Just wanted to mention that I've published a docker image of tinc 1.1pre15 > for the raspberry pi 2/3. > > It was compiled from source on a raspberry 3 and published as > byscontrol/tinc-rpi <https://hub.docker.com/r/byscontrol/tinc-rpi/> along > witht the configuration instructions. > > The

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

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: > https://cran.r-project.org/bin/linux/debian/#secure-apt > > So far

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