turborepo-remote-cache: Cache server not working

Hope anyone that reads this is having a great day!

I only have the following line in the Docker Container logs, and no other log appears when I use the remote cache.

54896/11/01 01:17PM 30 Server listening at http://0.0.0.0:3000 | severity=INFO pid=6 hostname=turborepo-remote-cache

How do I know when I run the npm script build command, the action is importing the cache, and/or exporting it?

Is the STORAGE_PATH environmental variable correctly used along with volumes?

The following contains the contents of the TurboRepo Remote Cache docker-compose.yml file.

version: '3.9'
services:

  turborepo-remote-cache:
    image: fox1t/turborepo-remote-cache:1.8.0
    container_name: turborepo-remote-cache
    hostname: turborepo-remote-cache
    environment:
      - NODE_ENV=production
      - TURBO_TOKEN='xxx'
      - LOG_LEVEL=debug
      - STORAGE_PROVIDER=local
      - STORAGE_PATH=/tmp
    volumes:
      - /mnt/appdata/repo-team/turborepo-remote-cache/tmp:/tmp
    ports:
      - 3535:3000
    networks:
      - proxy

networks:
  proxy:
    driver: bridge
    external: true

_Originally posted by @NorkzYT in https://github.com/ducktors/turborepo-remote-cache/discussions/84_

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 20

Most upvoted comments

@NorkzYT

Had the same issue, and did some Wiresharkin during the docker-build process. I noticed that there was TLS-handshake error when connecting to turbo-cache server. I was also using node-slim baseimage and after installing ca-certificates package to the container remote cache started to work:

RUN apt-get update && apt-get install -y
ca-certificates \

rahnarsson on Mar 21, 2023

@matteovivona Unfortunately, none.

just tried with version 1.12 and first package on my Dockerfile

-> [build 6/10] RUN ppm turbo --filter-api build => # @flow/sentry:build:
-> # @flow/feature-flag:build: cache hit, replaying output 2065d6fa18024458 => # @flow/feature-flag:build:
=> # @flow/feature-flag:build: > @flow/feature-flag@0.3.0 build /home/node/packages/feature-flag => => # @flow/feature-flag:build: > rimraf dist &8 tsc
=> # @flow/feature-flag:build:

second package

=> [build 6/10] RUN prpm turbo --filter-api build =› =› # @flow/filters:build:
-> -> # @flow/automations:build: cache miss, executing 393b11febee45d47 =› => # @flow/automations:build:
-> -> # @fLow/automations :build: > @fLow/automations@1.1.1 build /home/node/packages/automations => => # @flow/automations:build: > rimraf dist 8& tsc
=> # @flow/automations:build:

Interesting. Does it work for you without any failures? I ask since the second package says “cache miss”.

the second package, in this case, had to be re-built

matteovivona on Feb 3, 2023

Should we add this to the documentation on our side?

fox1t on Dec 31, 2022

Hey! What is your local turborepo client saying? Is the remote cache enabled? Can you double-check if you followed all steps here?

fox1t on Dec 28, 2022