Error on installing with docker

[luccabassoli]

Describe the bug

Starting monoscope-timescaledb ... done
Starting monoscope-app ... done
Attaching to monoscope-timescaledb, monoscope-app
monoscope-timescaledb |
monoscope-timescaledb | PostgreSQL Database directory appears to contain a database; Skipping initialization
monoscope-timescaledb |
monoscope-timescaledb | 2026-04-12 12:31:47.700 UTC [1] LOG: starting PostgreSQL 18.3 (Ubuntu 18.3-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04.3) 11.4.0, 64-bit
monoscope-timescaledb | 2026-04-12 12:31:47.701 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
monoscope-timescaledb | 2026-04-12 12:31:47.701 UTC [1] LOG: listening on IPv6 address "::", port 5432
monoscope-timescaledb | 2026-04-12 12:31:47.704 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
monoscope-timescaledb | 2026-04-12 12:31:47.709 UTC [24] LOG: database system was shut down at 2026-04-12 12:31:26 UTC
monoscope-timescaledb | 2026-04-12 12:31:47.714 UTC [1] LOG: database system is ready to accept connections
monoscope-timescaledb | 2026-04-12 12:31:47.717 UTC [27] LOG: TimescaleDB background worker launcher connected to shared catalogs
monoscope-app | monoscope-server: Uncaught exception ghc-internal:GHC.Internal.IO.Exception.IOException:
monoscope-app |
monoscope-app | libpq: failed (invalid sslmode value: "disable?keepalives=1&keepalives_idle=15&keepalives_interval=10&keepalives_count=3"
monoscope-app | )
monoscope-app |
monoscope-app | While handling libpq: failed (invalid sslmode value: "disable?keepalives=1&keepalives_idle=15&keepalives_interval=10&keepalives_count=3"
monoscope-app | | )
monoscope-app |
monoscope-app | HasCallStack backtrace:
monoscope-app | bracket, called at src/Start.hs:23:7 in monoscope-0.1.0.0-inplace:Start
monoscope-app |
Exception in thread Thread-7 (watch_events):
Traceback (most recent call last):
File "/usr/lib/python3.12/threading.py", line 1073, in _bootstrap_inner
self.run()
File "/usr/lib/python3.12/threading.py", line 1010, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python3/dist-packages/compose/cli/log_printer.py", line 202, in watch_events
for event in event_stream:
File "/usr/lib/python3/dist-packages/compose/project.py", line 626, in yield_loop
yield build_container_event(event)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/compose/project.py", line 594, in build_container_event
container = Container.from_id(self.client, event['id'])
~~~~~^^^^^^
KeyError: 'id'
monoscope-app exited with code 1

To Reproduce

No response

System

Ubuntu 24.04 - KVM Server

Additional context

No response

[luccabassoli]

[tonyalaribe]

Hi @luccabassoli, I just completed a migration from postgres-simple to hasql, which drastically improves query performance. I think this might be related.

I've created a new release v0.5.0 can you give it a try, and let me know if that works well enough for you.

[tonyalaribe]

Hi @luccabassoli, did you give it a try?

[luccabassoli]

Hi, I haven't tried it yet, but I'll give it a shot right now. Just a moment.

[luccabassoli]

Hi @tonyalaribe I ran the quick-start command on my VPS, but I'm still getting the same error. I just formatted it and reinstalled it using the command

[luccabassoli]

[tonyalaribe]

Hi @luccabassoli,
If its docker, you might need to download the new images. Otherwise you might still be running the old image.
Try docker compose pull first

docker compose pull && docker compose up

[luccabassoli]

Hi @tonyalaribe the problem is still happening. I'm following the instructions: pull and then push. But I'm still getting the error. I even reinstalled the VPS server.

[tonyalaribe]

That's strange. I'll spinup a VM and give it a try. It works fine from my local env.

…

On Tue, Apr 14, 2026, 9:57 PM Lucca Bassoli ***@***.***> wrote: *luccabassoli* left a comment (monoscope-tech/monoscope#356) <#356 (comment)> Hi @tonyalaribe <https://github.com/tonyalaribe> the problem is still happening. I'm following the instructions: pull and then push. But I'm still getting the error. I even reinstalled the VPS server. Screenshot.2026-04-14.at.16.56.06.png (view on web) <https://github.com/user-attachments/assets/0f418e00-b382-4992-ad1d-088dc96e2fdd> — Reply to this email directly, view it on GitHub <#356 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSCVAWIZAU7FSRVBDCUIH34V2J2ZAVCNFSM6AAAAACXV24ZJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENBWG4ZTKOJZGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tonyalaribe]

Hi @luccabassoli ,
I was able to reproduce the issue. I couldn't reproduce it before since I had a .env setup with a connection string. I've pushed a fix and created a new release: 1314bdf

The issue was an update that added keepalives to the connection string, but it only works when actually using a connection string, which the default Docker Compose config wasn't using.

Please give it another try.

[luccabassoli]

Hi @tonyalaribe It worked, thank you very much. One more question: I'm about to deploy to Coolify. When I use the Dockerfile, it always updates. When should I pull the changes again?

[tonyalaribe]

You can use the latest tag. So you lock yourself to a specific version. You would need to update the docker compose or add a docker compose local where you replace 'latest' with a specific version/tag which you can find on our github releases page

…

On Wed, Apr 15, 2026, 6:36 AM Lucca Bassoli ***@***.***> wrote: *luccabassoli* left a comment (monoscope-tech/monoscope#356) <#356 (comment)> Hi @tonyalaribe <https://github.com/tonyalaribe> It worked, thank you very much. One more question: I'm about to deploy to Coolify. When I use the Dockerfile, it always updates. When should I pull the changes again? — Reply to this email directly, view it on GitHub <#356 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSCVATPIUT2WYCTDN5CVST4V4GVJAVCNFSM6AAAAACXV24ZJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENBZGEZDKNRRGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>