How to make Drone Docker plugin to authenticate with a self-hosted registry having a self-signed TLS...
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm using Drone 1.0.0-rc1 with the Docker plugin. My docker registry is only accessible via TLS, however the certificate is self-signed.
The whole docker ecosystem complains about it with a similar error message, in case of the Drone build it's this:
x509: certificate signed by unknown authority
Normally I'm able to add the ca as a trusted authority to the OS running the different Docker solutions, however Drone is executing the builds (and the auth itself) inside a short-lived docker container.
How can I make it trust the cert?
docker authentication ssl x509 drone
add a comment |
I'm using Drone 1.0.0-rc1 with the Docker plugin. My docker registry is only accessible via TLS, however the certificate is self-signed.
The whole docker ecosystem complains about it with a similar error message, in case of the Drone build it's this:
x509: certificate signed by unknown authority
Normally I'm able to add the ca as a trusted authority to the OS running the different Docker solutions, however Drone is executing the builds (and the auth itself) inside a short-lived docker container.
How can I make it trust the cert?
docker authentication ssl x509 drone
add a comment |
I'm using Drone 1.0.0-rc1 with the Docker plugin. My docker registry is only accessible via TLS, however the certificate is self-signed.
The whole docker ecosystem complains about it with a similar error message, in case of the Drone build it's this:
x509: certificate signed by unknown authority
Normally I'm able to add the ca as a trusted authority to the OS running the different Docker solutions, however Drone is executing the builds (and the auth itself) inside a short-lived docker container.
How can I make it trust the cert?
docker authentication ssl x509 drone
I'm using Drone 1.0.0-rc1 with the Docker plugin. My docker registry is only accessible via TLS, however the certificate is self-signed.
The whole docker ecosystem complains about it with a similar error message, in case of the Drone build it's this:
x509: certificate signed by unknown authority
Normally I'm able to add the ca as a trusted authority to the OS running the different Docker solutions, however Drone is executing the builds (and the auth itself) inside a short-lived docker container.
How can I make it trust the cert?
docker authentication ssl x509 drone
docker authentication ssl x509 drone
asked Nov 16 '18 at 19:40
neo696e64neo696e64
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
A less than stellar but working solution is to add the following setting to the .drone.yml:
insecure: true
This makes it running the docker daemon with the --insecure-registry
argument which according to the docs
First, try using HTTPS.
- If HTTPS is available but the certificate is invalid, ignore the error about the certificate.
- If HTTPS is not available, fall back to HTTP.
In my case I know that my registry isn't even exposed through HTTP so looks good enough.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53344340%2fhow-to-make-drone-docker-plugin-to-authenticate-with-a-self-hosted-registry-havi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A less than stellar but working solution is to add the following setting to the .drone.yml:
insecure: true
This makes it running the docker daemon with the --insecure-registry
argument which according to the docs
First, try using HTTPS.
- If HTTPS is available but the certificate is invalid, ignore the error about the certificate.
- If HTTPS is not available, fall back to HTTP.
In my case I know that my registry isn't even exposed through HTTP so looks good enough.
add a comment |
A less than stellar but working solution is to add the following setting to the .drone.yml:
insecure: true
This makes it running the docker daemon with the --insecure-registry
argument which according to the docs
First, try using HTTPS.
- If HTTPS is available but the certificate is invalid, ignore the error about the certificate.
- If HTTPS is not available, fall back to HTTP.
In my case I know that my registry isn't even exposed through HTTP so looks good enough.
add a comment |
A less than stellar but working solution is to add the following setting to the .drone.yml:
insecure: true
This makes it running the docker daemon with the --insecure-registry
argument which according to the docs
First, try using HTTPS.
- If HTTPS is available but the certificate is invalid, ignore the error about the certificate.
- If HTTPS is not available, fall back to HTTP.
In my case I know that my registry isn't even exposed through HTTP so looks good enough.
A less than stellar but working solution is to add the following setting to the .drone.yml:
insecure: true
This makes it running the docker daemon with the --insecure-registry
argument which according to the docs
First, try using HTTPS.
- If HTTPS is available but the certificate is invalid, ignore the error about the certificate.
- If HTTPS is not available, fall back to HTTP.
In my case I know that my registry isn't even exposed through HTTP so looks good enough.
answered Nov 16 '18 at 20:49
neo696e64neo696e64
12
12
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53344340%2fhow-to-make-drone-docker-plugin-to-authenticate-with-a-self-hosted-registry-havi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown