Dave is there a specific reason you want to install both in one container?
It is somewhat antithetical to the purpose of docker if you don't have a
direct need.
Also, it sounds like you are making your own python base image when you
probably want to use a lightweight python image instead and just add layers
to the image.
But I totally get it if your intent is to learn or you want to build one
just for some specific application or for fun.
On Wed, Jun 24, 2020 at 4:15 PM Dave Lange <umbrellahouse at gmail.com>
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
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 Buster. I got slightly different
answers when I used apt versus apt-get. There were warnings about
unverified sources solved by a reference to the certificate key.
It turns out building the python container and commenting the R commands
out allowed me to manually step through my dockerfile lines. Its
repeatable
that the R install fails with the error above when in the dockerfile.
Running the commands manually allows the installation to finish
successfully. I sense that docker is multithreaded and hits the "use
buster-cran40" before it defines buster-cran40. Manually stepping through
the commands keeps the preferred order. At this point I'm happy with a
repeatable process.
It sounds like I have been re-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.
Thanks for the volunteer support I have received here.
Dave Lange
Kenmore, WA
[[alternative HTML version deleted]]