Troubleshooting container deployment issues

Use this section to troubleshoot common problems during installation and deployment of containers using DUX.

• Installation errors

  If you encounter installation issues, refer to your package manager's specific error messages and documentation.

  Example, for dnf users, check if the cache is updated.

  dnf makecache

• Deployment issues

  • Ensure to run dux init command after the initial installation.
  • Always perform a dry-run before deploying to production to validate the deployment manifest. See Best Practices for editing the manifest.yml file.

  dux deploy -d

  • Ensure that all the pre-requisites are met. See Pre-requisites to install dux.

• Log files and diagnostics

  • Check the dux.log in logs directory for any errors, warnings.

  For example,/opt/omnissa/dux/logs/dux.log contains general dux operation logs on Linux.

  • Check the CRUD logs (deploy, destroy, stop, restart), available in dux-audit.log directory.

  For example, /opt/omnissa/dux/logs/dux-audit.log contains container operations related logs on Linux.

• Platform specific issues

  • If the Docker is installed using snap package manager, there might be permission issues during Tunnel container deployment on Linux systems. Uninstall snap docker and install docker using the official installation guide - https://docs.docker.com/engine/install/ubuntu/.

    sudo snap remove docker --purge

    sudo reboot

    sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin

  • Check for other containers running with snap Docker before uninstalling. Running both Snap Docker and Docker CE simultaneously is not recommended due to conflicts with the network, port usage, system resources, and so on.

• Password handling with special characters

  When deploying with Basic Auth for UEM API authentication/ Outbound proxy authentication, always wrap your password in single quotes when using command-line options. Shell might misinterpret special characters in command-line parameters.

  Note: This recommendation applies only to the -u parameter for UEM Password and the -o parameter for Outbound Proxy Password in the deploy command. Passwords entered using interactive prompts (Enter UEM password:) do not require single quotes.

• Resolving ANSI escape characters display issue

  ANSI escape characters appear in output (example \u001b[31m), causing incorrectly formatted or colored text. ANSI escape code support not enabled in Windows PowerShell.

  To resolve this issue:

  1. Open Command Prompt or PowerShell with administrator privileges.
  2. Run the command: reg add HKCU\Console /v VirtualTerminalLevel /t REG_DWORD /d 1
  3. Restart your terminal.

• Podman container

  Containers do not automatically restart after system reboot when using Podman. Configure the container as a systemd service to ensure automatic restart. Contact Omnissa support for detailed configuration steps.

  sudo podman generate systemd --name vpnserver --files --new
  sudo cp container-vpnserver.service /etc/systemd/system/
  sudo chown root:root /etc/systemd/system/container-vpnserver.service
  sudo chmod 644 /etc/systemd/system/container-vpnserver.service
  sudo restorecon -v /etc/systemd/system/container-vpnserver.service
  sudo systemctl daemon-reload
  sudo systemctl enable container-vpnserver.service
  sudo systemctl start container-vpnserver.service
  sudo systemctl status container-vpnserver.service