Jenkins in docker and ssh
i have a jenkins that run inside a docker container (on a server A) and i want to publish an artifact over ssh in a server B.
I have installed the plugin "publish over ssh" in Jenkins but i don't know how to configure the ssh.
I guess that i must generate a public/private key on the server A and send my public key on the server B. But for which user?
I have a user jenkins on the server B but not on the server A. Should i generate the key with the same user that run the docker on the server A? Where should I put my keys?
Thanks.
ssh docker jenkins
add a comment |
i have a jenkins that run inside a docker container (on a server A) and i want to publish an artifact over ssh in a server B.
I have installed the plugin "publish over ssh" in Jenkins but i don't know how to configure the ssh.
I guess that i must generate a public/private key on the server A and send my public key on the server B. But for which user?
I have a user jenkins on the server B but not on the server A. Should i generate the key with the same user that run the docker on the server A? Where should I put my keys?
Thanks.
ssh docker jenkins
add a comment |
i have a jenkins that run inside a docker container (on a server A) and i want to publish an artifact over ssh in a server B.
I have installed the plugin "publish over ssh" in Jenkins but i don't know how to configure the ssh.
I guess that i must generate a public/private key on the server A and send my public key on the server B. But for which user?
I have a user jenkins on the server B but not on the server A. Should i generate the key with the same user that run the docker on the server A? Where should I put my keys?
Thanks.
ssh docker jenkins
i have a jenkins that run inside a docker container (on a server A) and i want to publish an artifact over ssh in a server B.
I have installed the plugin "publish over ssh" in Jenkins but i don't know how to configure the ssh.
I guess that i must generate a public/private key on the server A and send my public key on the server B. But for which user?
I have a user jenkins on the server B but not on the server A. Should i generate the key with the same user that run the docker on the server A? Where should I put my keys?
Thanks.
ssh docker jenkins
ssh docker jenkins
asked Jan 16 at 9:12
user985796user985796
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your question seems to relate more to using ssh than the fact that you're running Jenkins in Docker. So I'll focus on that.
When using ssh keypairs, you'll want to generate your keypair client-side and provide the public key to the host. So you're right that you want to generate on server A
and share your key with server B
.
For which user you want to add the key depends on where you add the key to the authorized_keys
-file on server B
. It doesn't matter what users you have on server A
, as long as you ssh into server B
using the correct user.
e.g.: if you have added the key to the authorized_keys
-file for user foo
on server B
, then you'll want to ssh into it using something akin to ssh foo@server_b
.
As for the location of storing your keys, the keypair will usually reside in ~/.ssh on your client. And, as stated above, the content of the public key will be stored as a line in the authorized_keys
-file on the host.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1394857%2fjenkins-in-docker-and-ssh%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
Your question seems to relate more to using ssh than the fact that you're running Jenkins in Docker. So I'll focus on that.
When using ssh keypairs, you'll want to generate your keypair client-side and provide the public key to the host. So you're right that you want to generate on server A
and share your key with server B
.
For which user you want to add the key depends on where you add the key to the authorized_keys
-file on server B
. It doesn't matter what users you have on server A
, as long as you ssh into server B
using the correct user.
e.g.: if you have added the key to the authorized_keys
-file for user foo
on server B
, then you'll want to ssh into it using something akin to ssh foo@server_b
.
As for the location of storing your keys, the keypair will usually reside in ~/.ssh on your client. And, as stated above, the content of the public key will be stored as a line in the authorized_keys
-file on the host.
add a comment |
Your question seems to relate more to using ssh than the fact that you're running Jenkins in Docker. So I'll focus on that.
When using ssh keypairs, you'll want to generate your keypair client-side and provide the public key to the host. So you're right that you want to generate on server A
and share your key with server B
.
For which user you want to add the key depends on where you add the key to the authorized_keys
-file on server B
. It doesn't matter what users you have on server A
, as long as you ssh into server B
using the correct user.
e.g.: if you have added the key to the authorized_keys
-file for user foo
on server B
, then you'll want to ssh into it using something akin to ssh foo@server_b
.
As for the location of storing your keys, the keypair will usually reside in ~/.ssh on your client. And, as stated above, the content of the public key will be stored as a line in the authorized_keys
-file on the host.
add a comment |
Your question seems to relate more to using ssh than the fact that you're running Jenkins in Docker. So I'll focus on that.
When using ssh keypairs, you'll want to generate your keypair client-side and provide the public key to the host. So you're right that you want to generate on server A
and share your key with server B
.
For which user you want to add the key depends on where you add the key to the authorized_keys
-file on server B
. It doesn't matter what users you have on server A
, as long as you ssh into server B
using the correct user.
e.g.: if you have added the key to the authorized_keys
-file for user foo
on server B
, then you'll want to ssh into it using something akin to ssh foo@server_b
.
As for the location of storing your keys, the keypair will usually reside in ~/.ssh on your client. And, as stated above, the content of the public key will be stored as a line in the authorized_keys
-file on the host.
Your question seems to relate more to using ssh than the fact that you're running Jenkins in Docker. So I'll focus on that.
When using ssh keypairs, you'll want to generate your keypair client-side and provide the public key to the host. So you're right that you want to generate on server A
and share your key with server B
.
For which user you want to add the key depends on where you add the key to the authorized_keys
-file on server B
. It doesn't matter what users you have on server A
, as long as you ssh into server B
using the correct user.
e.g.: if you have added the key to the authorized_keys
-file for user foo
on server B
, then you'll want to ssh into it using something akin to ssh foo@server_b
.
As for the location of storing your keys, the keypair will usually reside in ~/.ssh on your client. And, as stated above, the content of the public key will be stored as a line in the authorized_keys
-file on the host.
answered Jan 21 at 16:35
MartinMartin
7316
7316
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1394857%2fjenkins-in-docker-and-ssh%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