github shellhub-io/shellhub v0.31.1

one hour ago

Docker agents on http:// survive the update to v0.31

v0.31.0 refuses a plain http:// server address unless SHELLHUB_ALLOW_INSECURE_SERVER is set. A Docker agent pointed at http:// that updated itself to v0.31.0 removed its old container, then the new one exited on that check and restarted in a loop, leaving the device offline.

From v0.31.1, a Docker agent that updates itself carries SHELLHUB_ALLOW_INSECURE_SERVER=true over to the new container when its server address is http:// outside loopback, and keeps running. New installs on http:// still need the variable set explicitly. (#8066)

An agent already stuck in that loop on v0.31.0 does not recover on its own. Recreate its container with -e SHELLHUB_ALLOW_INSECURE_SERVER=true, or move the server address to https://.

Full Changelog: v0.31.0...v0.31.1

Don't miss a new shellhub release

NewReleases is sending notifications on new releases.