-
Notifications
You must be signed in to change notification settings - Fork 147
Document how to run vault-ui docker image without nodemon #226
Comments
You can just replace |
@Lucretius Thanks. To clarify, it would be good to document how to run the already-built docker image with |
If the docker image is primarily intended for people running |
No problem guys, this fix should be super quick. Working on it now. |
#227 handles the difference between development and default runs. By default, Vault-UI will launch with |
@margueritepd please test out |
@djenriquez I probably won't get to this before you want to close the ticket, but your change looks good! when I try it, if I run into issues I'll report back here. Thanks a lot! |
I got this error when running vault-ui as a docker container:
Apparently this is related to the
fs.inotify.max_user_watches
system setting being set too low, similar to what is described here.Currently it is the docker image's default to serve files via
nodemon
, which is what is using all these inotify watches:However, I am not running the container in development. I don't need these file-watching abilities, and I would prefer to circumvent
nodemon
. I think the correct way to do this is to run the docker image withnode server.js
ornode server.js start_app
as the command argument, but I am too unfamiliar with the node toolchain to be certain which is the correct command.It would be great if you could document the correct way of running the docker container that circumvents
nodemon
.The text was updated successfully, but these errors were encountered: