blob: 11cd9d2b9e4b369a2fec533b360e71f656b40639 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
# Fire up system container for GN
# Tags
* assigned: pjotrp
* priority: medium
* type: system administration
* keywords: system administration, GN, tux01, tux02, tux04, balg01
# Tasks
We have the following check list
* [ ] Create a system definition
* [ ] Fire up container and get a shell inside using nsenter
* [ ] Start mariadb
* [ ] Start redis
## Create a system definition
We create
=> https://git.genenetwork.org/gn-machines/tree/fallback.scm
and the accompanying shell script.
To build the system container you need to add channels. Check the setup with `guix describe'. It should show something like
```
Generation 1 Mar 01 2024 17:01:22 (current)
gn-bioinformatics 5fa3e2b
repository URL: https://git.genenetwork.org/guix-bioinformatics
branch: master
commit: 5fa3e2bcaafb498ec3bca51f72545f5a16b5a527
guix-forge 6c622a6
repository URL: https://git.systemreboot.net/guix-forge/
branch: main
commit: 6c622a67051c22eeefe37eedb17d427fbb70c99b
guix-past 921f845
repository URL: https://gitlab.inria.fr/guix-hpc/guix-past
branch: master
commit: 921f845dc0dec9f052dcda479a15e787f9fd5b0a
guix aeaa390
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: aeaa390b71a15335bef03f83bd9dc946fa535398
```
after fetching the latest channels with `git pull` defining ~/.config/guix/channels.scm:
```
(list (channel
(name 'gn-bioinformatics)
(url "https://git.genenetwork.org/guix-bioinformatics")
(branch "master"))
(channel
(name 'guix-forge)
(url "https://git.systemreboot.net/guix-forge/")
(branch "main")
(introduction
(make-channel-introduction
"0432e37b20dd678a02efee21adf0b9525a670310"
(openpgp-fingerprint
"7F73 0343 F2F0 9F3C 77BF 79D3 2E25 EE8B 6180 2BB3")))))
```
Now make sure the right guix gets fired up (the one you built) and run a container script as defined in gn-machines.
```
which guix
./fallback-deploy.sh
```
To get a shell inside the system container try
```
nsenter -at 399307 /run/current-system/profile/bin/bash --login
herd status
```
Note that mysql and virtuoso are running inside the container. It is important that these daemons do not share files with other daemons(!)
# https certificates
On the host we need to tell nginx to forward to the system container. This is done with the nginx streaming library.
Note we use the stream feature of nginx. This requires on debian
```
apt-get install libnginx-mod-stream
```
Inside the contianer, the first time you may check the certificates
```
acme renew
```
After that you should be able to run
```
wget localhost:8891
ERROR 400
```
because there is no upstream python server yet.
# Start mariadb
Herd will tell you that mariadb is running and if you use the client from the store you can see there is no GN database yet.
```
/gnu/store/xj4bfqch8zs3sfzvj65ykbvnpprwaj7f-mariadb-10.10.2/bin/mysql -e 'show databases'
```
mariadb initialized a new database in /var/lib/msyql. We need to stop the container and use an existing database on the host. Make sure not to share it with the host daemon! Disable mariadb in systemd if it is enabled.
On restart the permissions in the container were not mysql.mysql user. So I had to do
```
chown mysql:mysql -R /var/lib/mysql/
herd enable mysql
herd start mysql
/gnu/store/xj4bfqch8zs3sfzvj65ykbvnpprwaj7f-mariadb-10.10.2/bin/mysql -uwebqtlout -pwebqtlout -e 'show databases'
+---------------------------+
| Database |
+---------------------------+
| db_GeneOntology |
| db_webqtl |
| db_webqtl_s |
+---------------------------+
```
Once I got this working, however, I decided to run mariadb on the base system instead (outside the container). The same with redis (see below).
# Start redis
After adding the default redis-service make sure the database is mounted on /var/lib/redis. `herd status` in the container will tell redis is running.
Note that, again, file permissions may prevent redis from running. Debug output appears in /var/log/messages.
The way to deal with this is chown in the activation stage. The alternative is to run a service directly on the host machine.
|
