[Feature Request] Publish Docker image

[cretz]

Describe the solution you'd like

Need a docker image for this single binary

[slamdev]

while waiting for the official image you can use this one: https://github.com/slamdev/temporalite-container-image

version: "3.8"
services:
  temporal:
    # https://hub.docker.com/r/slamdev/temporalite/tags
    image: slamdev/temporalite:0.10.7
    restart: on-failure
    command:
      - --namespace=default
      - --db-filename=/tmp/db
    tmpfs:
      - /tmp
    ports:
      - "7233:7233"
      - "8233:8233"

ignore temporalite name, its temporal cli under the hood, I just re-purposed the repo that was used to build deprecated temporalite.

[ElanHasson]

@cretz Can i just send a PR for this?

I was thinking:

Add a GHA workflow to build, test, sign the image and push to ghcr on every release?

Edit: Is https://github.com/temporalio/cli/pull/463/files#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557 this?

#463

[cretz]

We are actually in the process of rewriting the innards of the CLI of which #463 is part, yes. We just don't have the publish step yet or the rest of the rewrite completed, stay tuned.

[ElanHasson]

Love it thanks!

[ElanHasson]

so, temporalio/admin-tools has the cli as well :)

[enricoschaaf]

Do I see this right that the is no replacement yet for https://github.com/slamdev/temporalite-container-image? Since the PR is merged I assumed it maybe there is but it seems the action just triggers docker builds of other containers that contain the cli but no standalone image.

[slamdev]

Do I see this right that the is no replacement yet for https://github.com/slamdev/temporalite-container-image? Since the PR is merged I assumed it maybe there is but it seems the action just triggers docker builds of other containers that contain the cli but no standalone image.

you can switch to official image now, that's how I use it:

  temporal:
    # https://hub.docker.com/r/temporalio/server/tags
    image: temporalio/server:1.21.5.0
    restart: on-failure
    user: "0:0" # running as root to avoid permission issues with writing to /tmp/sqlite/db
    entrypoint:
      - temporal
      - server
      - start-dev
      - --namespace=default
      - --db-filename=/tmp/sqlite/db
      - --ip=0.0.0.0
    tmpfs:
      - /tmp/sqlite
    ports:
      - "7233:7233"
      - "8233:8233"

PS: I archived my repo to remove the confusion :)

[cretz]

To clarify why this issue remains open, it is ideal to have a proper CLI container, versioned the same as the CLI and deployed when CLI is released. One should not have to use a full Temporal server container to use one of the binaries within (the CLI in this case) which is only as recent as that server release.

[JobaDiniz]

what's the difference between the CLI and the "server"?

For example, I'm using the CLI on my laptop to develop. But I want to use a docker image instead - if available - so which image should I use for development purposes? the temporalio/server:1.21.5.0?

[josh-berry]

So, if you need a container with a server for development purposes, for now you should use temporalio/server. This is the actual production-grade server, which of course will work fine in a CI/CD context as well.

If you need a Docker image with the CLI for its client functionality, you can use temporalio/admin-tools.

We don't currently have a container for just the dev-server that's embedded in the CLI (that's at least partially what this ticket is about).

It would be helpful for me hear y'all's thoughts on:

1. Do you care primarily about having the dev-server in its own container?
2. Or do you want the CLI in its own container separate from admin-tools (which holds other tools as well)?
3. Or do you want both?
4. And if you want both, would you want a single container for both dev-server and client functionality, or two different containers?

[paymog]

How do we use the admin-tools image? I think most of us just want an easy way to replace temporalite which is now deprecated. I personally just need an easy way to run a server and the web ui for local development and in CI/CD (don't need the web ui in CI/CD).