Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start demo deployment due to demo_client failure #137

Closed
sergei-zaiaev opened this issue Mar 8, 2022 · 2 comments
Closed

Unable to start demo deployment due to demo_client failure #137

sergei-zaiaev opened this issue Mar 8, 2022 · 2 comments
Assignees

Comments

@sergei-zaiaev
Copy link

Dear ETH CSCS Team,

I have attempted to run a demo deployment of FirecREST. Firstly, I got an error during the building of Docker images:

> docker compose build
...
=> ERROR [demo_compute internal] load metadata for docker.io/library/f7t-base:latest                                                         2.0s
 => [demo_client internal] load metadata for docker.io/library/python:3.7-alpine                                                              0.6s
 => [f7t-base internal] load metadata for docker.io/library/centos:7                                                                          0.0s
 => [demo_cluster internal] load build context                                                                                                0.0s
 => => transferring context: 36.65kB                                                                                                          0.0s
 => [f7t-base  1/47] FROM docker.io/library/centos:7                                                                                          0.0s
 => CANCELED [demo_cluster  2/47] RUN set -ex     && yum makecache fast     && yum -y install epel-release     && yum -y install        bzip  2.2s
 => [f7t-base internal] load build context                                                                                                    0.0s
 => => transferring context: 153B                                                                                                             0.0s
 => CANCELED [f7t-base 2/7] RUN yum install -y epel-release                                                                                   2.2s
 => [auth] library/f7t-base:pull token for registry-1.docker.io                                                                               0.0s
 => CANCELED [demo_client 1/4] FROM docker.io/library/python:3.7-
...
<Layers downloading>
...
 => [demo_client internal] load build context                                                                                                 0.1s
 => => transferring context: 314.58kB                                                                                                         0.1s
------
 > [demo_compute internal] load metadata for docker.io/library/f7t-base:latest:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

This has been simply solved by the following command:

docker build -f deploy/docker/base/Dockerfile . -t f7t-base 

After that, I have started the deployment using docker compose up -d command. All of the services have successfully started except the client, which failed with error code 1:

> docker compose logs client
client  | Traceback (most recent call last):
client  |   File "firecrest_demo.py", line 17, in <module>
client  |     from flask_oidc import OpenIDConnect
client  |   File "/usr/local/lib/python3.7/site-packages/flask_oidc/__init__.py", line 41, in <module>
client  |     from itsdangerous import JSONWebSignatureSerializer, BadSignature, \
client  | ImportError: cannot import name 'JSONWebSignatureSerializer' from 'itsdangerous' (/usr/local/lib/python3.7/site-packages/itsdangerous/__init__.py)

Do you have any idea how to fix this issue?

Thank you in advance!

@aledabin aledabin self-assigned this Mar 10, 2022
@sergei-zaiaev
Copy link
Author

This can be fixed by changing this line to:

RUN pip install itsdangerous==2.0.1 flask flask-WTF flask-bootstrap flask-oidc flask_sslify requests

Related issue

@aledabin
Copy link
Collaborator

Hello @FRONOX,
Thank you very much for your report and proposed solution, please try the latest release which fixes this and other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants