# GLSL shaders use non supported version 1.50 that makes CI/CD to fail in a docker container

**URL:** <https://discourse.slicer.org/t/glsl-shaders-use-non-supported-version-1-50-that-makes-ci-cd-to-fail-in-a-docker-container/8307>\
**Category:** Development\
**Tags:** extensions-manager, nightlybuild, docker, testing\
**Created:** [September 5, 2019, 10:35am UTC](https://discourse.slicer.org/t/glsl-shaders-use-non-supported-version-1-50-that-makes-ci-cd-to-fail-in-a-docker-container/8307 "2019-09-05T10:35:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [September 5, 2019, 10:35am UTC](https://discourse.slicer.org/t/glsl-shaders-use-non-supported-version-1-50-that-makes-ci-cd-to-fail-in-a-docker-container/8307/1 "2019-09-05T10:35:40Z")

</div>

@lassoan, @cpinter, we are trying to test our extension in a docker container as described by @unnmdnwb3 in [this](https://discourse.slicer.org/t/docker-image-for-nightly-master/) thread.

However, the test fails when executing slicer with [these](https://gitlab.com/BishopWolf/dosimetry4d/-/jobs/288261429) errors.

Basically the VTK version that is used enforces the use of GLSL version 1.50 which is unsopported by the opengl libraries. Is there any way to change VTK version while creating the slicer container? Which is the recommended version of VTK that does not have this problem? I can’t see this enforcement in VTK 8.2 for instance.

---

<div class="post-metadata">

**Author:** ![Alex\_Vergara](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/alex_vergara/32/15205_2.png) [@Alex\_Vergara](https://discourse.slicer.org/u/Alex_Vergara)\
**Post date:** [September 5, 2019, 12:34pm UTC](https://discourse.slicer.org/t/glsl-shaders-use-non-supported-version-1-50-that-makes-ci-cd-to-fail-in-a-docker-container/8307/2 "2019-09-05T12:34:31Z")

</div>

This is a quick view of the error for those interested but with no access to the project yet

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/b/3/b3a27ecabe5967d659d48ee579495151c7338f17.png)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [September 5, 2019, 12:47pm UTC](https://discourse.slicer.org/t/glsl-shaders-use-non-supported-version-1-50-that-makes-ci-cd-to-fail-in-a-docker-container/8307/3 "2019-09-05T12:47:26Z")

</div>

There are several docker container examples where appropriate OpenGL version is configured. See for example this topic:

> [@Workflow with Docker and Slicer](https://discourse.slicer.org/t/workflow-with-docker-and-slicer/4091):
>
> Hi, I’am a scientist and working with Slicer build inside a docker image but I want make some upgrade in a workflow and add SlicerJupyter extension. I have a dream that I am preparing a docker image for my friends in team. In last few days I did some research about your solution with docker but I got lost in this topic. What need I to create a dream workflow: Create docker image with build version Slicer Qt5 (always need builded version because I working with own extensions Build and install …