Connect using Docker - select operating system -> Connect using Docker - Debian

Connect using Docker - Debian

Summary

This page is your guide to setting up your awaBerry device using Docker on a Debian-based system. It provides direct download links for the essential Docker configuration file and the corresponding license. Additionally, you'll find easy-to-copy commands to help you build and run your awaBerry Docker image, and manage your device.

Page Access

You can access this page by navigating to: /connect_steps_docker?os=debian

Page Functionalities

1. Download Docker File Button

This button allows you to download the specific Docker configuration file for your selected operating system (Debian) and Docker version. Clicking this will open a download prompt or directly download the file to your device.

2. Download License Button

Click this button to download the license file associated with your awaBerry Docker setup. It's important to keep this license for your records.

3. Docker Setup Commands (Copyable)

Below the download buttons, you'll find three essential command lines:

  • Docker Build Command: Use this command to create your awaBerry Docker image from the downloaded Docker file. Simply click the copy icon next to the command to copy it to your clipboard, then paste and run it in your terminal.
  • Docker Run Command: After building the image, use this command to start your awaBerry Docker container. Copy it and run it in your terminal.
  • Docker Exec Command: This command allows you to access the running awaBerry Docker container for advanced management or troubleshooting. Copy and use it in your terminal if needed.

Each command is presented in a box with a convenient copy icon. Clicking the copy icon will automatically place the command into your clipboard, ready for pasting into your terminal.

4. Back to device list Button

Once you've completed the Docker setup or if you wish to return to your list of devices, click this button to navigate back to the main device management page.

Scenario Executions

Possible usage steps within this page

Scenario 1: Successfully download Docker files and copy commands

  1. Click the "Download Docker File" button. The Docker file will download to your device.
  2. Click the "Download license" button. The license file will download to your device.
  3. Click the copy icon next to the "Docker Build Command". The command will be copied to your clipboard, and a confirmation message will appear.
  4. Click the copy icon next to the "Docker Run Command". The command will be copied to your clipboard, and a confirmation message will appear.
  5. Click the copy icon next to the "Docker Exec Command". The command will be copied to your clipboard, and a confirmation message will appear.
  6. Click the "Back to device list" button to return to the previous page.

Scenario 2: Navigate back without downloading

  1. From this page, without performing any downloads or copies, click the "Back to device list" button. You will be safely redirected to the device list page.

Possible errors which may occur on this page

Error 1: Failed to open download link

If you click the "Download Docker File" or "Download license" button and nothing happens, or an error message appears, it could be due to:

  • No internet connection: Ensure your device has an active internet connection.
  • Browser restrictions: Some browsers might block automatic downloads. Check your browser's security settings or look for a prompt asking for permission to download.
  • Invalid URL: Although unlikely, if the download link is somehow malformed or unavailable, the download will fail. This is typically a system-level issue.

In such cases, try checking your internet connection, browser settings, or restarting the application.

Error 2: Device name already in use (displayed from a previous step)

Although this page focuses on downloads and commands, an error message "Device name is already in use - please use another one" might appear if a device name chosen in a preceding step was found to be duplicated. If you encounter this, you would typically need to go back to the device naming step to correct the input. On this page, this error would simply be displayed as an informational message.