public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: No network available during task do_install on debian bullseye/5.10 host - but on a debian buster/4.19 host network is available
Date: Fri, 8 Mar 2024 10:18:43 +0100	[thread overview]
Message-ID: <ZerX815JqU9Do9P4@ilbers.de> (raw)
In-Reply-To: <AS4PR10MB5149E76517F8A3576C2726EEFA202@AS4PR10MB5149.EURPRD10.PROD.OUTLOOK.COM>

Hello Bj�rn,

On 2024-03-07 15:33, 'Kaufmann, Bjoern' via isar-users wrote:
> In the first scenario the build runs inside the docker container on a debian buster VM with 4.19.0-26 kernel. In this scenario the logfile "build/tmp/work/debian-bullseye -amd64/my-recipe/2023.1-r0/temp/log.do_install" looks as follows:
...
> 944: eth0@if945: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
>     link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
>     inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
>        valid_lft forever preferred_lft forever

Sounds like a docker (or some combination of VM + kernel + buster + docker)
issue. The same docker version and global configuration (if any) under buster
and bullseye? Is "VM" VMware under Windows?

With kind regards,
Baurzhan

  reply	other threads:[~2024-03-08  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Adpwo/NmYIMx9YhTRFidWKEPdq+1RQEj/j2AAD71GIAAIhJlAAAAYZuAAAAWgEA=>
2024-03-07 15:33 ` Kaufmann, Bjoern
2024-03-08  9:18   ` Baurzhan Ismagulov [this message]
2024-03-11  8:24     ` Bjoern Kaufmann
2024-03-13 10:48   ` Anton Mikanovich
2024-03-14 16:50     ` Bjoern Kaufmann
2024-03-15  9:06       ` Bjoern Kaufmann
2024-03-15  9:17         ` Anton Mikanovich
2024-03-15  9:28           ` Schmidt, Adriaan
2024-03-18 13:58             ` Bjoern Kaufmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZerX815JqU9Do9P4@ilbers.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox