Hi all,

for the last couple of days, this Dockerfile:
'''
FROM frolvlad/alpine-glibc

RUN apk update && \
     apk --no-cache add bash ca-certificates wget libxext libxrender 
libstdc++
...
'''

fails to build with

'''
Step 2/16 : RUN apk update &&     apk --no-cache add bash 
ca-certificates wget libxext libxrender libstdc++
  ---> Running in 0cdc0c2def31
fetch 
https://dl-cdn.alpinelinux.org/alpine/v3.17/main/x86_64/APKINDEX.tar.gz
fetch 
https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.17/main: temporary error 
(try again later)
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.17/main: No 
such file or directory
ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.17/community: temporary 
error (try again later)
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.17/community: 
No such file or directory
'''

Is there a server problem or frolvlad container problem or something else?

TIA,
Dima

frolvlad/alpine-glibc is in no way related to alpinelinux developers.
You'll have to ask for help from people behind alpine-glibc.

On Sun, Apr 23, 2023 at 9:05 PM dmitri maziuk <dmitri.maziuk@gmail.com> wrote:
>
> Hi all,
>
> for the last couple of days, this Dockerfile:
> '''
> FROM frolvlad/alpine-glibc
>
> RUN apk update && \
>      apk --no-cache add bash ca-certificates wget libxext libxrender
> libstdc++
> ...
> '''
>
> fails to build with
>
> '''
> Step 2/16 : RUN apk update &&     apk --no-cache add bash
> ca-certificates wget libxext libxrender libstdc++
>   ---> Running in 0cdc0c2def31
> fetch
> https://dl-cdn.alpinelinux.org/alpine/v3.17/main/x86_64/APKINDEX.tar.gz
> fetch
> https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
> ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.17/main: temporary error
> (try again later)
> WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.17/main: No
> such file or directory
> ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.17/community: temporary
> error (try again later)
> WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.17/community:
> No such file or directory
> '''
>
> Is there a server problem or frolvlad container problem or something else?
>
> TIA,
> Dima

On 2023-04-23 1:43 PM, Konstantin Kulikov wrote:
> frolvlad/alpine-glibc is in no way related to alpinelinux developers.
> You'll have to ask for help from people behind alpine-glibc.

Well thank you for your very helpful reply but the question was whether

>> https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
>> ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.17/main: temporary error
>> (try again later)

is a problem with dl-cdn.alpinelinux.org which I expect is not 
maintained by "people behind alpine-glibc".

Any other takers?

Dima

On Sun Apr 23, 2023 at 8:54 PM CEST, dmitri maziuk wrote:
> On 2023-04-23 1:43 PM, Konstantin Kulikov wrote:
> > frolvlad/alpine-glibc is in no way related to alpinelinux developers.
> > You'll have to ask for help from people behind alpine-glibc.
>
> Well thank you for your very helpful reply but the question was whether
>
> >> https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
> >> ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.17/main: temporary error
> >> (try again later)
>
> is a problem with dl-cdn.alpinelinux.org which I expect is not 
> maintained by "people behind alpine-glibc".

there is no problem with it, so if you see that it's because you have actual
networking issues (from inside the container).

>
> Any other takers?
>
> Dima

On 2023-04-23 1:57 PM, alice wrote:

> there is no problem with it, so if you see that it's because you have actual
> networking issues (from inside the container).

Thank you, that I can work with.

Dima

On 2023-04-23 1:57 PM, alice wrote:

> there is no problem with it, so if you see that it's because you have actual
> networking issues (from inside the container).

Just to close this, the issue appears to be with my infra provider: it 
seems the VM I'm using isn't forwarding packets. I probably should have 
checked that first, but I've built containers there before so this is 
unexpected.

thanks all,
Dima