Server fails to start, docker compose

[jschneekloth]

Following these instructions to setup via docker (docker compose in this example).

My docker compose:

---
services:
  atomic-server:
    image: joepmeneer/atomic-server
    container_name: atomic-server
    restart: unless-stopped
    ports:
      - 9883:80
    volumes:
      - ~/volumes/atomic-data/atomic-storage:/atomic-storage

When running docker compose up -d I see the following output in logs and the server doesn't startup:

atomic-server  | exec /atomic-server-bin: exec format error
atomic-server  | exec /atomic-server-bin: exec format error
atomic-server  | exec /atomic-server-bin: exec format error
atomic-server  | exec /atomic-server-bin: exec format error
atomic-server  | exec /atomic-server-bin: exec format error
atomic-server  | exec /atomic-server-bin: exec format error
atomic-server  | exec /atomic-server-bin: exec format error

Any ideas on what might be going on here?

[joepio]

Could you try :develop instead of :latest? image: joepmeneer/atomic-server:develop

…

On Sun, 17 Dec 2023, 03:25 Jason, ***@***.***> wrote: Following these <https://docs.atomicdata.dev/atomicserver/installation> instructions to setup via docker (docker compose in this example). My docker compose: --- services: atomic-server: image: joepmeneer/atomic-server container_name: atomic-server restart: unless-stopped ports: - 9883:80 volumes: - ~/volumes/atomic-data/atomic-storage:/atomic-storage When running docker compose up -d I see the following output in logs and the server doesn't startup: atomic-server | exec /atomic-server-bin: exec format error atomic-server | exec /atomic-server-bin: exec format error atomic-server | exec /atomic-server-bin: exec format error atomic-server | exec /atomic-server-bin: exec format error atomic-server | exec /atomic-server-bin: exec format error atomic-server | exec /atomic-server-bin: exec format error atomic-server | exec /atomic-server-bin: exec format error Any ideas on what might be going on here? — Reply to this email directly, view it on GitHub <#744>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQVBEOS7K64GKLIYNEPEODYJZJ3BAVCNFSM6AAAAABAYAGNZ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2DKMBSG4YTCNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jschneekloth]

Thanks, that got the service starting up in docker:

atomic-server  | Atomic-server 0.36.1 
atomic-server  | Use --help for instructions. Visit https://docs.atomicdata.dev and https://github.com/atomicdata-dev/atomic-server for more info.
atomic-server  | 2023-12-17T15:07:31.989061Z  INFO atomic_server::appstate: Initializing AppState
atomic-server  | 2023-12-17T15:07:31.989072Z  INFO atomic_server::appstate: Opening database at "/atomic-storage/data/store"
atomic-server  | 2023-12-17T15:07:31.998853Z  INFO atomic_server::appstate: Initialize: creating and populating new Database...
atomic-server  | 2023-12-17T15:07:32.051581Z  INFO atomic_server::appstate: Setting default agent
atomic-server  | 2023-12-17T15:07:32.051901Z  WARN atomic_server::appstate: No existing config found, created a new Config at "/atomic-storage/config/config.toml". Copy this to your client machine (running atomic-cli or atomic-data-browser) to log in with these credentials. 
atomic-server  | server = "http://localhost"
atomic-server  | agent = "http://localhost/agents/AGENT"
atomic-server  | private_key = KEY
atomic-server  | 
atomic-server  | 2023-12-17T15:07:32.051937Z  INFO atomic_server::appstate: Default Agent is set: http://localhost/agents/AGENT
atomic-server  | 2023-12-17T15:07:32.051940Z  INFO atomic_server::appstate: Starting search service
atomic-server  | 2023-12-17T15:07:32.093892Z  INFO atomic_server::appstate: Starting commit monitor
atomic-server  | 2023-12-17T15:07:32.205360Z  INFO atomic_server::appstate: Creating initial Invite at http://localhost/setup
atomic-server  | 2023-12-17T15:07:32.205454Z  INFO atomic_lib::storelike: Building index (this could take a few minutes for larger databases)
atomic-server  | 2023-12-17T15:07:32.206619Z  INFO atomic_server::appstate: Setting rights to Drive http://localhost
atomic-server  | 2023-12-17T15:07:32.206624Z  INFO atomic_server::appstate: Adding all resources to search index
atomic-server  | 2023-12-17T15:07:32.206627Z  INFO atomic_server::search: Building search index...
atomic-server  | 2023-12-17T15:07:32.238447Z  INFO atomic_lib::storelike: Building index finished!
atomic-server  | 2023-12-17T15:07:34.809298Z  INFO atomic_server::search: Search index finished!
atomic-server  | 2023-12-17T15:07:34.809750Z  INFO atomic_server::serve: Binding HTTP server to endpoint :::80
atomic-server  | 
atomic-server  |          __                  _
atomic-server  |   ____ _/ /_____  ____ ___  (_)____      ________  ______   _____  _____
atomic-server  |  / __ `/ __/ __ \/ __ `__ \/ / ___/_____/ ___/ _ \/ ___/ | / / _ \/ ___/
atomic-server  | / /_/ / /_/ /_/ / / / / / / / /__/_____(__  )  __/ /   | |/ /  __/ /
atomic-server  | \__,_/\__/\____/_/ /_/ /_/_/\___/     /____/\___/_/    |___/\___/_/
atomic-server  | 
atomic-server  | 
atomic-server  | Visit http://localhost
atomic-server  | 
atomic-server  | 
atomic-server  | 2023-12-17T15:07:34.809807Z  INFO actix_server::builder: Starting 10 workers
atomic-server  | 2023-12-17T15:07:34.809820Z  INFO actix_server::server: Actix runtime found; starting in Actix runtime

Initial OOBE feels a bit awkward (perhaps due to being :develop), navigating to /setup gave json parsing errors, and there looks to be test data populating some areas with default, I think collections? defined after navigating around a bit. Will play around with this and update to the next :latest when available.

[joepio]

Thanks for the feedback @jschneekloth!