From dacf32a64281e794a7276319873768213b83f6de Mon Sep 17 00:00:00 2001 From: Maxime Beauchamp <15185355+baktun14@users.noreply.github.com> Date: Tue, 8 Oct 2024 14:52:08 -0400 Subject: [PATCH] chore: update console FAQ + add amd64 cpu support (#399) --- .../deployments/DeploymentLeaseShell.tsx | 7 +- apps/deploy-web/src/pages/faq/index.tsx | 92 +++++++++---------- packages/network-store/src/network.store.ts | 2 +- 3 files changed, 48 insertions(+), 53 deletions(-) diff --git a/apps/deploy-web/src/components/deployments/DeploymentLeaseShell.tsx b/apps/deploy-web/src/components/deployments/DeploymentLeaseShell.tsx index d78e77baf..7c92d7dcc 100644 --- a/apps/deploy-web/src/components/deployments/DeploymentLeaseShell.tsx +++ b/apps/deploy-web/src/components/deployments/DeploymentLeaseShell.tsx @@ -283,12 +283,7 @@ export const DeploymentLeaseShell: React.FunctionComponent = ({ leases }) {isConnectionClosed && ( - The connection to your Akash Console Shell was lost. ( - - More Info - - - ) + The connection to your Akash Console Shell was not established or lost. )} diff --git a/apps/deploy-web/src/pages/faq/index.tsx b/apps/deploy-web/src/pages/faq/index.tsx index f7c06cb97..f8a6f618d 100644 --- a/apps/deploy-web/src/pages/faq/index.tsx +++ b/apps/deploy-web/src/pages/faq/index.tsx @@ -6,6 +6,34 @@ import Layout from "@src/components/layout/Layout"; import { Title } from "@src/components/shared/Title"; const FaqEntries = [ + { + anchor: "cpu-support", + title: "Which CPUs are officially supported?", + content: ( + <> +

+ + Only x86_64 processors + {" "} + are officially supported for Akash deployments. This may change in the future and when ARM processors are supported it will be announced and + documented. +

+

+ If you're on MacOS or linux, you can specify the{" "} + + target platform + {" "} + when building your docker image. For example, if you're using a Dockerfile you can use the following command: +

+

+ docker build -t my-image --platform linux/amd64 . +

+ + ) + }, { anchor: "lease-closed", title: "My lease is closed, but the deployment isn't.", @@ -34,36 +62,6 @@ const FaqEntries = [ ) }, - { - anchor: "shell-lost", - title: "Can't access shell: 'The connection to your Akash Console Shell was lost.'", - content: ( - <> -

- There is a{" "} - - known issue - {" "} - where the shell access will stop working if the provider pod gets restarted. Here's two workarounds you can try: -

-
    -
  • - You can try the "UPDATE DEPLOYMENT" button in the "UPDATE" tab of your deployment. Even without changing your SDL, this should temporarily restore - the shell access. -
    - Update Deployment -
  • -
  • - A permanent solution would be to add your own ssh access to your deployment, here is an{" "} - - example SDL - {" "} - with ssh. -
  • -
- - ) - }, { anchor: "shell-arrows-and-completion", title: "Shell: UP arrow and TAB autocompletion does not work", @@ -130,23 +128,25 @@ export default function FaqPage() { Frequently Asked Questions -
    - {FaqEntries.map(entry => ( -
  • - {entry.title} -
  • - ))} -
+
+
    + {FaqEntries.map(entry => ( +
  • + {entry.title} +
  • + ))} +
-
- {FaqEntries.map(entry => ( -
- - {entry.title} - - {entry.content} -
- ))} +
+ {FaqEntries.map(entry => ( +
+ + {entry.title} + + {entry.content} +
+ ))} +
); diff --git a/packages/network-store/src/network.store.ts b/packages/network-store/src/network.store.ts index f919c4a90..6f13aff3f 100644 --- a/packages/network-store/src/network.store.ts +++ b/packages/network-store/src/network.store.ts @@ -105,7 +105,7 @@ export class NetworkStore { } } - private initiateNetworkFromUrlQuery(): Network["id"] { + private initiateNetworkFromUrlQuery(): Network["id"] | undefined { if (typeof window === "undefined") { return; }