# Sage installation problem Plugin env does not exist

**URL:** https://discourse.roots.io/t/sage-installation-problem-plugin-env-does-not-exist/28929
**Category:** sage
**Tags:** wsl, windows, bud, sage10
**Created:** 2024-11-21T16:14:46Z
**Posts:** 3

## Post 1 by @mamarmite — 2024-11-21T16:14:46Z

It seems really basic, and I’m sure I’m missing some basic things. But I stumble on this one.

## Context

I’m in win10, wsl 2 with a docker container.

I’m able to install everything, but can’t build.

The bud error is :  
`problem running config.before callback: Plugin env does not exist`  
It’s triggered from :slight_smile:

```
BudError

✘ problem running config.before callback: Plugin env does not exist

ℹ Stack trace

 at ./node_modules/ink/build/components/Static.js:24:16
 at Array.map (<anonymous>)
 at Static (./node_modules/ink/build/components/Static.js:23:36)
 at renderWithHooks (./node_modules/react-reconciler/cjs/react-reconciler.development.js:7478:18)
 at mountIndeterminateComponent (./node_modules/react-reconciler/cjs/react-reconciler.development.js:11247:13)
 at beginWork (./node_modules/react-reconciler/cjs/react-reconciler.development.js:12760:16)
 at beginWork$1 (./node_modules/react-reconciler/cjs/react-reconciler.development.js:19569:14)
 at performUnitOfWork (./node_modules/react-reconciler/cjs/react-reconciler.development.js:18703:12)
```

## What I tried / test

Dotenv is installed from sub packages and present in the yarn.lock

I tried building directly into the container, and directly in wsl with the container running with the URL up.

## My “question”

But I still feel in the fog of where the issue would be : in bud config, in my environment setup, both ?

I would take any hypothesis right now to try a new direction.

## Until

My next move would be to move out of docker and use a flat webserver to avoid the noise of debugging basic stuff like this.

---

## Post 2 by @mamarmite — 2024-11-22T16:20:59Z

Ok I manage to reproduce!

A fresh install works (in the same bedrocks structure).  
If I delete the `.yarn` repertory and redo the process `yarn` + `yarn build`. The same error occur.

So I will read about if it’s a bud problem where I should setup some clearing of some global cache ? I tried clearing the yarn cache, but it didn’t help.

---

## Post 3 by @mamarmite — 2024-11-22T16:55:11Z

Ok now I’m thinking it’s maybe lack of knowledge of yarn or bud.

I’m trying to “start fresh” and this error occur everything.

Do I missed some steps to do a fresh start ? :

- delete `/.yarn`
- delete `/node_modules`
- delete `yarn.lock`
- run : `yarn` to install
- run : `yarn build`