search

yrzr / gitlab-ce-arm64v8-docker

Build aarch64 docker image for gitlab-ce
https://hub.docker.com/r/yrzr/gitlab-ce-arm64v8
33 stars 6 forks source link

macos m2, version 16.3, restart error, gitlab-ctl start postgresql failed #1

Closed hxgqh closed 10 months ago

hxgqh commented 11 months ago

image

image

yrzr commented 11 months ago

@hxgqh Would you post the log file of Postgres? It can be located at /var/log/gitlab/postgresql/ inside the container.

yippee0539 commented 10 months ago

@hxgqh Would you post the log file of Postgres? It can be located at /var/log/gitlab/postgresql/ inside the container.

again on my m2 device. almost the same error below are logs tag is lastest

# gitlab-ctl tail postgresql 2023-10-29_13:32:02.58997 LOG: starting PostgreSQL 13.11 on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1\~20.04.2) 9.4.0, 64-bit 2023-10-29_13:32:02.59107 LOG: could not set permissions of file "/var/opt/gitlab/postgresql/.s.PGSQL.5432": Invalid argument 2023-10-29_13:32:02.59118 WARNING: could not create Unix-domain socket in directory "/var/opt/gitlab/postgresql" 2023-10-29_13:32:02.59129 FATAL: could not create any Unix-domain sockets 2023-10-29_13:32:02.59348 LOG: database system is shut down 2023-10-29_13:32:03.63752 LOG: starting PostgreSQL 13.11 on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1\~20.04.2) 9.4.0, 64-bit 2023-10-29_13:32:03.63861 LOG: could not set permissions of file "/var/opt/gitlab/postgresql/.s.PGSQL.5432": Invalid argument 2023-10-29_13:32:03.63875 WARNING: could not create Unix-domain socket in directory "/var/opt/gitlab/postgresql" 2023-10-29_13:32:03.63898 FATAL: could not create any Unix-domain sockets 2023-10-29_13:32:03.64102 LOG: database system is shut down 2023-10-29_13:32:04.67984 LOG: s

yippee0539 commented 10 months ago

help, help

yrzr commented 10 months ago

Seems this problem also replicates on the official image on AMD64, see this issue.

Would you try their solution and see if it works?

yippee0539 commented 10 months ago

Seems this problem also replicates on the official image on AMD64, see this issue.

Would you try their solution and see if it works?

yeah, it is solved now, thanks, my hero