# Web-only - do I need a separate image for each container?

**URL:** <https://meta.discourse.org/t/web-only-do-i-need-a-separate-image-for-each-container/294549>\
**Category:** Self-hosting\
**Created:** [February 7, 2024, 2:51pm UTC](https://meta.discourse.org/t/web-only-do-i-need-a-separate-image-for-each-container/294549 "2024-02-07T14:51:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lejeczek](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@lejeczek](https://meta.discourse.org/u/lejeczek)\
**Post date:** [February 7, 2024, 7:17pm UTC](https://meta.discourse.org/t/web-only-do-i-need-a-separate-image-for-each-container/294549/3 "2024-02-07T19:17:18Z")

</div>

Thanks for taking time, for trying, however.. it’s not what I’m asking.  
I’ll try again, pardon me if I fail.. again  
When I:  
 → $ ./launcher bootstrap a.forum.xyz # or similar  
then process creates:

```plaintext
-> $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
local_discourse/a.forum.xyz latest d7a7b6509811 2 hours ago 4.19GB

```

and that happens with each & every _launcher_ ran for a different/new forum.  
So I end up with multiple image of the same **discourse** - is it only me & result should be different?  
If not just me & that is desired & expected result, then that is - sure I am not devel and have no knowledge of the process(es) involved - rather really extremely wasteful (perhaps particularly with **web-only** container) - no?

What I was hoping for - when first tried discourse - what I expected was, pretty much what everything else, every other software which is _dockerized_ does, namely - get that one image and run many containers off it. Is **discourse** not cap/able of doing that?

---

_[View the full topic](https://meta.discourse.org/t/web-only-do-i-need-a-separate-image-for-each-container/294549)._