Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster.addService - option to pull container image instead of build #706

Closed
elijahmorg opened this issue Jul 18, 2024 · 2 comments
Closed
Assignees

Comments

@elijahmorg
Copy link

Add the ability to bypass building docker images and instead pull an already existing image. It could look something like this.

https://www.pulumi.com/registry/packages/docker/api-docs/remoteimage/

Reason for this is our containers are built in a different pipeline and already pushed into ECR. But being able to pull both from a public registry or private ECR would be good.

    const cluster = new sst.aws.Cluster("MyCluster", { vpc });
    const remoteImage = new docker.RemoteImage("ubuntu", { name: "ubuntu:precise" });

    cluster.addService("MyService", {
      public: {
        ports: [{ listen: "80/http" }],
      },
      transform: {
        image: {
          remoteImage: remoteImage,
        }
      }
    });
@fwang
Copy link
Contributor

fwang commented Sep 9, 2024

@elijahmorg Cluster switched to use the new DockerBuild component now - https://www.pulumi.com/registry/packages/docker-build/api-docs/image/

Does it support what you are trying to do?

/cc @arpadgabor

@fwang
Copy link
Contributor

fwang commented Sep 23, 2024

Supported in the latest version. image takes ie. nginx:latest.

@fwang fwang closed this as completed Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants