I remember this as being correct. Contajners is very close to the REST API of docker, and that's the way it works. It has no notion of current directory, as well in order to work fully remote.

Yes like its mentioned here, the lib is a thin layer on the REST api and that’s what it expects: a tar of the directory: https://docs.docker.com/engine/api/v1.45/#tag/Image/operation/ImageBuild The docker cli which works with the pwd has this extra logic of reading the path and making a tar before making the same call as a cli convenience. Like the other language SDKs contajners also doesn’t offer this as the user is expected to do this the way the language/problem sees fit. Hope that helps?