Sametime 12.x Duplicate Wasm in Container Image

Mindwatering Incorporated

Author: Tripp W Black

Created: 11/05 at 09:40 PM

 

Category:
Domino Troubleshooting
Sametime

Issue:


Sametime 12.0.4 having an issue with the LE acme.sh renewal. However, it is hard to read and find the error with 1000s of this error filling up the logs:

$ podman-compose logs nginx --since 10m
. . .
[warn] 696#696: duplicate extension "wasm", content type: "application/wasm",
previous content type: "application/wasm" in /config/nginx/nginx.conf:57
. . .

So we took a tangent to get some smaller logs ...


Resolution:


None; nothing permanent as a consumer of an image.

Important:
- The extra line is built into the image. To actually fix requires the source image provider (HCL) to update their image.
- We can update the file and reload nginx task running within the st1204_nginx_1 container; but, the change will be lost with the next podman-compose down command
- This is just a workaround so we can see the rest of the logs.

1. Verify WASM only listed once in nginx.conf and remove it:
a. Login:
$ ssh sametime.mindwatering.net
<enter pwd if not private key>

b. Locate the line (57) in the nginx.conf:
$ cd /home/myadminid/st1204/sametime-config/web/nginx/
$ sudo vi nginx.conf
<confirm only in the file once>

Note:
- The mime type is already included in mime.types in the nginx:alpine-slim image.

c. Remove application/wasm from types section in nginx examples or comment them out:
$ sudo vi nginx.conf
. . .
include /etc/nginx/mime.types;
types {
# add support for wasm MIME type, that is required by specification and it is not part of default mime.types file
# 2026/11/05 MW TB - this mime type already in nginx:alpine-slim image used by containers - commented out
# application/wasm wasm;
. . .
<esc>:wq (to save)

2. Restart the Nginx within its container:
a. Confirm container name for st1204_nginx_1:
$ sudo postman ps
<view list>

b. Issue the command:
$ podman exec -it st1204_nginx_1 nginx -s reload




previous page

×