Docker package manager issue

[3as8]

After adding the token in docker/docker-compose.yml and running docker-compose up -d docker throws an error:

"Error response from daemon: Head https://docker.pkg.github.com/v2/alisentas/mwexpress/mwexpress/manifests/latest: no 
basic auth credentials"

any help would be appreciated

[alisentas]

Hi @3as8,

I've changed the docker images a bit as part of an i18n refactoring, can you try to follow the new commands in new README.

cd docker/english
docker-compose build  # might take some time
docker-compose up -d
docker-compose down
docker-compose up -d  # restart second time for initial data changes to be applied

I think this will work and you won't need to download mwexpress image from docker registry.

[3as8]

Hi @3as8,

I've changed the docker images a bit as part of an i18n refactoring, can you try to follow the new commands in new README.

cd docker/english
docker-compose build  # might take some time
docker-compose up -d
docker-compose down
docker-compose up -d  # restart second time for initial data changes to be applied

I think this will work and you won't need to download mwexpress image from docker registry.

I ran exactly what you said and
docker-compose build
worked correctly, but after I used
docker-compose up -d
it downloaded some stuff before throwing an unexpected EOF error, after googling stuff about it I found out that alot of people are having this problem in docker, but I couldnt find a way to actually fix it, did you ever run into this issue and if you did, how did you fix it

Thanks for any help!

[alisentas]

If you're using Docker for Windows, can you try increasing the RAM you give to docker?
https://docs.docker.com/docker-for-windows/#resources
Something like 4Gb should do the trick.
Other than that, I didn't experience that issue on my machine.

[3as8]

turns out I had docker compose V2 active which I think was the problem becuase now in the docker screen mwe-db, mwe-db-ui and mwexpress are running, but mwe-logs is stuck on restarting and http://localhost:5432/ does not have anything hosted on it, and when I open http://localhost:8080 it gives me a login screen which I dont know what I have to do with, do I have to self host an sql database then enter its login info in this or what?. and thanks for the help

Edit: I just realized that I forgot to restart the container, and when I do docker-compose up -d it gives me an error

ERROR: Configuration for volume db_data specifies driver localdocker-compose down, but a volume with the same name uses a different driver (local). If you wish to use the new configuration, please remove the existing volume "english_db_data" first:
$ docker volume rm english_db_data

and I think using that command would remove the whole point of restarting

[alisentas]

Hi again @3as8,

You can safely use that volume remove command, maybe it's created by some older deployment. Restarting would still be necessary by the way.

A postgres database is automatically started as well when you do docker-compose up -d, to login to the database, in the http://localhost:8080, select these options:

System: PostgreSQL
Server: mwe-db
Username: mwe
Password: mwedb123
Database: mwedb

This information is configurable in the docker-compose.yml file by the way. If everythings working correctly, that is all applications state is "up" in docker-compose ps, then you should see some tables in that interface.

[3as8]

Well this is awkward, today I did docker-compose build so I can try the things you sent, but it now throws an error it never did which is pretty weird

ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
#11 3281.4     scikit-learn from https://files.pythonhosted.org/packages/36/dd/06b6f0ad7b86c3edc3a02d255f3fcc98e444a847cea10b3a0182251ca7b6/scikit_learn-0.24.2-cp38-cp38-manylinux2010_x86_64.whl#sha256=62214d2954377fcf3f31ec867dd4e436df80121e7a32947a0b3244f58f45e455 (from -r requirements.txt (line 16)):
#11 3281.4         Expected sha256 62214d2954377fcf3f31ec867dd4e436df80121e7a32947a0b3244f58f45e455
#11 3281.4              Got        f51a1f302d7440298099fe7b01bc4d9387b08c93d0e2f21c21445f3afd68fc99
#11 3281.4
------
executor failed running [/bin/sh -c pip install -r requirements.txt]: exit code: 1
ERROR: Service 'mwexpress' failed to build : Build failed

[alisentas]

Can you disable cache while building?

docker-compose build --no-cache

If that doesn't work, I'd recommend you clear everything up before building again:

docker kill $(docker ps -q)
docker rm $(docker ps -aq)
docker network prune -f
docker volume prune -f
docker rmi $(docker images -q)

And then continue as usual with docker-compose build and up

[3as8]

Looks like every possible fix leads to another error... This time with this new one:

failed commit on ref "layer-sha256:942374d5c11438b68e78d44b36c9eac8fe0a2570c33681d7263b0f3f069c06b9": "layer-sha256:942374d5c11438b68e78d44b36c9eac8fe0a2570c33681d7263b0f3f069c06b9" failed size validation: 31889842 != 196445179: failed precondition
ERROR: Service 'mwexpress' failed to build : Build failed