[{"_1":2,"_144":-5,"_145":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_138":139},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_55":56,"_57":-7,"_58":-7,"_59":-7,"_60":-7,"_61":-5,"_62":-5,"_63":11,"_64":11,"_48":65,"_128":17,"_96":97,"_129":95,"_130":47,"_31":32,"_131":11,"_132":17,"_133":134,"_135":-5,"_136":11,"_137":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},"content_type","unrecognized","creator",35095401,"digest","sha256:f0ab4106cbd53b1c6e9b130d2c60503bbe6c43b3f4191e6d59a0648db338dc0f","full_size",529403,"id",1208451980,"images",[],"last_updated","2026-06-22T22:10:54.318959Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.vmware.tac.metadata.config.v1+json","name","sha256-7e26b170735179298ae418a2ef9b3fa739953563d8f424e0dd542fb26808a79d.metadata","repository",19064307,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_66":67,"_78":79,"_82":83,"_84":85,"_86":11,"_39":87,"_88":89,"_90":91,"_46":95,"_96":97,"_98":99,"_100":81,"_101":102,"_103":104,"_105":106,"_107":-5,"_108":102,"_109":110,"_111":11,"_112":97,"_113":114,"_119":11,"_120":121,"_125":97,"_126":127},"categories",[68,72,75],{"_46":69,"_70":71},"Languages & frameworks","slug","languages-and-frameworks",{"_46":73,"_70":74},"Machine learning & AI","machine-learning-and-ai",{"_46":76,"_70":77},"Data science","data-science","content_types",[80,81,28],"helm","image","date_registered","2023-01-24T10:50:06.048442Z","description","Bitnami Helm chart for PyTorch","is_private","2026-09-21T08:35:52.268887Z","last_modified","2026-03-16T14:25:08.623535Z","media_types",[92,93,94,45],"application/vnd.cncf.helm.config.v1+json","application/vnd.oci.image.config.v1+json","application/vnd.oci.image.index.v1+json","pytorch","namespace","bitnamicharts","pull_count",697279,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for PyTorch\n\nPyTorch is a deep learning platform that accelerates the transition from research prototyping to production deployment. Bitnami image includes Torchvision for specific computer vision support.\n\n[Overview of PyTorch](https://pytorch.org/)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/pytorch\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [PyTorch](https://github.com/bitnami/containers/tree/main/bitnami/pytorch) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\nPython is built for full integration into Python that enables you to use it with its libraries and main packages.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n- PV provisioner support in the underlying infrastructure\n- ReadWriteMany volumes for deployment scaling\n\n## Installing the chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/pytorch\n```\n\n> **Note** You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThese commands deploy PyTorch on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured.\n\n> **Note** List all releases using `helm list`.\n\n## Configuration and installation details\n\nThis section describes resource settings, rolling tags, loading files, pod affinity, backup, and other options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Loading your files\n\nThe PyTorch chart supports three different ways to load your files. In order of priority, they are:\n\n 1. Existing config map\n 2. Files under the `files` directory\n 3. Cloning a git repository\n\nThis means that if you specify a config map with your files, it won't look for the `files/` directory nor the git repository.\n\nIn order to use use an existing config map, set the `configMap=my-config-map` parameter.\n\nTo load your files from the `files/` directory you don't have to set any option. Just copy your files inside and don't specify a `ConfigMap`.\n\nFinally, if you want to clone a git repository you can use those parameters:\n\n```console\ncloneFilesFromGit.enabled=true\ncloneFilesFromGit.repository=https://github.com/my-user/my-repo\ncloneFilesFromGit.revision=master\n```\n\n### Set pod affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Persistence\n\nThe [Bitnami PyTorch](https://github.com/bitnami/containers/tree/main/bitnami/pytorch) image can persist data. If enabled, the persisted path is `/bitnami/pytorch` by default.\n\nThe chart mounts a [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) at this location. The volume is created using dynamic volume provisioning.\n\n### Adjust permissions of persistent volume mountpoint\n\nAs the image run as non-root by default, it is necessary to adjust the ownership of the persistent volume so that the container can write data into it.\n\nBy default, the chart is configured to use Kubernetes Security Context to automatically change the ownership of the volume. However, this feature does not work in all Kubernetes distributions.\nAs an alternative, this chart supports using an `initContainer` to change the ownership of the volume before mounting it in the final destination.\n\nYou can enable this `initContainer` by setting `volumePermissions.enabled` to `true`.\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------------ | -------------------------------------------------------------------------------------------- | -------------- |\n| `kubeVersion` | Override Kubernetes version | `\"\"` |\n| `nameOverride` | String to partially override common.names.fullname template (will maintain the release name) | `\"\"` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `fullnameOverride` | String to fully override common.names.fullname template | `\"\"` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the deployment | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployment | `[\"infinity\"]` |\n\n### PyTorch parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- |\n| `image.registry` | PyTorch image registry | `REGISTRY_NAME` |\n| `image.repository` | PyTorch image repository | `REPOSITORY_NAME/pytorch` |\n| `image.digest` | PyTorch image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | PyTorch image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `worldSize` | Number of nodes that will run the code | `1` |\n| `containerPorts.pytorch` | PyTorch master port. `MASTER_PORT` will be set to this value | `49875` |\n| `livenessProbe.enabled` | Enable livenessProbe | `true` |\n| `livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `5` |\n| `livenessProbe.periodSeconds` | Period seconds for livenessProbe | `60` |\n| `livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `45` |\n| `livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` |\n| `livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |\n| `readinessProbe.enabled` | Enable readinessProbe | `true` |\n| `readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` |\n| `readinessProbe.periodSeconds` | Period seconds for readinessProbe | `5` |\n| `readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `40` |\n| `readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `5` |\n| `readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` |\n| `startupProbe.enabled` | Enable startupProbe | `true` |\n| `startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `5` |\n| `startupProbe.periodSeconds` | Period seconds for startupProbe | `5` |\n| `startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `20` |\n| `startupProbe.failureThreshold` | Failure threshold for startupProbe | `5` |\n| `startupProbe.successThreshold` | Success threshold for startupProbe | `1` |\n| `customLivenessProbe` | Custom livenessProbe that overrides the default one | `{}` |\n| `customReadinessProbe` | Custom readinessProbe that overrides the default one | `{}` |\n| `customStartupProbe` | Custom startupProbe that overrides the default one | `{}` |\n| `podSecurityContext.enabled` | Enabled Pytorch pods' Security Context | `true` |\n| `podSecurityContext.fsGroupChangePolicy` | Set filesystem group change policy | `Always` |\n| `podSecurityContext.sysctls` | Set kernel settings using the sysctl interface | `[]` |\n| `podSecurityContext.supplementalGroups` | Set filesystem extra groups | `[]` |\n| `podSecurityContext.fsGroup` | Set Pytorch pods' Security Context fsGroup | `1001` |\n| `containerSecurityContext.enabled` | Enabled containers' Security Context | `true` |\n| `containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` |\n| `containerSecurityContext.runAsUser` | Set containers' Security Context runAsUser | `1001` |\n| `containerSecurityContext.runAsGroup` | Set containers' Security Context runAsGroup | `1001` |\n| `containerSecurityContext.runAsNonRoot` | Set container's Security Context runAsNonRoot \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-pytorch-index.html_","has_starred","hub_user","immutable_tags_settings",{"_115":11,"_116":117},"enabled","rules",[118],".*","is_automated","permissions",{"_122":17,"_123":11,"_124":11},"read","write","admin","user","storage_size",36310712,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":140,"_31":32,"_142":-7,"_143":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":141,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/pytorch:sha256-7e26b170735179298ae418a2ef9b3fa739953563d8f424e0dd542fb26808a79d.metadata