Skip to main content

bentoutils

Contents

Console scripts for:

  1. bentopack - package an existing pretrained model and save to the Model Registry
Usage: bentopack [OPTIONS]

Options:
  --module TEXT  fully qualified module name containing service to package
  --clz TEXT     class name of service to package
  --name TEXT    model name
  --path TEXT    directory path of pretrained model
  --help         Show this message and exit.

Example:

bentopack \
    --module TopicBentoService \        # python module containing service class
    --clz TopicBentoService \           # service class
    --name tm_train3_roberta_l_weigh \  # pretrained model name
    --path /srv/models/multilabel-topic # local path to pretrained model (excluding name)
  1. deploy_to_knative - WIP

Uses Kaniko

kaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster.

kaniko solves two problems with using the Docker-in-Docker build method:

  • Docker-in-Docker requires privileged mode to function, which is a significant security concern.
  • Docker-in-Docker generally incurs a performance penalty and can be quite slow.

The setting --isdockerconfig is required when using a private registry such as Harbor.

We can build a Docker image with kaniko and push it to Docker Hub or any other standard Docker registry.

To push to DockerHub or any other username and password Docker registries we need to mount the Docker config.json file that contains the credentials. Caching will not work for DockerHub as it does not support repositories with more than 2 path sections (acme/myimage/cache), but it will work in Artifactory and maybe other registry implementations.

DOCKER_USERNAME=[...]
DOCKER_PASSWORD=[...]
AUTH=$(echo -n "${DOCKER_USERNAME}:${DOCKER_PASSWORD}" | base64)
cat << EOF > config.json
{
    "auths": {
        "https://index.docker.io/v1/": {
            "auth": "${AUTH}"
        }
    }
}
EOF

Alternatively, to create a secret to authenticate to Google Cloud Registry, follow these steps:

  1. Create a service account in the Google Cloud Console project you want to push the final image to with Storage Admin permissions.

  2. Download a JSON key for this service account

  3. Rename the key to kaniko-secret.json

  4. To create the secret, run:

    kubectl create secret generic kaniko-secret --from-file=

Note: If using a GCS bucket in the same GCP project as a build context, this service account should now also have permissions to read from that bucket.

See https://github.com/GoogleContainerTools/kaniko

Metadata

Release files for bentoutils 1.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for bentoutils 1.1.2
File Size Uploaded Provenance Actions
bentoutils-1.1.2.tar.gz 13.4 kB Without provenance Details for bentoutils-1.1.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for bentoutils 1.1.2
File Interpreter ABI Platform Actions
bentoutils-1.1.2-py3-none-any.whl Python 3 none any Details for bentoutils-1.1.2-py3-none-any.whl

Total release size: 28.5 kB

Release files / bentoutils-1.1.2.tar.gz

Download URL bentoutils-1.1.2.tar.gz
Size 13.4 kB
Tags Source
SHA-256 checksum
How to use checksums
abd00ce319241c10f1a9322b8562749a602bc47750b801b82ee5401a916c57fc
BLAKE2b-256 checksum
How to use checksums
c3188230cb18ad7c2d3a929999e92ea987f91272e5387eac6bf41d551ed49c9c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.54.0 CPython/3.8.5

Release files / bentoutils-1.1.2-py3-none-any.whl

Download URL bentoutils-1.1.2-py3-none-any.whl
Size 15.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bf8885c01d02a11bf22ba79d96c7754edb991b7632dce33d985959fe4287f072
BLAKE2b-256 checksum
How to use checksums
4e6d7e37997f1920fd231d8a8670973cec7dd7118bf8089828a8037909a86efb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.54.0 CPython/3.8.5

Security for bentoutils 1.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.1.2 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page