-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
docker run have been failed since yarn v3 introduced #9291
Comments
Related to #8764 (comment) |
That error can occur when you accidentally run |
This comment was marked as off-topic.
This comment was marked as off-topic.
docker run時にyarn installを改めて走らせるのは最終手段だよね… |
This comment was marked as off-topic.
This comment was marked as off-topic.
Could you see if you can reproduce the issue with Calckey? I think the way Calckey implemented Yarn 3 is slightly different than that of Misskey. |
.yarn/install-state.gz あたりが必要かも |
node_modulesの中身あったしシンボリックリンクではないらしい? |
これがビンゴだと思う |
ローカルでは動いたけどOktetoではダメだった |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
どこかのタイミングでシンボリックリンク先にするべきパスが変わることがある?
|
これホストから packages/*/node_modules 持ってきちゃってるからか (直しておきます) |
あ〜、dockerignoreか |
とはいえdockerignoreはOktetoで動かないのとは関係ないかも(ホストでyarn installしているわけではないしnodeすらインストールしない) |
それもそうだな (それはそうとして Okteto のログってどっかで見れるの) |
しゅいろに頼めば出てくる |
これなんで治ったんだっけ |
これなんで治ったんだっけ(2回目) |
これかな |
Reason
DockerfileのCOPYはシンボリックリンクをコピーしてくれない(原理上することができなさそう)docker run時にyarn installを改めて走らせるのはちょっと…The text was updated successfully, but these errors were encountered: