Skip to content

Cannot change git branch that dodal is pointing to in P51 k8s container #1363

Closed

Description

@subughimire420

In P51 container, the persistent volume is mounted in the scratch area.

Image

In theory, this should enable developers to change the git branches of modules installed in workspace_git.

In bluesky 1.7.1, I have run into permission issue.
Image

Acceptance Criteria

  • Change git branch of apps installed in workspace_git

Activity

  1. tpoliaw commented on Jan 30, 2026

    @tpoliaw
    Contributor

    While I think this was related to running as p51detector, would a temporary workaround be to pass the config option inline in the git command (so the /.gitconfig file doesn't need to be edited)?

    git -c safe.directory=/workspace_git/dodal status
    
  2. subughimire420 commented on Jan 30, 2026

    @subughimire420
    Author

    This bypassed the "dubious ownership" safety check but did not fix permission issues. As such could not pull & checkout to my dodal branch.

    Image
  3. dan-fernandes commented on Feb 2, 2026

    @dan-fernandes
    Contributor

    I think this may relate to securityContext not being propagated to the init container. Right now I don't think we can deterministically set / guess what user the init container will run at, and I have a feeling that this will cause permission errors when editing things the init container may have created (such as dependencies in the scratch area).

    I made and closed a PR here but will make a proper ticket for it.

    As discussed with @subughimire420 via Slack, the best approach right now is to have the main container run as UID 1000.

  4. added
    deploymentStuff related to running in production container
    on Feb 26, 2026
  5. abbiemery commented on Feb 26, 2026

    @abbiemery
    Contributor

    @subughimire420, @dan-fernandes did running as UID 1000 fix this? Is there anything left to be done on blueapi's side?

  6. subughimire420 commented on Feb 26, 2026

    @subughimire420
    Author

    Running as UID 1000 fixed the issue, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deploymentStuff related to running in production containerneeds confirmationDoes this bug still exist?

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions