Basic usage

First of all, install Docker on the host machine.
The easiest way to use the dockerized Meterian Client is via the script meterian-docker. It accepts all the standard parameters exactly in the same way, but it cannot be used in interactive mode, therefore you will need to provide it with a valid token using the environment variable METERIAN_API_TOKEN. We suggest you populate such variable in your startup script.
Assuming you put the script in your path, just move in the folder of your project and type:
1
    meterian-docker [Meterian CLI Options]
Copied!
Alternatively you can set the environment variable METERIAN_WORKDIR with the path to your project folder and run the convenience script:
1
    export METERIAN_WORKDIR=/project-folder
2
    meterian-docker
Copied!
Everything will work exactly like a normal invocation of the client. Please note that, by default, the script binds into the container the standard library cache folders used by the package managers (see the table below for the ones that we bind), so that the execution is as fast as it was running on your machine. If you really want you can avoid this by adding --unbound to your command line arguments.
Package Manager
Folder
*
~/.cache
~/.local
maven
~/.m2
dotnet
~/.dotnet
~/.nuget
ruby
$(gem environment gemdir)/cache
node
/usr/lib/node_modules
gradle
~/.gradle
sbt
~/.sbt
~/.ivy2
An additional option to note when using the meterian-docker script is --image: . 
By default the scripts uses the latest tag, but providing this option instructs it to use a given tag of the meterian/cli image.
1
    meterian-docker --image:latest-python
Copied!
The above example will cause the script to use the meterian/cli:latest-python image: we also provide platform-specific images should you not wish to use the full version to save bandwidth or space, as the "generic" image ("latest") contains all the tooling supported.

The Dockerized Client

Advanced usage

Last modified 3mo ago

Copy link