Anyone see this error when trying to run docker-compose up with the latest acs-deployment code? Pulling alfresco-pdf-renderer (quay.io/alfresco/alfresco-pdf-renderer:2.0.7)... ERROR: unauthorized: access to the requested resource is not authorized

[jbarret2]

I cloned the acs-deployment project and tried to run docker-compose up.   It was working for me with an earlier version but after getting the latest updates I get the following:

$ docker-compose up
Pulling alfresco (alfresco/alfresco-content-repository:6.1.0-RC2)...
6.1.0-RC2: Pulling from alfresco/alfresco-content-repository
0ffa5ac9f3c5: Pull complete
9f519097f0dc: Pull complete
e8ec98c72c18: Pull complete
132c3f55d14e: Pull complete
28e3fe6f062f: Pull complete
22d11b904ba1: Pull complete
919951b2a157: Pull complete
66cc4b614bec: Pull complete
263170024c98: Pull complete
2564d3cc17d0: Pull complete
e952a7f4e065: Pull complete
71d82cf3b4c3: Pull complete
568f3bcaf5ce: Pull complete
78b87bebe7c8: Pull complete
5b7a8bd9f993: Pull complete
583a36a6a1e3: Pull complete
17eefa6f5a75: Pull complete
a498979231f1: Pull complete
8f8268265329: Pull complete
fa9124f7096e: Pull complete
70345939c311: Pull complete
42b62d4e96e9: Pull complete
Digest: sha256:f80934235a8a4bf2a7c5a8d93cd786ca11415e0743be6dec1363897f51d148c5
Status: Downloaded newer image for alfresco/alfresco-content-repository:6.1.0-RC2
Pulling alfresco-pdf-renderer (quay.io/alfresco/alfresco-pdf-renderer:2.0.7)...
ERROR: unauthorized: access to the requested resource is not authorized

[angelborroy · Accepted solution]

They are moving Docker Images to "quay.io" (what is a private repository) to control the access to Enterprise releases.

You can ask for credentials to Alfresco Support.

[jpotts]

FWIW, I am running commit 866c962 of acs-community-deployment and it does not have this problem. I realize that's a separate project from acs-deployment, but if you're just looking to demo or try something with 6.x it might be worth a shot.

[joreun]

Thank you Jeff,

I was trying to follow the community page  https://community.alfresco.com/community/ecm/blog/2018/07/11/alfresco-content-services-60-now-availa... which refers to "git clone https://github.com/alfresco/acs-deployment.git" which produces the error mentionned above when calling docker-compose up.

After using "git clone https://github.com/alfresco/acs-community-deployment.git" as you mention, there is no more error

Joël

[jpotts]

If you are trying to follow along using Enterprise, then you should use acs-deployment. But if you use that you *must* have credentials supplied by Alfresco Support so that you can do a "docker login quay.io" before you run docker-compose. It is not enough to simply register an account with quay.io--you must have quay.io creds supplied by Alfresco Support.

If you are trying to follow along using Community Edition, then you should instead use acs-community-deployment. These images are pulled from Docker Hub rather than quay.io and do not require any special credentials.

Jeff

[jbarret2]

I am curious why there is a need to lock down these Docker images.   Enterprise still requires a valid license in order to use them.   

[jpotts]

And, to your point, the Enterprise Docker images have a very short timeout of two days.

I suspect it follows the similar line of reasoning which causes them to lock down their Enterprise Maven artifacts.