Version 7 Docker Deployment in AWS - Entrypoint changed

Community Support
1

Description

I’ve had some troubly upgrading to version 7 from version 6.12.0 in AWS, so thought I would post my experience here in case it’s of use to anyone else. Initially I was getting the error

runc create failed: unable to start container process: exec: “/bin/bash”: stat /bin/bash: no such file or directory

I’m running the image direct from the registry and was having the same problem with both 7.x images:

registry.rocket.chat/rocketchat/rocket.chat:7.0.0
registry.rocket.chat/rocketchat/rocket.chat:7.1.0

For my 6.x deployments I had the entrypoint and cmd set in my task definition thus:

"entryPoint": [
  "/bin/bash",
  "-c"
],
"command": [
  "node main.js"
],

This has clearly changed for 7.x - so the task was amended to

"entryPoint": [
      "docker-entrypoint.sh"
  ],
  "command": [
     "node",
    "main.js"
  ],

I also had to give the Target Group health check a bit more leeway (3 checks, 10 second timeout) as v7 seems to take a bit longer to boot up.

Server Setup Information

  • Version of Rocket.Chat Server: 7.1.0
  • Operating System: AWS ECS
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version: 6.0.3 / wiredTiger (oplog Enabled)
  • Proxy: n/a
  • Firewalls involved: AWS Load Balancer

Any additional Information

2

Probably best to re-visit the docs as they do change periodically.

It is recommended to use compose.

https://docs.rocket.chat/docs/deploy-with-aws

https://docs.rocket.chat/v1/docs/deploy-with-docker-docker-compose

Sample compose file:

Sample .env

You will be better off to re-align with these.