> I think lxd init should account for the fact that not all interfaces are 1500 by default.
I agree with this. Even if we can make it work on GCE, the standard requires that all interfaces in a broadcast domain should have the same MTU. A mismatch even between the host and the container should cause problems, shouldn't it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2073620 Title: http timeout from lxd container using n4-highcpu-2 gce instances Status in linux-gcp package in Ubuntu: New Bug description: When I start a n4-highcpu-2 instance in gce, I see that from an lxd container the command `apt update` returns in a timeout. This is reproduced just on n4-highcpu-2 (used us-east1-b) instances with different lxd versions (tried latest/stable and 5.3.x). steps to reproduce: $ snap install lxd --channel latest/stable $ lxd init --auto $ lxd.lxc launch ubuntu:noble $ lxd.lxc exec moved-chipmunk -- apt update 0% [Waiting for headers] [Waiting for headers] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2073620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
