Releases: datalad/datalad-container
Releases · datalad/datalad-container
0.5.0 (Jul 12, 2019) -- damn-you-malicious-users
New features - The default result renderer for `containers-list` is now a custom renderer that includes the container name in the output. Fixes - Temporarily skip two tests relying on SingularityHub -- it is down.
0.4.0 (May 29, 2019) -- run-baby-run
The minimum required DataLad version is now 0.11.5. New features - The call format gained the "{img_dspath}" placeholder, which expands to the relative path of the dataset that contains the image. This is useful for pointing to a wrapper script that is bundled in the same subdataset as a container. - `containers-run` now passes the container image to `run` via its `extra_inputs` argument so that a run command's "{inputs}" field is restricted to inputs that the caller explicitly specified. - During execution, `containers-run` now sets the environment variable `DATALAD_CONTAINER_NAME` to the name of the container. Fixes - `containers-run` mishandled paths when called from a subdirectory. - `containers-run` didn't provide an informative error message when `cmdexec` contained an unknown placeholder. - `containers-add` ignores the `--update` flag when the container doesn't yet exist, but it confusingly still used the word "update" in the commit message.
Upgrayeddd
0.3.1 (Mar 05, 2019) -- Upgrayeddd (for a tripple dose of pimpin')
Fixes
containers-list
recursion actually does recursion.
Upgrayedd
0.3.0 (Mar 05, 2019) -- Upgrayedd
API changes
-
containers-list
no longer lists containers from subdatasets by
default. Specify--recursive
to do so. -
containers-run
no longer considers subdataset containers in its
automatic selection of a container name when no name is specified.
If the current dataset has one container, that container is
selected. Subdataset containers must always be explicitly
specified.
New features
-
containers-add
learned to update a previous container when passed
--update
. -
containers-add
now supports Singularity's "docker://" scheme in
the URL. -
To avoid unnecessary recursion into subdatasets,
containers-run
now decides to look for containers in subdatasets based on whether
the name has a slash (which is true of all subdataset containers).
0.2.2 (Dec 19, 2018) -- The more the merrier
- list/use containers recursively from installed subdatasets - Allow to specify container by path rather than just by name - Adding a container from local filesystem will copy it now
Explicit lyrics
0.2.1 (Jul 14, 2018) -- Explicit lyrics
- Add support
datalad run --explicit
.
Docker
0.2 (Jun 08, 2018) -- Docker
- Initial support for adding and running Docker containers.
- Add support
datalad run --sidecar
. - Simplify storage of
call_fmt
arguments in the Git config, by benefitting
fromdatalad run
being able to work with single-string compound commmands.
The docs
The fixes
0.1.1 (May 22, 2018) -- The fixes
New features
- Add container images straight from singularity-hub, no need to manually
specify--call-fmt
arguments.
API changes
- Use "name" instead of "label" for referring to a container (e.g.
containers-run -n ...
instead ofcontainers-run -l
.
Fixes
- Pass relative container path to
datalad run
. containers-run
no longer hidesdatalad run
failures.
The release
0.1 (May 19, 2018) -- The Release
- Initial release with basic functionality to add, remove, and list
containers in a dataset, plus arun
command wrapper that injects
the container image as an input dependency of a command call.