One of the configured repositories failed (Unknown)

[antonioluzzi]

Hi, I have tried to build the Dockerfile, but I failed because yum didn't have enough cached data to continue. I have modified Dockerfile with my proxy configuration:

RUN echo "proxy=http://xx.xx.XX.xx:3128" >> /etc/yum.conf &&
echo "proxy_username=luzzia" >> /etc/yum.conf &&
echo "proxy_password=xxxxx" >> /etc/yum.conf RUN export http_proxy=http://xxx:[email protected]:3128

This is the stacktracke of exception:

One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=<repoid> ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>
    or
        subscription-manager repos --disable=<repoid>

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64

[killerboot]

Hi, Does this configuration work in a non docker environment? If you spin up VM with CentOS for example. Depending on your host OS, Docker will be running containers in an isolated network so the proxy might not be reachable for some reason. Or you need to restart network adaptor in CentOS after setting the proxy.

The docker image was built recently without using a proxy for yum, see latest tag in DockerHub https://cloud.docker.com/u/alfresco/repository/docker/alfresco/alfresco-content-repository-community

We are using the official CentOS docker image underneath: https://github.com/Alfresco/alfresco-docker-base-java/blob/master/Dockerfile#L6, so it may be worth asking their community as well.