# Is there an existing trame-slicer docker image?

**URL:** <https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481>\
**Category:** Development\
**Created:** [December 13, 2025, 8:52pm UTC](https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481 "2025-12-13T20:52:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rlhisey](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rlhisey](https://discourse.slicer.org/u/rlhisey)\
**Post date:** [December 13, 2025, 8:52pm UTC](https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481/1 "2025-12-13T20:52:50Z")

</div>

Hi, I’m looking for a way to create a basic Slicer application on the web using trame-slicer. Ideally, I think I’d like to run it in a docker container to make it somewhat portable. Is there an existing, recommended docker image that I could base my application on? I know there is a trame image but I believe that trame-slicer requires the slicer python interpreter. Sorry I’m fairly new to all of this

---

<div class="post-metadata">

**Author:** ![Thibault\_Pelletier](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/thibault_pelletier/32/4767_2.png) [@Thibault\_Pelletier](https://discourse.slicer.org/u/Thibault_Pelletier)\
**Post date:** [December 14, 2025, 9:18am UTC](https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481/2 "2025-12-14T09:18:21Z")

</div>

Hi @rlhisey,

There is no official trame-slicer docker image yet, but there is an open [draft PR](https://github.com/KitwareMedical/trame-slicer/pull/23) open on the subject to have a minimal dockerfile recipe to get people started on the deployment.

The docker image doesn’t rely on the Slicer environment but on the VTK MRML wheel which corresponds to the core 3D Slicer classes and compiled for Python 3.10 on Windows and Linux x64.

These wheels are compatible with deployment for cloud / k8s and desktop apps using PyInstaller / Tauri.

What kind of application are you looking to build?

Best,  
Thibault

---

<div class="post-metadata">

**Author:** ![rlhisey](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rlhisey](https://discourse.slicer.org/u/rlhisey)\
**Post date:** [December 14, 2025, 7:49pm UTC](https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481/3 "2025-12-14T19:49:58Z")

</div>

Thanks! Right now I’m just doing some investigation to see if it’s possible to run some basic Slicer functionality through a web interface mostly for my own learning. I’ll start with the docker file you’ve mentioned.

---

<div class="post-metadata">

**Author:** ![rlhisey](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rlhisey](https://discourse.slicer.org/u/rlhisey)\
**Post date:** [December 17, 2025, 2:41am UTC](https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481/4 "2025-12-17T02:41:54Z")

</div>

I took a look at the dockerfile PR mentioned above and running the medical\_viewer example throws `ImportError: cannot import name ‘vtkMRMLLayerDMObjectEventObserverScripted’ from ‘slicer’ (/usr/local/lib/python3.10/site-packages/slicer/ **init**.py)` I know the PR is still in draft so I may need to do some additional debugging, just wondering if there is something obvious I’m missing.

---

<div class="post-metadata">

**Author:** ![Thibault\_Pelletier](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/thibault_pelletier/32/4767_2.png) [@Thibault\_Pelletier](https://discourse.slicer.org/u/Thibault_Pelletier)\
**Post date:** [December 19, 2025, 7:07am UTC](https://discourse.slicer.org/t/is-there-an-existing-trame-slicer-docker-image/45481/5 "2025-12-19T07:07:20Z")

</div>

Hi @rlhisey,

This problem is likely due to an outdated vtk-mrml wheel being installed. Make sure you’re using the latest in the Docker image which [should be this one.](https://github.com/KitwareMedical/trame-slicer/releases/download/v1.4.0/vtk_mrml-9.4.0-cp310-cp310-manylinux_2_35_x86_64.whl)