<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Login on Bottlerocket</title><link>https://bottlerocket.dev/en/os/1.55.x/login/</link><description>Recent content in Login on Bottlerocket</description><generator>Hugo</generator><language>en</language><atom:link href="https://bottlerocket.dev/en/os/1.55.x/login/index.xml" rel="self" type="application/rss+xml"/><item><title>Regaining Access to a Bottlerocket Node</title><link>https://bottlerocket.dev/en/os/1.55.x/login/regaining-access/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://bottlerocket.dev/en/os/1.55.x/login/regaining-access/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The standard way to access a shell on a Bottlerocket node is to use either the admin container or the control container.
In some cases where both the admin and control containers are disabled, it is still possible to regain access to a Bottlerocket node.&lt;/p&gt;
&lt;h2 id="solution-description"&gt;Solution Description&lt;/h2&gt;
&lt;p&gt;In general, the solution is to mount the &lt;a href="https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/api/apiclient/README.md"&gt;API client&lt;/a&gt; and API socket into a container on the Bottlerocket node and use the API client to re-enable the admin container, control container, or both.&lt;/p&gt;</description></item></channel></rss>