#Hey! Quick Question

1 messages ยท Page 1 of 1 (latest)

celest compass
#

Yes ๐ŸŽ‰
You should be able to do this with two commands:

$ curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=v0.11.9 sh
$ docker pull registry.dagger.io/engine:v0.11.9
#

that should grab as much as is currently possible, but you can't predownload images to run in pipelines today sadly

grave flame
#

@celest compass I don't want people to install Dagger prior to coming to the workshop. So i'll leave that out

grave flame
#

@celest compass can we do docker load style onto dagger engine? ๐Ÿ˜›

#

so I can bring images on a USB stick or something.

#

dagger load ?

celest compass
#

i don't think so, no ๐Ÿ˜ฆ i quite like the idea, but it's fairly infeasible to do at the moment ๐Ÿ˜ข

grave flame
#

fair enuf.

chilly ridge
#

You "could" do a thing where folks run a prep script on fast network before they come to get their Dagger Engine prepped with images in cache. Seems to work when I throttle my wi-fi afterwards since Dagger will just check the digest of the image. You could use long image digest shas to make sure.

#!/bin/bash

cd /tmp && curl -L https://dl.dagger.io/dagger/install.sh | DAGGER_VERSION=v0.11.9 sh

function core() {
 (
  set -ex
  cd $(mktemp -d)
  echo "{\"name\":\"$1\", \"sdk\":\"go\"}" > dagger.json
  echo 'package main' > main.go
  shift
  /tmp/bin/dagger call "$@"
 )
}

core container from --address node:20 sync
core container from --address node:18 sync
core container from --address node:16 sync
core container from --address docker.io/library/node:14@sha256:a158d3b9b4e3fa813fa6c8c590b8f0a860e015ad4e59bbce5744d2f6fd8461aa sync
# other images you want