Docker deployment gitlab service ssh push does not go up

for the service deployed with docker-compose, the web page opens normally, and the public key has been added to the setting.
No matter how push prompts the permission error..

version: "3"
services:
  gitlab:
    image: gitlab/gitlab-ce
    container_name: gitlab
    restart: always
    hostname: "129.211.1.18"
    environment:
      TZ: "Asia/Shanghai"
      GITLAB_OMNIBUS_CONFIG: |
        external_url "http://129.211.1.18:9090"
        gitlab_rails["time_zone"] = "Asia/Shanghai"
        unicorn["worker_timeout"] = 60
        unicorn["worker_processes"] = 2
        gitlab_rails["gitlab_shell_ssh_port"] = 2222
    ports:
      - "9090:9090"
      - "2222:22"
    volumes:
      - "/home/gitlab/config:/etc/gitlab"
      - "/home/gitlab/logs:/var/log/gitlab"
      - "/home/gitlab/data:/var/opt/gitlab/git-data"

Docker gitlab

May.06,2022

self-answer: the push prefix does not add ssh://, which leads to the fact that it is https, so it doesn't work.

Previous: How to modify module variables imported by node

Next: How to synchronize the structure or data of database A to database B by datagrip

My younger brother is learning docker, and wants to build a gitlab service. Why does the gitlab container always starting, or starting a few seconds after it starts?
I am learning docker, and want to build a gitlab service. Why does the gitlab container keep starting, or ask for advice from all kinds of gods a few seconds after it starts? description of the sharp-sharp-sharp problem the environmental background of...

Docker gitlab-ce

Apr.09,2021