/build/static/layout/Breadcrumb_cap_w.png

Virtual Kontainers [SOLVED]

I am starting to try to use our virtual kontainers as it is just sitting there lonely (Sorry Bob). It has been a little while since training. After I create a kontainer, it displays in the creation tab. I then click on the "Upload Package" to the Kbox. After doing so, am I able to "Remove Package on Source" and still be able to use the kontainer? I just want to make sure before I actually remove the package that it will still be able to be deployed with it just being uploaded to the kbox.

Thanks in advance!

0 Comments   [ + ] Show comments

Answers (2)

Posted by: bkelly 14 years ago
Red Belt
0
Yes, you can safely remove the original source once it is updated. One reason you might want to keep it around is if you needed to update the package-- with the Kontainer Creator Utility you can install patches and updates targeting an existing Kontainer Package (.kvi) file. However, you could also just deploy it to any other system and obtain the package from there. Short answer: yes, it is safe to remove it.
Posted by: ustacp 14 years ago
Second Degree Blue Belt
0
Oh, ok. That makes sense. That is probably what I will do is just deploy it and update from there so I do not have to have a dedicated kontainer PC. Do you guys happen to have an article explaining how to update an existing kontainer? I did not notice it in the VK guide, unless I over looked it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ