search for: dockerfiles

On Fri, 29 Jan 2016 06:31, Keith Keller <kkeller at ...> wrote: > On 2016-01-29, reynierpm at gmail.com <reynierpm at gmail.com> wrote: >> >> I am building a Dockerfile and I am setting up MariaDB repos as follow: > > This question is probably way offtopic for a CentOS mailing list. > >> # Setup MariaDB repos >> RUN touch

I am building a Dockerfile and I am setting up MariaDB repos as follow: # Setup MariaDB repos RUN touch /etc/yum.repos.d/MariaDB.repo I should write this inside the MariaDB.repo file: [mariadb] name = MariaDB baseurl = http://yum.mariadb.org/5.5/centos6-amd64 gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1 What's the right way to do this? The one below? echo

...as been > | educational for me. If someone wants to change my starting point to > | something that already has stable/latest production for debian, Python3 > and > | R4 and will be updated for the future I would appreciate the head start. > > Should be easy. Look at the variety of Dockerfiles is maintain inside the > Rocker Project -- while most are based on Debian's testing release you can > still look at them (though note that some are also Ubuntu based) > > You could start at https://github.com/rocker-org/rocker but also look at > other repositories in the same o...

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

On 2016-01-29, reynierpm at gmail.com <reynierpm at gmail.com> wrote: > I am building a Dockerfile and I am setting up MariaDB repos as follow: This question is probably way offtopic for a CentOS mailing list. > # Setup MariaDB repos > RUN touch /etc/yum.repos.d/MariaDB.repo > > What's the right way to do this? The one below? > > echo "[mariadb]" >>

Lauren, On 15 October 2024 at 13:51, Gerber, Lauren J wrote: | I just tried fixing my script and added library(BiocManager) before library | (ggbreak), then rebuilt the image, and am still getting the same error. You need _two_ distinct commands. First install.packages("BiocManager") and second once that is done use it to install 'ggbreak' from BioConductor

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

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

...y (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 fresh ubuntu, > no R packages pre-installed > docker pull registry.gitlab.com/jangorecki/dockerfiles/r-devel > https://gitlab.com/jangorecki/dockerfiles/-/raw/master/r-devel/Dockerfile > On Sat, Jun 27, 2020 at 12:37 AM Jan Gorecki <j.gorecki at wit.edu.pl> wrote: >> >> Hi R developers, >> >> On R-devel (2020-06-24 r78746) I am getting those two new exception...

...nts to change my starting point to > > | something that already has stable/latest production for debian, Python3 > > > > and > > > > | R4 and will be updated for the future I would appreciate the head start. > > > > Should be easy. Look at the variety of Dockerfiles is maintain inside the > > Rocker Project -- while most are based on Debian's testing release you can > > still look at them (though note that some are also Ubuntu based) > > > > You could start at https://github.com/rocker-org/rocker but also look at > > other...

...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 -- so you need to inject 'sudo' calls. Otherwise it really is 'just' getting one key and adding one repo, but it helps to have had the same user <-> root issues before ... So below is a working ...

...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 -- so you need to inject 'sudo' calls. Otherwise it really is 'just' getting one key and adding one repo, but it helps to have had the same user <-> root issues before ... So below is a working ...

...-inventing the wheel, which has been | educational for me. If someone wants to change my starting point to | something that already has stable/latest production for debian, Python3 and | R4 and will be updated for the future I would appreciate the head start. Should be easy. Look at the variety of Dockerfiles is maintain inside the Rocker Project -- while most are based on Debian's testing release you can still look at them (though note that some are also Ubuntu based) You could start at https://github.com/rocker-org/rocker but also look at other repositories in the same org at GH. Dirk -- htt...

...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 -- so you need to inject 'sudo' calls. Otherwise it really is 'just' getting one key and adding one repo, but it helps to have had the same user <-> root issues before ... So below is a working ...

...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 -- so you need to inject 'sudo' calls. Otherwise it really is 'just' getting one key and adding one repo, but it helps to have had the same user <-> root issues before ... So below is a working ...

...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 -- so you need to inject 'sudo' calls. Otherwise it really is 'just' getting one key and adding one repo, but it helps to have had the same user <-> root issues before ... So below is a working ...

Hi R developers, On R-devel (2020-06-24 r78746) I am getting those two new exceptions during R check. I found a change which eventually may be related https://github.com/wch/r-source/commit/69de92b9fb1b7f2a7c8d1394b8d56050881a5465 I think this may be a regression. I grep'ed package manuals and R code for unique.default but don't see any. Usage section of the unique method looks fine as

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

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 \

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,