In the installer instruction for Windows it is claimed that the dagger binary is placed inside the System32 folder if permissions allow it, which seems to be no longer part of the install.ps1 script (and seems like a bad idea anyways).
Signed-off-by: Jan Gräfen <223234+jangraefen@users.noreply.github.com>
Resolve#1551 and #1020.
We are never returning the result of solved operations so Buildkit could not
cache the layer.
This commit implements a simple system to forward operations' result to the
main build to cache it.
Signed-off-by: Vasek - Tom C <tom.chauveau@epitech.eu>
Updates the `Go on Docker Swarm` use case to europa config. Diagrams are also included for better UX
Signed-off-by: guillaume <guillaume.derouville@gmail.com>
ID 1216 was clashing with docker-cli-load doc.
The filename follows the convention of the other use cases.
Remove from docs sidebar until we do the quick fixes.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
- move Dagger 0.1 references to the top
- move Dagger CUE API under Core Concepts, after What is CUE?
- move Go on Docker Swarm under Use Cases
A few minor title changes:
- Dagger CUE API (0.2+) -> Dagger CUE API
- What is Cue? -> What is CUE?
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
This also accounts for dagger.io/dagger/core split introduced in
https://github.com/dagger/dagger/pull/1866
We should hold this merge until we are ready to cut the release,
otherwise links & some instructions will be broken until we release
v0.2.3.
Even though I would have preferred to have docs/update-version.sh in
Dagger, this is the quickest thing for now.
Related to https://github.com/dagger/dagger/issues/1854
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Thank you Tanguy for the "fresh pair of eyes" perspective.
Thank you Tom for the link suggestions.
Supersedes https://github.com/dagger/dagger/pull/1847
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
This also updates Getting Started - CI/CD in your local dev - Linux & Mac doc.
A few other related doc changes were pulled in by this.
I wanted to try different versions of dagger on Linux, and this was the
easiest way of doing that:
curl -L https://dl.dagger.io/dagger/install.sh -O
# make this change, and then:
DAGGER_VERSION=0.2.0 sh install.sh
# ...
./bin/dagger version
dagger 0.2.0 (e499297e) linux/amd64
DAGGER_VERSION=0.2.1 sh install.sh
# ...
./bin/dagger version
dagger 0.2.1 (69b4845d) linux/amd64
This change enables anyone to do the following instead:
curl -L https://dl.dagger.io/dagger/install.sh \
| DAGGER_VERSION=0.2.0 sh
Until this gets merged, you can test how this change works in practice
via this temporary file:
curl -L https://dl.dagger.io/dagger/install-pr-1819.sh \
| DAGGER_VERSION=0.2.0 sh
One thing which I was not sure about is how the file from this
repository ends up on https://dl.dagger.io/dagger/install.sh. I think
this is a manual process today, but I need to confirm this assumption.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>