#In the current version of Dagger the SDK

1 messages ยท Page 1 of 1 (latest)

vernal badger
#

I'm likely going to be running the PHP SDK from a container from day 0, as I don't want people to have PHP running on their machines to use this ..

docker images already have PHP pre-installed/compiled ๐Ÿ™‚ so it saves a huge effort

hot falcon
#

That will not be possible

#

(it won't fit in the current Dagger SDK model)

vernal badger
#

understood.

#

I'm missing the whole Dagger systems design architecture image, in my head, to see how things "talk to each other" ..

hot falcon
#

but 1) maybe we missed a way to actually make it possible, and 2) I totally understand why you want to do it, which is why we switched to fully containerizing SDKs in Zenith ๐Ÿ™‚

vernal badger
#

Zenith ftw! ๐Ÿ™‚

hot falcon
vernal badger
#

@hot falcon i take it this OCI part means any container engine (docker and others) - right?

#

Dagger Engine -> Docker Engine -> pipelines[] ??

hot falcon
#

Actually the diagram is over-simplifying, technically the Dagger Engine has no dependency, it just needs to run on an OS that supports running linux containers (and have the privileges to do so)

vernal badger
#

Understood. I seen it more as a communication arrow than dependency arrow

#

UML purists maybe have diff opinions ๐Ÿ˜›