In the meantime you may want to use machine policies to remove the duplicated targets. Our goal is to update this image to de-register the Tentacle when the container SIGKILL signal is passed in. This registration will occur on every startup and you may end up with multiple instances if you stop/start a container. When an Octopus Tentacle container starts up, it will attempt to invoke the register-with command to connect and add itself as a machine to that server with the provided roles and environments. For this reason, Octopus Tentacles inside a container may not be appropriate for many deployment tasks. Tentacles set up this way will run inside a container and script execution will not happen on the host itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |