Miniconda runtime image in common properties list does not have curl installed
See original GitHub issue{
--
2 | "display_name": "Miniconda Python 3.x",
3 | "metadata": {
4 | "image_name": "continuumio/miniconda3:latest"
5 | },
6 | "schema_name": "runtime-image"
7 | }
This image will fail when used since we are dependent on curl being available on all runtime images used with elyra. Also we should update the image tags to use a pinned version instead of latest
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Installation issues · Issue #88 · NVIDIA/MinkowskiEngine
Hi! I've tried to install MinkowskiEngine via pip and have had different issues on every machine I've tried. To try isolate this install...
Read more >Using the RUN instruction in a Dockerfile with 'source' does ...
Original Answer. FROM ubuntu:14.04 RUN rm /bin/sh && ln -s /bin/bash /bin/sh. This should work for every Ubuntu docker base image. I generally...
Read more >Solutions to common problems - Synopsys Detect
Solution. If the curl command described above does not successfully return a value for property DETECT_LATEST, you must determine why, and make the...
Read more >Configure images on the fly when loading images into ... - GitLab
DEBIAN_FRONTEND=noninteractive apt-get install --assume-yes curl software-properties-common ca-certificates openssl Reading package lists.
Read more >Defining metadata (meta.yaml)
The lower case name of the package. It may contain "-", but no spaces. package: name: bsdiff4 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Concur with @kevin-bates, we already have anaconda working fine, so I am fine dropping miniconda. And BTW, this has not been on a release yet.
We could avoid maintaining our own image if we can find a comparable replacement and just re-use the
miniconda.json
filename. Then that image will appear as a default (after an install).Have we confirmed that
pip install elrya
overwrites the data_files we also deliver? If it doesn’t and since uninstall doesn’t remove them (AFAIK), would a subsequentpip install elyra
be a means of working around that?