# Paraviewweb docker issue

**URL:** https://discourse.paraview.org/t/paraviewweb-docker-issue/13090
**Category:** Web Support
**Created:** [October 24, 2023, 2:25pm UTC](https://discourse.paraview.org/t/paraviewweb-docker-issue/13090 "2023-10-24T14:25:59Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![scottm](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/65b543/32.png) [@scottm](https://discourse.paraview.org/u/scottm)
#### Post date: [October 24, 2023, 2:25pm UTC](https://discourse.paraview.org/t/paraviewweb-docker-issue/13090/1 "2023-10-24T14:25:59Z")

</div>

Hi,

I am trying to setup paraviewweb inside a docker container. I have followed this tutorial [Kitware/paraviewweb-demo: Website and launcher for ParaViewWeb container demo (github.com)](https://github.com/Kitware/paraviewweb-demo), the osmesa version and using the kitware/paraview:pvw-v5.7.1-osmesa-py3 image.

When I start the container I can see the 4 application (Visualizer, Divvy, Lite and Glance) but if I try and connect to Lite for example I get a “Connection closed before receiving a handshake response” error or for Visualizer & Divvy I get “Session did not start before timeout expired. Check session logs.”

Also I have checked the logs found at

> /pvw/launcher/logs

and they all say the following:

> Presets were imported successfully  
> wslink: Starting factory  
> CRITICAL:twisted:wslink: Starting factory

I have not modified anything yet this happened on a fresh container.

Does anyone know what the issue might be.

Thanks.

---

<div class="post-metadata">

### Author: ![jourdain](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jourdain/32/11_2.png) [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [October 24, 2023, 3:13pm UTC](https://discourse.paraview.org/t/paraviewweb-docker-issue/13090/2 "2023-10-24T15:13:26Z")

</div>

I’m not sure what could be happening. But you may want to use an image younger than four years old.  
I would use a trame based image and setup ParaView 5.11 either by mounting it or bundling it within your image.

HTH,

Seb

---

<div class="post-metadata">

### Author: ![scottm](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/s/65b543/32.png) [@scottm](https://discourse.paraview.org/u/scottm)
#### Post date: [October 25, 2023, 9:44am UTC](https://discourse.paraview.org/t/paraviewweb-docker-issue/13090/3 "2023-10-25T09:44:41Z")

</div>

Would using the Trame docker image still allow me to use Paraview-lite through a launcher config?

---

<div class="post-metadata">

### Author: ![jourdain](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jourdain/32/11_2.png) [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [October 25, 2023, 4:59pm UTC](https://discourse.paraview.org/t/paraviewweb-docker-issue/13090/4 "2023-10-25T16:59:10Z")

</div>

yes, the core infrastructure is exactly the same