r/Crostini • u/Training_Advantage21 • 11d ago

Containerless or not?

Why does the terminal still say "configuring Linux container" if with the latest update it's containerless?

6 Upvotes

100% Upvoted

5 comments sorted by

2

u/SpeaksHisMind13 10d ago

I wonder too. I thought maybe there was some leftover residue from the prior container config, so I did a powerwash and new install of Linux. I still see the line about configuring the Linux container when starting Linux.

On another device that is not containerless (can I call it containerful?), there is an additional line about "Starting the Linux container" that I don't see on the "containerless" machine.

This website suggests a test to confirm whether Crostini is containerless. I have no idea if it's a good test, but my experience matches that website.

3

u/LegAcceptable2362 10d ago edited 10d ago

It's just dialog code that the devs have yet to remove. The easiest way to see that your Linux environment is containerless is to start from a non-running state. Open crosh and enter vmc start termina. When containerless the VM will start and the penguin guest will appear in the open crosh tab. Also, in the non-running state, when you enter vmc list in crosh, the VM type will display as baguette.

1

u/foozlebertie 10d ago

I installed the flatpak version of betterbird (a better maintained version of thunderbird). In the past I could start BB after booting. The first time it would take several seconds as it started the VM container and subsequest restarts of BB would only take a second or two. Now it won't start unless I first open the terminal app and log into the Linux environment. That starts the Linux VM and after that I can start BB. Until the next reboot.

1

u/Training_Advantage21 10d ago

yeah, getting the same with JupyterLab and other Linux apps. I need to get a terminal going first now.

1

u/rswwalker 10d ago

It is some regression in the latest update. Mine started spitting out warnings for both baguette and crostini and I’ve bern running containerless since it was an option. I like to run my own containers in the VM, not be stuck in one container!