Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Handling yum_requirements.txt in the new Docker image

See original GitHub issue

Currently it appears there is no sudo in the new Docker image. So installing packages with yum is problematic (e.g. using yum_requirements.txt). How would we like to address this?

xref: https://github.com/conda-forge/openspecfun-feedstock/pull/2 ref: https://circleci.com/gh/conda-forge/openspecfun-feedstock/6

Issue Analytics

State:
Created 5 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

3reactions

jakirkhamcommented, Sep 17, 2018

Ok, is there a PR to fix that bug?

@CJ-Wright, answering over here to keep things easy to follow. Hope that is ok.

There is PR ( https://github.com/conda-forge/docker-images/pull/64 ), which would add a Docker image based on our existing one with devtoolset removed. We would need to make a minor changes to get it to build on CI and deploy. Some refactoring would also simplify the changeset, but could be dealt with orthogonally. There is a question about how that Docker image should be named as well. It should be relatively simple to switch the image used in conda-smithy.

0reactions

jakirkhamcommented, Oct 13, 2018

Added PR ( https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/135 ), which will switch us over to the condaforge/linux-anvil-comp7 Docker image for the new compiler rebuilds.