7.14.0-SNAPSHOT Docker container won't start

[axw]

Kibana version: 7.14.0-SNAPSHOT

Original install method (e.g. download page, yum, from source, etc.): Docker

Describe the bug:

Kibana container won't start with default config.

Steps to reproduce:

1. docker run --rm -it docker.elastic.co/kibana/kibana:7.14.0-SNAPSHOT

log   [08:45:17.479] [fatal][root] Error: Invalid server options  {
  "port": 5601,
  "routes": {
    "cache": {                     
      "privacy": "private",
      "otherwise": "private, no-cache, no-store, must-revalidate"
    },
    "cors": false,
    "payload": {
      "maxBytes": 1048576
    },
    "validate": {
      "failAction": function defaultValidationErrorHandler(request, h, err) {\n    // Newer versions of Joi don't format the key for missing params the same way. This shim\n    // provides backwards compatibility. Unfortunately, Joi doesn't export it's own Error class\n    
// in JS so we have to rely on the `name` key before we can cast it.\n    //\n    // The Hapi code we're 'overwriting' can be found here:\n    //     https://github.com/hapijs/hapi/blob/master/lib/validation.js#L102\n    if (err && err.name === 'ValidationError' && err.hasO
wnProperty('output')) {\n        const validationError = err;\n        const validationKeys = [];\n        validationError.details.forEach((detail) => {\n            if (detail.path.length > 0) {\n                validationKeys.push(hoek_1.default.escapeHtml(detail.path.joi
n('.')));\n            }\n            else {\n                // If no path, use the value sigil to signal the entire value had an issue.\n                validationKeys.push('value');\n            }\n        });\n        validationError.output.payload.validation.keys = val
idationKeys;\n    }\n    throw err;\n},
      "options": {
        "abortEarly": false
      }
    }
  },
  "state": {
    "strictHeader": false,
    "isHttpOnly": true,
    "isSameSite": false
  },
  "host" [1]: "0"
}

[1] "host" must be a valid hostname
    at Object.exports.apply (/usr/share/kibana/node_modules/@hapi/hapi/lib/config.js:19:15)
    at Object.internals.setup (/usr/share/kibana/node_modules/@hapi/hapi/lib/core.js:649:23)
    at new module.exports.internals.Core (/usr/share/kibana/node_modules/@hapi/hapi/lib/core.js:116:46)
    at new module.exports (/usr/share/kibana/node_modules/@hapi/hapi/lib/server.js:23:18)
    at createServer (/usr/share/kibana/node_modules/@kbn/server-http-tools/target/create_server.js:13:20)
    at HttpServer.setup (/usr/share/kibana/src/core/server/http/http_server.js:106:53)
    at HttpService.runNotReadyServer (/usr/share/kibana/src/core/server/http/http_service.js:194:53)
    at HttpService.setupNotReadyService (/usr/share/kibana/src/core/server/http/http_service.js:171:38)
    at HttpService.setup (/usr/share/kibana/src/core/server/http/http_service.js:81:39)
    at Server.setup (/usr/share/kibana/src/core/server/server.js:183:23)
    at Root.setup (/usr/share/kibana/src/core/server/root/index.js:44:14)
    at bootstrap (/usr/share/kibana/src/core/server/bootstrap.js:97:5)
    at Command.<anonymous> (/usr/share/kibana/src/cli/serve/serve.js:224:5)

Expected behavior: container should start

Any additional context:

Previous instance: #86716

Maybe related to #99899? (There are some validation changes around the special "0" value.)

[simitt]

Could that be a similar issue as in #86716?

[axw]

@simitt exact same symptoms (noted at the bottom of the description :))
The fix for that led me to code that was changed in #99899.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[lukeelmers]

@pgayvallet Do you think this is possibly related to the recent joi upgrade?

[pgayvallet]

Should be fixed by #100551

[pgayvallet]

Not sure how often our image snapshots are updated though. @elastic/kibana-operations ?

[pgayvallet]

Fixed by #100551, closing