Skip to content

Check errors in container startup #91

@eberrigan

Description

@eberrigan
ubuntu@ip-172-31-39-96:~$ sudo docker logs e70bfee89859
/var/run/postgresql:5432 - accepting connections
Running init.sql...
/var/run/postgresql:5432 - accepting connections
ALTER SYSTEM
psql:/app/init.sql:4: NOTICE:  role "lablink" does not exist, skipping
DROP ROLE
CREATE ROLE
ALTER ROLE
CREATE DATABASE
GRANT
You are now connected to database "lablink_db" as user "postgres".
SET
CREATE TABLE
CREATE FUNCTION
CREATE TRIGGER
Configuring PostgreSQL to listen on all addresses...
ALTER SYSTEM
init.sql executed successfully.
/var/run/postgresql:5432 - accepting connections
Error: Could not locate a Flask application. Use the 'flask --app' option, 'FLASK_APP' environment variable, or a 'wsgi.py' or 'app.py' file in the current directory.

Usage: flask [OPTIONS] COMMAND [ARGS]...
Try 'flask --help' for help.

Error: No such command 'db'.
Starting Flask app...
/app/get_config.py:16: UserWarning:
The version_base parameter is not specified.
Please specify a compatability version level, or None.
Will assume defaults for version 1.1
  with initialize(config_path="conf"):
2025-06-13 17:51:37 - hydra.core.utils - DEBUG - Setting JobRuntime:name=UNKNOWN_NAME
2025-06-13 17:51:37 - hydra.core.utils - DEBUG - Setting JobRuntime:name=get_config
sys:1: UserWarning:
'config' is validated against ConfigStore schema with the same name.
This behavior is deprecated in Hydra 1.1 and will be removed in Hydra 1.2.
See https://hydra.cc/docs/1.2/upgrades/1.0_to_1.1/automatic_schema_matching for migration instructions.
2025-06-13 17:51:37 - get_config - DEBUG - db:
  dbname: lablink_db
  host: localhost
  port: 5432
  table_name: vms
  message_channel: vm_updates
machine:
  machine_type: g4dn.xlarge
  repository: null
  image: ghcr.io/talmolab/lablink-sleap-client-image:linux-amd64
  ami_id: ami-067cc81f948e50e06
app:

 * Serving Flask app 'main'
 * Debug mode: off
2025-06-13 17:51:38 - werkzeug - INFO - WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5000
 * Running on http://172.17.0.2:5000
2025-06-13 17:51:38 - werkzeug - INFO - Press CTRL+C to quit

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions