wasmer run
CLI
Run a WebAssembly file or Wasmer container.
Usage
Run a Wasmer package
All packages published on Wasmer Registry can be run with the wasmer run
command.
wasmer run python/python
Some commands, such as cowsay
have multiple commands that we can run (eg. cowsay
or cowthink
)
wasmer run syrusakbary/cowsay --command-name=cowthink Hello world
If in your current dir you have a wasmer.toml
file, you can simply run the local package with:
wasmer run .
Wasmer run also allows running from URLs (in case a package is hosted on a different registry).
wasmer run https://wasmer.io/python/python
Run a Wasm file
wasmer run my_program.wasm
Run a Wasm file with a custom compiler
wasmer run my_program.wasm --singlepass
You can also use
--cranelift
or--llvm
instead of--singlepass
.
Run a WASI or WASIX Module
You can pass the arguments that will be given to the WASI program:
wasmer run my_wasi_program.wasm -- arg1 arg2 arg3
You can also pass environment variables:
wasmer run my_wasi_program.wasm --env MYVAR=MYVALUE -- arg1 arg2 arg3
Help
This is the help output from the Wasmer CLI for wasmer run --help
(last updated 2025-01):
Run a WebAssembly file or Wasmer container
Usage: wasmer run [OPTIONS] <INPUT> [ARGS]...
Arguments:
<INPUT>
The file, URL, or package to run
[ARGS]...
Command-line arguments passed to the package
Options:
--wasmer-dir <WASMER_DIR>
Set Wasmer's home directory
[env: WASMER_DIR=/home/imago/.local/share/wasmenv/current]
[default: /home/imago/.local/share/wasmenv/current]
--cache-dir <CACHE_DIR>
The directory cached artefacts are saved to
[env: WASMER_CACHE_DIR=/home/imago/.wasmer/cache]
[default: /home/imago/.local/share/wasmenv/current/cache]
-v, --verbose...
Generate verbose output (repeat for more verbosity)
-q, --quiet
Do not print progress messages
--registry <REGISTRY>
The registry to fetch packages from (inferred from the environment by default)
[env: WASMER_REGISTRY=]
--log-format <LOG_FORMAT>
The format to use when generating logs
[env: LOG_FORMAT=]
[default: text]
Possible values:
- text: Human-readable logs
- json: Machine-readable logs
--token <TOKEN>
The API token to use when communicating with the registry (inferred from the environment by default)
[env: WASMER_TOKEN=wap_1f8cd65ed491ab8087f54f8078f389a7bb6e7236c808aac61a487b4236f90d2f]
--color <COLOR>
When to display colored output
[default: auto]
[possible values: auto, always, never]
--singlepass
Use Singlepass compiler
--cranelift
Use Cranelift compiler
--llvm
Use LLVM compiler
--enable-verifier
Enable compiler internal verification.
Available for cranelift, LLVM and singlepass.
--llvm-debug-dir <LLVM_DEBUG_DIR>
LLVM debug directory, where IR and object files will be written to.
Only available for the LLVM compiler.
--enable-simd
Enable support for the SIMD proposal
--disable-threads
Disable support for the threads proposal
--enable-threads
Deprecated, threads are enabled by default
--enable-reference-types
Enable support for the reference types proposal
--enable-multi-value
Enable support for the multi value proposal
--enable-bulk-memory
Enable support for the bulk memory proposal
--enable-all
Enable support for all pre-standard proposals
--dir <DIR>
WASI pre-opened directory
--mapdir <GUEST_DIR:HOST_DIR>
Map a host directory to a different location for the Wasm module
--env <KEY=VALUE>
Pass custom environment variables
--forward-host-env
Forward all host env variables to guest
[env: FORWARD_HOST_ENV=]
--use <USE>
List of other containers this module depends on
--include-webc <WEBC>
List of webc packages that are explicitly included for execution Note: these packages will be used instead of those in the registry
--map-command <MAPCMD>
List of injected atoms
--net[=<NETWORKING>]
Enable networking with the host network.
Allows WASI modules to open TCP and UDP connections, create sockets, ...
Optionally, a set of network filters could be defined which allows fine-grained control over the network sandbox.
Rule Syntax:
<rule-type>:<allow|deny>=<rule-expression>
Examples:
- Allow a specific domain and port: dns:allow=example.com:80
- Deny a domain and all its subdomains on all ports: dns:deny=*danger.xyz:*
- Allow opening ipv4 sockets only on a specific IP and port: ipv4:allow=127.0.0.1:80/in.
--no-tty
Disables the TTY bridge
--enable-async-threads
Enables asynchronous threading
--enable-cpu-backoff <ENABLE_CPU_BACKOFF>
Enables an exponential backoff (measured in milli-seconds) of the process CPU usage when there are no active run tokens (when set holds the maximum amount of time that it will pause the CPU) (default = off)
--journal <JOURNALS>
Specifies one or more journal files that Wasmer will use to restore and save the state of the WASM process as it executes.
The state of the WASM process and its sandbox will be reapplied using the journals in the order that you specify here.
The last journal file specified will be created if it does not exist and opened for read and write. New journal events will be written to this file
--enable-compaction
Flag that indicates if the journal will be automatically compacted as it fills up and when the process exits
--without-compact-on-drop
Tells the compactor not to compact when the journal log file is closed
--with-compact-on-growth <WITH_COMPACT_ON_GROWTH>
Tells the compactor to compact when it grows by a certain factor of its original size. (i.e. '0.2' would be it compacts after the journal has grown by 20 percent)
Default is to compact on growth that exceeds 15%
[default: 0.15]
--snapshot-on <SNAPSHOT_ON>
Indicates what events will cause a snapshot to be taken and written to the journal file.
If not specified, the default is to snapshot when the process idles, when the process exits or periodically if an interval argument is also supplied.
Additionally if the snapshot-on is not specified it will also take a snapshot on the first stdin, environ or socket listen - this can be used to accelerate the boot up time of WASM processes.
--snapshot-period <SNAPSHOT_INTERVAL>
Adds a periodic interval (measured in milli-seconds) that the runtime will automatically take snapshots of the running process and write them to the journal. When specifying this parameter it implies that `--snapshot-on interval` has also been specified
--http-client
Allow instances to send http requests.
Access to domains is granted by default.
--deny-multiple-wasi-versions
Require WASI modules to only import 1 version of WASI
-a, --addr <ADDR>
The address to serve on
[env: ADDR=]
[default: 127.0.0.1:8000]
--stack-size <STACK_SIZE>
Set the default stack size (default is 1048576)
-e, --entrypoint <ENTRYPOINT>
The entrypoint module for webc packages
-i, --invoke <INVOKE>
The function to invoke
--COREDUMP_PATH <COREDUMP_PATH>
Generate a coredump at this path if a WebAssembly trap occurs
--hash-algorithm <HASH_ALGORITHM>
Hashing algorithm to be used for module hash
Possible values:
- sha256: Sha256
- xx-hash: XXHash
-h, --help
Print help (see a summary with '-h')