This is bcos the hash of password in DB still uses scram encryption. After this step 1 you may (most likely) continue to have the issue of authentication error. Use vi (or other editor) to replace scram-sha-256 with md5 in the file nf and post_hba.conf location of the files depends on your local set up.RUN pip3 install psycopg2-binary -no-binary psycopg2-binary RUN apt update -y & apt install -y build-essential libpq-dev For this, add the following commands to the dockerfile. The second solution is to build the psycopg2 file and install libq and other dependencies.Change base image name to 'python:3.9.6-alpine3.14' I used 'python:3.9-slim-buster' at docker and I've got error. If you're getting an error, you'll probably see a number like 90xxx here. If you want to know your libq version used in your docker-image, you can do the following, respectively. It is explained with examples in the answer given here. I didn't try local, solutions are for docker container.Īccording to the main image we defined at the beginning of the Dockerfile, our libq versions may differ. My question is: why did it happened? Is it a bug or just me stupidly installing it manually and not excluding it from the yum update command ? Can anybody shed some light on that issue? I have found out that the upgrade process manged to somehow conflict with the existing psql installation and to delete the current psql server. Once this process was done I noticed my application stopped working. I have installed locally a PostgreSQL server 9.6.2 on aws Centos server a while ago using these commands: rpm -i Ī few days ago, I have upgraded the server using yum update.
0 kommentar(er)
