This is a part of docker-compose.yml and it could not create tmp.json file by this way.
I am also aware about opening a lot of ports while starting docker compose, since it could be made by using same docker network and refering to containers by it’s name in one network, but it’s fixable in compare the real problem with this tmp.json file and other dirs.
The only way is starting from root, but it’s not safe (adding this in docker container): user: root
Do you maybe have a solution?
There are no additional istruction in documentation insted of command I use
Even after starting a container by running root I get this error inside plasmic-plasmic-wab-1 container:
Created plexus Plexus project sku8iwsELqAmVdbX3sqZff for user admin@admin.example.com
Unbundling with deps sku8iwsELqAmVdbX3sqZff
/plasmic/platform/wab/src/wab/server/util/apm-util.ts:18
logger().info(${name} took ${new Date().getTime() - start}ms${suffix});
^
TypeError: (0 , import_observability.logger) is not a function
at (/plasmic/platform/wab/src/wab/server/util/apm-util.ts:18:7)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async getMigratedBundle (/plasmic/platform/wab/src/wab/server/db/BundleMigrator.ts:159:10)
at async loadDepPackages (/plasmic/platform/wab/src/wab/server/db/DbBundleLoader.ts:57:11)
at async unbundleWithDeps (/plasmic/platform/wab/src/wab/server/db/DbBundleLoader.ts:150:19)
at async PkgMgr.upsertLatest (/plasmic/platform/wab/src/wab/server/pkg-mgr/index.ts:128:18)
at async PkgMgr.unbundleAndSave (/plasmic/platform/wab/src/wab/server/pkg-mgr/index.ts:48:5)
at async PkgMgr.seedPkg (/plasmic/platform/wab/src/wab/server/pkg-mgr/index.ts:81:5)
at async (/plasmic/platform/wab/src/wab/server/db/DbInit.ts:100:37)
at async Promise.all (index 1)
Node.js v24.6.0
error Command failed with exit code 1.
info Visit yarn run | Yarn for documentation about this command.
$ npm run run-ts – src/wab/server/db/DbInit.ts
npm warn Unknown env config “version-commit-hooks”. This will stop working in the next major version of npm.
npm warn Unknown env config “version-tag-prefix”. This will stop working in the next major version of npm.
npm warn Unknown env config “version-git-message”. This will stop working in the next major version of npm.
npm warn Unknown env config “argv”. This will stop working in the next major version of npm.
npm warn Unknown env config “version-git-tag”. This will stop working in the next major version of npm.
How do you connect your frontend website to your self-hosted backend ? There are no option to provide a custom plasmic admin pannel address instead of studio.plasmic.app.
I’ve deployed plasmic successfully but still have a problem to connect to it a new plasmic project.
Here is the issue:
yarn create plasmic-app
If your browser doesn't automatically open, enter the following URL:
https://studio.plasmic.app/auth/plasmic-init/****************************
It ask for studio.plasmic.app instead of my localhost:3003 domain.
Using docker everything is built and ran locally. It creates 2 images , one for the wab , and another for db , u can access using one of these ports locally
Hmm i feel this is your local permission issue . Also after cloning you need to modify in that one place plasmic/platform/wab/src/wab/server/observability/index.ts
Then docker-compose up --build
Around 17 things it composes/builds then
Thats about it for me , able to see plasmic running via docker
Since on the last update changed node:18-alpine to node:24-alpine image.
There is a small difference inside containers.
Inside node:24-alpine container there is node user and node group already created. Which means they already have UID and GID 1000, like 1000:1000.
Here when Dockerfile creates a new user plasmic, it creates it with UID and GID 1001, like 1001:1001.
Since, the basice non-root user on the host has UID and GID 1000, plasmic user in the container never inherits all permissions form the main host user with UID 1000.
Just need to replace existing code considering node user deletion and setting 1000 UID and GID for our new plasmic user.
This worked for me, too. Since we can’t add issues to the github repo, I am guessing this thread should do the trick? Hoping it gets updated in future versions.
@david_d@EmCmNeDt i can do some updates for either docker file (to update it to node 24 and apply the changes) or update the readme with the solution
I think the first one is more preferred?
Btw sorry for such a late reply, i’m not sure why this thread wasn’t in my notifications list
Yes, the first is preferred, since node:24-alpine is already in the dockerfile, despite its incompatibility with the default GUID permissions inheritance.
