Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cache not being utilized when called through Docker build
See original GitHub issueI’ve successfully cloned the turborepo-remote-cache and I’ve hooked it up in AWS. Everything is working fine, up until I try to use the cache from docker. Here’s my dockerfile:
FROM docker.artifactory.moveaws.com/node:16 as build
COPY . /app
WORKDIR /app
RUN yarn install
RUN yarn build
RUN npx turbo run build
Both RUN yarn build and RUN npx turbo run build are not updating the cache. Originally I thought that my docker instance couldn’t communicate with the deployed service, but when I added a CURL inside the container, I could verify that outbound calls are properly triggered.
My question is, has anyone run into this? Maybe someone has an example of a dockerfile already out there? Or what could possibly be the issue that the commands won’t trigger the cache during the build phase?
Issue Analytics
- State:
- Created a year ago
- Comments:18
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@fox1t I believe @mkotsollaris is referring to building a docker image that uses the remote-cache and not deploying the remote cache. I am also running into issues when trying to reach out to my deployed remote-cache. When docker is running a turbo command it is not using hosted remote cache
You can follow here https://github.com/fox1t/turborepo-remote-cache#deploy-on-docker You are not setting the vars.
You can also use the official image we pushed on docker hub.