This article will go through the process of creating a Dockerfile, building a Docker image, then converting it to a Golem image and using it in a requestor script.

• Have Docker installed and Docker service available. If you don't have Docker installed follow these instructions
• Gvmkit-build installed (see instructions)
• Yagna service installed and running with the try_golem app-key configured (see instructions)

This is the simple Dockerfile we are going to use, using the Node base image, creating one volume, and setting the working directory. Simply create a file with the name Dockerfile, without any file extension, and paste the following contents:

FROM node:latest
WORKDIR /golem/work
VOLUME /golem/work
COPY Dockerfile /golem/info/description.txt
COPY Dockerfile /golem/work/info.txt

Note we copy the Dockerfile content into 2 different locations:

• to /golem/info (this folder is not defined as VOLUME)
• and to /golem/work (this folder is defined as VOLUME)

To build the Docker image from the Dockerfile, we can run the following command in the same directory (.) as the Dockerfile to build an image tagged golem-node:

docker build -t golem-node .

The output should look like this:

Now when you have a Docker image built, we can convert it to a Golem image. To save time, we will also upload it to the registry with the same command. To do this, you need to run the appropriate command that uses gvmkit-build to convert and push the image golem-node to the registry.

gvmkit-build golem-node --push --nologin

After running the command, you will see an output that looks like this:

The hash is found after the image link, which in this case gives us the hash 8b238595299444d0733b41095f27fadd819a71d29002b614c665b27c. If you ever lose your hash, you can always recover/re-generate it by running the same command again.

Let's use the newly created image in a requestor script and ensure this is the one we have just made.

We need to prepare our environment:

mkdir golem-example
cd golem-example
npm init
npm i @golem-sdk/task-executor
npm i @golem-sdk/pino-logger

We can now create our index.mjs requestor file, with the imageHash: "8b238595..." matching our image hash.

import { TaskExecutor } from "@golem-sdk/task-executor";
import { pinoPrettyLogger } from "@golem-sdk/pino-logger";
(async () => {
  const executor = await TaskExecutor.create({
    logger: pinoPrettyLogger(),
    api: { key: "try_golem" },
    demand: {
      workload: {
        imageHash: "8b238595299444d0733b41095f27fadd819a71d29002b614c665b27c",
      },
    },
    market: {
      rentHours: 0.5,
      pricing: {
        model: "linear",
        maxStartPrice: 0.5,
        maxCpuPerHourPrice: 1.0,
        maxEnvPerHourPrice: 0.5,
      },
    },
  });

  try {
    const result = await executor.run(async (exe) => {
      console.log("Description.txt: ", (await exe.run("cat /golem/info/description.txt")).stdout);
      console.log("/golem/work content: ", (await exe.run("ls /golem/work")).stdout);
    });
  } catch (err) {
    console.error("An error occurred:", err);
  } finally {
    await executor.shutdown();
  }
})();

In the script, we specify that our task should use the newly created image (indicated by imageHash: 8b238595...). We try to run two commands. The first one prints the content of the decription.txt file (it is a copy of the Dockerfile used to create the image). The second command should list the content of the /golem/work folder. We copied some files there as well (check the content of the Dockerfile above or the description.txt file on the provider), but as /golem/work is defined as VOLUME and created as new when VM is started, this folder will be empty.

Run the following command after ensuring the Yagna service is running and configured correctly:

node index.mjs

You have successfully created and used your Golem image in a requestor script!

Note that the content of the description.txt file that was created in the /golem/info folder is accessible, while the /golem/work folder is empty.