Can't install

[CoreKit-glitch]

Reproduction / Replay Link (Optional)

No response

Description

Hello,

i follow the get started part to install openstatus with docker but i can't rid of pulling images after running

docker compose up -d

 ⠼ Image tinybirdco/tinybird-local:latest       Pulling                                                                  1.5s
 ! Image openstatus/workflows:latest            pull access denied for openstatus/workflows, repository does not exist or may require 'docker login': denied: requested access to the resource is denied 1.4s                                          1.4s
 ! Image openstatus/server:latest               pull access denied for openstatus/server, repository does not exist or may req[+] up 6/35r login': denied: requested access to the resource is denied 1.4s                                             1.4s
 ⠴ Image tinybirdco/tinybird-local:latest [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling                                                    1.6s  ! Image openstatus/workflows:latest pull access denied for openstatus/workflows, repository does not exist or may require 'docker login': denied: requested access to the resource is denied 1.4s r openstatus/dashboard, repository does not exist or may  ! Image openstatus/server:latest pull access denied for openstatus/server, repository does not exist or may require 'docker l[+] up 6/35ed: requested access to the resource is denied 1.4s ied for openstatus/status-page, repository does not exist or ma ⠦ Image tinybirdco/tinybird-local:latest [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling                                                    1.7s  ! Image openstatus/workflows:latest pull access denied for openstatus/workflows, repository does not exist or may require 'docker login': denied: requested access to the resource is denied 1.4s s/dashboard, repository does not exist or may require 'do ! Image openstatus/server:latest pull access denied for openstatus/server, repository does not exist or may require 'docker l[+] up 6/35ed: requested access to the resource is denied 1.4s penstatus/status-page, repository does not exist or may require ⠧ Image tinybirdco/tinybird-local:latest [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling   

Images list from docker-compose file are :

    image: ghcr.io/tursodatabase/libsql-server:latest
    image: tinybirdco/tinybird-local:latest
    image: openstatus/workflows:latest
    image: openstatus/server:latest
    image: openstatus/private-location:latest
    image: openstatus/dashboard:latest
    image: openstatus/status-page:latest

How can i install and test this product that look very interesting to me ?

Thanks for your help :)

Source : Source : https://github.com/openstatusHQ/openstatus?tab=readme-ov-file#getting-started-

Environment

[linear]

OPE-542

[thibaultleouay]

Can you try with docker compose build first ?

[CoreKit-glitch]

full guide : https://github.com/openstatusHQ/openstatus/blob/main/DOCKER.md

[thibaultleouay]

Please try with docker compose build first and if it fixes it we should update the docs

[CoreKit-glitch]

Hello,

I followed this documentation https://github.com/openstatusHQ/openstatus/blob/main/DOCKER.md

to sum up :

• git clone
• cp .env.docker.example .env.docker
• Fill variables (AUTH_SECRET, DATABASE_URL, DATABASE_AUTH_TOKEN, RESEND_API_KEY) as requested
• export DOCKER_BUILDKIT=1
• docker compose build

=> stuck on step 65/77 with this message

i'll try on a VM with higher CPU and RAM specs.

Keep you in touch

[CoreKit-glitch]

i tried on a VM with higher speci it looks built stage run successfull now (4CPU, 8GB RAM)

But now, i'm facing of this error

OS : Ubuntu 24.04
Docker v29.1.4

Still investigating

[CoreKit-glitch]

i still can't make it working.

Might this part in .env.docker should be filled by something else ?

DATABASE_URL=http://libsql:8080 DATABASE_AUTH_TOKEN=basic:test

Any help appreciated

[Ariastarcos]

Docker build & registry

• Building the images locally (with docker compose build) before running docker compose up -d indeed resolves the registry problem, as docker (by default) prefers local images over registry images.
• The minimum required RAM to build the images appears to be ~6.43GB (!!) (300-800MB in use by system resources outside of building the images)
  • Our build halted because of this as well: Building 135.0s (89/95) -> [+] Building 521.7s (89/95), which just keeps going indefinitely. The exact layer, for both stages, is :build: Creating an optimized production build ....
  • Cancelling out of the build process, which writes the (at this point) in-memory cache layers to disk, and resuming it afterwards does not resolve this. Meaning the dashboard builder and status-page builder stages alone consume all this memory.

Database IO error

This is a result of the libsql initialization. To resolve this issue, mount the expected volume for the workflows service in the docker-compose.yaml file:

    # Internal Services
    workflows:
        # ...
        volumes:
            - ./data:/app/data

You do not need to rebuild the images after making this change, simply docker compose up -d --force-recreate.

After mounting the volume:

deploy@status:~/docker/openstatus$ ls data/
replica.db  replica.db-client_wal_index

PR: #1744

For the developers

This still produces an error when mounted for the first time, but the application starts. To resolve this, use the correct file protocol: file://./dev.db or file:///app/data/replica.db:

-  env().NODE_ENV === "development" ? "dev.db" : "/app/data/replica.db";
+  env().NODE_ENV === "development" ? "./dev.db" : "/app/data/replica.db";
- url: `file:${file}`,
+ url: `file://${file}`,

PR: #1745

[CoreKit-glitch]

Hello

Thanks for the help of @@Ariastarcos

Indeed, theses changes allow my 'docker compose up' to go further. (be careful of ./data folder permission to avoid a 'permission denied' error instead of 'no such file or directory'.

However, openstatus-workflows container still failing.

Here is the output of my last try.

WARN[0000] No services to build [+] up 7/7 Container openstatus-tinybird Recreated Container openstatus-libsql Recreated Container openstatus-workflows Recreated Container openstatus-server Recreated Container openstatus-dashboard Recreated Container openstatus-status-page Recreated Container openstatus-private-location Recreated Attaching to openstatus-dashboard, openstatus-libsql, openstatus-private-location, openstatus-server, openstatus-status-page, openstatus-tinybird, openstatus-workflows Container openstatus-libsql Waiting openstatus-libsql | _ _ openstatus-libsql | ___ __ _| | __| | openstatus-libsql | / __|/ _ | |/ ` |
openstatus-libsql | _ \ (| | | (| |
openstatus-libsql | |/_, ||_,|
openstatus-libsql | ||
openstatus-libsql |
openstatus-libsql | Welcome to sqld!
openstatus-libsql |
openstatus-libsql | version: 0.24.33
openstatus-libsql | commit SHA: b5dab26b005c51ac8a67a868f8eaa1f9674877a9
openstatus-libsql | build date: 2025-12-26
openstatus-libsql |
openstatus-libsql | This software is in BETA version.
openstatus-libsql | If you encounter any bug, please open an issue at https://github.com/tursodatabase/libsql/issues
openstatus-libsql |
openstatus-libsql | config:
openstatus-libsql | - mode: primary (0.0.0.0:5001)
openstatus-libsql | - database path: iku.db
openstatus-libsql | - extensions path:
openstatus-libsql | - listening for HTTP requests on: 0.0.0.0:8080
openstatus-libsql | - grpc_tls: no
openstatus-libsql | 2026-01-16T14:54:47.674104Z INFO sqld: listening for incoming user HTTP connection on 0.0.0.0:8080
openstatus-libsql | 2026-01-16T14:54:47.676607Z INFO sqld: listening for incoming gRPC connection on 0.0.0.0:5001
openstatus-libsql | 2026-01-16T14:54:47.681901Z INFO restore: libsql_server::namespace::meta_store: restoring meta store
openstatus-libsql | 2026-01-16T14:54:47.682012Z INFO restore: libsql_server::namespace::meta_store: meta store restore completed
openstatus-libsql | 2026-01-16T14:54:47.683470Z INFO libsql_server: Server sending heartbeat to URL every 30s
openstatus-libsql | 2026-01-16T14:54:47.684293Z INFO libsql_server::rpc: serving internal rpc server without tls
openstatus-libsql | 2026-01-16T14:54:47.686996Z INFO create:try_new_primary:make_primary_connection_maker: libsql_server::replication::primary::logger: SQLite autocheckpoint: 1000
openstatus-tinybird | /usr/lib/python3/dist-packages/supervisor/options.py:473: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
openstatus-tinybird | self.warnings.warn(
openstatus-tinybird | 2026-01-16 14:54:47,812 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
openstatus-tinybird | 2026-01-16 14:54:47,813 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
openstatus-tinybird | 2026-01-16 14:54:47,818 INFO RPC interface 'supervisor' initialized
openstatus-tinybird | 2026-01-16 14:54:47,818 CRIT Server 'unix_http_server' running without any HTTP authentication checking
openstatus-tinybird | 2026-01-16 14:54:47,818 INFO supervisord started with pid 1
openstatus-tinybird | 2026-01-16 14:54:48,824 INFO spawned: 'clickhouse' with pid 7
openstatus-tinybird | 2026-01-16 14:54:48,828 INFO spawned: 'nginx' with pid 8
openstatus-tinybird | 2026-01-16 14:54:48,832 INFO spawned: 'redis' with pid 9
openstatus-tinybird | 2026-01-16 14:54:48,835 INFO spawned: 'sentinel' with pid 12
openstatus-tinybird | 2026-01-16 14:54:48,845 INFO spawned: 'setup' with pid 13
openstatus-tinybird | 2026-01-16 14:54:48,855 INFO spawned: 'tinybird' with pid 14
openstatus-tinybird | 2026-01-16 14:54:48,866 INFO spawned: 'tinybird-hfi' with pid 25
openstatus-tinybird | 2026-01-16 14:54:48,873 INFO spawned: 'tinybird-kafka' with pid 26
openstatus-tinybird | 2026-01-16 14:54:48,883 INFO spawned: 'tinybird-mcp' with pid 31
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: clickhouse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: sentinel entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: setup entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: tinybird entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,919 INFO success: tinybird-hfi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,922 INFO success: tinybird-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:49,922 INFO success: tinybird-mcp entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Container openstatus-libsql Healthy
Container openstatus-libsql Waiting
Container openstatus-workflows Waiting
openstatus-tinybird | 2026-01-16 14:54:53,580 INFO exited: tinybird-kafka (exit status 1; not expected)
Container openstatus-libsql Healthy
openstatus-workflows | 14:54:54.301 INF logtape·meta LogTape loggers are configured. Note that LogTape itself uses the meta logger, which has category [
openstatus-workflows | "logtape", "meta"
openstatus-workflows | ]. The meta logger purposes to log internal errors such as sink exceptions. If you are seeing this message, the meta logger is automatically configured. It's recommended to configure the meta logger with a separate sink so that you can easily notice if logging itself fails or is misconfigured. To turn off this message, configure the meta logger with higher log levels than info. See also https://logtape.org/manual/categories#meta-logger.
openstatus-workflows | Starting server on port 3000
openstatus-workflows | Started server: http://localhost:3000
openstatus-tinybird | 2026-01-16 14:54:54,587 INFO spawned: 'tinybird-kafka' with pid 774
openstatus-tinybird | 2026-01-16 14:54:55,589 INFO success: tinybird-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:54:57,264 INFO exited: tinybird-kafka (exit status 1; not expected)
openstatus-tinybird | 2026-01-16 14:54:58,268 INFO spawned: 'tinybird-kafka' with pid 803
openstatus-tinybird | 2026-01-16 14:54:58,499 INFO exited: setup (exit status 1; not expected)
openstatus-tinybird | 2026-01-16 14:54:59,504 INFO spawned: 'setup' with pid 814
openstatus-tinybird | 2026-01-16 14:54:59,509 INFO success: tinybird-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:55:00,513 INFO success: setup entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
openstatus-tinybird | 2026-01-16 14:55:02,080 INFO exited: tinybird-kafka (exit status 1; not expected)
openstatus-tinybird | 2026-01-16 14:55:03,088 INFO spawned: 'tinybird-kafka' with pid 831
openstatus-tinybird | 2026-01-16 14:55:04,554 INFO success: tinybird-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Container openstatus-workflows Error dependency workflows failed to start
dependency failed to start: container openstatus-workflows is unhealthy

`

I'll continue to update this case

[Ariastarcos]

@CoreKit-glitch See #1746 to resolve this issue.