Vendor javascript missing from the dockerfile about web HOT 7 CLOSED

Can you provide some additional information on how to replicate this issue @aconite33?

Running docker run -it --entrypoint sh bitwarden/web:2.26.1 (which is the web vault version matching server release 1.46.2), and ls app outputs the following files

main.70e6ec4e17a466ff6daf.js       polyfills.3ab3aecac16277160ac5.js.LICENSE.txt
main.70e6ec4e17a466ff6daf.js.map   polyfills.3ab3aecac16277160ac5.js.map
main.7b7aed24fb95652a39f4.css      vendor.7f0a909b78a411824308.js
main.7b7aed24fb95652a39f4.css.map  vendor.7f0a909b78a411824308.js.LICENSE.txt
polyfills.3ab3aecac16277160ac5.js  vendor.7f0a909b78a411824308.js.map

from web.

I followed the instructions here: https://bitwarden.com/help/install-on-premise-linux/

Here is what I have when I step inside our running web docker:

I have to download the vendor javascript file and insert it into the docker file.

from web.

That's weird.

I wonder if re-creating the web container would work. Could you try running the same commands as I did above and check if the file exists there?

docker run -it --entrypoint sh bitwarden/web:2.26.1
ls app

from web.

Running:

docker run -it --entrypoint sh bitwarden/web:2.26.1
ls app

Results in the same issue. No vendor.js supplied.

Even executing docker-compose up --build, I cannot get to pull the vendor.js file appropriately.

However, using the script with rebuild option worked. (Can't believe I missed this).

I can confirm that the vendorjs is now sitting there. I will update after I leave it running for a few days. We didn't have any issues when we first setup on prem, but only had this after the docker had been running for a few days.

from web.

It sounds odd. Nice that rebuild worked but has me confused as to why the vendor file would disappear.

from web.

I agree. I'll monitor it for a few days and if it happens again, I'll post back here.

If it goes a week or so without issue, I believe we can close it. I do know that I first started encountering it after I did a upgrade command via the script.

from web.

@aconite33 I'm closing this now.
If this happens again or continues to be an issue please feel free to re-open this issue and let us know, along with any additional detail to assist with reproduction and root cause analysis.

from web.