OS Manuals

/usr/bin/model-archiver

Executable binaries for model-archiver installed for python3.11

From py3.11-model-archiver-bin 1.1.11-r2 (enterprise-packages), captured 2026-11-08 by running model-archiver --help (exit 0). permalink

usage: model-archiver [-h] --model-name MODEL_NAME --model-path MODEL_PATH --handler HANDLER
                      [--runtime {python,python2,python3}] [--export-path EXPORT_PATH]
                      [--archive-format {tgz,no-archive,default}] [-f] [-c]

Model Archiver Tool

options:
  -h, --help            show this help message and exit
  --model-name MODEL_NAME
                        Exported model name. Exported file will be named as
                        model-name.mar and saved in current working directory if no --export-path is
                        specified, else it will be saved under the export path
  --model-path MODEL_PATH
                        Path to the folder containing model related files.
  --handler HANDLER     Handler path to handle custom MMS inference logic.
  --runtime {python,python2,python3}
                        The runtime specifies which language to run your inference code on.
                        The default runtime is "python".
  --export-path EXPORT_PATH
                        Path where the exported .mar file will be saved. This is an optional
                        parameter. If --export-path is not specified, the file will be saved in the
                        current working directory.
  --archive-format {tgz,no-archive,default}
                        The format in which the model artifacts are archived.
                        "tgz": This creates the model-archive in <model-name>.tar.gz format.
                        If platform hosting MMS requires model-artifacts to be in ".tar.gz"
                        use this option.
                        "no-archive": This option creates an non-archived version of model artifacts
                        at "export-path/{model-name}" location. As a result of this choice,
                        MANIFEST file will be created at "export-path/{model-name}" location
                        without archiving these model files
                        "default": This creates the model-archive in <model-name>.mar format.
                        This is the default archiving format. Models archived in this format
                        will be readily hostable on native MMS.
  -f, --force           When the -f or --force flag is specified, an existing .mar file with same
                        name as that provided in --model-name in the path specified by --export-path
                        will overwritten
  -c, --convert         When this option is used, model-archiver looks for special files and tries
                        preprocesses them. For example, if this option is chosen when running
                        model-archiver tool on a model with ".onnx" extension, the tool will try and
                        convert ".onnx" model into an Multi model.
Options (9)
OptionDescriptionSource
-h, --helpshow this help message and exithelp
--model-name MODEL_NAMEExported model name.help
--model-path MODEL_PATHPath to the folder containing model related files.help
--handler HANDLERHandler path to handle custom MMS inference logic.help
--runtime pythonThe runtime specifies which language to run your inference code on.help
--export-path EXPORT_PATHPath where the exported .mar file will be saved.help
--archive-format tgzThe format in which the model artifacts are archived.help
-f, --forceWhen the -f or --force flag is specified, an existing .mar file with same name as that provided in --model-name in the path specified by --export-path will overwrittenhelp
-c, --convertWhen this option is used, model-archiver looks for special files and tries preprocesses them.help

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.