Unable to use non-interactive session for conda_builder_linux
Closed this issue · 2 comments
Hi,
First off, thanks for your patience, ContinuumIO folk. I'm aware I open a lot of issues.
Second, I've been trying to get continuumio/conda_builder_linux:latest
working in non-interactive mode, to no avail. It appears to skip whatever command I enter. For example
docker run continuumio/conda_builder_linux:latest echo foo
Outputs
WARNING: No ABI default set. Falling back to compatibility mode with GCC 4.
Welcome to the conda-builder image, brought to you by Continuum Analytics.
Binaries produced with this image should be compatible with any Linux OS
that is at least CentOS 5 or newer (Glibc lower bound), and anything
that uses G++ 5.2 or older (libstdc++ upper bound)
GCC is: gcc (GCC) 5.2.0
Default C++ ABI: 4 (C++98)
GLIBC is: glibc 2.5
ld/binutils is: GNU ld (GNU Binutils) 2.26.20160125
Native arch is x86_64. To build 32-bit code, set the ARCH environment
variable to 32. (-e "ARCH=32" docker argument)
The dev user (currently signed in) has passwordless sudo access.
miniconda (2.7) is installed at /opt/miniconda.
git is also available.
Helpful aliases:
clone_recipes: clones the conda/conda-recipes repo from Github
clone_anaconda: clones the continuumIO/anaconda (private) repo from Github
anaconda_setup: clones anaconda repo and sets up continuum internal build system.
(Note the lack of a 'foo').
If I use
./start_cpp11_32.sh echo foo # or ./docker_wrapper.sh echo foo
I get
Unable to find image 'echo:latest' locally
docker: Error response from daemon: pull access denied for echo, repository does not exist or may require 'docker login'.
See 'docker run --help'.
If I try
./docker_wrapper.sh continuumio/conda_builder_linux:latest echo foo
I enter interactive mode.
Lastly, if I try to work around the issue by piping a command in, it does not have access to the environment variables set by internal_startup.sh
echo 'which conda' | docker run -i continuumio/conda_builder_linux:latest
WARNING: No ABI default set. Falling back to compatibility mode with GCC 4.
Welcome to the conda-builder image, brought to you by Continuum Analytics.
Binaries produced with this image should be compatible with any Linux OS
that is at least CentOS 5 or newer (Glibc lower bound), and anything
that uses G++ 5.2 or older (libstdc++ upper bound)
GCC is: gcc (GCC) 5.2.0
Default C++ ABI: 4 (C++98)
GLIBC is: glibc 2.5
ld/binutils is: GNU ld (GNU Binutils) 2.26.20160125
Native arch is x86_64. To build 32-bit code, set the ARCH environment
variable to 32. (-e "ARCH=32" docker argument)
The dev user (currently signed in) has passwordless sudo access.
miniconda (2.7) is installed at /opt/miniconda.
git is also available.
Helpful aliases:
clone_recipes: clones the conda/conda-recipes repo from Github
clone_anaconda: clones the continuumIO/anaconda (private) repo from Github
anaconda_setup: clones anaconda repo and sets up continuum internal build system.
which: no conda in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
Thanks for your time,
Sean
Sorry, these images are really old and should be considered deprecated. We now use compiler packages instead. I'd avoid these docker images if I were you. Do you have any suggestions for how we can indicate that they probably should not be used?
Docs on the new compilers is at https://conda.io/docs/user-guide/tasks/build-packages/compiler-tools.html
Whoops, my mistake. Sorry for the time!
I would probably update the readme to have a big, bold "this image is deprecated" sort of bit 😃