Releases: into-docker/into-docker
Version 1.1.7
This is version 1.1.7 of into-docker, which is now build against GraalVM CE (Java 21).
Version 1.1.6
This is version 1.1.6 of into-docker, with some small adjustments.
Features
- Explicitly use the docker engine's platform when no platform is set.
- Improve error message when connection to docker engine fails.
- Upgrade dependencies.
Version 1.1.5
This is version 1.1.5 of into-docker, with some small adjustments.
Features
- (BREAKING) Remove
--force-platform
CLI option (useDOCKER_DEFAULT_PLATFORM
environment variable instead). - Do not print progress if
CI
environment variable is set totrue
.
Version 1.1.4
This is version 1.1.4 of into-docker, introducing support for platforms.
Features
--platform
CLI option to choose runner container platform.--force-platform
CLI option to force usage of the platform also for the builder container.- Heed
DOCKER_DEFAULT_PLATFORM
environment variable.
Version 1.1.3
This is version 1.1.3 of into-docker, which updates underlying libraries.
Features
- Progress bar when pulling images.
Version 1.1.2
This is version 1.1.2 of into-docker, which updates underlying libraries to now support Apple Silicon architectures.
Features
- Support Apple Silicon.
- Introduce local caching using cache volume (
-i
/--incremental
).
Version 1.1.1
This is version 1.1.1 of into-docker, which incorporates a single bugfix.
Bugfixes
- Correctly handle entries with trailing slash in a builder's ignore file, e.g.
node_modules/
(see #30).
Version 1.1.0
This is version 1.1.0 of into-docker, which incorporates a few improvements and bugfixes:
Housekeeping
- Uses GraalVM 20.3.0.
- Upgrades dependencies.
- More comprehensive e2e test.
- Increased test coverage, more granular tests for single build steps.
Bugfixes
- Addresses permission issue when using non-root build user.
- Correctly handles builder/runner images that have defined an
ENTRYPOINT
(see #20 and #21 - thanks @r0man!). - Fixes a regression when writing artifacts and building an image at the same time (see #26).
Improvements
- Uses a shared volume to transfer artifacts between containers, rather than an explicit copy out of one and back into the other.
- Flag
--no-volumes
can be used to restore the original behaviour.
- Flag
- Uses
DOCKER_API_VERSION
environment variable to target the correct API version (instead of always expecting the latest one). - Only pulls the desired tag from a registry instead of all of them.
- Introduces the
.buildenv
mechanism to pass environment variables to the build script. - Fails early if no source files are found (or all of them are ignored).
Version 1.1.0-RC4
This is version 1.1.0-RC4 of into-docker, which incorporates a few improvements and bugfixes:
Housekeeping
- Uses GraalVM 20.3.0.
- Upgrades dependencies.
- More comprehensive e2e test.
Bugfixes
- Addresses permission issue when using non-root build user.
- Correctly handles builder/runner images that have defined an
ENTRYPOINT
(see #20 and #21 - thanks @r0man!). - (NEW) Fixes a regression when writing artifacts and building an image at the same time (see #26).
Improvements
- Uses a shared volume to transfer artifacts between containers, rather than an explicit copy out of one and back into the other.
- Flag
--no-volumes
can be used to restore the original behaviour.
- Flag
- Uses
DOCKER_API_VERSION
environment variable to target the correct API version (instead of always expecting the latest one). - Only pulls the desired tag from a registry instead of all of them.
- Introduces the
.buildenv
mechanism to pass environment variables to the build script.
Version 1.1.0-RC3
This is version 1.1.0-RC3 of into-docker, which incorporates a few improvements and bugfixes:
Housekeeping
- Uses GraalVM 20.3.0.
- Upgrades dependencies.
- More comprehensive e2e test.
Bugfixes
- Addresses permission issue when using non-root build user.
- Correctly handles builder/runner images that have defined an
ENTRYPOINT
(see #20 and #21 - thanks @r0man!).
Improvements
- Uses a shared volume to transfer artifacts between containers, rather than an explicit copy out of one and back into the other.
- Flag
--no-volumes
can be used to restore the original behaviour.
- Flag
- Uses
DOCKER_API_VERSION
environment variable to target the correct API version (instead of always expecting the latest one). - Only pulls the desired tag from a registry instead of all of them.
- (NEW) Introduces the
.buildenv
mechanism to pass environment variables to the build script.