Open mojuha opened 1 year ago
Dear Morten and the Team,
I encountered the same issue, and I followed these steps to resolve it. I'm just someone who is curious about this project and not involved in the development.
I'm using Ubuntu 22.04.
At the repository's root directory, I ran the following commands:
cd .docker/pythonserver
(sudo apt-get install vim), optional sudo vim Dockerfile
In the Dockerfile, I changed the Python version from 2.7 to 3.11. FROM python:3.11
Press Esc and type :wq to save changes.
Afterward, I updated the package list. sudo apt-get update
Finally, I brought up the Docker compose:
sudo docker-compose up
If it still doesn't work, you may want to check for any internet connection limitations. I hope these steps work for you as well.
Best,
We get the following message (testing various versions of Ubuntu and Debian): => ERROR [pythonserver 5/8] RUN pip install fabric 4.0s => [nodeserver 1/15] FROM docker.io/library/node:lts-slim@sha256:7c9f2200d17af63837575055fe8d054f3df08c2875dbb5725ce5559852da2b20 0.0s => [nodeserver internal] load build context 0.0s => => transferring context: 176B 0.0s => CACHED [nodeserver 2/15] RUN groupadd --system --gid "0" --non-unique etherpad && useradd --system --uid "5001" --non-unique --gid etherpad --create-home etherpad 0.0s => CACHED [nodeserver 3/15] RUN apt-get update; apt-get install curl -y 0.0s => CACHED [nodeserver 4/15] RUN echo "Getting version: develop" && curl --location --fail --silent --show-error --output /opt/etherpad-lite.tar.gz https://github.com/ether/etherpad-lite/archive/"develop".ta 0.0s => CACHED [nodeserver 5/15] RUN chown etherpad:etherpad "/opt/etherpad-lite" 0.0s => CACHED [nodeserver 6/15] WORKDIR /opt/etherpad-lite 0.0s => CANCELED [nodeserver 7/15] RUN { [ -z "ep_disable_chat" ] || npm install --no-save --legacy-peer-deps ep_disable_chat; } && src/bin/installDeps.sh && rm -rf ~/.npm 4.2s
Additional/related thought: When reviewing the "docker-compose.yml" file, one of us suspects that the problem may lie in the fact that the components/packages are not tagged with version numbers. By default, Docker will download the latest version, and there is a certain possibility that the problem may lie here?
Thank you and best regards, Morten and team