Pass channel_priority strict to conda with repo2docker


I saw Interplay of conda-forge/broken channel and the channel ordering `strict` · Issue #731 · jupyterhub/repo2docker · GitHub about the default “channel_priority” setting for repo2docker, but I was wondering if there is also a way to pass the setting for a specific repository (e.g. by adding a .condarc, or some other configuration file); the reason is to work around this issue: Compilation of C++ programs in conda-forge environments is broken on some platforms · Issue #1505 · conda-forge/ · GitHub).

Thanks in advance!


I managed to work around the issue by running repo2docker locally, with the patch from Use the `strict` config option for conda by ocefpaf · Pull Request #714 · jupyterhub/repo2docker · GitHub</titl applied, but if there is a solution that works with the Github action that’d still be more convenient :slight_smile:

1 Like