Tailscale installed within crostini (chromeos Linux container) causes container to crash on future startups

[TheDabblingDuck]

What is the issue?

After installing tailscale on the crostini linux VM in chromeos, it initially worked as expected. However after stopping the linux VM, I was no longer able to start it at all. Clicking on "penguin" in the chromeos terminal window causes a new tab to open and quickly close as there seems to be a crash on starting the Linux container.

The Linux container is still accessible via the following commands in the crosh (Chrome os native) terminal. However accessing it this way does not seem to allow running GUI apps.
vmc start termina
lxc start penguin
lxc exec penguin bash' At this point, tailscale down` can be executed but does not fix the issue

Steps to reproduce

1. Create a new Linux container in chromeos
2. Install tailscale with the command curl -fsSL https://tailscale.com/install.sh | sh
3. Login to tailscale, which works as intended
4. Stop the Linux container with sudo shutdown now or a reboot of the machine
5. Attempt to restart the linux container from the chromeos 'terminal' app

Are there any recent changes that introduced the issue?

No response

OS

Linux, Other

OS version

ChromeOS Version 125.0.6422.31 (Official Build) beta (64-bit)

Tailscale version

1.66.1

Other software

No response

Bug report

No response

[danopia]

I experienced this as a user when tailscale was set to auto start within Crostini.
I believe this was related to ChromeOS VMs and Tailscale using an overlapping CGNAT subnet. Something that the tailscale team has been aware of in various ways over the years.
I worked around by not setting auto start on tailscaled, and instead manually starting the tailscaled service when needed.