Backup problem after moving to docker

Hi

I am using latest version of gitlable-ce. 2 days ago I’ve moved all my setup to official docker container.
Nothing has changed in terms of cpu/ram etc.
Everythings works like a charm except backup.
When I run ‘gitlab-rake gitlab:backup:create’ on container shell I got error

bc2017-05-15_06:05:45.22838 LOG:  server process (PID 3430) was terminated by signal 9: Killed
2017-05-15_06:05:45.23151 DETAIL:  Failed process was running: COPY public.merge_request_diffs (id, state, st_commits, st_diffs, merge_request_id, created_at, updated_at, base_commit_sha, real_size, head_commit_sha, start_commit_sha) TO stdout;
2017-05-15_06:05:45.23152 LOG:  terminating any other active server processes
2017-05-15_06:05:45.24489 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.24491 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.24491 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.24492 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.24492 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.24492 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.24494 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.24495 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.24495 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.24496 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.24496 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.24497 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.24652 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.24653 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.24653 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.24852 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.24854 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.24854 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.26217 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.26219 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.26219 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.26297 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.26298 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.26299 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.26535 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.26537 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.26538 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.26669 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.26671 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.26672 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.26709 WARNING:  terminating connection because of crash of another server process
2017-05-15_06:05:45.26710 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-05-15_06:05:45.26711 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-05-15_06:05:45.29861 LOG:  all server processes terminated; reinitializing
2017-05-15_06:05:45.37183 LOG:  database system was interrupted; last known up at 2017-05-15 06:05:00 GMT
2017-05-15_06:05:45.44987 LOG:  database system was not properly shut down; automatic recovery in progress
2017-05-15_06:05:45.45566 LOG:  redo starts at CA/8000098
2017-05-15_06:05:45.45838 LOG:  unexpected pageaddr C9/FA000000 in log segment 00000001000000CA00000009, offset 0
2017-05-15_06:05:45.45844 LOG:  redo done at CA/8000098
2017-05-15_06:05:45.46673 LOG:  MultiXact member wraparound protections are now enabled
2017-05-15_06:05:45.46800 LOG:  database system is ready to accept connections
2017-05-15_06:05:45.46918 LOG:  autovacuum launcher started