Poetry problem

[ihsaan-ullah]

On mac (apple chip) poetry installation fails. I am using the latest develop branch

 => CANCELED [codabench-compute_worker 2/9] RUN apt-get update && curl -fsSL https://get.docker.com | sh                                             36.5s
 => [codabench-flower  1/10] FROM docker.io/library/python:3.9-alpine@sha256:8a3f589d10f082c9392f43ebab335f625076d9b3689c41cee43a23ab379076a9         0.0s
 => CACHED [codabench-flower  2/10] RUN apk add --no-cache ca-certificates && update-ca-certificates curl                                             0.0s
 => CACHED [codabench-flower  3/10] RUN apk add curl                                                                                                  0.0s
 => ERROR [codabench-flower  4/10] RUN curl -sSL https://install.python-poetry.org | python3 -                                                       36.3s
 => [codabench-site_worker 4/9] RUN poetry config virtualenvs.create false                                                                            0.6s
 => [codabench-django 5/9] RUN poetry config virtualenvs.in-project false                                                                             0.6s
 => [codabench-site_worker 6/9] COPY pyproject.toml ./                                                                                                0.0s
 => [codabench-site_worker 7/9] COPY poetry.lock ./                                                                                                   0.0s
 => CANCELED [codabench-site_worker 8/9] RUN poetry install                                                                                           1.9s
------                                                                                                                                                     
 > [codabench-flower  4/10] RUN curl -sSL https://install.python-poetry.org | python3 -:                                                                   
#0 36.30 Retrieving Poetry metadata                                                                                                                        
#0 36.30                                                                                                                                                   
#0 36.30 # Welcome to Poetry!
#0 36.30 
#0 36.30 This will download and install the latest version of Poetry,
#0 36.30 a dependency and package manager for Python.
#0 36.30 
#0 36.30 It will add the `poetry` command to Poetry's bin directory, located at:
#0 36.30 
#0 36.30 /root/.local/bin
#0 36.30 
#0 36.30 You can uninstall at any time by executing this script with the --uninstall option,
#0 36.30 and these changes will be reverted.
#0 36.30 
#0 36.30 Installing Poetry (1.8.3)
#0 36.30 Installing Poetry (1.8.3): Creating environment
#0 36.30 Installing Poetry (1.8.3): Installing Poetry
#0 36.30 Installing Poetry (1.8.3): An error occurred. Removing partial environment.
#0 36.30 Poetry installation failed.
#0 36.30 See /poetry-installer-error-ohakc5ah.log for error logs.
------
failed to solve: executor failed running [/bin/sh -c curl -sSL https://install.python-poetry.org | python3 -]: exit code: 1

[ihsaan-ullah]

It seems that the problem is coming from building flower. Commenting the flower section in docker-compose.yaml fixes the problem

[ihsaan-ullah]

localhost:8000 works but does not load style

localhost does not work (without port 8000)

[Didayolo]

Same problem here.

[Didayolo]

@ihsaan-ullah I made a first suggestion of update here:

https://github.com/codalab/codabench/pull/1520/files

Changing the base image of Dockerfile.flower and specifying the platform. Now that building passes, but collect static command returns an error:

Error response from daemon: Container 67527f5458a7dae3d3e7c39a3316d215d6c4a431e9a93bfb5fb05277d13590a5 is restarting, wait until the container is running

and the website is not showing up.

[ObadaS]

@Didayolo Can you try rebuilding the flower docker image without the platform specified ? Or by specifying the ARM platform if possible. Feels weird to use x64 architecture for M1 apple chip, no ?

[Didayolo]

@ObadaS This is what we use in other dockerfiles. This needs to be clarified. I think the idea is to build for a given target platform.

---

It worked!

[Didayolo]

I close this issue for now, @ihsaan-ullah please confirm that it works for you with the changes proposed here: #1520. We can continue following this in the PR.