# Paraview web inside docker container

**URL:** https://discourse.paraview.org/t/paraview-web-inside-docker-container/8136
**Category:** Web Support
**Created:** [October 7, 2021, 8:22am UTC](https://discourse.paraview.org/t/paraview-web-inside-docker-container/8136 "2021-10-07T08:22:57Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Drew\_Lazzeri](https://discourse.paraview.org/user_avatar/discourse.paraview.org/drew_lazzeri/32/7289_2.png) [@Drew\_Lazzeri](https://discourse.paraview.org/u/Drew_Lazzeri)
#### Post date: [October 8, 2021, 9:14pm UTC](https://discourse.paraview.org/t/paraview-web-inside-docker-container/8136/6 "2021-10-08T21:14:33Z")

</div>

Hi Sunag,

I think the simplest path forward would be to use two images, [docker’s storage support](https://docs.docker.com/storage/) to transfer the files between them. One image would be your OpenFOAM simulation, specifying to keep the vtk files outside of docker after it runs. The other would be our provided paraview web image, which will have access to the vtk files with the `-v` volume in the docker run command

```auto
sudo docker run --gpus all \
    -p 0.0.0.0:9000:80 \
    -v ~:/data \
    -e "SERVER_NAME=localhost:9000" \
    -e "PROTOCOL=ws" \
    -ti kitware/paraviewweb:pvw-egl-demo-v5.6.0

```

---

_[View the full topic](https://discourse.paraview.org/t/paraview-web-inside-docker-container/8136)._