Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Hi guys,
Following the documentation of using docker containers for job deployments I had to run ./bin/dssadmin/build-code-env-images --all
However, this command isn't recognised by dssadmin itself although it is listed as a command in the CLI.
[dataiku@dataiku-production dataiku-data]$ ./bin/dssadmin
Usage: dssadmin ACTION [ARGUMENT ...]
Actions:
install-hadoop-integration [-keytab KEYTAB_FILE_LOCATION -principal KERBEROS_PRINCIPAL]
install-spark-integration [-sparkHome SPARK_HOME] [-pysparkPython PYSPARK_PYTHON]
install-h2o-integration [-sparklingWaterDir SPARKLING_WATER_DIR]
install-R-integration [-noDeps] [-repo REPO_URL | -pkgDir DIR]
build-container-exec-base-image [-tag TAG]
build-container-exec-code-env-images [--all] [--dry-run]
build-container-exec-base-image [-t TAG]
build-code-env-images [--all] [--dry-run]
build-mad-kubernetes-base-image [-tag TAG]
install-monitoring-integration -graphiteServer HOSTNAME:PORT [-prefix PREFIX] [-pkg LOCAL_COLLECTD_PACKAGE]
regenerate-config
install-impersonation [-pythonBin PYTHONBIN] [-noInstallSudoSnippet] DSS_USER
run-diagnosis [OPTIONS] OUTPUT_FILE
install-dashboard-export [-noDeps]
compact-internal-databases
[dataiku@dataiku-production dataiku-data]$ ./bin/dssadmin build-code-env-images
[-] Unsupported action build-code-env-images
Afterwards, I ran build-container-exec-code-env-images but this didn't build any sort of usable image in the container exec settings.
Am I overlooking something?
EDIT:
Hi,
There is some duplication in this help message, which will be amended in the next DSS release.
The correct command to build the base image is given by the documentation on setting up Container execution:
./bin/dssadmin build-container-exec-base-image
If you are trying to build container execution images for code envs, remember to first mark for which container execution configuration you want to make code env available, in the code env's settings. Then updating the code env should build the corresponding docker image(s) (provided you already have a base image).
The build-container-exec-code-env-images command is rather when you want to rebuild those images for all code envs , e.g. after rebuilding the base image (required when you upgrade DSS to a newer version).