arpradhan/amazonlinux-node

Docker image for amazon linux installed with node

amazonlinux-node's Issues

Access Denied

Hi,

Thanks for sharing your Dockerfile. When I create the image from my laptop using docker build -f Dockerfile.node -t amazonlinux:latest ., it fails eventually.

The error is

 ❯ docker build -f Dockerfile.node -t amazonlinux:latest .
Sending build context to Docker daemon  74.75kB
Step 1/4 : FROM amazonlinux:latest
latest: Pulling from library/amazonlinux
f64ae36417d7: Pull complete
Digest: sha256:2a6e194ea0e495b7cb65528a9772e8af113f31c46a140a91a15eaa22fd9e9627
Status: Downloaded newer image for amazonlinux:latest
 ---> 01da4f8f9748
Step 2/4 : RUN yum install gcc44 gcc-c++ libgcc44 cmake wget tar gzip make -y
 ---> Running in 3f0b47e30c53
Loaded plugins: ovl, priorities


 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: amzn2-core/2/x86_64
Could not retrieve mirrorlist http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list error was
12: Timeout on http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list: (28, 'Resolving timed out after 5000 milliseconds')
The command '/bin/sh -c yum install gcc44 gcc-c++ libgcc44 cmake wget tar gzip make -y' returned a non-zero code: 1

I tried accessing http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list and this is was the result I got, https://cdn.amazonlinux.com/2/core/2.0/x86_64/f411915d42f2ca5dd67a9188146d5145ea4be8fe27832236109953a951c16df4

I accessed that new link and I got

 ❯ curl https://cdn.amazonlinux.com/2/core/2.0/x86_64/f411915d42f2ca5dd67a9188146d5145ea4be8fe27832236109953a951c16df4
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>DDDA5F06AF89D29D</RequestId><HostId>NgjgaitDhBXJa9I2gsxvpRLM3TTH5NWs0tWQTrgVFqjQ8yv+9CCWsda7EzPsy4qmjr4LVs7ABMM=</HostId></Error>