# Which docker image to use for production installation (possibly kubernetes)?
**URL:** https://community.wowza.com/t/which-docker-image-to-use-for-production-installation-possibly-kubernetes/102679
**Category:** Wowza Streaming Engine
**Tags:** server-administration
**Created:** [July 2, 2025, 2:08pm UTC](https://community.wowza.com/t/which-docker-image-to-use-for-production-installation-possibly-kubernetes/102679 "2025-07-02T14:08:23Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@cjcolvar](https://community.wowza.com/u/cjcolvar)
#### Post date: [July 2, 2025, 2:08pm UTC](https://community.wowza.com/t/which-docker-image-to-use-for-production-installation-possibly-kubernetes/102679/1 "2025-07-02T14:08:23Z")
There are two docker images for the Wowza Streaming Engine: `wowzamedia/wowza-streaming-engine-linux` is recommended on “Set up Wowza Streaming Engine on the Docker container platform” and `wowza/wowza-streaming-engine` is recommended on “Trial Wowza Streaming Engine using a Docker Compose deployment” . It looks like `wowzamedia/wowza-streaming-engine-linux` has both WSE and the manager running in the same container where they have been split into two distinct containers in the other case. Focusing on just WSE, it appears that the container startup scripts are different between the two and make use of different environment variables. I have a custom module and I like how `wowza/wowza-streaming-engine` will copy in contents of a `lib.addon` directory so I can mount that directory instead of having to mount the whole `lib` directory. Is the only difference between the two images the startup scripts or is there any difference in the application code? Is it okay to use `wowza/wowza-streaming-engine` in a production environment? Which would be better suited for a kubernetes environment?
---
### Author:  [@sayali.talathi](https://community.wowza.com/u/sayali.talathi)
#### Post date: [July 25, 2025, 6:28am UTC](https://community.wowza.com/t/which-docker-image-to-use-for-production-installation-possibly-kubernetes/102679/2 "2025-07-25T06:28:26Z")
For most production or single-container setups, we recommend using **`wowzamedia/wowza-streaming-engine-linux`**. It runs both the Wowza Streaming Engine and the Manager in the **same container** , making it easier to manage and deploy — ideal for standard use cases.
The **`wowza/wowza-streaming-engine`** image is more suited for **trial, Docker Compose, or Kubernetes** environments. It separates the Engine and Manager into different containers, offering more modularity but requiring additional configuration.
As for using `wowza/wowza-streaming-engine` in **production** , it’s technically possible, but just keep in mind that it’s not the image we actively recommend or test for production scenarios — that would be the `-linux` one.
For **Kubernetes** , though, the separate-container approach of `wowza/wowza-streaming-engine` can be more flexible if you’re trying to follow microservice-style patterns — but you might need to tweak the Dockerfiles or compose setup a bit to make it more production-ready.