Isaiah

Self-hostable clone of lazydocker for the web.
Manage your Docker fleet with ease

Table of Contents - Install - Configure

Table of Contents

• Introduction
• Features
• Deployment and Examples
  • Deploy with Docker
  • Deploy with Docker Compose
  • Deploy as a standalone application
    • Using an existing binary
    • Building the binary manually
    • Updating
• Multi-node deployment
  • General information
  • Setup
• Multi-host deployment
  • General information
  • Setup
• Forward Proxy Authentication / Trusted SSO
• Configuration
• Theming
• Troubleshoot
• Security
• Disclaimer
• Contribute
• Credits

Introduction

Isaiah is a self-hostable service that enables you to manage all your Docker resources on a remote server. It is an attempt at recreating the lazydocker command-line application from scratch, while making it available as a web application without compromising on the features.

Features

Isaiah has all these features implemented :

• For stacks :
  • Bulk update, Bulk pause, Bulk unpause, Bulk restart, Bulk down
  • Up, Down, Pause, Unpause, Stop, Restart, Update
  • Create and Edit stacks using docker-compose.yml files in your browser
  • Inspect (live logs, docker-compose.yml, services)
• For containers :
  • Bulk stop, Bulk remove, Bulk restart, Bulk update, Prune
  • Remove, Pause, Unpause, Restart, Rename, Update, Edit, Open in browser
  • Open a shell inside the container (from your browser)
  • Inspect (live logs, stats, env, full configuration, top)
• For images :
  • Prune
  • Remove
  • Run (create and start a container using the image)
  • Open on Docker Hub
  • Pull a new image (from Docker Hub)
  • Bulk pull all latest images (from Docker Hub)
  • Inspect (full configuration, layers)
• For volumes :
  • Prune
  • Remove
  • Browse volume files (from your browser, via shell)
  • Inspect (full configuration)
• For networks :
  • Prune
  • Remove
  • Inspect (full configuration)
• Built-in automatic Docker host discovery
• Built-in authentication by master password (supplied raw or sha256-hashed)
• Built-in authentication by forward proxy authentication headers (e.g. Authelia / Trusted SSO)
• Built-in terminal emulator (with support for opening a shell on the server)
• Responsive for Desktop, Tablet, and Mobile
• Support for multiple layouts
• Support for custom CSS theming (with variables for colors already defined)
• Support for keyboard navigation
• Support for mouse navigation
• Support for search through Docker resources and container logs
• Support for ascending and descending sort by any supported field
• Support for customizable user settings (line-wrap, timestamps, prompt, etc.)
• Support for custom Docker Host / Context.
• Support for extensive configuration with .env
• Support for HTTP and HTTPS
• Support for standalone / proxy / multi-node / multi-host deployment

On top of these, one may appreciate the following characteristics :

• Written in Go (for the server) and Vanilla JS (for the client)
• Holds in a ~4 MB single file executable
• Holds in a ~4 MB Docker image
• Works exclusively over Websocket, with very little bandwidth usage
• Uses the official Docker SDK for 100% of the Docker features

For more information, read about Configuration and Deployment.

Deployment and Examples

Please make sure that Docker 23.0.0+ is installed before proceeding, or consider updating beforehand.

If you are using the Stacks feature to manage Docker Compose stacks, please use Docker 26.0.0+.

The default password is : one-very-long-and-mysterious-secret

Deploy with Docker

You can run Isaiah with Docker on the command line very quickly.

You can use the following commands :

# Create a .env file
touch .env

# Edit .env file ...

# Option 1 : Run Isaiah attached to the terminal (useful for debugging)
docker run \
  --env-file .env \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  -p <YOUR-PORT-MAPPING> \
  mosswill/isaiah

# Option 2 : Run Isaiah as a daemon
docker run \
  -d \
  --env-file .env \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  -p <YOUR-PORT-MAPPING> \
  mosswill/isaiah

# Option 3 : Quick run with default settings
docker run -v /var/run/docker.sock:/var/run/docker.sock:ro -p 3000:3000 mosswill/isaiah

Note : Since version 1.36.2, all the Docker images are also mirrored on Github. You can run from ghcr.io/will-moss/isaiah:latest

Deploy with Docker Compose

To help you get started quickly, multiple example docker-compose files are located in the "examples/" directory.

Here's a description of every example :

• docker-compose.simple.yml: Run Isaiah as a front-facing service on port 80., with environment variables supplied in the docker-compose file directly.

• docker-compose.volume.yml: Run Isaiah as a front-facing service on port 80, with environment variables supplied as a .env file mounted as a volume.

• docker-compose.ssl.yml: Run Isaiah as a front-facing service on port 443, listening for HTTPS requests, with certificate and private key provided as mounted volumes.

• docker-compose.proxy.yml: A full setup with Isaiah running on port 80, behind a proxy listening on port 443.

• docker-compose.traefik.yml: A sample setup with Isaiah running on port 80, behind a Traefik proxy listening on port 443.

• docker-compose.agent.yml: A sample setup with Isaiah operating as an Agent in a multi-node deployment.

• docker-compose.host.yml: A sample setup with Isaiah expecting to communicate with other hosts in a multi-host deployment.

When your docker-compose file is on point, you can use the following commands :

# Option 1 : Run Isaiah in the current terminal (useful for debugging)
docker-compose up

# Option 2 : Run Isaiah in a detached terminal (most common)
docker-compose up -d

# Show the logs written by Isaiah (useful for debugging)
docker logs <NAME-OF-YOUR-CONTAINER>

Warning : Always make sure that your Docker Unix socket is mounted, else Isaiah won't be able to communicate with the Docker API.

Note : Since version 1.36.2, all the Docker images are also mirrored on Github. You can pull from ghcr.io/will-moss/isaiah:latest

Deploy as a standalone application

You can deploy Isaiah as a standalone application, either by downloading an existing binary that fits your architecture, or by building the binary yourself on your machine.

Using an existing binary

An install script was created to help you install Isaiah in one line, from your terminal :

As always, check the content of every file you pipe in bash

# Multiple options are provided to cater to differences between
# operating systems and versions of curl.

# Option 1:
bash <(curl -s https://raw.githubusercontent.com/will-moss/isaiah/master/scripts/remote-install.sh)

# Option 2:
curl -s https://raw.githubusercontent.com/will-moss/isaiah/master/scripts/remote-install.sh > install.sh
chmod 755 install.sh
./install.sh

This script will try to automatically download a binary that matches your operating system and architecture, and put it in your /usr/[local/]bin/ directory to ease running it. Later on, you can run :

# Create a new .env file
touch .env

# Edit .env file ...

# Run Isaiah
isaiah

# Check current version
isaiah -v

In case you feel uncomfortable running the install script, you can head to the Releases, find the binary that meets your system, and install it yourself.

Building the binary manually

In this case, make sure that your system meets the following requirements :

• You have Go 1.21 installed
• You have Node 20+ installed along with npm and npx

When all the prerequisites are met, you can run the following commands in your terminal :

As always, check the content of everything you run inside your terminal

# Retrieve the code
git clone https://github.com/will-moss/isaiah
cd isaiah

# Run the local install script
./scripts/local-install.sh

# Move anywhere else, and create a dedicated directory
cd ~
mkdir isaiah-config
cd isaiah-config

# Create a new .env file
touch .env

# Edit .env file ...

# Option 1 : Run Isaiah in the current terminal
isaiah

# Option 2 : Run Isaiah as a background process
isaiah &

# Option 3 : Run Isaiah using screen
screen -S isaiah
isaiah
<CTRL+A> <D>

# Optional : Remove the cloned repository
# cd <back to the cloned repository>
# rm -rf ./isaiah

The local install script will try to perform a production build on your machine, and move isaiah to your /usr/[local/]bin/ directory to ease running it. In more details, the following actions are performed :

• Local install of Babel, LightningCSS, Less, and Terser
• Prefixing, Transpilation, and Minification of CSS and JS assets
• Building of the Go source code into a single-file executable (with CSS and JS embed)
• Cleaning of the artifacts generated during the previous steps
• Removal of the previous isaiah executable, if any in /usr/[local/]bin/
• Moving the new isaiah executable in /usr/[local/]bin with 755 permissions.

If you encounter any issue during this process, please feel free to tweak the install script or reach out by opening an issue.

Updating

You can update your isaiah executable by running the install script once again, or by performing the steps to build it manually once again. Both procedures will take care of overwriting any existing executable.

For Docker deployments, just pull the latest image and recreate your container / stack.

Multi-node deployment

Using Isaiah, you can manage multiple nodes with their own distinct Docker resources from a single dashboard.

Before delving into that part, please get familiar with the general information below.

General information

You may find these information useful during your setup and reading :

• Isaiah distinguishes two types of nodes : Master and Agent.
• The word node refers to any machine (virtual or not) holding Docker resources.
• The Master node has three responsabilities :
  • Serving the web interface.
  • Managing the Docker resources inside the environment on which it is already installed.
  • Acting as a central proxy between the client (you) and the remote Agent nodes.
• The Master node has the following characteristics :
  • There should be only one Master node in a multi-node deployment.
  • The Master node should be the only part of your deployment that is publicly exposed on the network.
• The Agent nodes have the following characteristics :
  • They are headless instances of Isaiah, and they can't exist without a Master node.
  • As with the Master node, they have their own authentication if you don't disable it explicitly.
  • On startup, they perform registration with their Master node using as a Websocket client
  • For as long as the Master node is alive, a Websocket connection remains established between them.
  • The Agent node should never be publicly exposed on the network.
  • The Agent node never communicates with the client (you). Everything remains between the nodes.
  • There is no limit to how many Agent nodes can connect to a Master node.

In other words, one Master acts as a Proxy between the Client and the Agents.
For example, when a Client wants to stop a Docker container inside an Agent, the Client first requests it from Master. Then, Master forwards it to the designated Agent. When the Agent has finished, they reply to Master, and Master forwards that response to the initial Client.

Schematically, it looks like this :

• Client ------------> Master : Stop container C-123 on Agent AG-777
• Master ------------> Agent : Stop container C-123
• Agent ------------> Master : Container C-123 was stopped
• Master ------------> Client : Container C-123 was stopped on Agent AG-777

Now that we understand how everything works, let's see how to set up a multi-node deployment.

Setup

First, please ensure the following :

• Your Master node is running, exposed on the network, and available in your web browser
• Your Agent node has Isaiah installed and configured with the following settings :
  • SERVER_ROLE equal to Agent
  • MASTER_HOST configured to reach the Master node
  • MASTER_SECRET equal to the AUTHENTICATION_SECRET setting on the Master node, or empty when authentication is disabled
  • AGENT_NAME equal to a unique string of your choice

Then, launch Isaiah on each Agent node, and you should see logs indicating whether connection with Master was established. Eventually, you will see Master or The name of your agent in the lower right corner of your screen as agents register.

If encounter any issue, please read the Troubleshoot section.

You may want to note that you don't need to expose ports on the machine / Docker container running Isaiah when it is configured as an Agent.

Feature: When Master and Agent nodes have the same secret, no authentication prompt will be required after logging into Master

Additional notes on configuration

Please note that, in a multi-node deployment, the following affirmations about the configuration are true :

• The configuration settings that have no comment about multi-node deployments are all both available for Master and Agent nodes, except for SSL_ENABLED and SERVER_PORT since Agent nodes do not behave like a server that listens for incoming connections.
  • So, for instance, you could have a different TABS_ENABLED setting for each node, regardless of them being a Master or Agent.
  • These settings were all designed to work in a single-node deployment initially, without multi-node enabled at all, but they also work in a multi-node deployment transparently due to how the code is written.
• The configuration settings that have a comment about multi-node deployments will be interpreted only in a multi-node deployment, and fully ignored in a single-node deployment. Even more so, they are absolutely required for a multi-node deployment to work. And the ones that mention "for Agent node" will be fully ignored by the Master node.
• For the only configuration setting that mentions "for both Master and Agent nodes", which is SERVER_ROLE, this is just a requirement for the code to identify "Who is a Master? Who is an Agent?" at startup, and it is interpreted only in a multi-node deployment.

You may want to check the issue #19 to learn more about that part.

Multi-host deployment

Using Isaiah, you can manage multiple hosts with their own distinct Docker resources from a single dashboard.

Before delving into that part, please get familiar with the general information below.

General information

The big difference between multi-node and multi-host deployments is that you won't need to install Isaiah on every single node if you are using multi-host. In this setup, Isaiah is installed only on one server, and communicates with other Docker hosts directly over TCP / Unix sockets. It makes it easier to manage multiple remote Docker environments without having to setup Isaiah on all of them.

In a multi-host deployment, Isaiah sends requests directly to the /var/run/docker.sock socket on the remote machines. So, that file must be exposed in one way or another.

Please note that, in a multi-host setup, there must be a direct access between the main host (where Isaiah is running) and the other ones. Usually, they should be on the same network, or visible through a secured gateway / VPN / filesystem mount.

Let's see how to set up a multi-host deployment.

Setup

In order to help you get started, a sample file was created.

First, please ensure the following :

• Your Master host is running, exposed on the network, and available in your web browser
• Your Master host has the setting MULTI_HOST_ENABLED set to true.
• Your Master host has access to the other Docker hosts over TCP / Unix socket.

Second, please create a docker_hosts file next to Isaiah's executable, using the sample file cited above:

• Every line should contain two strings separated by a single space.
• The first string is the name of your host, and the second string is the path to reach it.
• The path to your host should look like this : [PROTOCOL]://[URI]
• Example 1 : Local unix:///var/run/docker.sock
• Example 2 : Remote tcp://my-domain.tld:4382

If you're using Docker, you can mount the file at the root of the filesystem, as in :
docker ... -v my_docker_hosts:/docker_hosts ...

Finally, launch Isaiah on the Master host, and you should see logs indicating whether connection with remote hosts was established. Eventually, you will see Master with The name of your host in the lower right corner of your screen.

Forward Proxy Authentication / Trusted SSO

If you wish to deploy Isaiah behind a secure proxy or authentication portal, you must configure Forward Proxy Authentication.

This will enable you to :

• Log in, once and for all, into your authentication portal.
• Connect to Isaiah without having to type your AUTHENTICATION_SECRET every time.
• Protect Isaiah using your authentication proxy rather than the current mechanism (cleartext / hashed password).
• Manage the access to Isaiah from your authentication portal rather than through your .env configuration.

Before proceeding, please ensure the following :

• Your proxy supports HTTP/2 and Websockets.
• Your proxy can communicate with Isaiah on the network.
• Your proxy forwards authentication headers to Isaiah (but not to the browser).

For example, if you're using Nginx Proxy Manager (NPM), you should do the following :

• In the tab "Details"
• Tick the box "Websockets support"
• Tick the box "HTTP/2 support"
• Tick the box "Block common exploits"
• Tick the box "Force SSL"


• In the tab "Advanced"
• In your custom location block, add the lines :
• proxy_set_header Upgrade $http_upgrade;
• proxy_set_header Connection "upgrade";

Then, configure Isaiah using the following variables :

• Set FORWARD_PROXY_AUTHENTICATION_ENABLED to true.
• Set FORWARD_PROXY_AUTHENTICATION_HEADER_KEY to the name of the forwarded authentication header your proxy sends to Isaiah.
• Set FORWARD_PROXY_AUTHENTICATION_HEADER_VALUE to the value of the header that Isaiah should expect (or use * if all values are accepted).

By default, Isaiah is configured to work with Authelia out of the box. Hence, you can just set FORWARD_PROXY_AUTHENTICATION_ENABLED to true and be done with it.

If everything was properly set up, you will encounter the following flow :

• Navigate to isaiah.your-domain.tld.
• Get redirected to authentication-portal.your-domain.tld.
• Fill in your credentials.
• Authentication was successful.
• Get redirected to isaiah.your-domain.tld.
• Isaiah does not prompt you for the password, you're automatically logged in.

Configuration

To run Isaiah, you will need to set the following environment variables in a .env file located next to your executable :

Note : Regular environment variables provided on the commandline work too

Note : Boolean values are case-insensitive, and can be represented via "ON" / "OFF" / "TRUE" / "FALSE" / 0 / 1.

Note : To sort rows in reverse using the SORTBY_ parameters, prepend your field with the minus symbol, as in -Name

Note : Use either AUTHENTICATION_SECRET or AUTHENTICATION_HASH but not both at the same time.

Note : You can generate a sha256 hash using an online tool, or using the following commands : On OSX : echo -n your-secret | shasum -a 256 On Linux : echo -n your-secret | sha256sum

Additionally, once Isaiah is fully set up and running, you can open the Parameters Manager by pressing the X key. Using this interface, you can toggle the following options based on your preferences :

Note : You must have Isaiah open in your browser and be authenticated to access these options. Once set up, these options will be saved to your localStorage.

Theming

You can customize Isaiah's web interface using your own custom CSS. At runtime, Isaiah will look for a file named custom.css right next to the executable. If this file exists, it will be loaded in your browser and it will override any existing CSS rule.

In order to help you get started, a sample file was created. It shows how to modify the CSS variables responsible for the colors of the interface. (All the values are the ones used by default) You can copy that file, update it, and rename it to custom.css.

If you're using Docker, you should mount a custom.css file at the root of your container's filesystem. Example : docker ... -v my-custom.css:/custom.css ...

Finally, you will find below a table that describes what each CSS color variable means :

On a side note, creating custom layouts using only CSS isn't implemented yet as it requires interaction with Javascript. That said, implementing this feature should be quick and simple since the way layouts are managed currently is already modular.

Ultimately, please note that Isaiah already comes with three themes : dawn, moon, and the default one. The first two themes are based on Rosé Pine, and new themes may be implemented later.

Troubleshoot

Should you encounter any issue running Isaiah, please refer to the following common problems with their solutions.

Isaiah is unreachable over HTTP / HTTPS

Please make sure that the following requirements are met :

• If Isaiah runs as a standalone application without proxy :

  • Make sure your server / firewall accepts incoming connections on Isaiah's port.
  • Make sure your DNS configuration is correct. (Usually, such record should suffice : A isaiah XXX.XXX.XXX.XXX for https://isaiah.your-server-tld)
  • Make sure your .env file is well configured according to the Configuration section.

• If Isaiah runs on Docker :

  • Perform the previous (standalone) verifications first.
  • Make sure you mounted your server's Docker Unix socket onto the container that runs Isaiah (/var/run/docker.sock)
  • Make sure your Docker container is accessible remotely

• If Isaiah runs behind a proxy :

  • Perform the previous (standalone) verifications first.
  • Make sure that SERVER_PORT (Isaiah's port) are well set in .env.
  • Check your proxy forwarding rules.

In any case, the crucial part is Configuration and making sure your Docker / Proxy setup is correct as well.

On startup, Isaiah shows 0 containers, 0 networks, 0 volumes, and 0 images

You must update Docker on your system to fix that issue.

Isaiah uses the native Docker Engine API, and it requires Docker to be at least on version 23.0.0+

On a system with a lot of Docker resources, Isaiah is inconsistent or crashes

This is due to a limitation on the message size during the WebSocket communication. When your server has a lot of Docker resources on it (~150+), Isaiah will send all these resources in a single WebSocket message by default. This can cause the server to crash.

There are two solutions :

• Increase the maximum size of a message : Increase the value of the setting SERVER_MAX_READ_SIZE
• Enabled chunked communication : Set SERVER_CHUNKED_COMMUNICATION_ENABLED to TRUE and adjust SERVER_CHUNKED_COMMUNICATION_SIZE if it's not already satisfying.

You may encounter the same issue in a multi-node deployment, and the cleanest solution here would be to enable chunked communication on the node that hosts a lot of Docker resources.

The emulated shell behaves unconsistently or displays unexpected characters

Please note that the emulated shell works by performing the following steps :

• Open a headless terminal on the remote server / inside the remote Docker container.
• Capture standard output, standard error, and bind standard input to the web interface.
• Display standard output and standard error on the web interface as they are streamed over Websocket from the terminal.

According to this implementation, the remote terminal never receives key presses. It only receives commands.

Also, the following techniques are used to try to enhance the user experience on the web interface :

• Enable clearing the shell (HTML) screen via "Ctrl+L" (while the real terminal remains untouched)
• Enable quitting the (HTML) shell via "Ctrl+D" (by sending an "exit" command to the real terminal)
• Handle "command mirror" by appending "# ISAIAH" to every command sent by the user (to distinguish it from command output)
• Handle both "\r" and "\n" newline characters
• Use a time-based approach to detect when a command is finished if it doesn't output anything that shows clear ending
• Remove all escape sequences meant for coloring the terminal output
• Handle up and down arrow keys to cycle through commands history locally

Therefore it appears that, unless we use a VNC-like solution, the emulation can neither be enhanced nor use keyboard-based features (such as tab completion).

Unless a contributor points the project in the right direction, and as far as my skills go, I personally believe that the current implementation has reached its maximum potential.

I leave here a few ideas that I believe could be implemented, but may require more knowledge, time, testing :

• Convert escape sequences to CSS colors
• Wrap every command in a "block" (begin - command - end) to easily distinguish user-sent commands from output
• Sending to the real terminal the key presses captured from the web (a.k.a sending key presses to a running process)

Ultimately, please also note that in a multi-node / multi-host setup, the extra network latency and unexpected buffering from remote terminals may cause additional display artifacts.

An error happens when spawning a new shell on the server / inside a Docker container

The default commands used to spawn a shell, although being more or less standard, may not fit your environment. In this case, please edit the TTY_SERVER_COMMAND and TTY_CONTAINER_COMMAND settings to define a command that works better in your setup.

Also, please note that if you have deployed Isaiah using Docker, trying to open a system shell (S key) will not work. Isaiah being confined to its Docker container, it won't be able to open a shell out of it (on your hosting system).

The connection with the remote server randomly stops or restarts

This is a known incident that happens when the Websocket server receives a data message that exceeds its maximum read size. You should be able to fix that by updating the SERVER_MAX_READ_SIZE setting to a higher value (default is 100,000 bytes). This operation shouldn't cause any problem or impact performances.

I can neither click nor use the keyboard, nothing happens

In such a case, please check the icon in the lower right corner. If you see an orange warning symbol, it means that the connection with the server was lost. When the connection is lost, all inputs are disabled, until the connection is reestablished (a new attempt is performed every second).

The interface is stuck loading indefinitely

This incident arises when a crash occurs while inside a shell or performing a Docker command. The quickest "fix" for that is to refresh your browser tab (Ctrl+R/Cmd+R).

The real "fix" (if any) could be to implement a "timeout" (client-side or server-side) after which, the "loading" state is automatically discarded

If you encounter this incident consistently, please reach out by opening an issue so we look deeper into that part

The web interface seems to randomly crash and restart

If you haven't already, please read about the SERVER_MAX_READ_SIZE setting in the Configuration section.

That incident occurs when the Websocket messages sent from the client to the server are too big. The server's reaction to overly large messages sent over Websocket is to close the connection with the client. When that happens, Isaiah (as a client in your browser) automatically reopens a connection with the server, hence explaining the "crash-restart" cycle.

The web interface does not save my preferences

First, please ensure that your browser supports the localStorage API.

Second, please ensure that you're not using the private browsing or incognito or anonymous browsing mode. This mode will turn off the localStorage, hence disabling the user preferences saved by Isaiah in your browser.

If you wish to use Isaiah inside a private browser window while still having your preferences stored somewhere, use the CLIENT_PREFERENCE_XXX settings in your deployment. These settings will be stored server-side, and understood by your browser without ever using localStorage, hence circumventing the limitation of the private browsing mode.

All the preferences described in the second table of Configuration are available server-side, using their uppercased-underscore counterpart. See below :

• theme becomes CLIENT_PREFERENCE_THEME
• enableOverviewOnLaunch becomes CLIENT_PREFERENCE_ENABLE_OVERVIEW_ON_LAUNCH
• enableMenuPrompt becomes CLIENT_PREFERENCE_ENABLE_MENU_PROMPT
• enableLogLinesWrap becomes CLIENT_PREFERENCE_ENABLE_LOG_LINES_WRAP
• enableJumpFuzzySearch becomes CLIENT_PREFERENCE_ENABLE_JUMP_FUZZY_SEARCH
• enableTimestampDisplay becomes CLIENT_PREFERENCE_ENABLE_TIMESTAMP_DISPLAY
• enableLogLinesStrippedBackground becomes CLIENT_PREFERENCE_ENABLE_LOG_LINES_STRIPPED_BACKGROUND

I can't see my Docker Stacks (Docker Compose) in the user interface / A feature isn't available

Please ensure that Isaiah is running on the hosting system directly, and not inside a Docker container.

For certain features (including, managing Docker Compose projects), Isaiah needs to run commands on the hosting system. For example, it runs docker compose ls to find all the Docker Compose projects, or even docker compose -f FILE up -d to up a stack.

As a result, if Isaiah is running inside a Docker container, it won't be able to run those commands on the hosting system.

For ease of deployment, you may want to use the install script described here.

A feature that works on desktop is missing from the mobile user interface

Please note that you can horizontally scroll the mobile controls located in the bottom part of your screen to reveal all of them. If, for any reason, you still encounter a case when a feature is missing on your mobile device, please open an issue indicating the browser you're using, your screen's viewport size, and the model of your phone.

In a multi-node deployment, the agent's registration with master is stuck loading indefinitely

This issue arises when the authentication settings between Master and Agent nodes are incompatible.
To fix it, please make sure that :

• When authentication is enabled on Master, the Agent has a MASTER_SECRET setting defined.
• When authentication is disabled on Master, the Agent has no MASTER_SECRET setting defined.

Also don't forget to restart your nodes when changing settings.

Something else

Please feel free to open an issue, explaining what happens, and describing your environment.

Security

Due to the very nature of Isaiah, I can't emphasize enough how important it is to harden your server :

• Always enable the authentication (with AUTHENTICATION_ENABLED and AUTHENTICATION_SECRET settings) unless you have your own authentication mechanism built into a proxy.
• Always use a long and secure password to prevent any malicious actor from taking over your Isaiah instance.
• You may also consider putting Isaiah on a private network accessible only through a VPN.

Keep in mind that any breach or misconfiguration on your end could allow a malicious actor to fully take over your server.

Disclaimer

I believe that, although we're both in the open-source sphere and have all the best intentions, it is important to state the following :

• Isaiah isn't a competitor or any attempt at replacing the lazydocker project. Funnily enough, I'm myself more comfortable running lazydocker through SSH rather than in a browser.
• I've browsed almost all the open issues on lazydocker, and tried to implement and improve what I could (hence the TTY_CONTAINER_COMMAND variable, as an example, or even the Image pulling feature).
• Isaiah was built from absolute zero (for both the server and the client), and was ultimately completed using knowledge from lazydocker that I'm personally missing (e.g. the container states and icons).
• Before creating Isaiah, I tried to "serve lazydocker over websocket" (trying to send keypresses to the lazydocker process, and retrieving the output via Websocket), but didn't succeed, hence the full rewrite.
• I also tried to start Isaiah from the lazydocker codebase and implement a web interface on top of it, but it seemed impractical or simply beyond my skills, hence the full rewrite.

Ultimately, thanks to the people behind lazydocker both for the amazing project (that I'm using daily) and for paving the way for Isaiah.

PS : Please also note that Isaiah isn't exactly 100% feature-equivalent with lazydocker (e.g. charts are missing) PS2 : What spurred me to build Isaiah in the first place is a bunch of comments on the Reddit self-hosted community, stating that Portainer and other available solutions were too heavy or hard to use. A Redditor said that having lazydocker over the web would be amazing, so I thought I'd do just that.

Contribute

This is one of my first ever open-source projects, and I'm not a Docker / Github / Docker Hub / Git guru yet.

If you can help in any way, please do! I'm looking forward to learning from you.

From the top of my head, I'm sure there's already improvement to be made on :

• Terminology (using the proper words to describe technical stuff)
• Coding practices (e.g. writing better comments, avoiding monkey patches)
• Shell emulation (e.g. improving on what's done already)
• Release process (e.g. making explicit commits, pushing Docker images properly to Docker Hub)
• Github settings (e.g. using discussions, wiki, etc.)
• And more!

Credits

Hey hey ! It's always a good idea to say thank you and mention the people and projects that help us move forward.

Big thanks to the individuals / teams behind these projects :

• lazydocker : Isaiah wouldn't exist if Lazydocker hadn't been created prior, and to say that it is an absolutely incredible and very advanced project is an understatement.
• Heroicons : For the great icons.
• Melody : For the awesome Websocket implementation in Go.
• GoReleaser : For the amazing release tool.
• Fuse : For the amazing fuzzy-search library.
• The countless others!

And don't forget to mention Isaiah if it makes your life easier!