# Session configuration

**URL:** <https://renku.discourse.group/t/session-configuration/888>\
**Category:** RenkuLab\
**Created:** [21 August 2023 15:45 UTC](https://renku.discourse.group/t/session-configuration/888 "2023-08-21T15:45:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![carloferrigno](https://avatars.discourse-cdn.com/v4/letter/c/779978/32.png) [@carloferrigno](https://renku.discourse.group/u/carloferrigno)\
**Post date:** [21 August 2023 15:45 UTC](https://renku.discourse.group/t/session-configuration/888/1 "2023-08-21T15:45:11Z")

</div>

Hello, after the platform update, I see this message

The session cannot be configured exactly as requested for this project. You can still start one, but some things may not work correctly.

In my project

> **[Reproducible Data Science | Open Research | Renku](https://renkulab.io/projects/carlo.ferrigno/ppanda-light)**
>
> Work together on data science projects reproducibly. Share code, data and computational environments whilst accessing free computing resources.

which is linked from a published paper

> **[Energy-resolved pulse profiles of accreting pulsars: Diagnostic tools for...](https://www.aanda.org/component/article?access=doi&doi=10.1051%2F0004-6361%2F202347062)**
>
> Astronomy & Astrophysics (A&A) is an international journal which publishes papers on all aspects of astronomy and astrophysics

but I have no idea of what is the issue, any clue?

---

<div class="post-metadata">

**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://renku.discourse.group/u/lorenzo)\
**Post date:** [21 August 2023 16:25 UTC](https://renku.discourse.group/t/session-configuration/888/2 "2023-08-21T16:25:42Z")

</div>

Hello,

You should see that message when you define [session settings](https://renkulab.io/projects/carlo.ferrigno/ppanda-light/settings/sessions) that are unavailable.  
Actually, it seems that your requirements work well with the available session classes; I suspect something should be tuned on our side. I’m checking this and I’ll get back to you soon.  
In the meantime, do you mind sharing a screenshot of what you see [on this page](http://renkulab.io/projects/carlo.ferrigno/ppanda-light/sessions/new) (the whole page, even split into multiple images if it’s too big for the screen)? That will help us to be sure you see the proper classes.

> **[Reproducible Data Science | Open Research | Renku](https://renkulab.io/projects/carlo.ferrigno/ppanda-light/sessions/new)**
>
> Work together on data science projects reproducibly. Share code, data and computational environments whilst accessing free computing resources.

---

<div class="post-metadata">

**Author:** ![carloferrigno](https://avatars.discourse-cdn.com/v4/letter/c/779978/32.png) [@carloferrigno](https://renku.discourse.group/u/carloferrigno)\
**Post date:** [21 August 2023 16:56 UTC](https://renku.discourse.group/t/session-configuration/888/3 "2023-08-21T16:56:00Z")

</div>

Hi,

thanks.  
I copy below the screenshot, hope you see it.

I made a push today and it failed building.  
See:  
[https://gitlab.renkulab.io/carlo.ferrigno/ppanda-light/-/jobs/658035](https://gitlab.renkulab.io/carlo.ferrigno/ppanda-light/-/jobs/658035)

On my local clone, I issued  
renku session start  
and asked to build, but it failled since the renku update. Before, it was working.

It fails when using requirement and environment as on [renkulab.io](http://renkulab.io), but I cannot debug what is wrong without more verbose logging. How can I get it?

Curiously, the building with  
docker build .  
does not stop at the same point, so it is something mysteriously linked to renku

Bests,

Carlo

 ![](https://global.discourse-cdn.com/free1/uploads/renku/original/1X/05cbc156220ed9d131c02cce07794d393c40499f.png)

---

<div class="post-metadata">

**Author:** ![tolevski](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/tolevski/32/137_2.png) [@tolevski](https://renku.discourse.group/u/tolevski)\
**Post date:** [22 August 2023 07:58 UTC](https://renku.discourse.group/t/session-configuration/888/4 "2023-08-22T07:58:34Z")

</div>

Hi @carloferrigno our image builders have been flagged by Anaconda and have been blocked because (as we recently found out) you need a license to use it at the scale we do with Renku. We are trying to get an academic license but that may take some time.

Until then and going forward you can simply remove the `defaults` channel from your `environment.yaml` file and replace it with `conda-forge`. `conda-forge` is more open and does not have the same terms of service as anaconda’s defaults channel. So simply by doing that change you will be able to get your images to build.

We have seen this occur across several projects. We will make an announcement with an explanation and steps to remedy this on the general discourse so that it is more visible and reaches more users.

---

<div class="post-metadata">

**Author:** ![lorenzo](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@lorenzo](https://renku.discourse.group/u/lorenzo)\
**Post date:** [22 August 2023 09:31 UTC](https://renku.discourse.group/t/session-configuration/888/5 "2023-08-22T09:31:47Z")

</div>

@carloferrigno here is the post with instructions to fix the problem with building images, as already mentioned by @tolevski

> [@snake Addressing issues with Renku image builders](https://renku.discourse.group/t/addressing-issues-with-renku-image-builders/892):
>
> warning Issue: we have observed issues across multiple projects when building Renku images using conda with the defaults channel supported by [Anaconda.com](http://anaconda.com/)hammer_and_wrench Solution: we recommend Renku users to complete the following steps in their projects. Remove defaults channel from the environment.yml file. Add conda-forge channel in the environment.yml file if it is not already there (in the default Renku projects, conda-forge is not there). [environment.yml cannot have defaults, …

For the warning banner, we are fixing it on our side. In short, pinning memory requirements triggers that warning _even if sessions with enough memory are available_. You can safely ignore it for now. The fix should be rolled out within a few days.

Sorry for the inconvenience; sadly, a few things piled up with this release since it brings quite a few changes in many parts of the system.

---

<div class="post-metadata">

**Author:** ![carloferrigno](https://avatars.discourse-cdn.com/v4/letter/c/779978/32.png) [@carloferrigno](https://renku.discourse.group/u/carloferrigno)\
**Post date:** [22 August 2023 09:44 UTC](https://renku.discourse.group/t/session-configuration/888/6 "2023-08-22T09:44:29Z")

</div>

Hi,

thanks, I have made the change in my repository and it worked.

Bests,

Carlo

---

<div class="post-metadata">

**Author:** ![elisabetc](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/elisabetc/32/811_2.png) [@elisabetc](https://renku.discourse.group/u/elisabetc)\
**Post date:** [23 August 2023 07:46 UTC](https://renku.discourse.group/t/session-configuration/888/7 "2023-08-23T07:46:03Z")

</div>

Wonderful @carloferrigno ! Thank you for letting us know.
