Latest release won't launch

[Sean-on-Git]

Describe the Bug

Pulled "latest" release tonight.

Crash loop on the docker container launch

chrome-1       | [0716/232046.985674:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
chrome-1       | [0716/232046.986571:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
chrome-1       | [0716/232046.986606:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
chrome-1       | [0716/232046.986945:WARNING:dns_config_service_linux.cc(427)] Failed to read DnsConfig.
chrome-1       | [0716/232047.050105:INFO:policy_logger.cc(145)] :components/policy/core/common/config_dir_policy_loader.cc(118) Skipping mandatory platform policies because no policy file was found at: /etc/chromium/policies/managed
chrome-1       | [0716/232047.050124:INFO:policy_logger.cc(145)] :components/policy/core/common/config_dir_policy_loader.cc(118) Skipping recommended platform policies because no policy file was found at: /etc/chromium/policies/recommended
chrome-1       | 
chrome-1       | DevTools listening on ws://0.0.0.0:9222/devtools/browser/2ead864f-d235-4040-9478-46ecc65d60e8
chrome-1       | [0716/232047.051708:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
chrome-1       | [0716/232047.068662:WARNING:sandbox_linux.cc(418)] InitializeSandbox() called with multiple threads in process gpu-process.
karakeep       | s6-rc: info: service s6rc-oneshot-runner: starting
karakeep       | s6-rc: info: service s6rc-oneshot-runner successfully started
karakeep       | s6-rc: info: service fix-attrs: starting
karakeep       | s6-rc: info: service init-db-migration: starting
karakeep       | Running db migration script
karakeep       | s6-rc: info: service fix-attrs successfully started
karakeep       | s6-rc: info: service legacy-cont-init: starting
karakeep       | s6-rc: info: service legacy-cont-init successfully started
chrome-1       | [0716/232047.105215:WARNING:dns_config_service_linux.cc(427)] Failed to read DnsConfig.
karakeep       | s6-rc: info: service init-db-migration successfully started
karakeep       | s6-rc: info: service svc-workers: starting
karakeep       | s6-rc: info: service svc-web: starting
karakeep       | s6-rc: info: service svc-workers successfully started
karakeep       | s6-rc: info: service svc-web successfully started
karakeep       | s6-rc: info: service legacy-services: starting
karakeep       | s6-rc: info: service legacy-services successfully started
karakeep       | node:internal/modules/run_main:92
karakeep       |   const type = getNearestParentPackageJSONType(mainPath);
karakeep       |                ^
karakeep       | 
karakeep       | Error: Invalid package config /app/package.json.
karakeep       |     at shouldUseESMLoader (node:internal/modules/run_main:92:16)
karakeep       |     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:20)
karakeep       |     at node:internal/main/run_main_module:36:49 {
karakeep       |   code: 'ERR_INVALID_PACKAGE_CONFIG'
karakeep       | }
karakeep       | 
karakeep       | Node.js v22.17.0
karakeep       | node:internal/modules/run_main:92
karakeep       |   const type = getNearestParentPackageJSONType(mainPath);
karakeep       |                ^
karakeep       | 
karakeep       | Error: Invalid package config /app/package.json.
karakeep       |     at shouldUseESMLoader (node:internal/modules/run_main:92:16)
karakeep       |     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:20)
karakeep       |     at node:internal/main/run_main_module:36:49 {
karakeep       |   code: 'ERR_INVALID_PACKAGE_CONFIG'
karakeep       | }
karakeep       | 
karakeep       | Node.js v22.17.0

This was working fine on "latest" release before pulling latest image.

I'd like to go back to "release" but it seems that isn't possible without wiping my sqlite db.

Steps to Reproduce

Docker pull "latest" release
docker compose up -d

Expected Behaviour

Launch Karakeep

Screenshots or Additional Context

No response

Device Details

No response

Exact Karakeep Version

nightly

Have you checked the troubleshooting guide?

• I have checked the troubleshooting guide and I haven't found a solution to my problem

[MohamedBassem]

hmmm, I can't seem to reproduce the issue on my local instance or even on a fresh installation:

/tmp ❯❯❯ docker pull ghcr.io/karakeep-app/karakeep:latest                                                                                                                                                                                                                                                                                                     ✘ 1
latest: Pulling from karakeep-app/karakeep
Digest: sha256:630cc92bcce80937ea8c4516fedb5f6af5e43e2c2225776f4aee6e754851ab46
Status: Image is up to date for ghcr.io/karakeep-app/karakeep:latest
ghcr.io/karakeep-app/karakeep:latest



/tmp ❯❯❯ docker run --rm -e NEXTAUTH_SECRET=test ghcr.io/karakeep-app/karakeep:latest
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service init-db-migration: starting
Running db migration script
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-db-migration successfully started
s6-rc: info: service svc-workers: starting
s6-rc: info: service svc-web: starting
s6-rc: info: service svc-workers successfully started
s6-rc: info: service svc-web successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
  ▲ Next.js 14.2.25
  - Local:        http://localhost:3000
  - Network:      http://0.0.0.0:3000

 ✓ Starting...
 ✓ Ready in 131ms
2025-07-17T08:10:51.216Z info: Workers version: nightly
2025-07-17T08:10:51.228Z info: [crawler] Loading adblocker ...
[next-auth][warn][NEXTAUTH_URL]
https://next-auth.js.org/warnings#nextauth_url
<-- GET /api/health
--> GET /api/health 200 1ms
2025-07-17T08:10:54.406Z info: Running in browserless mode
2025-07-17T08:10:54.406Z info: Starting crawler worker ...
2025-07-17T08:10:54.407Z info: Starting inference worker ...
2025-07-17T08:10:54.407Z info: Starting search indexing worker ...
2025-07-17T08:10:54.407Z info: Starting tidy assets worker ...
2025-07-17T08:10:54.407Z info: Starting video worker ...
2025-07-17T08:10:54.407Z info: Starting feed worker ...
2025-07-17T08:10:54.407Z info: Starting asset preprocessing worker ...
2025-07-17T08:10:54.407Z info: Starting webhook worker ...
2025-07-17T08:10:54.407Z info: Starting rule engine worker ...

And also E2E tests are passing. Do you have anything special in your docker setup? Mind sharing your docker compose?

[Sean-on-Git]

ENV

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# environment file for karakeep
# Read-it-later and bookmarking service

# Nightly
KARAKEEP_VERSION=latest

# Latest Install
#KARAKEEP_VERSION=release

# See https://docs.karakeep.app/configuration for more information
#DATA_DIR=/data
#MEILI_ADDR=http://127.0.0.1:7700
MEILI_MASTER_KEY=REDACTED
NEXTAUTH_URL=REDACTED
NEXTAUTH_SECRET=REDACTED

# Enable summarizing automatically to Ollama
INFERENCE_ENABLE_AUTO_SUMMARIZATION=true

# Browser
#BROWSER_WEB_URL=

# OAUTH_SETTINGS
OAUTH_CLIENT_SECRET=REDACTED
OAUTH_CLIENT_ID=REDACTED
OAUTH_WELLKNOWN_URL=REDACTED
OAUTH_PROVIDER_NAME="Authentik"
DISABLE_PASSWORD_AUTH=true

# AI settings
#OPENAI_BASE_URL=https://llama.local.seans.pro
#INFERENCE_TEXT_MODEL=gemma-3-4b-it-Q2_K.gguf
OLLAMA_BASE_URL=https://ollama.local.seans.pro
INFERENCE_TEXT_MODEL=gemma3:1b
INFERENCE_IMAGE_MODEL=llava-ph3:3.8b

# Change Asset DIR to external storage.
# Begin archiving web pages
#ASSETS_DIR=/backup0/docker_external_volumes/karakeep/assets
CRAWLER_FULL_PAGE_ARCHIVE=true
STORAGE=/backup0/docker_external_volumes

YAML

# karakeep
# Read-it-later and bookmarking service
services:
  karakeep:
    image: ghcr.io/karakeep-app/karakeep:${KARAKEEP_VERSION:-release}
    container_name: karakeep
    restart: unless-stopped
    volumes:
      # By default, the data is stored in a docker volume called "data".
      # If you want to mount a custom directory, change the volume mapping to:
      # - /path/to/your/directory:/data
      - ./data:/data
      - ${STORAGE}/karakeep/assets:/data/assets
    ports:
      - 13040:3000
    env_file:
      - karakeep.env
    environment:
      MEILI_ADDR: http://meilisearch:7700
      BROWSER_WEB_URL: http://chrome:9222
      # OPENAI_API_KEY: ...

      # You almost never want to change the value of the DATA_DIR variable.
      # If you want to mount a custom directory, change the volume mapping above instead.
      DATA_DIR: /data # DON'T CHANGE THIS
  chrome:
    image: gcr.io/zenika-hub/alpine-chrome:123
    restart: unless-stopped
    env_file:
      - karakeep.env
    command:
      - --no-sandbox
      - --disable-gpu
      - --disable-dev-shm-usage
      - --remote-debugging-address=0.0.0.0
      - --remote-debugging-port=9222
      - --hide-scrollbars
  meilisearch:
    image: getmeili/meilisearch:v1.13.3
    restart: unless-stopped
    env_file:
      - karakeep.env
    environment:
      MEILI_NO_ANALYTICS: "true"
    volumes:
      - ./meilisearch:/meili_data

[Sean-on-Git]

This was resolved today after pulling the latest nightly release @MohamedBassem

Closing as resolved