Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gitlab-runner
gitlab-runner
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,029
    • Issues 2,029
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 192
    • Merge Requests 192
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-runnergitlab-runner
  • Merge Requests
  • !776

Closed
Opened Dec 11, 2017 by MBcom@MBcom3 of 4 tasks completed3/4 tasks
  • Report abuse
Report abuse

Increased timeout times to solve issue #2408

  • Overview 38
  • Commits 7
  • Pipelines 7
  • Changes 2

What does this MR do?

Added higher timeouts in common/const.go, vendor/github.com/docker/go-connections/sockets/sockets.go and helpers/docker/sockets.go to avoid jobs being aborted, when docker daemon can not connect to docker.sock. This solves issue #2408 (closed).

Why was this MR needed?

This MR is needed because jobs which are using additional services like postgres, often (80-90%) fail with the error message: Cannot connect to unix:///var/run/docker.sock. Is the docker daemon running?.

Are there points in the code the reviewer needs to double check?

Maybe check, why "unit test (no race)" fails sometimes. In our production checks this error is not important for stability concerns, but it is not nice. Other checks are ok.

  • Documentation created/updated
  • Tests
    • Added for this feature/bug #2408 (closed)
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

#2408 (closed)

Edited Sep 02, 2020 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: gitlab-org/gitlab-runner!776
Source branch: master