[Bug Report]: Docker Image carbone-ee:full-5.0.0 ERR_SOCKET_BAD_PORT

[radoen-psi]

Environment
Carbone Version: image: carbone/carbone-ee:full-5.0.0
Other: Using Docker Image

Expected Behaviour
the container should start

Actual Behaviour
Log from the container...

Carbone: Starting server...

Basic authentication is enabled. Use it only in a secure environment.
Authentication is on
Carbone webserver is started and listens on port NaN
Studio is on
node:net:2091
    validatePort(options.port, 'options.port');
    ^

RangeError [ERR_SOCKET_BAD_PORT]: options.port should be >= 0 and < 65536. Received type number (NaN).
    at Server.listen (node:net:2091:5)
    at /snapshot/carbone-ee/node_modules/restana/index.js:60:14
    at new Promise (<anonymous>)
    at Function.start (/snapshot/carbone-ee/node_modules/restana/index.js:58:25)
    at startServer (/snapshot/carbone-ee/lib/webserver.js)
    at /snapshot/carbone-ee/lib/webserver.js
    at /snapshot/carbone-ee/lib/helper.js
    at verifyToken (/snapshot/carbone-ee/node_modules/kitten-jwt/index.js:214:10)
    at /snapshot/carbone-ee/node_modules/kitten-jwt/index.js:230:12
    at parseToken (/snapshot/carbone-ee/node_modules/kitten-jwt/index.js:189:10) {
  code: 'ERR_SOCKET_BAD_PORT'
}

Other comments
This are the envs variable I'm using

        env:
           - name: CARBONE_EE_STUDIO
             value: 'true'
           - name: CARBONE_EE_AUTHENTICATION
             value: 'true'
           - name: APP_ROOT
             value: /app/
           - name: CARBONE_EE_LICENSE
             valueFrom:
               secretKeyRef:
                 name: carbone-license
                 key: license
           - name: CARBONE_EE_STUDIOUSER
             valueFrom:
               secretKeyRef:
                 name: carbone-user
                 key: creds
           - name: CARBONE_EE_PORT
             value: '4000'

I just updated the image from carbone-latest to carbone-latest-5.0.0 to test it but container doesn't start

[jorgelon]

see this #237

[radoen-psi]

Hi @jorgelon just tested latest image (5.0.3) still same behavior. Our side needs a bit of work to rename the service and upgrade all environments that use the old name. any chance to restore old behavior in the 5.0.X ?

[radoen-psi]

any news?

[jorgephiguera]

Hi @jorgelon just tested latest image (5.0.3) still same behavior. Our side needs a bit of work to rename the service and upgrade all environments that use the old name. any chance to restore old behavior in the 5.0.X ?

I am not a carbone developer. In my case renaming the service fixed it.
You can also try with the latest tag full-5.0.3-L25.2-O9.0-C141