Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
concrexit
concrexit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • thalia
  • concrexitconcrexit
  • Merge Requests
  • !1277

Merged
Created May 28, 2019 by Jelle Besseling@jbesselingMaintainer

Start uwsgi with `exec` so it receives signals correctly

  • Overview 0
  • Commits 2
  • Changes 2

Short description

This article advices to use exec when starting docker containers using a shell script.

It makes sure the entrypoint of the docker container receives the signals sent by docker, e.g. when docker stop is used.

Edited May 28, 2019 by Jelle Besseling
Assignee
Assign to
Reviewer
Request review from
24
Milestone
24
Assign milestone
Time tracking
Source branch: uwsgi-exec