Обсуждение: pgAdmin4 Docker deployment issue

Поиск
Список
Период
Сортировка

pgAdmin4 Docker deployment issue

От
Bas Cancrinus
Дата:
Dear list,

I'm trying to deploy the official pgAdmin4 Docker image (dpage/pgadmin4) in a sloppy.io Docker container. Unfortunately my health checks keep on failing. When I looked at the logs (see below) I noticed that the image spawned many worker threads.

I believe that the thread spawning could be the reason for the image not to start. Is it possible to control the amount of spawned worker threads? Has anybody had similar experiences with this image?

Many thanks in advance!

Cheers,
Bas

Here are the relevant logs:

[1] [INFO] Starting gunicorn 19.7.1
[1] [INFO] Listening at: http://0.0.0.0:80 (1)
[1] [INFO] Using worker: threads
[13] [INFO] Booting worker with pid: 13
[18] [INFO] Booting worker with pid: 18
[23] [INFO] Booting worker with pid: 23
[28] [INFO] Booting worker with pid: 28
[33] [INFO] Booting worker with pid: 33
[38] [INFO] Booting worker with pid: 38
[43] [INFO] Booting worker with pid: 43
[48] [INFO] Booting worker with pid: 48
[53] [INFO] Booting worker with pid: 53
[58] [INFO] Booting worker with pid: 58
[63] [INFO] Booting worker with pid: 63
[68] [INFO] Booting worker with pid: 68
[73] [INFO] Booting worker with pid: 73
[78] [INFO] Booting worker with pid: 78
[83] [INFO] Booting worker with pid: 83
[88] [INFO] Booting worker with pid: 88
[93] [INFO] Booting worker with pid: 93
[98] [INFO] Booting worker with pid: 98
[103] [INFO] Booting worker with pid: 103
[108] [INFO] Booting worker with pid: 108
[113] [INFO] Booting worker with pid: 113
[118] [INFO] Booting worker with pid: 118
[123] [INFO] Booting worker with pid: 123
[128] [INFO] Booting worker with pid: 128
[133] [INFO] Booting worker with pid: 133
[138] [INFO] Booting worker with pid: 138
[143] [INFO] Booting worker with pid: 143
[148] [INFO] Booting worker with pid: 148
[153] [INFO] Booting worker with pid: 153
[158] [INFO] Booting worker with pid: 158
[163] [INFO] Booting worker with pid: 163
[168] [INFO] Booting worker with pid: 168
[173] [INFO] Booting worker with pid: 173
[178] [INFO] Booting worker with pid: 178
[183] [INFO] Booting worker with pid: 183
[188] [INFO] Booting worker with pid: 188
[193] [INFO] Booting worker with pid: 193
[198] [INFO] Booting worker with pid: 198
[203] [INFO] Booting worker with pid: 203
[208] [INFO] Booting worker with pid: 208
[213] [INFO] Booting worker with pid: 213
[218] [INFO] Booting worker with pid: 218
[223] [INFO] Booting worker with pid: 223
[228] [INFO] Booting worker with pid: 228
[233] [INFO] Booting worker with pid: 233
[238] [INFO] Booting worker with pid: 238
[243] [INFO] Booting worker with pid: 243
[248] [INFO] Booting worker with pid: 248
[253] [INFO] Booting worker with pid: 253
[258] [INFO] Booting worker with pid: 258
[263] [INFO] Booting worker with pid: 263
[268] [INFO] Booting worker with pid: 268
[273] [INFO] Booting worker with pid: 273
[1] [INFO] Handling signal: term
[1] [INFO] Shutting down: Master
--
Bas Cancrinus, MSc.
Pettenkoferstr. 10A, 10247 Berlin, Germany

Re: [MASSMAIL]pgAdmin4 Docker deployment issue

От
gilberto.castillo@etecsa.cu
Дата:
Hi
See you https://medium.com/@gilbertocastillo

El 2018-06-18 13:56, Bas Cancrinus escribió:
> Dear list,
> 
> I'm trying to deploy the official pgAdmin4 Docker image
> (dpage/pgadmin4) in a sloppy.io [1] Docker container. Unfortunately my
> health checks keep on failing. When I looked at the logs (see below) I
> noticed that the image spawned many worker threads.
> 
> I believe that the thread spawning could be the reason for the image
> not to start. Is it possible to control the amount of spawned worker
> threads? Has anybody had similar experiences with this image?
> 
> Many thanks in advance!
> 
> Cheers,
> Bas
> 
> Here are the relevant logs:
> 
> [1] [INFO] Starting gunicorn 19.7.1
> [1] [INFO] Listening at: http://0.0.0.0:80 (1)
> [1] [INFO] Using worker: threads
> [13] [INFO] Booting worker with pid: 13
> [18] [INFO] Booting worker with pid: 18
> [23] [INFO] Booting worker with pid: 23
> [28] [INFO] Booting worker with pid: 28
> [33] [INFO] Booting worker with pid: 33
> [38] [INFO] Booting worker with pid: 38
> [43] [INFO] Booting worker with pid: 43
> [48] [INFO] Booting worker with pid: 48
> [53] [INFO] Booting worker with pid: 53
> [58] [INFO] Booting worker with pid: 58
> [63] [INFO] Booting worker with pid: 63
> [68] [INFO] Booting worker with pid: 68
> [73] [INFO] Booting worker with pid: 73
> [78] [INFO] Booting worker with pid: 78
> [83] [INFO] Booting worker with pid: 83
> [88] [INFO] Booting worker with pid: 88
> [93] [INFO] Booting worker with pid: 93
> [98] [INFO] Booting worker with pid: 98
> [103] [INFO] Booting worker with pid: 103
> [108] [INFO] Booting worker with pid: 108
> [113] [INFO] Booting worker with pid: 113
> [118] [INFO] Booting worker with pid: 118
> [123] [INFO] Booting worker with pid: 123
> [128] [INFO] Booting worker with pid: 128
> [133] [INFO] Booting worker with pid: 133
> [138] [INFO] Booting worker with pid: 138
> [143] [INFO] Booting worker with pid: 143
> [148] [INFO] Booting worker with pid: 148
> [153] [INFO] Booting worker with pid: 153
> [158] [INFO] Booting worker with pid: 158
> [163] [INFO] Booting worker with pid: 163
> [168] [INFO] Booting worker with pid: 168
> [173] [INFO] Booting worker with pid: 173
> [178] [INFO] Booting worker with pid: 178
> [183] [INFO] Booting worker with pid: 183
> [188] [INFO] Booting worker with pid: 188
> [193] [INFO] Booting worker with pid: 193
> [198] [INFO] Booting worker with pid: 198
> [203] [INFO] Booting worker with pid: 203
> [208] [INFO] Booting worker with pid: 208
> [213] [INFO] Booting worker with pid: 213
> [218] [INFO] Booting worker with pid: 218
> [223] [INFO] Booting worker with pid: 223
> [228] [INFO] Booting worker with pid: 228
> [233] [INFO] Booting worker with pid: 233
> [238] [INFO] Booting worker with pid: 238
> [243] [INFO] Booting worker with pid: 243
> [248] [INFO] Booting worker with pid: 248
> [253] [INFO] Booting worker with pid: 253
> [258] [INFO] Booting worker with pid: 258
> [263] [INFO] Booting worker with pid: 263
> [268] [INFO] Booting worker with pid: 268
> [273] [INFO] Booting worker with pid: 273
> [1] [INFO] Handling signal: term
> [1] [INFO] Shutting down: Master
> --
> 
> Bas Cancrinus, MSc.
> Pettenkoferstr. 10A, 10247 Berlin, Germany
> 
> 
> Links:
> ------
> [1] http://sloppy.io


Re: pgAdmin4 Docker deployment issue

От
Bas Cancrinus
Дата:
Nailed it: I didn't assign enough RAM to the container. Increasing it from 64M to 128M solved my problem.

On Mon, Jun 18, 2018 at 7:56 PM Bas Cancrinus <bas@bascan.eu> wrote:
Dear list,

I'm trying to deploy the official pgAdmin4 Docker image (dpage/pgadmin4) in a sloppy.io Docker container. Unfortunately my health checks keep on failing. When I looked at the logs (see below) I noticed that the image spawned many worker threads.

I believe that the thread spawning could be the reason for the image not to start. Is it possible to control the amount of spawned worker threads? Has anybody had similar experiences with this image?

Many thanks in advance!

Cheers,
Bas

Here are the relevant logs:

[1] [INFO] Starting gunicorn 19.7.1
[1] [INFO] Listening at: http://0.0.0.0:80 (1)
[1] [INFO] Using worker: threads
[13] [INFO] Booting worker with pid: 13
[18] [INFO] Booting worker with pid: 18
[23] [INFO] Booting worker with pid: 23
[28] [INFO] Booting worker with pid: 28
[33] [INFO] Booting worker with pid: 33
[38] [INFO] Booting worker with pid: 38
[43] [INFO] Booting worker with pid: 43
[48] [INFO] Booting worker with pid: 48
[53] [INFO] Booting worker with pid: 53
[58] [INFO] Booting worker with pid: 58
[63] [INFO] Booting worker with pid: 63
[68] [INFO] Booting worker with pid: 68
[73] [INFO] Booting worker with pid: 73
[78] [INFO] Booting worker with pid: 78
[83] [INFO] Booting worker with pid: 83
[88] [INFO] Booting worker with pid: 88
[93] [INFO] Booting worker with pid: 93
[98] [INFO] Booting worker with pid: 98
[103] [INFO] Booting worker with pid: 103
[108] [INFO] Booting worker with pid: 108
[113] [INFO] Booting worker with pid: 113
[118] [INFO] Booting worker with pid: 118
[123] [INFO] Booting worker with pid: 123
[128] [INFO] Booting worker with pid: 128
[133] [INFO] Booting worker with pid: 133
[138] [INFO] Booting worker with pid: 138
[143] [INFO] Booting worker with pid: 143
[148] [INFO] Booting worker with pid: 148
[153] [INFO] Booting worker with pid: 153
[158] [INFO] Booting worker with pid: 158
[163] [INFO] Booting worker with pid: 163
[168] [INFO] Booting worker with pid: 168
[173] [INFO] Booting worker with pid: 173
[178] [INFO] Booting worker with pid: 178
[183] [INFO] Booting worker with pid: 183
[188] [INFO] Booting worker with pid: 188
[193] [INFO] Booting worker with pid: 193
[198] [INFO] Booting worker with pid: 198
[203] [INFO] Booting worker with pid: 203
[208] [INFO] Booting worker with pid: 208
[213] [INFO] Booting worker with pid: 213
[218] [INFO] Booting worker with pid: 218
[223] [INFO] Booting worker with pid: 223
[228] [INFO] Booting worker with pid: 228
[233] [INFO] Booting worker with pid: 233
[238] [INFO] Booting worker with pid: 238
[243] [INFO] Booting worker with pid: 243
[248] [INFO] Booting worker with pid: 248
[253] [INFO] Booting worker with pid: 253
[258] [INFO] Booting worker with pid: 258
[263] [INFO] Booting worker with pid: 263
[268] [INFO] Booting worker with pid: 268
[273] [INFO] Booting worker with pid: 273
[1] [INFO] Handling signal: term
[1] [INFO] Shutting down: Master
--
Bas Cancrinus, MSc.
Pettenkoferstr. 10A, 10247 Berlin, Germany
--
Bas Cancrinus, MSc.
Pettenkoferstr. 10A, 10247 Berlin, Germany