#1 Global Leader in Data Resilience

Security Context Constraints(SCC) capabilities setting for Generic Storage Backup and Restore with OCP 4.11 or higher

KB ID: 4629
Product: Veeam Kasten for Kubernetes
Published: 2024-06-17
Last Modified: 2024-06-17
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Purpose

This article describes Security Context Constraints(SCC) capabilities that need to be added to use Generic Backup and Restore feature capabilities on OCP 4.11 and higher.

Known Issues

With OCP 4.11, default security context constraints (SCC) have changed. Due to this, when using Generic Storage Backup and Restore with OCP 4.11 or higher, the following error message might be seen

Failed to exec command in pod: command terminated with exit code 255

Full error message

[{\"name\":\"FailedSubPhases\",\"value\":[{\"Err\":{\"cause\":{\"cause\":{\"cause\":{\"cause\":{\"cause\":{\"message\":\"{\\\"message\\\":\\\"Failed to backup data\\\",\\\"function\\\":\\\"kasten.io/k10/kio/kanister/function.(*backupDataFunc).Exec\\\",\\\"linenumber\\\":122,\\\"file\\\":\\\"kasten.io/k10/kio/kanister/function/backup_data.go:122\\\",\\\"cause\\\":{\\\"message\\\":\\\"2 errors have occurred\\\",\\\"errors\\\":[{\\\"message\\\":\\\"Failed to create the backup repository\\\",\\\"function\\\":\\\"kasten.io/k10/kio/kopia.CreateKopiaRepository\\\",\\\"linenumber\\\":472,\\\"file\\\":\\\"kasten.io/k10/kio/kopia/repository.go:472\\\",\\\"cause\\\":{\\\"message\\\":\\\"Failed to exec command in pod: command terminated with exit code 255\\\"}},{\\\"message\\\":\\\"Failed to connect to the backup repository\\\",\\\"function\\\":\\\"kasten.io/k10/kio/kopia.ConnectToKopiaRepository\\\",\\\"linenumber\\\":558,\\\"file\\\":\\\"kasten.io/k10/kio/kopia/repository.go:558\\\",\\\"cause\\\":{\\\"message\\\":\\\"Failed to exec command in pod: command terminated with exit code 255\\\"}}]}}\"}

Solution

To continue using the Generic Storage Backup feature on OCP 4.11 and higher and to resolve the error shown above, security context constraints(SCC) capabilities need to be added manually to the container spec as shown below 

securityContext:
  capabilities:
    add: ["CAP_CHOWN", "CAP_DAC_OVERRIDE", "CAP_FOWNER"]

If container spec changes are not permitted, update the allowedCapabilities field in SCC as shown below

allowedCapabilities:
- CHOWN
- DAC_OVERRIDE
- FOWNER

Note: Backups will be unavailable until the changes are completed

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.