能否将Docker容器作为服务运行？如何在GitLab CI/CD配置文件中实现依赖SQL数据库服务的主服务构建？

Alright, let's break down your questions about GitLab CI and Docker services clearly:

Yes, the core setup is valid for your use case, but there's a small redundancy and a key detail to note:

• The services directive works as intended: GitLab CI's services field is specifically designed to launch dependent containers alongside your job's main container. Your test.com/sql-db:1.0 will start up before the main-svc:1.5 job container runs, which fulfills the dependency need for main-svc to access the SQL database.
• Redundant docker pull command: The line docker pull test.com/main-svc:1.5 in your script is unnecessary. When you specify the image field for the job, GitLab Runner automatically pulls that image (if it's not already cached locally) to use as the job's execution environment. You can safely remove this line unless you have a specific reason to force a fresh pull (like bypassing cache for a critical update).
• Critical connection detail: To ensure main-svc can actually connect to sql-db, you need to use the service's name as the hostname in your database connection string. GitLab CI maps each service to a hostname matching its service name (so here, use sql-db instead of localhost). If your main-svc is configured to look for the DB at localhost, you'll need to adjust its settings to use sql-db as the database host.

Absolutely! GitLab CI's services feature supports any valid Docker image—whether it's your own custom image from Nexus, a public image like Redis, or any other containerized service. You can even add additional configuration for the service container if needed:

For example, if you want to add a second service with a custom alias and environment variables:

Build:
  image: test.com/main-svc:1.5
  services:
    - name: test.com/sql-db:1.0
    - name: test.com/another-service:2.0
      alias: my-custom-service  # Lets you access this service via the "my-custom-service" hostname
      variables:
        SERVICE_CONFIG_VAR: "specific-value"  # Pass environment variables to the service container
  script:
    - # Your job execution commands here

Just make sure your GitLab Runner has access to pull the image (if it's in a private Nexus repo, you'll need to configure runner credentials or set up authentication in your GitLab CI/CD settings).

内容的提问来源于stack exchange，提问作者user2201789