New issue
Advanced search Search tips

Issue 845154 link

Starred by 3 users
Status: WontFix
Owner:
smbar...@chromium.org
Closed: May 2018
Cc:
tbuck...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Crostini stopped working after updates due to missing sshd configuration

Project Member Reported by flackr@chromium.org, May 21 2018 
Chrome Version: 68.0.3431.0 (Official Build) dev (64-bit)
OS: ChromeOS

What steps will reproduce the problem?
(1) Click on terminal app

What is the expected result?
Terminal window should show up.

What happens instead?
Nothing happens.

I also tried manually running the container and got the following:
/usr/bin/run_container.sh: 170: /usr/bin/run_container.sh: cannot create /run/tokens/penguin_token: Permission denied

I thought this might be the same as  issue 845001  but the symptoms seem to be different so I thought I'd file a separate bug.

Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by flackr@chromium.org, May 21 2018

Summary: Crostini stopped working after updates due to missing sshd configuration (was: Crostini stopped working after updates)
Actually, it looks like on the first run the error is slightly different:
run_container: warning: container token not supplied; garcon may not function
error: Missing source '/run/sshd/penguin/authorized_keys' for disk 'ssh_authorized_keys'
Try `lxc info --show-log penguin` for more info
run_container: error: Failed to start container 'penguin'

So I'm guessing it lost my sshd configuration. Writing the authorized_keys file gives me an error about ssh_host_key which I then replaced with my ssh private key and the container seemed to work again.

Comment 2 by vapier@chromium.org, May 21 2018

Owner: smbar...@chromium.org

Comment 3 by smbar...@chromium.org, May 21 2018 

Can you check which component version you're using? In the VM, run `cat /etc/lsb-release`.

You should be on 10696.0.0 which has some fixes for SSH bind mounts. If you're on an older version, make sure to update under chrome://components, and then restart the VM by signing out of Chrome OS.

Comment 4 by flackr@chromium.org, May 21 2018 

chrome://components said that cros-termina was Version: 10685.0.0 (Shouldn't this auto-update?). After clicking update it said version 10696.0.0. Running the container from crosh now works.

Terminal, however, still does not work, but this seems to be described by  issue 845001 .

Comment 5 by smbar...@chromium.org, May 22 2018

Status: WontFix (was: Untriaged)
The component does auto-update, but I'm not sure of the interval. Allegedly it's every 5 hours...ish.

For the Terminal hanging problem, the tracking bug is  issue 843682  which should be fixed with the next dev push.

Comment 6 by flackr@chromium.org, May 22 2018 

FWIW, this problem seemed to be around for quite a long time of use of the Chromebook (at least a week). I suspect the auto-update wasn't happening.
►

Sign in to add a comment