Gateway Docker Image Doesn't Display Error On Second Install about firezone HOT 5 CLOSED

I don't think that we can do anything about it: this is the way docker works. The only fix would be to wrap the docker script into our own and handle edge cases there.

from firezone.

Is there no way to recognize that the auth key or ID is already in use, and fail the install with a readout to that effect?

from firezone.

My concern is — how would someone know they can't re-use the Docker install script?

from firezone.

Hm yeah, docker run -d doesn't bubble the underlying command exit code or output through to the terminal.

@jefferenced There's not a great solution to this particular issue -- ideally we'd nudge users to either copy the command once from the UI, or send them to docs for a different command that can be re-used successfully.

What @AndrewDryga is suggesting could work too, but wrapping in a script obfuscates the actual commands that are being run which is a security turn-off for some folks.

I think probably the best thing to do in the short term is to just make the deploy page more clear that the command only runs successfully once. Users with any familiarity with Docker will know to check the container's exit status / logs.

from firezone.

That makes sense, and maybe something like "one-time use / single use" would be sufficient?

from firezone.