-
Notifications
You must be signed in to change notification settings - Fork 60
Open
Description
Expected Behavior (Mandatory)
Pip should install the dependencies and the docker container should run the example app, as described in the README
Actual Behavior (Mandatory)
docker-compose up stops as an error with the pip install command occurs:
Building backend
[+] Building 2.0s (7/9)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 83B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/python:3 0.5s
=> [internal] load build context 0.0s
=> => transferring context: 4.48kB 0.0s
=> [1/5] FROM docker.io/library/python:3@sha256:19973e1796237522ed1fcc1357c766770b47dc15854eafdda055b65953fe5ec1 0.0s
=> CACHED [2/5] WORKDIR /usr/src/app 0.0s
=> ERROR [3/5] RUN pip install -e '.[dev]' 1.4s
------
> [3/5] RUN pip install -e '.[dev]':
#6 1.205 Obtaining file:///usr/src/app
#6 1.205 ERROR: file:///usr/src/app does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.
------
executor failed running [/bin/sh -c pip install -e '.[dev]']: exit code: 1
ERROR: Service 'backend' failed to build : Build failed
How to Reproduce the Problem
Follow the instruction in README : use docker-compose up inside the tests/ directory.
Specifications (Mandatory)
Currently used versions
Versions
- OS: macOS 14.1 (Sonoma), M1 Pro chip
- Library: django-neomodel 0.1.1 2023-08
- Neo4j: 5.4 (entreprise)
Metadata
Metadata
Assignees
Labels
No labels