Troubleshooting

• Join our slack channel and post the example causing trouble
• Email us at team@aperturedata.io with a description of the problem

caution

Setting up (or updating) the virtual environment for the python client can sometimes cause version dependencies mismatches. This is because the ApertureDB SDK does not pin the version numbers of some of its dependencies, and those get released in separate cycles.

There's a docker image that is built during the CI process and is a guaranteed stable environment in such a case. This image also includes a installation of Jupyter Lab. It can be run as follows

docker run --interactive --tty aperturedata/aperturedb-notebook

The docker compose file would include the following service in such a case.

services:

  aperturedb:
    image: aperturedata/aperturedb-community
    restart: always
    privileged: true
    volumes: # Map ApertureDB storage and logs into local directory
      - ./aperturedb/db:/aperturedb/db
      - ./aperturedb/logs:/aperturedb/logs
    ports:
      - 55555:55555 # HOST_PORT:CONTAINER_PORT
    environment:
      ADB_PORT: 55555

  webui:
    image: aperturedata/aperturedb-webui
    ports:
      - 80:80 # HOST_PORT:CONTAINER_PORT
    restart: always
    depends_on:
      - aperturedb
    environment:
      - APP_PRIVATE_VDMS_SERVER_ADDR=aperturedb
      - APP_PRIVATE_VDMS_SERVER_PORT=55555

  notebook:
    image: aperturedata/aperturedb-notebook
    ports:
      - 8888:8888 # HOST_PORT:CONTAINER_PORT
    restart: always
    command: bash -c "adb config create aperturedb_docker --host aperturedb --no-interactive && /start.sh"
    depends_on:
      - aperturedb