“Container has no container token files” error when Deploying a Container
Applies to: Cloudhouse Application Compatibility Packages/Compatibility Containers
17/06/2020 Cliff Hobbs ID: 587181
To fix this issue, ensure there is a Deploy Access Token in the root of your ACP. The file will be named:
- <package_ID> is the value entered in the App ID field on the Package page of the Auto Packager. Example: Notepad++_x64
For example deploy-access-Notepad++_x64.token
If you still encounter problems, please contact your Cloudhouse Partner in the first instance (if relevant), otherwise contact Cloudhouse Support for further assistance.
When trying to deploy a Cloudhouse Application Compatibility Package (also known as a Cloudhouse Compatibility Container™) using Cloudhouse.Container.Deployment.exe, I see a window flash open then disappear.
Looking in the DeploymentWorkflowLog.txt (located in the root of the ACP), I see entries like:
ERROR Cloudhouse.Container.Deployment.Program - Failed:
Cloudhouse.Container.Core.Exceptions.InvalidLicenceException: Container has no container token files.
at Cloudhouse.Container.Deployment.Program.Main(String args)
ERROR Cloudhouse.Container.Deployment.Program - Exiting with code: -1
You will see this error if the ACP you are trying to deploy does not have a Deploy Access Token.