Provisioning a Gitlab CI VirtualBox Runner with Vagrant
1) Context
I am running a build pipeline using Gitlab's VirtualBox runner (Gitlab version 10.6.3). When I manually create a base image (e.g. my-base-vm), then the build runs perfectly on the 1-n clones that Gitlab-CI creates.
2) Observed error
However, when I want to provision the base image using Vagrant (version 2.2.2), the Gitlab CI build ouput for my job shows the following:
Running with gitlab-runner 11.2.0 (35e8515d)
on myproject-build-machine 1c8ab769
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Preparation failed: ssh: handshake failed: read tcp 127.0.0.1:35542->127.0.0.1:34963: read: connection reset by peer
Will be retried in 3s ...
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Job failed: execution took longer than 1h0m0s seconds
The image is based on the base image ubuntu/bionic64.
3) Configuration
The runner (clone from my-base-vm) seems to have the right NAT rules though (output of VBoxManage showvminfo my-base-vm-runner-1c8ab769-concurrent-0):
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = 127.0.0.1, host port = 32805, guest ip = , guest port = 22
NIC 1 Rule(1): name = ssh, protocol = tcp, host ip = 127.0.0.1, host port = 2222, guest ip = , guest port = 22
The Gitlab config.toml is configured with the correct username + password (vagrant:vagrant) and the Vagrant file provisions the machine to accept username and password as means of authentication (excerpt from Vagrantfile):
config.vm.provision "shell", inline: <<-SHELL
sed -i 's/ChallengeResponseAuthentication no/ChallengeResponseAuthentication yes/g' /etc/ssh/sshd_config
sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config
service ssh restart
SHELL
virtualbox vagrant gitlab
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
add a comment |
1) Context
I am running a build pipeline using Gitlab's VirtualBox runner (Gitlab version 10.6.3). When I manually create a base image (e.g. my-base-vm), then the build runs perfectly on the 1-n clones that Gitlab-CI creates.
2) Observed error
However, when I want to provision the base image using Vagrant (version 2.2.2), the Gitlab CI build ouput for my job shows the following:
Running with gitlab-runner 11.2.0 (35e8515d)
on myproject-build-machine 1c8ab769
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Preparation failed: ssh: handshake failed: read tcp 127.0.0.1:35542->127.0.0.1:34963: read: connection reset by peer
Will be retried in 3s ...
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Job failed: execution took longer than 1h0m0s seconds
The image is based on the base image ubuntu/bionic64.
3) Configuration
The runner (clone from my-base-vm) seems to have the right NAT rules though (output of VBoxManage showvminfo my-base-vm-runner-1c8ab769-concurrent-0):
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = 127.0.0.1, host port = 32805, guest ip = , guest port = 22
NIC 1 Rule(1): name = ssh, protocol = tcp, host ip = 127.0.0.1, host port = 2222, guest ip = , guest port = 22
The Gitlab config.toml is configured with the correct username + password (vagrant:vagrant) and the Vagrant file provisions the machine to accept username and password as means of authentication (excerpt from Vagrantfile):
config.vm.provision "shell", inline: <<-SHELL
sed -i 's/ChallengeResponseAuthentication no/ChallengeResponseAuthentication yes/g' /etc/ssh/sshd_config
sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config
service ssh restart
SHELL
virtualbox vagrant gitlab
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
add a comment |
1) Context
I am running a build pipeline using Gitlab's VirtualBox runner (Gitlab version 10.6.3). When I manually create a base image (e.g. my-base-vm), then the build runs perfectly on the 1-n clones that Gitlab-CI creates.
2) Observed error
However, when I want to provision the base image using Vagrant (version 2.2.2), the Gitlab CI build ouput for my job shows the following:
Running with gitlab-runner 11.2.0 (35e8515d)
on myproject-build-machine 1c8ab769
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Preparation failed: ssh: handshake failed: read tcp 127.0.0.1:35542->127.0.0.1:34963: read: connection reset by peer
Will be retried in 3s ...
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Job failed: execution took longer than 1h0m0s seconds
The image is based on the base image ubuntu/bionic64.
3) Configuration
The runner (clone from my-base-vm) seems to have the right NAT rules though (output of VBoxManage showvminfo my-base-vm-runner-1c8ab769-concurrent-0):
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = 127.0.0.1, host port = 32805, guest ip = , guest port = 22
NIC 1 Rule(1): name = ssh, protocol = tcp, host ip = 127.0.0.1, host port = 2222, guest ip = , guest port = 22
The Gitlab config.toml is configured with the correct username + password (vagrant:vagrant) and the Vagrant file provisions the machine to accept username and password as means of authentication (excerpt from Vagrantfile):
config.vm.provision "shell", inline: <<-SHELL
sed -i 's/ChallengeResponseAuthentication no/ChallengeResponseAuthentication yes/g' /etc/ssh/sshd_config
sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config
service ssh restart
SHELL
virtualbox vagrant gitlab
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
1) Context
I am running a build pipeline using Gitlab's VirtualBox runner (Gitlab version 10.6.3). When I manually create a base image (e.g. my-base-vm), then the build runs perfectly on the 1-n clones that Gitlab-CI creates.
2) Observed error
However, when I want to provision the base image using Vagrant (version 2.2.2), the Gitlab CI build ouput for my job shows the following:
Running with gitlab-runner 11.2.0 (35e8515d)
on myproject-build-machine 1c8ab769
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Preparation failed: ssh: handshake failed: read tcp 127.0.0.1:35542->127.0.0.1:34963: read: connection reset by peer
Will be retried in 3s ...
Using VirtualBox version 5.2.18_Ubuntur123745 executor...
Creating new VM...
ERROR: Job failed: execution took longer than 1h0m0s seconds
The image is based on the base image ubuntu/bionic64.
3) Configuration
The runner (clone from my-base-vm) seems to have the right NAT rules though (output of VBoxManage showvminfo my-base-vm-runner-1c8ab769-concurrent-0):
NIC 1 Rule(0): name = guestssh, protocol = tcp, host ip = 127.0.0.1, host port = 32805, guest ip = , guest port = 22
NIC 1 Rule(1): name = ssh, protocol = tcp, host ip = 127.0.0.1, host port = 2222, guest ip = , guest port = 22
The Gitlab config.toml is configured with the correct username + password (vagrant:vagrant) and the Vagrant file provisions the machine to accept username and password as means of authentication (excerpt from Vagrantfile):
config.vm.provision "shell", inline: <<-SHELL
sed -i 's/ChallengeResponseAuthentication no/ChallengeResponseAuthentication yes/g' /etc/ssh/sshd_config
sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/g' /etc/ssh/sshd_config
service ssh restart
SHELL
virtualbox vagrant gitlab
virtualbox vagrant gitlab
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
asked Jan 25 at 0:28
Maximilian C.Maximilian C.
1062
1062
add a comment |
add a comment |
0
active
oldest
votes
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%2f1398148%2fprovisioning-a-gitlab-ci-virtualbox-runner-with-vagrant%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1398148%2fprovisioning-a-gitlab-ci-virtualbox-runner-with-vagrant%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
