Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
bob.admin
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
bob
bob.admin
Commits
4b4a198c
Commit
4b4a198c
authored
8 years ago
by
André Anjos
Browse files
Options
Downloads
Patches
Plain Diff
Fix indentation
parent
5f5d26c7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
install/docker-ci/README.md
+27
-26
27 additions, 26 deletions
install/docker-ci/README.md
with
27 additions
and
26 deletions
install/docker-ci/README.md
+
27
−
26
View file @
4b4a198c
...
@@ -8,46 +8,46 @@ This guide assumes you want to install a new CI machine from scratch, with
...
@@ -8,46 +8,46 @@ This guide assumes you want to install a new CI machine from scratch, with
1.
Install a base Debian 8.x distribution
1.
Install a base Debian 8.x distribution
2.
Install the following packages:
2.
Install the following packages:
```
sh
```
sh
$
apt-get update
$
apt-get update
$
apt-get
install
openssh-server curl vim-nox htop
$
apt-get
install
openssh-server curl vim-nox htop
```
```
3.
Make sure to copy access keys for personel at
`/root/.ssh/authorized_keys`
3.
Make sure to copy access keys for personel at
`/root/.ssh/authorized_keys`
4.
Access your machine via ssh from this point onwards, make sure it is OK
4.
Access your machine via ssh from this point onwards, make sure it is OK
5.
Follow the steps in section "Kernel Support" below for extended CPU and
5.
Follow the steps in section "Kernel Support" below for extended CPU and
memory control on docker containers, in case you need those
memory control on docker containers, in case you need those
6.
If there are locale problems, install the missing locales with:
6.
If there are locale problems, install the missing locales with:
```
sh
```
sh
$
dpkg-reconfigure locales
$
dpkg-reconfigure locales
```
```
7.
Install docker:
7.
Install docker:
```
sh
```
sh
$
curl
-sSL
https://get.docker.com/ | sh
$
curl
-sSL
https://get.docker.com/ | sh
```
```
8.
Install Gitlab CI:
8.
Install Gitlab CI:
```
sh
```
sh
$
curl
-L
https://packages.gitlab.com/install/repositories/runner/gitlab-ci-multi-runner/script.deb.sh | bash
$
curl
-L
https://packages.gitlab.com/install/repositories/runner/gitlab-ci-multi-runner/script.deb.sh | bash
```
```
9.
Add the
`gitlab-runner`
user to the docker group:
9.
Add the
`gitlab-runner`
user to the docker group:
```
sh
```
sh
$
usermod
-aG
docker gitlab-runner
$
usermod
-aG
docker gitlab-runner
```
```
10.
Register the runner and fine-tune its configuration:
10.
Register the runner and fine-tune its configuration:
```
sh
```
sh
$
gitlab-ci-multi-runner register
$
gitlab-ci-multi-runner register
$
vim /etc/gitlab-runner/config.toml
$
vim /etc/gitlab-runner/config.toml
$
service gitlab-runner restart
$
service gitlab-runner restart
```
```
If you'd like to user
`docker build`
, you'll need to register 2 runners: one
If you'd like to user
`docker build`
, you'll need to register 2 runners: one
with the
`docker`
executor and another with a
`shell`
executor (that can
with the
`docker`
executor and another with a
`shell`
executor (that can
access
`docker build`
. More information here:
access
`docker build`
. More information here:
https://docs.gitlab.com/ce/ci/docker/using_docker_build.html
https://docs.gitlab.com/ce/ci/docker/using_docker_build.html
11.
Configure docker to access Idiap's registry:
11.
Configure docker to access Idiap's registry:
```
sh
```
sh
$
mkdir
-p
/etc/docker/certs.d/docker.idiap.ch
$
mkdir
-p
/etc/docker/certs.d/docker.idiap.ch
$
scp ./docker.crt root@<machine>:/etc/docker/certs.d/docker.idiap.ch/
$
scp ./docker.crt root@<machine>:/etc/docker/certs.d/docker.idiap.ch/
$
scp ./gitlab.crt root@<machine>:/etc/docker/certs.d/docker.idiap.ch/
$
scp ./gitlab.crt root@<machine>:/etc/docker/certs.d/docker.idiap.ch/
```
```
## Kernel Support
## Kernel Support
...
@@ -99,4 +99,5 @@ $ make menuconfig
...
@@ -99,4 +99,5 @@ $ make menuconfig
# Save the new configuration
# Save the new configuration
$
fakeroot make-kpkg
--initrd
--revision
=
1.0.bob kernel_image
$
fakeroot make-kpkg
--initrd
--revision
=
1.0.bob kernel_image
$
dpkg
-i
../linux-image-
*
.dpkg
$
dpkg
-i
../linux-image-
*
.dpkg
$
shutdown
-r
now
```
```
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment