Closed cptechie closed 3 years ago
Actually on second thought, startapp.sh
might not be the best location for this. Might be better to put the command directly inside Dockerfile
. But you get the point.
Thanks, I modified the dockerfile. The warning is gone :)
This didn't work for me with a fresh container. I am still getting the warning dialog. I get the following if I bash into the container:
root@fae21a234e83:/app# itweb-settings list
...
deployment.manifest.attributes.check: ALL
...
The expected value of the variable is NONE
. I am using the image automationgeek/isy994-adminconsole-docker:latest
Give another try, I changed a few things.
JF
On Thu, Apr 1, 2021 at 2:12 PM cptechie @.***> wrote:
This didn't work for me with a fresh container. I am still getting the warning dialog. I get the following if I bash into the container:
@.***:/app# itweb-settings list ... deployment.manifest.attributes.check: ALL ...
The expected value of the variable is NONE. I am using the image automationgeek/isy994-adminconsole-docker:latest
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/therealmysteryman/isy994-adminconsole-docker/issues/1#issuecomment-812082642, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGZMZRMSIDAP5WHUIJ2XACTTGSZSHANCNFSM42C44AQA .
-- Jean-François @. @.>
Can you add the following snippet to
startapp.sh
right beforeexec javaws /app/admin.jnlp
?itweb-settings -set deployment.manifest.attributes.check NONE
Or we can wrap it around an environmental variable such as
ISY994_IGNORE_MANIFEST_ATTRIBUTES
or similar.This resolves the warning dialog below upon restart of the container.