You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to add a prefix variable that can be appended to all container names, allowing us to run a fully offline copy of drone using a mirrored set of containers.
Essentially we're using Artifactory, and we want to have a non-internet connected test environment - and plugins for the various elements would be mirrored to artifactory - requiring a prefix to be specified for the FQDN on the container pulls.
Right now, no internet - no love - unless I've missed something dramatic here.
-steve
The text was updated successfully, but these errors were encountered:
drone will always fall back to the local Docker cache (on the host machine) and will happily if the required images are in the local cache. If you want to change to use an internal registry you will need to publish images or plugins to your registry and then reference them in the yaml using the full name:
Then you will need to include your plugins in the white list. You can do so by adding the following configuration to your drone server:
PLUGIN_FILTER=plugins/* foo.com/*
Alternatively you can manually download the images from artifactory to your host machine and then re-tag them so they work with drone out of the box. You could probably script this and have a cron script regularly download and update:
docker pull foo.com/slack
docker tag $(docker images -q foo.com/slack) plugins/drone-slack
For all future questions, please use our gitter room to reserve the issue tracker for bug reports. Thanks!
Hello,
Is it possible to add a prefix variable that can be appended to all container names, allowing us to run a fully offline copy of drone using a mirrored set of containers.
Essentially we're using Artifactory, and we want to have a non-internet connected test environment - and plugins for the various elements would be mirrored to artifactory - requiring a prefix to be specified for the FQDN on the container pulls.
Right now, no internet - no love - unless I've missed something dramatic here.
-steve
The text was updated successfully, but these errors were encountered: