You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C:\Program Files\Docker Toolbox\docker.exe: error parsing HTTP 403 response body: invalid character '<' looking for beginning of value: "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>AKIAIF2ALI2VM33FK36Q</AWSAccessKeyId><RequestId>3A3BD7D837D70686</RequestId><HostId>qTDAYO3py7Ta1V+kT+C1FBCDV0lSYUXqJY0zKAnVOdDzuy4kKalbNwcwVRQRygzB7KIaS8wYmV0=</HostId></Error>".
See 'C:\Program Files\Docker Toolbox\docker.exe run --help'.
Workaround is to pin version to 9.4-2.1-2.0; make the run command:
When running:
docker run --name gis -p 5432:5432 -e POSTGRES_USER=$PGUSER -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_DB=gis -d starefossen/pgrouting
We get:
Workaround is to pin version to
9.4-2.1-2.0
; make the run command:docker run --name gis -p 5432:5432 -e POSTGRES_USER=$PGUSER -e POSTGRES_PASSWORD=mysecretpassword -e POSTGRES_DB=gis -d starefossen/pgrouting:9.4-2.1-2.0
The text was updated successfully, but these errors were encountered: