Trying to deploy Docker image Community-4.5.0 on AWS

Hi,

I have an AWS deployment that seems to be failing at service startup with this error:

3290 ? Ss 0:00 runsvdir -P /etc/service log: -server: fatal: unable to open supervise/lock: file does not exist?runsv couchbase-server: fatal: unable to open supervise/lock: file does not exist?runsv couchbase-server: fatal: unable to open supervise/lock: file does not exist?runsv couchbase-server: fatal: unable to open supervise/lock: file does not exist?runsv couchbase-server: fatal: unable to open supervise/lock: file does not exist?

(This is from ps axww on the container)

What could be going wrong here? I have my data volume mounted on /opt/couchbase/var … but this will blow away the files in var/lib that are part of the base image. This confuses me as well.

Thanks for any help.

–Toby

Hi @tthain,

What command exactly did you run to start your docker container?

It’s precisely the default entry point on the container:

        "Entrypoint": [
            "/entrypoint.sh"
        ],

I was more interested in the command you used to actually run your docker container on the host machine.

e.g docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase

OK, turns out this is my fault. Don’t try it with a read only root fs. :slight_smile:

1 Like