Docker allows context paths which do not have to be in a sub-directory relative to the dockefile, they can be parent directories or the Dockerfile and context can be separated. A docker context must be absolute if it is not a sub-directory, e.g. ../ is not a valid context.
Currently SST assumes the context will be in a relative position to the $cli.paths.root, this may not be the same root of the project in all cases, e.g. a monorepo where the modules are hoisted to a parent package.json.
Currently it is not possible to deploy a service having a context with an absolute path which is a parent directory of the sst.config.ts.
Docker allows context paths which do not have to be in a sub-directory relative to the dockefile, they can be parent directories or the Dockerfile and context can be separated. A docker context must be absolute if it is not a sub-directory, e.g.
../
is not a valid context.Currently SST assumes the context will be in a relative position to the
$cli.paths.root
, this may not be the same root of the project in all cases, e.g. a monorepo where the modules are hoisted to a parentpackage.json
.Currently it is not possible to deploy a service having a context with an absolute path which is a parent directory of the
sst.config.ts
.