X-Original-To: alpine-user@lists.alpinelinux.org
Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25])
	by lists.alpinelinux.org (Postfix) with ESMTP id CC2F6F84F20
	for <alpine-user@lists.alpinelinux.org>; Wed,  3 Apr 2019 14:53:48 +0000 (UTC)
Received: from mx1.tetrasec.net (mail.local [127.0.0.1])
	by mx1.tetrasec.net (Postfix) with ESMTP id 42F419E1D52;
	Wed,  3 Apr 2019 14:53:48 +0000 (UTC)
Received: from ncopa-macbook.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: alpine@tanael.org)
	by mx1.tetrasec.net (Postfix) with ESMTPSA id 8CF519E0081;
	Wed,  3 Apr 2019 14:53:47 +0000 (UTC)
Date: Wed, 3 Apr 2019 15:53:40 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Tristan Kohl <tristan@iceity.de>
Cc: alpine-user@lists.alpinelinux.org
Subject: Re: [alpine-user] APK hangs on some packages
Message-ID: <20190403155340.7b4df67e@ncopa-macbook.copa.dup.pw>
In-Reply-To: <bba9404b-2e6c-6d76-6fe1-256d393cc181@iceity.de>
References: <bba9404b-2e6c-6d76-6fe1-256d393cc181@iceity.de>
X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl)
X-Mailinglist: alpine-user
Precedence: list
List-Id: Alpine Development <alpine-user.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-user+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-user@lists.alpinelinux.org>
List-Help: <mailto:alpine-user+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-user+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 3 Apr 2019 16:14:52 +0200
Tristan Kohl <tristan@iceity.de> wrote:

> Hey guys,
> 
> I build most of my images on top of Alpine. However for the last couple
> of days I come accross some weird problem which causes apk add to hang
> for some packages. I tried following Dockerfile on an Alpine 3.9 host
> with Docker 18.09.1-ce and my Void Linux desktop with docker 18.09.4.
> 
> 
> FROM alpine:latest
> 
> RUN apk add --no-cache build-base cmake git linux-headers perl
> 
> <snip>
> 
> 
> 
> #> docker build -t test .  
> Sending build context to Docker daemon   2.56kB
> Step 1/18 : FROM alpine:latest
>  ---> 5cb3aa00f899  
> Step 2/18 : RUN apk add --no-cache build-base cmake git linux-headers perl
>  ---> Running in 9736754a88cc  
> fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz
> fetch
> http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz
> (1/41) Upgrading musl (1.1.20-r3 -> 1.1.20-r4)
> (2/41) Installing binutils (2.31.1-r2)
> (3/41) Installing libmagic (5.35-r0)
> (4/41) Installing file (5.35-r0)
> (5/41) Installing gmp (6.1.2-r1)
> (6/41) Installing isl (0.18-r0)
> (7/41) Installing libgomp (8.2.0-r2)
> (8/41) Installing libatomic (8.2.0-r2)
> (9/41) Installing libgcc (8.2.0-r2)
> (10/41) Installing mpfr3 (3.1.5-r1)
> (11/41) Installing mpc1 (1.0.3-r1)
> (12/41) Installing libstdc++ (8.2.0-r2)
> (13/41) Installing gcc (8.2.0-r2)
> 
> 
> Process hangs here (I let it alone for >1h and then killed it), but
> running an Alpine instance via
> 
> docker run -it --rm alpine
> 
> and trying to install those packages manually one by one has worked both
> times I tried this (today and on Sunday). However, installing gcc or
> build-base did not work (aka. hang) two or three times and only
> succedded on consecutive tries. Weirdly enough, calling
> 
> apk add g++
> 
> pulled in gcc and finished within seconds as I was used to...
> 
> So I "think" there is no problem with docker's network setup but I have
> no idea of the inner workings so please tell me where to look if you
> think this is a docker issue.

This sounds like an MTU blackhole issue. I know that Fastly
(dl-cdn.a.o) does not have a working PMTU, because they filter
out need-to-frag ICMP packets. I guess its their DDoS feature that
does.

Check the MTU size in your container, on the host and in your LAN.

If you host and container have differnet MTU size, then you can
probably resolve it with clamp-mss on your host.

There is also a tool called 'mtu' that can help you find where a
blackhole is, in case it is a problem with your ISP or somewhere else
on the internet.

  apk add mtu

-nc


> 
> Cheers,
> Tristan
> 
> P.S.: Previous builds ~2 weeks ago worked and there was no docker update
> as far as I can remember.
> 
> 
> ---
> Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
> Help:         alpine-user+help@lists.alpinelinux.org
> ---
> 



---
Unsubscribe:  alpine-user+unsubscribe@lists.alpinelinux.org
Help:         alpine-user+help@lists.alpinelinux.org
---