Docker container is getting killed with Molecule create

[anis016]

molecule.yml looks as follows.

driver:
  name: docker
platforms:
  - name: ad.hadoop.com
    image: osixia/openldap:1.5.0
    command: /sbin/init
    capabilities:
      - SYS_ADMIN
    volumes:
      - /sys/fs/cgroup:/sys/fs/cgroup:ro
    privileged: true
    pre_build_image: true

I can list the container

$ molecule list

                ╷             ╷                  ╷               ╷         ╷            
  Instance Name │ Driver Name │ Provisioner Name │ Scenario Name │ Created │ Converged  
╶───────────────┼─────────────┼──────────────────┼───────────────┼─────────┼───────────╴
  ad.hadoop.com │ docker      │ ansible          │ default       │ true    │ false  

However, the container dies after probably like 5/10 seconds. Please check the docker logs

$ docker logs 7166c29a5cc93d26eb8a8c45642c01c45242c1136ec99a93e3c26783c2265f8f

***  INFO   | 2021-07-27 09:02:29 | CONTAINER_LOG_LEVEL = 3 (info)
***  INFO   | 2021-07-27 09:02:29 | Search service in CONTAINER_SERVICE_DIR = /container/service :
***  INFO   | 2021-07-27 09:02:29 | link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools
***  INFO   | 2021-07-27 09:02:29 | link /container/service/slapd/startup.sh to /container/run/startup/slapd
***  INFO   | 2021-07-27 09:02:29 | link /container/service/slapd/process.sh to /container/run/process/slapd/run
***  INFO   | 2021-07-27 09:02:29 | Environment files will be proccessed in this order : 
Caution: previously defined variables will not be overriden.
/container/environment/99-default/default.startup.yaml
/container/environment/99-default/default.yaml

To see how this files are processed and environment variables values,
run this container with '--loglevel debug'
***  INFO   | 2021-07-27 09:02:29 | Running /container/run/startup/:ssl-tools...
***  INFO   | 2021-07-27 09:02:29 | Running /container/run/startup/slapd...
***  INFO   | 2021-07-27 09:02:29 | openldap user and group adjustments
***  INFO   | 2021-07-27 09:02:29 | get current openldap uid/gid info inside container
***  INFO   | 2021-07-27 09:02:29 | -------------------------------------
***  INFO   | 2021-07-27 09:02:29 | openldap GID/UID
***  INFO   | 2021-07-27 09:02:29 | -------------------------------------
***  INFO   | 2021-07-27 09:02:29 | User uid: 911
***  INFO   | 2021-07-27 09:02:29 | User gid: 911
***  INFO   | 2021-07-27 09:02:29 | uid/gid changed: false
***  INFO   | 2021-07-27 09:02:29 | -------------------------------------
***  INFO   | 2021-07-27 09:02:29 | updating file uid/gid ownership
***  INFO   | 2021-07-27 09:02:30 | Database and config directory are empty...
***  INFO   | 2021-07-27 09:02:30 | Init new ldap server...
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.57+dfsg-1~bpo10+1... done.
  Creating initial configuration... done.
  Creating LDAP directory... done.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of restart.
***  INFO   | 2021-07-27 09:02:31 | Start OpenLDAP...
***  INFO   | 2021-07-27 09:02:31 | Waiting for OpenLDAP to start...
***  INFO   | 2021-07-27 09:02:31 | Add bootstrap schemas...
config file testing succeeded
***  INFO   | 2021-07-27 09:02:31 | Add image bootstrap ldif...
***  INFO   | 2021-07-27 09:02:32 | Add custom bootstrap ldif...
***  INFO   | 2021-07-27 09:02:32 | Add TLS config...
***  INFO   | 2021-07-27 09:02:32 | No certificate file and certificate key provided, generate:
***  INFO   | 2021-07-27 09:02:32 | /container/service/slapd/assets/certs/ldap.crt and /container/service/slapd/assets/certs/ldap.key
2021/07/27 09:02:32 [INFO] generate received request
2021/07/27 09:02:32 [INFO] received CSR
2021/07/27 09:02:32 [INFO] generating key: ecdsa-384
2021/07/27 09:02:32 [INFO] encoded CSR
2021/07/27 09:02:32 [INFO] signed certificate with serial number 470563146943884652306326665881826386836734023354
***  INFO   | 2021-07-27 09:02:32 | Link /container/service/:ssl-tools/assets/default-ca/default-ca.pem to /container/service/slapd/assets/certs/ca.crt
***  INFO   | 2021-07-27 09:02:32 | Disable replication config...
***  INFO   | 2021-07-27 09:02:32 | Stop OpenLDAP...
***  INFO   | 2021-07-27 09:02:32 | Configure ldap client TLS configuration...
***  INFO   | 2021-07-27 09:02:32 | Remove config files...
***  INFO   | 2021-07-27 09:02:32 | First start is done...
***  INFO   | 2021-07-27 09:02:32 | Remove file /container/environment/99-default/default.startup.yaml
***  INFO   | 2021-07-27 09:02:32 | Environment files will be proccessed in this order : 
Caution: previously defined variables will not be overriden.
/container/environment/99-default/default.yaml

To see how this files are processed and environment variables values,
run this container with '--loglevel debug'
***  INFO   | 2021-07-27 09:02:32 | Running /container/run/process/slapd/run...
***  INFO   | 2021-07-27 09:02:32 | Running /sbin/init...
***  INFO   | 2021-07-27 09:02:32 | /sbin/init exited with status 127.
***  INFO   | 2021-07-27 09:02:32 | Shutting down /container/run/process/slapd/run (PID 426)...
60ffcba8 @(#) $OpenLDAP: slapd 2.4.57+dfsg-1~bpo10+1 (Jan 30 2021 06:59:51) $
        Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
60ffcba8 slapd starting
*** WARNING | 2021-07-27 09:03:02 | /container/run/process/slapd/run (PID 426) did not shut down in time. Forcing it to exit.
***  INFO   | 2021-07-27 09:03:02 | Killing all processes...

But I can create the container using the normal docker run command. Any idea what could be the issue?

Thanks!

[ssbarnea]

I think that is clearly the outcome of a 30s timeout somewhere. I was not able to find one hardcoded in the driver and I supposed it may be either in your config or an ansible default. You will need to dig yourself and find it. TBH, 30s to start a container is generous already but I can understand that some users may want more time.

[anis016]

I investigated this further but couldn't work with the default ones, so I had to create the user-defined create.yml file and added the task docker_container myself. It looks something like below. After this, I was able to create the docker container using Molecule.

- name: Create molecule instance(s)
  docker_container:
    name: "{{ item.name }}"
    hostname: "{{ item.hostname }}"
    image: "{{ item.image }}"
    networks: "{{ item.networks }}"
    state: started
    recreate: false
    log_driver: json-file
    command: "{{ item.command | default(omit) }}"
    privileged: "{{ item.privileged | default(omit) }}"
    volumes: "{{ item.volumes | default(omit) }}"
    capabilities: "{{ item.capabilities | default(omit) }}"
    ports: "{{ item.ports | default(omit) }}"
    env: "{{ item.env | default(omit) }}"
  register: server
  with_items: "{{ molecule_yml.platforms }}"
  loop_control:
    label: "{{ item.name }}"
  no_log: false
  async: 7200
  poll: 0

In the molecule.yml it looks as follows.

- name: ad.hadoop.com
  hostname: ad.hadoop.com
  image: osixia/openldap:1.5.0
  env:
    LDAP_ORGANISATION: "hadoop-ou"
    LDAP_DOMAIN: "hadoop.com"
    domainname: "hadoop.com"
    hostname: "hadoop-ad"
  ports:
    - "389:389"
    - "636:636"