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:> Dave, > > That's partial information for so hard to work with. One nice aspects about > Docker is that if something complex fails, you can try something simpler. > You appear to have made some assumptions here as to whether you could pile > our instructions top on an existing python3 container---and "that depends". > Your error messages indicate 'buster' as a release, which is not what I use > in for the Rocker r-base container. So you can't just copy and paste. You > could however look at Johannes backport to buster, add its repo into to > your Docker setup and build that. And you can test that step by step. > Good luck! > > Cheers, Dirk
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 update Debian's R to 4.0.2 this morning, I also updated the (base) Rocker container giving you R 4.0.2 easily. The error, if any, and as I see it, is with Dave who assumed one can blindly mix distros, releases and whatnot. He appears to have started from buster and then copied and pasted my Dockerfile "recipe" which a) assumes testing and b) allows itself to pull brandew R (as today) from unstable. This is getting off topic here. In essence Dave just needs a patient Docker tutor. Sadly I don't have time for that right now -- sorry! Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
Am Montag, 22. Juni 2020, 20:06:18 CEST schrieb Dirk Eddelbuettel:> 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....> > This is getting off topic here. In essence Dave just needs a patient Docker > tutor.or maybe using conventional installations may be less complex, ironically... Johannes> Sadly I don't have time for that right now -- sorry!> > Dirk
My base is python with R being installed. Thanks to Dirk's message I found an error message saying debian unstable has been added a number of times to my etc/apt/sources.list file. Now I'm trying to find that file and get it edited back to "normal". Dave On Mon, Jun 22, 2020 at 10:37 AM Johannes Ranke <johannes.ranke at jrwb.de> wrote:> 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: > > Dave, > > > > That's partial information for so hard to work with. One nice aspects > about > > Docker is that if something complex fails, you can try something simpler. > > You appear to have made some assumptions here as to whether you could > pile > > our instructions top on an existing python3 container---and "that > depends". > > Your error messages indicate 'buster' as a release, which is not what I > use > > in for the Rocker r-base container. So you can't just copy and paste. > You > > could however look at Johannes backport to buster, add its repo into to > > your Docker setup and build that. And you can test that step by step. > > Good luck! > > > > Cheers, Dirk > > > >[[alternative HTML version deleted]]