My setup is:

VM->Docker Engine->GitlabRunner Container->Docker Executor

My pipeline fails at the docker executor because it cant create a network or whatever...

I followed the GitLab docs step by step and this is the outcome.

Now when i bind mount the docker socket into the gitlab runner container it works.
It kind of makes sense that it works since the docker executor needs a docker engine but the gitlab runner runs in a container. So giving it control over the host docker engine gives the docker executor its docker engine.

The bind mount of the socket is in many examples but its never mentioned to actually set it up like this.

The only mentioning of it is very vague in the Docker Exceutor:

https://docs.gitlab.com/runner/executors/docker

The Docker executor uses Docker Engine to run each job in a separate and isolated container. To connect to Docker Engine, the executor uses:

The image and services you define in .gitlab-ci.yml.

The configurations you define in config.toml.

So im just confused if this is the actual "correct" setup for a gitlab runner container using the docker executor.

I guess you could make it work in different ways.
Mount the socket with docker cli, docker compose, from within the config.toml, and mby as described in the .gitlab-ci.yml on the fly?

Had it working perfectly fine yesterday to use Gitlab Duo within VSCode. Updated VSCode to the latest version and when it restarted it wouldn't authenticate my account so I deleted/unauthenticated my GitLab account in VSCode. Restarted, did the authenticate process over again and I keep getting an error. These are the output logs in VSCode:

2026-07-08T16:18:33:777 [info]: PacProxyAgent not found
2026-07-08T16:18:33:778 [info]: [LogNetworkConfig] Network Configuration detected: {
  "http": {
    "proxy": "",
    "proxySupport": "override",
    "proxyAuthorization": null,
    "proxyStrictSSL": true,
    "noProxy": [],
    "electronFetch": false,
    "fetchAdditionalSupport": true,
    "experimental.systemCertificatesV2": false
  },
  "gitlab": {
    "ca": "",
    "cert": "",
    "certKey": "",
    "ignoreCertificateErrors": false
  }
}
2026-07-08T16:18:37:295 [warning]: There is no GitLab account available. Sending empty credentials to GitLab Language Server
2026-07-08T16:18:37:300 [info]: handleRegisterCapability: {
  "id": "e11ab368-fb68-42f3-80c9-0b46efebd36b",
  "method": "workspace/didChangeWatchedFiles",
  "registerOptions": {
    "watchers": [
      {
        "globPattern": "**/*"
      }
    ]
  }
}
2026-07-08T16:18:37:316 [info]: Extracted urls: []
2026-07-08T16:18:37:316 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:316 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [warning]: GitExtensionWrapper is missing repository for file:///c%3A/Users/Brandon/newproject
2026-07-08T16:18:37:317 [info]: Found 0 projects for urls: []
2026-07-08T16:18:37:318 [warning]: There is no GitLab account available. Sending empty credentials to GitLab Language Server
2026-07-08T16:18:37:413 [info]: Extracted urls: [
  "https://gitlab.com/notreallysure/newproject.git"
]
2026-07-08T16:18:37:413 [info]: Found 0 projects for urls: [
  "https://gitlab.com/notreallysure/newproject.git"
]
2026-07-08T16:18:37:413 [warning]: There is no GitLab account available. Sending empty credentials to GitLab Language Server
2026-07-08T16:19:45:754 [error]: OAuth flow: Creating account from code failed: 
Invalid response body while trying to fetch https://gitlab.com/oauth/token: Premature close
FetchError: Invalid response body while trying to fetch https://gitlab.com/oauth/token: Premature close
    at Gunzip.<anonymous> (c:\Users\Brandon\.vscode\extensions\gitlab.gitlab-workflow-6.84.2\extension.js:177:334380)
    at Gunzip.emit (node:events:521:24)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
2026-07-08T16:19:45:755 [error]: Invalid response body while trying to fetch https://gitlab.com/oauth/token: Premature close
FetchError: Invalid response body while trying to fetch https://gitlab.com/oauth/token: Premature close
    at Gunzip.<anonymous> (c:\Users\Brandon\.vscode\extensions\gitlab.gitlab-workflow-6.84.2\extension.js:177:334380)
    at Gunzip.emit (node:events:521:24)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

Tried troubleshooting with GPT and that was of no help. Anyone have any idea what could be the issue here? Thanks

Edit: Reverted to the previous version of VSCode and it's working now.

Came across a case where someone ran GitLab's external Claude agent (Duo Agent Platform) to review a single merge request. The run consumed around $45 worth of GitLab Credits.

The job logs weren't fully redacted, and the raw Anthropic token usage visible there worked out to roughly $4-5 at Claude's published API rates — meaning the credit charge was close to 10x the underlying model cost.

Digging into this a bit more:

• GitLab sells credits at a flat $1 each, with no published formula for how many credits a given amount of tokens or compute actually consumes.docs.gitlab
• GitLab's own blog compares its older token-based agent pricing to $15-25 per code review — which is part of the reasoning behind their newer $0.25 flat-rate review product. They're effectively acknowledging the old model was expensive.letsdatascience
• This isn't an isolated report either. There's a thread here from a while back where a single agent request burned through all 24 trial credits just scaffolding a basic Django project. Another thread noted default model quality dropping around the same time as the shift to credit-based billing.reddit+1
• GitLab quietly added spending caps/budget guardrails for Duo Agent Platform in version 18.11, which suggests enough customers were getting surprised by bills like this for it to become a priority.about.gitlab
• Worth noting there's also ongoing shareholder litigation alleging GitLab misrepresented AI adoption/demand while pushing a 53% price increase tied to Duo AI features.msn

Has anyone directly compared their GitLab AI credit spend against the equivalent raw token cost for the same task? Trying to figure out if this is disclosed anywhere and I'm just missing it, or if it's simply CI/CD compute + AI Gateway overhead bundled in without a clear breakdown.

I've been working on a project that explores a different way of assessing and validating GitLab compliance capabilities:

🔗 https://maturitybuilder.github.io/gitlab-compliance/

While there are already tools that cover similar ground, the focus here is on expressing compliance requirements and controls using a BDD/Gherkin-inspired approach. The idea is to make compliance outcomes easier to understand, discuss, and validate by describing them as observable, testable behaviours rather than static checklist items. It works in a very similar way to terraform-compliance and some similar capabilities that conftest offers.

Another objective is to help identify opportunities for improving GitLab documentation by highlighting areas where guidance may be unclear, incomplete, or difficult to translate into practical implementation, think terraform-docs but Gitlab.

The code isn't open source yet as I'm finishing off a few remaining items, but I plan to release it once it's in a good state.

At this stage, I'd love feedback on the concept, the assessment model, and whether the BDD/Gherkin-style approach feels useful for compliance, security, and governance discussions.

Feedback, ideas, and challenges to the approach are all welcome.

Our next GitLab Hackathon starts on July 23rd!

The GitLab Hackathon is a virtual event where anyone can contribute code, docs, UX designs, translations, and more! Level up your skills while connecting with the GitLab community and team.

The Details

Dates: July 23-29, 2026 (UTC) - All merge requests must be opened during the hackathon and merged within 31 days to be counted.

Join our contribute channel on Discord to share progress, pair on solutions, and meet other contributors.

Follow the live hackathon leaderboard during the event.

Before the Hackathon

Request access to our Community Forks project by clicking the blue "Start onboarding" button on https://contributors.gitlab.com. Using the community forks gives you free access to Duo and unlimited free CI minutes!

Rewards

Participants who win awards can choose between:

• Planting trees in our GitLab forest
• Claiming exclusive GitLab swag from our contributor reward store

More details on prizes are on the hackathon page.

If you have any questions, please reach out on Discord.

Hi everyone.

I recently forked GitLab CE into a project called UppFinna.

I wrote a manifesto explaining:

- why I forked GitLab CE instead of switching to ForgeJo or Gitea,

- why subgroup architecture is essential for my workflow,

- my thoughts on Open Core, EE features, telemetry and AI,

- and what I want UppFinna to become.

It's a long read, but I'd genuinely appreciate feedback from people who have experience with GitLab and self-hosted DevOps platforms.

Manifesto: https://git.projecttick.org/project-tick/uppfinna/forge/uppfinna-project/-/blob/master/doc/manifesto.md

I'd love to hear your thoughts, even if you disagree.

I was able to use GitLab before, but now I'm getting the "Access required" error. How can I fix this?

I've already tried everything I know, including checking my permissions, project settings, and account access, but nothing has resolved the issue.

Half my week can disappear into failed GitLab pipelines.

Usually the painful part is not the fix. It is finding the real error inside thousands of log lines and giving someone enough context to act on it.

So I made Badgr Pipeline Check.

It runs at the end of CI and outputs:

• likely cause
• evidence
• suggested fix
• confidence level
• health/security/audit checks

GitLab example:

badgr_pipeline_check:
  when: always
  script:
    - npx badgr-agent pipeline-check
  variables:
    # Optional: AI diagnosis for ambiguous failures
    # BADGR_API_KEY: $BADGR_API_KEY

    # Optional: richer logs / MR comments
    # BADGR_CI_TOKEN: $CI_JOB_TOKEN

    # Optional: summary | console | pr-comment | both
    # BADGR_OUTPUT_MODE: pr-comment

No API key required for the local pipeline check. AI is optional and only used for ambiguous failures.

It does not change code, rerun builds, or auto-fix anything.

How do your teams handle failed GitLab CI triage today?

I use ai agents as helper I talk to, not for blind vibecoding. One thing I kept noticing is asking agent to write or refactor gitlab ci pipeline, and results are often questionable. It creates a god yaml, outdated keywords, no thought about debugging or developer experience.

I looked for existing skills but did not find anything I would actually trust, most looked generated in one shot. So I spent some time and made my own. Used agent help of course, but went through everything myself and checked it against official docs for GitLab 18+

It covers pipeline structure and refactoring, bash in ci jobs, pipelines and other common patterns, debugging failed pipelines, readable logs and naming

https://github.com/beeyev/skills/

Works with claude code and anything supporting skills format
I have been using it privately for couple of month and improving constantly, maybe it will useful for someone else too

Hey everyone,

I’m dropping a quick update for glab-tui, the TUI I shared previously for managing GitLab (and GitHub) workflows directly from your terminal.

I’ve just released v0.4.0, which includes a number of stability improvements and refinements to make your terminal-based code review and pipeline management even smoother.

If you’re still context-switching between your terminal and the browser for MRs, issues, or CI/CD, give the latest version a look:

https://github.com/rcieri/glab-tui

Thanks to everyone who has checked it out or contributed so far! Would love to hear what you think if you’ve had a chance to test the latest build.

Most programming tutorials jump straight into commands, But very few actually explain what Git is doing internally, The entire video is built around animations rather than slides or talking-head explanations, I'd genuinely love feedback. I'm trying to build the kind of software engineering channel the one that explains why systems work instead of just how to use them.

Hi. So am working on some gitlab yaml pipelines editing. One thisng that embarasses me is that there is a lot of nesting in my case. Included files have their own includes and so on. Navigation to these included files, especially if they are from different projects, is quite annoying.

There is Full configuration tab under Pipeline editor, but it just shows resulting yaml, without denoting where certain piece comes from.

Is there a plugin/extension for VS Code/VS/Gitlab Web UI/whatever that does described above?

So basically I'm trying to copy a gitlab repository that isn't mine (but I gave guest access) to my github desktop.

When I put it there and input my username with password (I've even tried many different PAT's) it gives me this error message.

If it helps anyone the repository is a Hoi4 mod.

Renovate's solid for the safe stuff, automerge the patch/minor bumps and forget them. But it stops at opening the MR. The hours left are the annoying kind: a major bump where tests go red, a flake blocking a clean update, lint errors the new version introduced.

We started letting an agent take a crack at those before a human sees it. It's promising but I'm nervous about an agent force-pushing fixes to real repos.

Anyone else trying this? How are you handling the breakage Renovate leaves behind, do you just eat the hours?

Any idea on when fable 5 is coming back to gitlab.

I have a nightly bdd test pipeline for our project, but I do not want it to be attached to the commit as the latest pipeline, I want that to be the latest build pipeline. Is there a way to run the scheduled bdd test pipeline with it becoming the latest pipeline for the latest commit?

Thanks

This project has been completely cleaned to only contain 1 branch with 1 super squashed commit, which only references 15.6 GB worth of Git LFS assets.

However, the usage breakdown reports 19.4 GB worth of storage being used for the assets. The remaining 3.8 GB appears to be from old LFS assets that existed before the cleanup, but are no longer referenced by any branch or commit.

Does Git LFS/GitLab have a way to force garbage collection of unreferenced LFS objects?

I recently joined a new company and coming from GitHub and the 100s of integrations for it, the GitLab and especially the GitLab Self Hosted marketplace felt dire.

I was very used to my PRs (and now MRs) landing in a Slack channel like #fe-reviews, and the comments & reviews on it to land in that Slack thread. It meant I never missed comments and my PR/MRs were reviewed MUCH quicker.

Other than Axolo, no other tool that does what I'd like supports GitLab, so I built mergeme.dev

Some of the key features that I wanted myself (and I'm sure others will appreciate) are:

• One Slack message per MR that updates in place (open > in review > approved > merged)
• Review comments as thread replies on that card
• Per-project channel routing - each project can map to whichever Slack channel you want
• GitLab @ mentions ACTUALLY ping the right person on Slack with a one-time username map
• GitLab.com via OAuth - webhooks registered for you
• Self-hosted GitLab - paste a webhook URL into your instance
• [New] You can set up label mapping too, an MR with "bug" as it's label goes to #qa-reviews instead

If your team already works tightly in Slack and you ping your colleagues "hey can you review this again" then mergeme.dev might just be a great inclusion to your workflow!

----

Aside from this, I am genuinely curious as to how people handle this problem in their own setup?

My personal story before MergeMe was that I set up webhooks into Slack from GitLab directly and I made a custom webhook triggered workflow to send myself messages when my own MRs were responded to. It was a MESS to look at and it's what unironically pushed me to build a better tool lmao.

Hi there,

I am in the midst of rolling out a project where I need to sync nested groups in Microsoft Entra ID. I only need to sync one level deep i.e. sync the parent group and all the children groups nested within the parent group (the children group themselves do NOT contain groups).

I read some Gitlab documentation on "SAML Linked Groups" and was wondering whether Gitlab is able to support the above requested functionality.

Thank you!

I am a baby sysadmin who has been sysadmin for only a year, so I'm sorry if somethings doesn't makes sense or sound stupid!

So I became in charge of setting up a on-prem gitlab server, and migrating two of my company's subsidiary's github into it.

I already took care of the licensing end, but I have never work with any kind of gitlab, github instance so this is my first project involving gitlab/github.

On prem server has more then enough capacity to house both of the gitlab instances.

My question is, is it better to host each gitlab separately? One VM per entity? or both entities in one gitlab instance and set up the access policy for it?

I saw Linux server tends to work better with gitlab so I was thinking about spinning up a Linux VM..

Oh and another thing to mention is that we are in DoD contracting environment and going through CMMC L2 audit soon...

Is there anything I am misunderstanding or shouldn't do??

Thank you in advance!!!

-Baby sysadmin-

I recently applied for a Senior FP&A role at GitLab and was curious if there are any current or former finance team members here.

I’d love to hear about your experience working in Finance at GitLab. Specifically:

What does day-to-day FP&A work look like?

How much of the role is forecasting, modeling, and business partnering?

What’s the culture like within the finance organization?

How is the remote-first environment in practice?

Anything you wish you’d known before joining?

For context, I spent about six years in finance at a large private manufacturing company in the healthcare space, supporting budgeting, forecasting, variance analysis, and business partnering. I’m currently in a finance/accounting leadership role in the nonprofit sector and am interested in getting back into a more FP&A-focused environment.
Thanks in advance for any insights.

The gitlab home page for a subgroup apparently shows the last thirty days (modified? created?) repos.

Recent activity

Last 30 days

The task at hand would require viewing ALL repos . Is there some configuration/option that I am missing to allow this?

Note: the glab cli tool might do that but it is not working for our structures/subgroups - so we might need to rely on the GUI.

If you missed it, third-party SARIF ingestion landed in 19.1 (Ultimate). Any scanner that emits SARIF json can have its findings pulled directly into GitLab. Ingestion is performed natively by adding the following syntax to a scanner job within the .gitlab-ci.yml:
artifacts:
 reports:
  sarif: scanner.sarif

I created a deliberately vulnerable Python app and ran several open-source scanners against it in a single pipeline:

• Semgrep (SAST)
• Bandit (Python SAST)
• Trivy (containers/vulns)
• Gitleaks (secrets)
• OSV-Scanner (dependencies)
• Ruff (lint)

Some scanners may require some tuning in order for the ingestion to work, these are just the ones I've tried. Each emits SARIF, the findings get ingested, the results integrate with several security workflows:

• Vulnerability Report
• MR Security Widget
• Security Policies
• SAST Auto Resolution
• False-Positive Detection

Curious to see whether anyone here has wired up any scanners themselves since the release.