➖ Docker can be a range of GIDs #4
linear_issue_open.yml
on: pull_request
sync-to-linear
4s
Annotations
1 error and 1 warning
sync-to-linear
Failed to create Linear issue: [{"message":"Variable \"$input\" got invalid value { title: \"➖ Docker can be a range of GIDs\", description: \"## Issue\\nWe've seen builds where the order of installs from the `install-utils` script can impact the `gid` of the `docker` group, but we specify that `docker` must be in `993` in our GOSS test\\n\\nhttps://github.com/buildkite/elastic-ci-stack-for-aws/blob/9965c106699eb60d938f81c813e81b9456b6a181/goss.yaml#L104\\n\\nThe install order in our instance [build](https://github.com/buildkite/elastic-ci-stack-for-aws/blob/9965c106699eb60d938f81c813e81b9456b6a181/packer/linux/buildkite-ami.pkr.hcl#L84) can determine the GIDs that packages get; `install-utils` runs first, so `993` may be taken by the time we install Docker.\\n\\n## Change\\nWe allow the `docker` group to have a GID between `990` and `995`, inclusive. We could expand this, but it _feels_ like a fine range to start with given we aren't aiming to add lots of packages.\\n\\n\\nOriginal PR: https://github.com/buildkite/elastic-ci-stack-for-aws/pull/1436\" }; Field \"teamId\" of required type \"String!\" was not provided.","locations":[{"line":2,"column":24}],"extensions":{"code":"BAD_USER_INPUT","type":"graphql error","userError":true,"meta":{}}}]
|
sync-to-linear
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|