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

Path is not absolute: ./.config #8649

Open
anthonyshew opened this issue Jul 2, 2024 Discussed in #8645 · 0 comments
Open

Path is not absolute: ./.config #8649

anthonyshew opened this issue Jul 2, 2024 Discussed in #8645 · 0 comments

Comments

@anthonyshew
Copy link
Contributor

Discussed in #8645

Originally posted by lz-er July 2, 2024

Summary

We are using the node:20.9.0-buster docker image to build our project.
After updating turbo from 1.4.6 to 2.0.6 we get the error above, no path is configured with TURBO_CONFIG_DIR_PATH and overwriting it does not fix the issue.

Log from one of the failed builds:

09:48:38  2024-07-02T07:48:38.784+0000 [TRACE] log: registering event source with poller: token=Token(1), interests=READABLE
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_lib::cli: failed to start telemetry: Invalid config directory: Path is not absolute: ./.config
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38  2024-07-02T07:48:38.788+0000 [DEBUG] turborepo_telemetry: telemetry sender not initialized
09:48:38    x Path is not absolute: ./.config

Log when we provide an custom absolute path with TURBO_CONFIG_DIR_PATH=/dev/shm/ubuntu/workspace/mono_repo:

16:29:34  2024-07-01T14:29:33.964+0000 [TRACE] log: registering event source with poller: token=Token(1), interests=READABLE
16:29:34  2024-07-01T14:29:33.967+0000 [DEBUG] turborepo_telemetry::config: Telemetry config path: /dev/shm/ubuntu/workspace/mono_repo/turborepo/telemetry.json
16:29:34  2024-07-01T14:29:33.968+0000 [DEBUG] turborepo_telemetry: Starting telemetry event queue flush (num_events=9)
16:29:34  2024-07-01T14:29:33.968+0000 [DEBUG] turborepo_telemetry: Done telemetry event queue flush
16:29:34    x Path is not absolute: ./.config

It all works on our machines locally (Windows and Linux (Ubuntu)) but not on the build server in the docker image.

What we tried so far additionally:

  1. Disabling telemetry with flag: TURBO_TELEMETRY_DISABLED and DO_NOT_TRACK

Additional information

No response

Example

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant