Hi all, I am getting the following error message:

Preparing your SST app
Detected tsconfig.json
Transpiling source
There was a problem transpiling the source.

It appears this is caused by the following error handling in the SST code:

try {
    const result = await esbuild.build(esbuildOptions);
    require('fs').writeFileSync(metafile, JSON.stringify(result.metafile))
  } catch (e) {
    // Not printing to screen because we are letting esbuild print
    // the error directly
    logger.debug(e);
    throw new Error("There was a problem transpiling the source.");
  }

Anyone got any ideas as to why this is happening? I am trying to start SST from inside a docker container.

If you run the same thing outside of a docker container, do you get the same problem?

@Ross Coundon It works outside the container without any issues

Nice! Btw @Fazi, I’m curious why you are running SST inside docker?

Hi @Frank, the reason is mostly because I am using Python lambda functions, which need a couple of libraries installed to run in the local environment. I initially used virtual environments, but found that docker was a bit easier to manage with other devs (i.e. no need to get other developers to download poetry or pyenv etc as docker was already available).

Ah I see. For

sst start

, I was thinking to support building and running Python functions inside docker. But ur setup also works! I think urs might even be faster b/c SST doesn’t have to start/stop a docker contain to handle each request.

thanks @Frank

Ah smart running everything inside docker

Hey @Fazi, any chance you can share your Dockerfile? I'm trying to do the same thing for my current work and I'm fairly new to Docker. I'm certain I'm making awful mistakes in my current setup

Hi @Seth Geoghegan, I actually couldn't get it to work inside Docker - I think the issue was it was launching a docker container inside a docker container (kinda like that Inception film), and this caused the inner Docker container to not know how to communicate with the outside world. Fixing it seemed a bit too fiddly (I was also using Docker relatively newly). Instead what I did was to use Poetry https://python-poetry.org/. I stuck the Poetry.toml file in the root of my project (thus every subfolder, such as test, sourcePath, utilities etc had access to the poetry environment). As I was using Python for lambda functions, I simply output a requirements.txt file from poetry into my source path. This for me worked very well with serverless and made writing Lambda functions a breeze. Here is what my docker file looked like at the time nonetheless:

version: "3.9"
services:
    sst_integration:
        image: 'sst-integration'
        container_name: 'sst-integration'
        build: ./sst_integration
        ports: 
            - "8040:8040"
        volumes:
            - ./sst_integration:/src/sst_integration
            - /src/sst_integration/node_modules
            - ~/.aws/:/root/.aws:ro
        stdin_open: true
        tty: true
        networks:
            - sandbox
networks:
    sandbox:
        name: sandbox_network

I am sure there are much better ways to get it all working though.

Thanks for this! I have gotten it working, but it's awfully slow. I think it has more to do with my dev environment (mac+docker and volumes/mounts) than SST.

@Seth Geoghegan Great, glad to hear it is working for you!