Closed caosbad closed 2 years ago
Thanks. Can you try adding @unlock-protocol/unlock-core locally first?
@julien51 Did you mean the npm package named @unlock-protocol/unlock-core ? I can't find it on npm~
Ho no sorry, I meant unlockprotocol/unlock-core
. Just run docker pull unlockprotocol/unlock-core
first and then you should be good to build ?
@julien51 run docker pull unlockprotocol/unlock-core
done, but still not work, should I need to change the config file LOCKSMITH_PURCHASER_ADDRESS
? And Im not sure what's that config mean.
Change the dockfile content FROM unlock-core
to FROM unlockprotocol/unlock-core
can build success , should I replace them all ?
Sorry for the delays here.
run docker pull unlockprotocol/unlock-core done, but still not work,
Same error?
should I need to change the config file LOCKSMITH_PURCHASER_ADDRESS ? And Im not sure what's that config mean.
You should not have to change this, I think.
Change the dockfile content FROM unlock-core to FROM unlockprotocol/unlock-core can build success , should I replace them all ?
So ideally we'd want to build from a unlock-core in case the image has been locally updated. We need to find a way to load unlock-core
from unlockprotocol/unlock-core
first.
Honestly I am not great with docker... so this probably needs to be refactored :(
I was able to load the locksmith image after namespacing unlock-core. Also I pulled unlockprotocol/unlock-core before changing it. Seems to be working fine now.
Describe the bug When run docker-compose got failed error
To Reproduce Steps to reproduce the behavior: run
Expected behavior runing success with docker
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context