Age | Commit message (Collapse) | Author |
|
For images running on Kubernetes, there is no guarantee on how duplicate
environment variables in the image config will be handled. This seems
to be different from Docker, where the last environment variable value
is consistently selected.
The current code for `streamLayeredImage` was exploiting that assumption
to easily propagate environment variables from the base image, leaving
duplicates unchecked. It should rather resolve these duplicates to
ensure consistent behavior on Docker and Kubernetes.
|
|
dockerTools.buildLayeredImage: support fromImage
|
|
It is now possible to pass a `fromImage` to `buildLayeredImage` and
`streamLayeredImage`, similar to what `buildImage` currently supports.
This will prepend the layers of the given base image to the resulting
image, while ensuring that at most `maxLayers` are used. It will also
ensure that environment variables from the base image are propagated
to the final image.
|
|
|
|
|
|
|
|
|
|
lbpdt/feature/docker-tools-layered-image-name-slashes
dockerTools.buildLayeredImage: image names with registry/ prefix
|
|
dockerTools.buildLayeredImage: configurable store root
|
|
|
|
Add fetcher: fetchFromSourcehut
|
|
|
|
When using `buildLayeredImage`, it is not possible to specify an image
name of the form `<registry>/my/image`, although it is a valid name.
This is due to derivations under `buildLayeredImage` using that image
name as their derivation name, but slashes are not permitted in that
context.
A while ago, #13099 fixed that exact same problem in `buildImage` by
using `baseNameOf name` in derivation names instead of `name`. This
change does the same thing for `buildLayeredImage`.
|
|
`stream_layered_image.py` currently assumes that the store root will be
at `/nix/store`, although the user might have configured this
differently. This makes `buildLayeredImage` unusable with stores having
a different root, as they will fail an assertion in the python script.
This change updates that assertion to use `builtins.storeDir` as the
source of truth about where the store lives, instead of assuming
`/nix/store`.
|
|
- This is the first packages which uses Dune in order to build and install
so I had to refactor build-support/coq/default.nix in order to support it.
- I added a new feature: one can now release.v.sha256 empty to try to download
with a fake sha256, hence failures are reported and one can copy paste the
sha256 given by the error message.
- I updated the documentation of languages-frameworks/coq.section.md accordingly.
|
|
|
|
Closes #115455
|
|
Fixes build failures with clang:
clang-7: error: unknown argument: '-fPIC -target'
clang-7: error: no such file or directory: '@<(printf %qn -O2'
clang-7: error: no such file or directory: 'x86_64-apple-darwin'
Introduced by 60c5cf9cea56ffd607b48fe07ff1174ea6a13afc in #112449
|
|
|
|
fetchFromBitbucket: remove hack for Mercurial
|
|
|
|
|
|
|
|
|
|
Add response file support when compiling with clang
|
|
|
|
|
|
rustPlatform.buildRustPackage: support debug builds
|
|
|
|
android prebuilt: Fix eval
|
|
|
|
Revert "php: Add php package versions to extensions/packages pnames"
|
|
dockerTools: fix build on Darwin
|
|
Fixes #110665
Introduced by #109420
|
|
Signed-off-by: Ana Hobden <operator@hoverbear.org>
|
|
treewide: remove stdenv where not needed
|
|
This reverts commit a081dcf86de4f100efe604a52b32df4b14892f44.
|
|
|
|
nixos/kresd, nixos/dokuwiki, tests/fpm, build-bazel-package, libcutl: fix string escaping
|
|
treewide: Fix various tools wrappers "with packages"
|
|
Since #112276, we should always put `makeWrapper` in
`nativeBuildInputs`. But `buildEnv` was saying put it in `buildInputs`.
That's wrong!
Fix the instructions, and make the right thing possible.
|
|
darwin: introduce darwinArch, apply in {cc,bintools}-wrappers
|
|
|
|
This makes it possible to pass flags to `cargo test`, which is needed if
a crate is compiled with custom feature flags.
|
|
|
|
|
|
|
|
The `checkType` argument of buildRustPackage was not used anymore
since the refactoring of `buildRustPackage` into hooks. This was
an oversight that is fixed by this change.
The check type can also be passed directly to cargoCheckHook using the
`cargoCheckType` environment variable.
|
|
|
|
|