Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 47A51782B89 for <~alpine/users@lists.alpinelinux.org>; Thu, 4 Mar 2021 11:55:25 +0000 (UTC) Received: by mail-lj1-f181.google.com with SMTP id a17so32972400ljq.2 for <~alpine/users@lists.alpinelinux.org>; Thu, 04 Mar 2021 03:55:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=458C49skXhTOjuThrNjX287wq26QAg8EMaexuP8rcjI=; b=hQ/ZopgduAYHdI80flY8wCln0L7iP+/Q9YBaKzpxsbaSNQUohSLkbsyeM7hqfSk37f D3Ffx0+6/ndfjLVJ/uvvG/eUUzmKsMl3EXb1FZtjAQk7YPOsLeklR86VOGybfCYgmv2y g25ONiJPtYk5pVZyQzeznMrrAlF1AYyDtn58nSCt76lq0SvZF3JlZo8iQ77zhfe/KGtq pcdZzpTG4auow6w3ogn/jLY9Ry3fSkfdqC7LSUkLS7J1xFE+aEva3wcWLh5CRDhZtTgB X18XnxqX9lZv+vIK3noo5AMfKFLhOHslH4ehYaoRaaDVvTAmpIsklxiuu1oTEHhfnh2w Ugqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=458C49skXhTOjuThrNjX287wq26QAg8EMaexuP8rcjI=; b=njsiKvpSqpv6Ft6HBHUNmZREyE2lE26QGCYV3DJJvlT7jb9oQxKRShGkdVwLN5HHMy dT5al7n7hRrRCeOKaGNXD9/oACL+M6Z9gBJxKmf1ISL7RmLfN3eJaL5XfcyK76nYbgez 7kh8ZfXw0u1CVrY1/KHsADxVjWfmEfZMMu68rwy+0RRVxBFd3IJpIdsj8wGyVVWfcDo1 szEogD8ToVXxvSyWnk+HGCntda1vL6kXKsHVnMu1845pseNJLShTwC4Pnjm1MnDeJ9Z6 A8fjTjsakImp8mZcL36wCOzl5ANncR7TQvQkjoVXTihEIqn6r26e0BB//CYfwwTIITig iaAg== X-Gm-Message-State: AOAM530cDtc1dUJBO/WSawU8DVSVUl3yk7AHpEGn8edZDaozzhR23fX6 oeMVJNPu0RYgc0cebvwznqyFl+NB5lPspbPPZDS+kBoLIDs= X-Google-Smtp-Source: ABdhPJy5qfIioyUNXkxaRXOLXbHQELc7gjz6yLIWrdVFXBOCAvOWq000WoxMf9Y55R3urMFk4IWWpwQ4F1Yl+J+W0AM= X-Received: by 2002:a2e:b6c7:: with SMTP id m7mr2032383ljo.241.1614858923506; Thu, 04 Mar 2021 03:55:23 -0800 (PST) MIME-Version: 1.0 References: <8D5539B9-2FF3-4BDD-A06C-F11716D7A8B2@goodeast.com> In-Reply-To: <8D5539B9-2FF3-4BDD-A06C-F11716D7A8B2@goodeast.com> From: Banibrata Dutta Date: Thu, 4 Mar 2021 17:25:11 +0530 Message-ID: Subject: Re: Sporadic, unpredictable docker / docker-compose (on Alpine 3.13) issues with DNS name resolution To: "~alpine/users@lists.alpinelinux.org" <~alpine/users@lists.alpinelinux.org> Content-Type: multipart/alternative; boundary="0000000000007f7f7905bcb4a45a" --0000000000007f7f7905bcb4a45a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 4, 2021 at 6:56 AM Paul Suh wrote: > I just ran into this as well. I=E2=80=99m not using it for production so = I wasn=E2=80=99t > worried about it until I saw this email. Restarting the docker daemon > seemed to fix things. I hadn=E2=80=99t used my Docker system for a almost= year > (working on other projects) and didn=E2=80=99t see this problem back then= . > > My docker system is: > Alpine 3.12.4 > Docker version 20.10.3, build 48d30b5b32e99c932b4ea3edca74353feddd83ff > docker-compose version 1.25.4, build unknown > > Running as a qemu guest on Proxmox 6.3-4, 1.11 GB RAM used of 16 GB > allocated, 4 vCPUs available. 570 MB used out of a 16 GB boot disk. Docke= r > images and containers are stored on an iSCSI mount coming from a FreeNAS > server hosted on the same hardware. > > Underlying hardware is a SuperMicro X11SDV-4C-TLN2F Server Motherboard - > Intel Xeon D-2123IT Quad-core (4 Core) 2.20 GHz, 64 GB RAM, LSI 9207-8i > HBA, 8 x 4 GB Ironwolf drives, 3 x Samsung 860 EVO 250 GB SSD, 1 x Samsun= g > EVO 860 500 GB SSD. > Thanks for the reply. In my case I've tried several things, which do not help consistently: - Restarting docker daemon - Restarting the VM - Ensuring the Virtualbox SW is latest on the host system Only thing that I'm yet to do is to reinstall docker and docker-compose. I was a bit wary of doing that, but might as well try it. Is it worth filing a bug? And where should the bug be filed? > Possibly. If our issues are indeed similar, either of us can create a bug reporrt, and other person can upvote it. Need to figure out how to report bugs on Alpine. > =E2=80=94Paul > > > > > > On Mar 3, 2021, at 4:11 PM, Banibrata Dutta > wrote: > > > > Hi Folks, > > > > Have been using docker and docker-compose inside Virtualbox VMs running > Alpine 3.13 guestOS, on a Windows 10 Professional host. The Alpine Guest > has 2 vCPUs, 4GB vRAM, and even when all containers are running the RAM > usage remains below 1GB. > > > > =E2=80=A2 Docker version 20.10.3, build > 48d30b5b32e99c932b4ea3edca74353feddd83ff > > =E2=80=A2 docker-compose version 1.27.4, build unknown > > I use 2 docker-compose .yml files to bring up, 2 set of containers. > First .yml file brings up Telgraf, InfluxDB, Grafana containers based on > images from DockerHub. The second .yml brings up a POJO-server (Java) wit= h > application and another 3 tester/simulators.They all share a dedicated > network =E2=80=98mynet=E2=80=99 (using bridged driver). The above setup s= eems to work > perfectly at times. For example: > > > > =E2=80=A2 Sometimes , containers don=E2=80=99t seem to get hostna= me assigned (i.e. > the mnemonic container-id is set as hostname, as is default) while at oth= er > times specific hostname is indeed assigned. > > > > =E2=80=A2 Then, for a few containers (not all), the inter-contain= er > DNS/name resolution doesn=E2=80=99t seem to work, but at the same time fe= w other > containers have perfectly working inter-container DNS/name resolution. Wh= en > inter-container DNS resolution does-not, if I log into the container > runtime using =E2=80=98docker exec -it bash=E2=80=99, and try to do 'ping= ', I get the > following error: > > ping: somehostname: Temporary failure in name resolution > > > > =E2=80=A2 Sometimes, some containers (not all) require the "servi= ce: > > hostname: " declaration in the docker-compose .yml file to get specific > hostname assigned to the container, but for other containers at other > times, that declaration is not needed, and only the =E2=80=9Ccontainer_na= me=E2=80=9D > declaration is enough (in .yml file) to have specific hostname for that > container !! > > > > Wondering if anyone can help figure out why is the behaviour erratic ? > What can I do to fix it ? Is this an issue with Docker only on Alpine ? > > > > Thanks in anticipation. > > > > --0000000000007f7f7905bcb4a45a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Mar 4, 2021 at 6:56 AM Paul Suh &= lt;plsuh@goodeast.com> wrote:<= br>
I just ran into = this as well. I=E2=80=99m not using it for production so I wasn=E2=80=99t w= orried about it until I saw this email. Restarting the docker daemon seemed= to fix things. I hadn=E2=80=99t used my Docker system for a almost year (w= orking on other projects) and didn=E2=80=99t see this problem back then.
My docker system is:
Alpine 3.12.4
Docker version 20.10.3, build 48d30b5b32e99c932b4ea3edca74353feddd83ff
docker-compose version 1.25.4, build unknown

Running as a qemu guest on Proxmox 6.3-4, 1.11 GB RAM used of 16 GB allocat= ed, 4 vCPUs available. 570 MB used out of a 16 GB boot disk. Docker images = and containers are stored on an iSCSI mount coming from a FreeNAS server ho= sted on the same hardware.

Underlying hardware is a SuperMicro X11SDV-4C-TLN2F Server Motherboard - In= tel Xeon D-2123IT Quad-core (4 Core) 2.20 GHz, 64 GB RAM, LSI 9207-8i HBA, = 8 x 4 GB Ironwolf drives, 3 x Samsung 860 EVO 250 GB SSD, 1 x Samsung EVO 8= 60 500 GB SSD.

Thanks for the reply. I= n my case I've tried several things, which do not help consistently:
- Restarting docker daemon
- Restarting the VM
= - Ensuring the Virtualbox SW is latest on the host system

Only thing that I'm yet to do is to reinstall docker and docker= -compose. I was a bit wary of doing that, but might as well try it.

Is it worth filing a bug? And where should the bug be filed?
=C2=A0
Possibly. If our issues are indeed similar, either= of us can create a bug reporrt, and other person can upvote it. Need to fi= gure out how to report bugs on Alpine.


=E2=80=94Paul


>
> On Mar 3, 2021, at 4:11 PM, Banibrata Dutta <banibrata.dutta@gmail.com> = wrote:
>
> Hi Folks,
>
> Have been using docker and docker-compose inside Virtualbox VMs runnin= g Alpine 3.13 guestOS, on a Windows 10 Professional host. The Alpine Guest = has 2 vCPUs, 4GB vRAM, and even when all containers are running the RAM usa= ge remains below 1GB.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Docker version 20.10.3, build 48d3= 0b5b32e99c932b4ea3edca74353feddd83ff
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 docker-compose version 1.27.4, bui= ld unknown
> I use 2 docker-compose .yml files to bring up, 2 set of containers. Fi= rst .yml file brings up Telgraf, InfluxDB, Grafana containers based on imag= es from DockerHub. The second .yml brings up a POJO-server (Java) with appl= ication and another 3 tester/simulators.They all share a dedicated network = =E2=80=98mynet=E2=80=99 (using bridged driver). The above setup seems to wo= rk perfectly at times. For example:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Sometimes , containers don=E2=80= =99t seem to get hostname assigned (i.e. the mnemonic container-id is set a= s hostname, as is default) while at other times specific hostname is indeed= assigned.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Then, for a few containers (not al= l), the inter-container DNS/name resolution doesn=E2=80=99t seem to work, b= ut at the same time few other containers have perfectly working inter-conta= iner DNS/name resolution. When inter-container DNS resolution does-not, if = I log into the container runtime using =E2=80=98docker exec -it bash=E2=80= =99, and try to do 'ping ', I get the following error:
> ping: somehostname: Temporary failure in name resolution
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Sometimes, some containers (not al= l) require the "service: > hostname: " declaration in the dock= er-compose .yml file to get specific hostname assigned to the container, bu= t for other containers at other times, that declaration is not needed, and = only the =E2=80=9Ccontainer_name=E2=80=9D declaration is enough (in .yml fi= le) to have specific hostname for that container !!
>
> Wondering if anyone can help figure out why is the behaviour erratic ?= What can I do to fix it ? Is this an issue with Docker only on Alpine ? >
> Thanks in anticipation.
>

--0000000000007f7f7905bcb4a45a--