Open simplylu opened 1 year ago
Hello @js-on,
this is currently a bug which has not been fixed. It definitely was working sometime before. We have a custom postinstall hook, which normally should install sqlite if the --sqlite
flag is used on npm ci --sqlite
. Normally this should also work inside of the builder stage, but it could be that some native stuff is not correctly copied.
In the meantime, however, there are two ways to fix this problem.
FROM vocascan/server:latest
RUN npm install sqlite3
After that update your "docker-compose.yml" file and add the "build" property and remove the "image" property. This could look like this:
version: "3.8"
services:
vocascan:
restart: always
build:
context: .
dockerfile: Dockerfile
tty: true
environment:
VOCASCAN_CONFIG: "/etc/vocascan/vocascan.config.js"
ports:
- "8000:8000"
volumes:
- "./vocascan.config.js:/etc/vocascan/vocascan.config.js:ro"
This will pull the vocascan/server image as base image, and will build a local image with the sqlite3 npm package installed. I just tested it locally, with success.
Describe the bug Docker container crashes on startup when current Dockerfile is used for the build or the official image, and one selects sqlite as DB backend.
To Reproduce Steps to reproduce the behavior: Via Dockerfile
Via official container
Expected behavior Container should start without any problems.
Desktop (please complete the following information):
Additional context Traceback
Possible solution: I changed the Dockerfile to the following, and at least the error disappeared. Need to test further whether the container works as expected or not.