Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
VirtaMove Knowledge Center
VirtaMove Documentation
  • VirtaMove Support Knowledge Base
    VirtaMove Support Knowledge Base
     This trigger is hidden
Results will update as you type.
  • V-Migrate Documentation
    • 01. Managing Your VirtaMove Licensing
    • 02. Installation Guide
    • 03. Application Migration Guide
    • 04. Administration Guide
      • Requirements
      • Introduction the Administrative Console
      • Managing the Security Key
      • Managing Container Settings
      • Docking and Undocking Containers
      • Updating the VirtaMove Activation Code
      • Managing Tethered VAAs
      • Managing Container Services
      • Managing Credentials for Container Users
      • Running Containers
      • Moving, Compressing, and Deleting Containers
      • Upgrading Containers
      • Logging
      • Testing Containers
      • Junctions in Windows 2008 R2
    • 05. CLI Guide
    • About VirtaMove V-Migrate Documentation
  • V-Maestro Documentation
  • VirtaLinux Documentation
    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    Docking and Undocking Containers
    Updated Aug 26, 2022

      Docking and Undocking Containers

      Table of Contents

      • 1 Docking
        • 1.1 Docking and the VirtaMove License
        • 1.2 Docking and Antivirus Software
          • 1.2.1 To Dock a Container
        • 1.3 Docking a Tethered Container
      • 2 Undocking
        • 2.1 To Undock a Container

      Docking

      Docking a container integrates and prepares the container’s environment as part of the underlying operating system so that the application is ready to run.

      When you dock a container, it is registered with VirtaMove and any system definitions that were defined for the container when it was created. System definitions include file associations; in some cases, a file may need to be copied to the operating system.

      VirtaMove runs a basic sanity test on a container when you attempt to dock the container. Certain conditions on an operating system may interfere with VirtaMove software and an attempt to dock a container, such as an antivirus software or group account permissions. In such a case, the following error message may be displayed when docking fails:

      Failed to intercept OS calls. Sanity test failed. Cannot dock.

      Docking and the VirtaMove License

      If you have not yet activated your VirtaMove license, you will be prompted to do so when you try to dock a container that has tether enabled. See Activating Your VirtaMove LicensePreview for information.

      You will not be able to dock a container if you do not activate your VirtaMove license. If you require a new license key, contact VirtaMove customer support at support@virtamove.com.

      Docking and Antivirus Software

      Each time you dock a container, VirtaMove performs an antivirus check and alerts you if antivirus software is found. This alert does not interfere with the docking process.

      It is recommended that you do not install and run antivirus software or "endpoint security" agents on the destination machine during the migration process.

      Example: Docking via the CLI

      >virtadock c:\appliances\av_test Attempting to dock c:\appliances\av_test. Please wait... Local Antivirus Installed: Yes

      To Dock a Container

      • Do one of the following:

        • At the command prompt, enter the following:

          virtadock <container>

        • In the Administrative Console, select the container, and then click Dock.

        • In the Administrative Console, right-click an undocked container in the container pane, and then click Dock.

      Once the container is docked, you can start any required container services and then run the container application.

      Docking a Tethered Container

      If Tether is enabled for a container and the tethering process did not succeed, you will not be able to dock the container.

      You cannot dock a container with a service if a service with the same name exists on the underlying operating system. The Status column will display "CONFLICT" and an error message will be displayed at the bottom of the Administrative Console window. You must resolve the conflict before you dock the container.

      Managing Source ServicesPreview

      Undocking

      Undocking a container makes the container unavailable by stopping services and removing the container’s registry entries and file set from the underlying operating system. Next, the container is unregistered from VirtaMove and any system definitions that were exported when the container was docked are removed.

      To Undock a Container

      Do one of the following:

      • At the command prompt, enter the following:

        virtaundock <Container>

      • In the Administrative Console, select the container, and then click Undock. The container status is updated to Undocked.

      • In the Administrative Console, right-click a docked container in the container pane, and then click Undock.

       

       

      {"serverDuration": 11, "requestCorrelationId": "283ee0b7ddf440528201343fb90e62c0"}