search

inveniosoftware / invenio-cli

CLI module for Invenio
https://invenio-cli.readthedocs.io
MIT License
10 stars 43 forks source link

invenio-cli does not detects container creation error #265

Open BalazsBago opened 3 years ago

BalazsBago commented 3 years ago

Package version (if known): invenio-cli, version 1.0.0

Describe the bug

I have tried to install the latest version of Inveio RDM (v6) with invenio-cli and ran into an issue with both local and containerized installation. It looks like the invenio-cli can not create docker containers.

Steps to Reproduce

  1. Install a firewall which prevents your machine to access docker registries.
  2. Prepare an rdm project
  3. Run service initialisation: containerized command invenio-cli containers start --lock --build --setup or local command invenio-cli services setup

Expected behavior

Running services

Additional context

Outputs:

invenio-cli containers start --lock --build --setup ... Making sure containers are up... redis up and running! postgresql up and running! es up and running! Containers started and healthy. Flushing redis cache... .... docker.errors.NotFound: 404 Client Error for http+docker://localhost/v1.39/containers/rdm-v6_web-ui_1/json: Not Found ("No such container: rdm-v6_web-ui_1")

invenio-cli services setup Making sure containers are up... redis up and running! postgresql up and running! es up and running! Containers started and healthy. Checking services are not setup... Services setup status consistent. Creating database... Creating database postgresql+psycopg2://eli-rdm-v6:***@localhost/eli-rdm-v6 ... psycopg2.OperationalError: could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?

ppanero commented 3 years ago

After disccusions with @BalazsBago in the chat, the issue is related to error reporting. When manually running the docker command the user is getting:

docker-compose -f docker-compose.yml up 
Pulling es (docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2)...
ERROR: Get https://docker.elastic.co/v2/: x509: certificate signed by unknown authority
Probably the company firewall causes this error

Meaning that the CLI should have shown an error when creating containers but returned success.