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
Solved! Go to 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.
I've tried again (I've started from scratch, so I've downloaded again from git, change immediatelly the value in community-docker-compose.yml and did the "docker-compose") and now it is working fine. From https://github.com/Alfresco/acs-deployment I see that there was a commit commit today, so, maybe, that fixed my problem (or maybe, launching the "docker-compose" the first time with the wrong value in community-docker-compose.yml created some problem ).
I think that the value in community-docker-compose.yml should be updated (from "quay.io/alfresco/search-services:2.1.0-SNAPSHOT" to "alfresco/alfresco-search-services:2.0.3" so other users will not have my same problem).
Thank you abhinavmishra14 for all the support and answers you provided me in this thread
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.
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.
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
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
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.
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.
I tried to install the last community edition, docker-compose install (https://docs.alfresco.com/content-services/community/install/containers/docker-compose/), for education purposes. On the second command got this error because the images are now on a payed repository. What is the purpose to have a community edition if you still have to pay for staff. At least remove this option from the install guide and let us strugle with the old fashion way. (
I was trying to install the last community edition using the docker-compose steps but I get the "Error response from daemon: unauthorized: access to the requested resource is not authorized". Does this means that it is no longer possible to install it using docker how it is explained in https://docs.alfresco.com/content-services/community/install/containers/docker-compose/ ? What is now another "easy" way to install it and do some tests? I've tried the zip-version ( https://docs.alfresco.com/content-services/community/install/zip/ ) but it requires to install many other tools and also modify several configuration files, but I was just looking to test the community edition without the need to do a complicate installation
It still works and it should work. I hope you used the right commands and right docker-compose file.
Take this docker compose file as a reference and try to launch: https://github.com/Alfresco/acs-deployment/blob/master/docker-compose/community-docker-compose.yml
There is a bug/typo in the docker-compose file shared above though. You need to change anything that referes to "quay.io/alfresco" to "alfresco". Change it to "alfresco/alfresco-search-services:2.0.3"
This reference: https://github.com/Alfresco/acs-deployment/blob/master/docker-compose/community-docker-compose.yml#L...
Here is full docker-compose file with fixes, if you want to use it:
# This docker-compose file will spin up an ACS cluster on a local host or on a server and it requires a minimum of 12GB Memory to distribute among containers. # Limit container memory and assign X percentage to JVM. There are couple of ways to allocate JVM Memory for ACS Containers # For example: 'JAVA_OPTS: "$JAVA_OPTS -XX:+PrintFlagsFinal -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap"' # See Oracle docs (https://docs.oracle.com/javase/9/gctuning/parallel-collector1.htm#JSGCT-GUID-CAB83393-3438-44ED-98F0-D15641B43C7D). # If the container memory is not explicitly set then the flags above will set the max heap default to 1/4 of the container's memory, which may not be ideal. # For performance tuning, assign the container memory and give a percentage of it to the JVM. # Using version 2 as 3 does not support resource constraint options (cpu_*, mem_* limits) for non swarm mode in Compose version: "2" services: alfresco: image: alfresco/alfresco-content-repository-community:7.2.0 mem_limit: 1600m environment: JAVA_TOOL_OPTIONS: " -Dencryption.keystore.type=JCEKS -Dencryption.cipherAlgorithm=DESede/CBC/PKCS5Padding -Dencryption.keyAlgorithm=DESede -Dencryption.keystore.location=/usr/local/tomcat/shared/classes/alfresco/extension/keystore/keystore -Dmetadata-keystore.password=mp6yc0UD9e -Dmetadata-keystore.aliases=metadata -Dmetadata-keystore.metadata.password=oKIWzVdEdA -Dmetadata-keystore.metadata.algorithm=DESede " JAVA_OPTS: " -Ddb.driver=org.postgresql.Driver -Ddb.username=alfresco -Ddb.password=alfresco -Ddb.url=jdbc:postgresql://postgres:5432/alfresco -Dsolr.host=solr6 -Dsolr.port=8983 -Dsolr.http.connection.timeout=1000 -Dsolr.secureComms=secret -Dsolr.sharedSecret=secret -Dsolr.base.url=/solr -Dindex.subsystem.name=solr6 -Dshare.host=127.0.0.1 -Dshare.port=8080 -Dalfresco.host=localhost -Dalfresco.port=8080 -Daos.baseUrlOverwrite=http://localhost:8080/alfresco/aos -Dmessaging.broker.url=\"failover:(nio://activemq:61616)?timeout=3000&jms.useCompression=true\" -Ddeployment.method=DOCKER_COMPOSE -DlocalTransform.core-aio.url=http://transform-core-aio:8090/ -Dcsrf.filter.enabled=false -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80 " transform-core-aio: image: alfresco/alfresco-transform-core-aio:2.5.7 mem_limit: 1536m environment: JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80" ports: - "8090:8090" share: image: alfresco/alfresco-share:7.2.0 mem_limit: 1g environment: REPO_HOST: "alfresco" REPO_PORT: "8080" JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80 -Dalfresco.host=localhost -Dalfresco.port=8080 -Dalfresco.context=alfresco -Dalfresco.protocol=http " postgres: image: postgres:13.3 mem_limit: 512m environment: - POSTGRES_PASSWORD=alfresco - POSTGRES_USER=alfresco - POSTGRES_DB=alfresco command: postgres -c max_connections=300 -c log_min_messages=LOG ports: - "5432:5432" solr6: image: alfresco/alfresco-search-services:2.0.3 mem_limit: 2g environment: # Solr needs to know how to register itself with Alfresco SOLR_ALFRESCO_HOST: "alfresco" SOLR_ALFRESCO_PORT: "8080" # Alfresco needs to know how to call solr SOLR_SOLR_HOST: "solr6" SOLR_SOLR_PORT: "8983" # Create the default alfresco and archive cores SOLR_CREATE_ALFRESCO_DEFAULTS: "alfresco,archive" # HTTPS or SECRET ALFRESCO_SECURE_COMMS: "secret" # SHARED SECRET VALUE JAVA_TOOL_OPTIONS: " -Dalfresco.secureComms.secret=secret " ports: - "8083:8983" # Browser port activemq: image: alfresco/alfresco-activemq:5.16.4-jre11-centos7 mem_limit: 1g ports: - "8161:8161" # Web Console - "5672:5672" # AMQP - "61616:61616" # OpenWire - "61613:61613" # STOMP proxy: image: alfresco/alfresco-acs-nginx:3.2.0 mem_limit: 128m environment: DISABLE_PROMETHEUS: "true" DISABLE_SYNCSERVICE: "true" DISABLE_ADW: "true" depends_on: - alfresco ports: - "8080:8080" links: - alfresco - share
There is another alternative for installation if you want to deploy without docker: https://docs.alfresco.com/content-services/community/install/ansible/
If you are planning to go with distribution based installation, you can follow this doc: https://javaworld-abhinav.blogspot.com/2021/06/setup-acs70-ass201-and-transformation-service.html
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.