Skip to content

Docker key.json has invalid contents and the system refuses to boot #1706

@mdcollins05

Description

@mdcollins05

Describe the issue you are experiencing

I'm 2 for 2 now on this. Each reboot after an upgrade to the OS somehow leads to a corrupt key.json file on my Home Assistant OS install. Each time I have to boot via a recovery USB drive, mount the right partition (in this case /dev/sda7) and delete the /etc/docker/key.json file to fix the system. I don't intentionally manage this file in any way, nor do I care about the contents, so the Docker generated version is just fine with me.

As a test, I fixed the file, booted into Home Assistant and then restarted back into my recovery USB to inspect the contents. They were valid JSON instead of the invalid content.

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

6.6

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. Update Home Assistant OS via supervisor in the web interface
  2. Home Assistant then fails to reboot into a valid system

Anything in the Supervisor logs that might be useful for us?

Nothing in there from the update or prior to the successful boot of my system.

Anything in the Host logs that might be useful for us?

Nothing

System Health information

System Health

version core-2021.11.1
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.9.7
os_name Linux
os_version 5.10.88
arch x86_64
timezone America/Los_Angeles
Home Assistant Community Store
GitHub API ok
Github API Calls Remaining 4890
Installed Version 1.16.0
Stage running
Available Repositories 932
Installed Repositories 9
Home Assistant Cloud
logged_in true
subscription_expiration January 13, 2022, 4:00 PM
relayer_connected true
remote_enabled false
remote_connected false
alexa_enabled true
google_enabled false
remote_server us-west-2-1.ui.nabu.casa
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 7.1
update_channel stable
supervisor_version supervisor-2021.12.2
docker_version 20.10.9
disk_total 219.4 GB
disk_used 7.4 GB
healthy true
supported true
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons chrony (2.2.1), Samba share (9.5.1), Z-Wave JS to MQTT (0.27.0), Node-RED (10.1.1), Terminal & SSH (9.2.1), Network UPS Tools (0.9.0)
keymaster
zwave_integration zwave_js
network_status on
Lovelace
dashboards 4
resources 6
views 8
mode storage

Additional information

This is the contents of the file:
PXL_20220106_031713090

And this is the log entries from journalctl:
PXL_20220106_032525837

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions