werf icon indicating copy to clipboard operation
werf copied to clipboard

A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.

Results 292 werf issues
Sort by recently updated
recently updated
newest added

The following features might significantly affect performance: - When calculating a target from a Dockerfile, werf handles all other dockerfile stages instead of handling only the dependent ones. - When...

type: feature
scope: build
scope: dockerfile

The patch cannot be applied because of different EOL ( `patch does not apply`). Adding a ".gitattributes" file fixes a build error: ``` * text=auto *.* text eol=lf ```

type: bug
scope: build
priority: low

1. Suppose we are using `gitlab` remote instead of default hardcoded into git `origin`. 2. Suppose we have added a submodule with relative url. 3. Werf build command will try...

type: feature
priority: low
scope: common

Suppose we have following submodule dir in the root of the project git: ``` some_submodule/werf.yaml ``` When `some_submodule` is initialized, `werf --dir some_submodule` command dot-git detector will use `some_submodule/.git` git...

type: feature
priority: low
scope: common

Validate all regular expressions from the `werf-giterminism.yaml` configuration file early in the configuration parsing phase. This will simplify giterminism-manager interface to match regular expressions (`(bool, error)` -> `bool`).

type: feature
priority: low
scope: giterminism

Extend Dockerfile with custom instructions to introduce stapel-builder features into dockerfile-builder, such as: - integration with Git and incremental rebuilds support using application of git-patches to the tracked files; -...

type: feature
scope: build
priority: low
scope: dockerfile

Check if werf supports storing multiple projects in the single container registry repo. Possible problem is collision of meta-images like: client-id, metadata-by-commit, managed-images. Collision of stages-images is not an issue,...

type: feature
priority: low
scope: common

There should be convinient way to store cache of external dependencies (Gemfile, or package.json, or go.mod, etc.) in the docker images instead of mounts. Mounts leads to harmful and unpredictable...

type: feature
scope: build
priority: low
scope: stapel

Werf should print full output of docker-run for rsync import server when this error occurs

type: bug
scope: build
priority: low
scope: stapel
scope: docker

CLI params like: - `--config-templates-dir`; - `--set`; - `--set-string`; - `--set-file`; - `--values`; - `--secret-values`; - `--add-label`; - `--add-annotation`; - `--virtual-merge`; - `--virtual-merge-from-commit`; - `--virtual-merge-into-commit`; Should be restricted to use...

type: feature
priority: normal
scope: giterminism