# Moved VTK webassembly SDK docker image to new kitware/vtk-wasm-sdk
**URL:** https://discourse.vtk.org/t/moved-vtk-webassembly-sdk-docker-image-to-new-kitware-vtk-wasm-sdk/13542
**Category:** Announcements
**Created:** [March 14, 2024, 10:02pm UTC](https://discourse.vtk.org/t/moved-vtk-webassembly-sdk-docker-image-to-new-kitware-vtk-wasm-sdk/13542 "2024-03-14T22:02:56Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@jaswantp](https://discourse.vtk.org/u/jaswantp)
#### Post date: [March 14, 2024, 10:02pm UTC](https://discourse.vtk.org/t/moved-vtk-webassembly-sdk-docker-image-to-new-kitware-vtk-wasm-sdk/13542/1 "2024-03-14T22:02:56Z")
The [vtk-wasm-sdk](https://gitlab.kitware.com/vtk/vtk-wasm-sdk) CI will now publish webassembly builds of VTK in [kitware/vtk-wasm-sdk](https://hub.docker.com/r/kitware/vtk-wasm-sdk). The older [kitware/vtk-wasm](https://hub.docker.com/r/kitware/vtk-wasm-sdk) docker repo is no longer maintained.
There seems to be no clean way of deprecating/archiving docker images. [docker/hub-feedback#907](https://github.com/docker/hub-feedback/issues/907), [opencontainers/image-spec!902](https://github.com/opencontainers/image-spec/pull/903). So I’ve resorted to publishing an empty image that displays a warning message.
If you do `docker run kitware/vtk-wasm:latest`, it will just print a warning message and fail to build your project.
```shell
$ docker run --rm kitware/vtk-wasm:latest
WARNING: This image is no longer maintained. Please use https://hub.docker.com/r/kitware/vtk-wasm-sdk instead.
```
If you extended the `kitware/vtk-wasm` image, I’m afraid there’s no way to know until you actually run a command like `cmake` or `ninja` as they do not exist in that image.
---
### Author:  [@jaswantp](https://discourse.vtk.org/u/jaswantp)
#### Post date: [March 14, 2024, 10:06pm UTC](https://discourse.vtk.org/t/moved-vtk-webassembly-sdk-docker-image-to-new-kitware-vtk-wasm-sdk/13542/2 "2024-03-14T22:06:19Z")
We will also update the `Overview` section in dockerhub to point to the new repository.