Foregrounding a long-running (init) process? #196
senpro-ingwersenk
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am running dinit in my container to manage a few services I'd like to run (about five or so) and it is configured to log everything to the common console. However, how exactly do I see the container logs? - Think
docker logs -f $id, but for the devcontainer.Config (removed a few project specifics):
{ "name": "Devcontainers Environment", "build": { "dockerfile": "Dockerfile", "args": { "DINIT_VERSION": "v0.19.3", "SURREALDB_VERSION": "v2.1.4" } }, "workspaceMount": "source=${localWorkspaceFolder}/,target=/workspace,type=bind,consistency=cached", "workspaceFolder": "/workspace", "forwardPorts": [5000, 8000, 8080, 8090], "otherPortsAttributes": { "onAutoForward": "ignore" }, "portsAttributes": { "5000": { "label": "Surrealist", "protocol": "http", "onAutoForward": "openPreview" }, "8080": { "label": "App HTTP", "protocol": "http", "onAutoForward": "ignore" }, "8090": { "label": "Air-To-App Proxy", "protocol": "http", "onAutoForward": "openBrowserOnce" }, "8000": { "label": "SurrealDB", "protocol": "http" } }, "hostRequirements": { "cpus": 2, "memory": "3gb", "storage": "256mb" }, "customizations": { "vscode": { "extensions": [ "golang.go", "dbaeumer.vscode-eslint", "vitejs.vite", "tamasfe.even-better-toml", "esbenp.prettier-vscode", "surrealdb.surrealql", "bradlc.vscode-tailwindcss", "WallabyJs.console-ninja", "jawei.autopreviewer" ] } }, "containerEnv": { "TZ": "Europe/Berlin", "SURREAL_NO_BANNER": "true", "SURREAL_STRICT": "true", "SURREAL_CLIENT_IP": "socket", "SURREAL_AUTH": "true", "SURREAL_USER": "...", "SURREAL_PASS": "...", "SURREAL_NAMESPACE": "...", "SURREAL_DATABASE": "...", "SURREAL_HIDE_WELCOME": "true", "WORKSPACE_FOLDER": "${containerWorkspaceFolder}" }, "overrideCommand": true, "postStartCommand": ["/usr/local/bin/dinit", "-o"] }My current "solution" is
postStartCommand- but that isn't exactly a great solution, now is it x)After restoring my session from the previous day, I can't get to dinit's output anymore - but the command is still alive:
...so that's good. Still, it'd be great to have this sorted the proper way.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions