Marc Bihlmaier

@juanluisbaptiste Did you push that to anywhere? Seems the images 6.0.37 and 6.0.40 still have this error. ~~Idea: what about copying `${OTRS_ROOT}/current_version` to `${OTRS_CONFIG_DIR}/current_version` if this does not exist?~~ ~~I...

Here are the logs of the container after adding ``` $Self->{"Loader::Enabled::JS"} = 0; ``` ``` k -n znuny-production logs app-0 | grep 404 10.244.7.142 - - [27/May/2022:09:42:14 +0000] "GET /favicon.ico...

Upgrade `image: "juanluisbaptiste/otrs:6.0.28"` -> `"juanluisbaptiste/otrs:6.0.37"` seems to be ok

~~I had read that before, but with~~ ~~> Upgrade is successful only if I manually create a file "current_version" in volume mounted to /opt/otrs/Kernel/ and put information about current version...

Update: Upgrade from `6.0.37` to `6.0.40` (with the files existing like above) does also result in the jquery-errors.

Upgrade from `juanluisbaptiste/otrs:6.0.37` to `juanluisbaptiste/znuny:latest`also results in the jquery-errors. So https://github.com/juanluisbaptiste/docker-otrs/commit/96fe6926b319c052f7cb9b7b788d84cef4851176 does not seem to fix this.

@juanluisbaptiste Can you tell me what you want me to test exactly? Actually we are running `juanluisbaptiste/otrs:6.0.37` in production. Maybe I've copied the files manually, I do not remember ......

> I just pushed an updated 6.0.40 image. from https://github.com/juanluisbaptiste/docker-otrs/issues/118#issuecomment-1143098042 That was the information I was missing... Ok, I am going to test that tag next week, probably on Monday.

Hallo, I am still running `juanluisbaptiste/otrs:6.0.28` - Can the Znuy image be used for production already? - Are there any migration steps to be noticed? Thanks for your great work!

@juanluisbaptiste ok, thanks