Open rickstaa opened 4 months ago
@eliteprox, @ad-astra-video, I've been setting up a development container this morning to simplify debugging the timeout issues with external containers as reported in LIV-299. I managed to get the build running, but I'm encountering errors when attempting to use the go-livepeer binaries within the development container. These seem to be related to missing permissions, mounts, environment variables, or configuration values. Have you come across these errors before?
Reopen in Container
to initiate the container setup..vscode/launch.json
:
{
"name": "Launch Transcoder",
"type": "go",
"request": "launch",
"mode": "auto",
"program": "${workspaceFolder}/cmd/livepeer",
"buildFlags": "-tags=mainnet,experimental",
"env": {
"GO111MODULE": "on",
"CGO_ENABLED": "1",
"CGO_LDFLAGS": "-L/usr/local/cuda/lib64 -L/home/elite/compiled/lib",
"PATH": "/usr/local/cuda/bin:${PATH}",
"PKG_CONFIG_PATH": "/home/elite/compiled/lib/pkgconfig",
"LD_LIBRARY_PATH": "/home/elite/compiled/lib"
},
"args": [
"-transcoder",
"-nvidia", "0",
"-orchAddr", "https://127.0.0.1:8935",
"-orchSecret", "1234",
"-cliAddr", "127.0.0.1:7926",
"-maxSessions", "5",
"-dataDir", "/livepeer/arbitrum-one-mainnet/transcoder",
"-v", "7"
]
}
Reopen in Container
to initiate the container setup.
What does this pull request do? Explain your changes. (required)
This is my first attempt at creating a working Vscode dev container for the go-livepeer repository. This development container will greatly simplify me dev workflow in cases where the AI subnet fails inside a container but not when using the binary.
Specific updates (required)
How did you test each of these updates (required)
Does this pull request close any open issues?
Checklist:
make
runs successfully./test.sh
pass