docker sed incompatibility
I'm trying to install the serversplitter.blueprint but I am getting errors which are apparently sed related as noted by their support team for this extension.
I'm using this docker image for the panel: ghcr.io/blueprintframework/blueprint:v1.11.10
error logs for install:
ERROR in resources/scripts/blueprint/extensions/serversplitter/ServerSplitterContainer.tsx:48:80
TS2339: Property 'parentId' does not exist on type 'Server'.
46 | export default function ServerSplitterContainer() {
47 | const uuid = ServerContext.useStoreState((state) => state.server.data!.uuid);
> 48 | const parentId = ServerContext.useStoreState((state) => state.server.data!.parentId);
| ^^^^^^^^
49 | const splitterLimit = ServerContext.useStoreState((state) => state.server.data!.featureLimits.splits);
50 | const swapLimit = ServerContext.useStoreState((state) => state.server.data!.limits.swap);
51 | const [viewServer, setViewServer] = useState<Server>();
ERROR in resources/scripts/blueprint/extensions/serversplitter/ServerSplitterContainer.tsx:49:99
TS2339: Property 'splits' does not exist on type '{ databases: number; allocations: number; backups: number; }'.
47 | const uuid = ServerContext.useStoreState((state) => state.server.data!.uuid);
48 | const parentId = ServerContext.useStoreState((state) => state.server.data!.parentId);
> 49 | const splitterLimit = ServerContext.useStoreState((state) => state.server.data!.featureLimits.splits);
| ^^^^^^
50 | const swapLimit = ServerContext.useStoreState((state) => state.server.data!.limits.swap);
51 | const [viewServer, setViewServer] = useState<Server>();
52 | const [deleteServerAction, setDeleteServerAction] = useState<Server>();
error Command failed with exit code 2.8 Replies
@Loki ^
sed is fully supported in the Docker image; until recently, it was how we overrode the default permissions and webuser in the blueprint.sh file. I don't see any actionable information in those errors; did their support team give you any more information?
the sed version used in the docker image does not support the -z flag
I'll look into that today. Thanks.
Thanks all
@Smyrii It's done
Thank ya mate
No problem