Phorcys Posts - Answer Overflow

Phorcys

Posts Comments

CCoder.com

•Created by Phorcys on 9/21/2024 in #help

No port-forwarding in the web UI

(from @DuckyDev in #general)

53 replies

CCoder.com

•Created by Phorcys on 6/13/2024 in #help

Troubleshooting steps for SCIM

From @mark - https://discord.com/channels/747933592273027093/971231372373033030/1250830381255495783 --- Are there any troubleshooting steps for SCIM integration (presumably) performing wonky actions like randomly suspending my Coder users? It seems every day around 4--5% of my users are getting suspended and there's no cause given in the audit log.

12 replies

CCoder.com

•Created by Phorcys on 5/29/2024 in #help

Get last created workspace of user via CLI

From https://discord.com/channels/747933592273027093/971231372373033030/1245469675895394325 - @joshiscool --- Hi, is there any easy way to see when a workspace is created? I know its in the json output of coder ls but it would be nice if it was in a more accisble place. an engineer on my team creates alot of workspaces and wants to open the latest one she created, basically. I told her to run

coder ls -o json | jq '[.[] | {name, created_at}]'

coder ls -o json | jq '[.[] | {name, created_at}]'

But this feels subopitmal

22 replies

CCoder.com

•Created by Phorcys on 5/15/2024 in #help

Running `vkcube` in a Docker workspace

https://discord.com/channels/747933592273027093/971231372373033030/1236981138455531562 / https://discord.com/channels/747933592273027093/971231372373033030/1239601013162508328 --- Hi @Phorcys I'm still having problems running vkcube, can not understand why nvidia gpu is not selected. Any other tip to make it work? I already have

  devices {
    host_path = "/dev/nvidia0"
  }
  devices {
    host_path = "/dev/nvidiactl"
  }
  devices {
    host_path = "/dev/nvidia-uvm-tools"
  }
  devices {
    host_path = "/dev/nvidia-uvm"
  }
  devices {
    host_path = "/dev/nvidia-modeset"
  }

  devices {
    host_path = "/dev/nvidia0"
  }
  devices {
    host_path = "/dev/nvidiactl"
  }
  devices {
    host_path = "/dev/nvidia-uvm-tools"
  }
  devices {
    host_path = "/dev/nvidia-uvm"
  }
  devices {
    host_path = "/dev/nvidia-modeset"
  }

and gpus = "all"

5 replies

CCoder.com

•Created by Phorcys on 5/15/2024 in #help

Cannot publish template to Coder via CLI

From https://discord.com/channels/747933592273027093/971231372373033030/1240063511124508822 --- Any ideas why uploading a template using seems to succeed all the way to cleaning up then Encountered an error running "coder templates push" API request error to "POST:https://url/f86ad2c5-d63b-4072-9aca-8f94eb4645cb/templates". Status code 400 Trace=[Usage: coder templates push [flags] [template] Error: ] Validation failed. If I put the template in the web interface it builds fine and I can publish it that way. It occurs for any template I've tried. coder client (and server) version 2.9.4

2 replies

CCoder.com

•Created by Phorcys on 5/15/2024 in #help

Sub-path reverse-proxying with Coder

From @STRONG.CODΞ in https://discord.com/channels/747933592273027093/971231372373033030/1239657571099607100 --- Hey, im having a little trouble with the network configs. Im hosting code-server in docker and didnt change much except the passwords and config location. The only problem I have now is that if im hosting lets say a page with expressJS and im using a seperate css and js file which are located in /public i cant access them because: 1. [port].sub.domain.com cant be accessed so I need to use sub.domain.com/proxy/[port]. 2. When using sub.domain.com/proxy/3000 its trying to get the css file from sub.domain.com/proxy/style.css which is not a file. I hope you are able to understand my problem nd may be able to help me. Thank you in advance.

18 replies

CCoder.com

•Created by Phorcys on 10/2/2022 in #help

Docker templates not working whenever a subfolder is used

If the docker images are in a subfolder, the workspace will straight up fail to create. here are the logs :

Initializing the backend...
Initializing provider plugins...
- Finding kreuzwerker/docker versions matching "2.22.0"...
- Finding coder/coder versions matching "0.5.0-pre"...
- Using kreuzwerker/docker v2.22.0 from the shared cache directory
- Using coder/coder v0.5.0-pre from the shared cache directory
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Warning: Incomplete lock file information for providers
Due to your customized provider installation methods, Terraform was forced to
calculate lock file checksums locally for the following providers:
- coder/coder
- kreuzwerker/docker
The current .terraform.lock.hcl file only includes checksums for linux_amd64,
so Terraform running on another platform will fail to install these
providers.
To calculate additional checksums for another platform, run:
terraform providers lock -platform=linux_amd64
(where linux_amd64 is the platform to generate)
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Terraform 1.3.0
data.coder_workspace.me: Refreshing...
data.coder_workspace.me: Refresh complete after 0s [id=03c744e4-e924-4214-b422-06cd7556814c]
coder_agent.dev: Plan to create
coder_app.novnc[0]: Plan to create
coder_app.code-server: Plan to create
docker_volume.home_volume: Plan to create
docker_image.workspace_image: Plan to create
docker_container.workspace[0]: Plan to create
Plan: 6 to add, 0 to change, 0 to destroy.
docker_volume.home_volume: Creating...
coder_agent.dev: Creating...
docker_image.workspace_image: Creating...
coder_agent.dev: Creation complete after 0s [id=978ef762-a4ed-4349-8449-de7139524e92]
coder_app.novnc[0]: Creating...
coder_app.code-server: Creating...
coder_app.novnc[0]: Creation complete after 0s [id=7677e148-29f1-40a2-8cdb-b43a9ea07c03]
coder_app.code-server: Creation complete after 0s [id=8d2e3337-6606-473f-9e9a-1da771f61220]
docker_volume.home_volume: Creation complete after 1s [id=coder-phorcys-testworkspace-root]
docker_image.workspace_image: Creation errored after 2s

Initializing the backend...
Initializing provider plugins...
- Finding kreuzwerker/docker versions matching "2.22.0"...
- Finding coder/coder versions matching "0.5.0-pre"...
- Using kreuzwerker/docker v2.22.0 from the shared cache directory
- Using coder/coder v0.5.0-pre from the shared cache directory
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Warning: Incomplete lock file information for providers
Due to your customized provider installation methods, Terraform was forced to
calculate lock file checksums locally for the following providers:
- coder/coder
- kreuzwerker/docker
The current .terraform.lock.hcl file only includes checksums for linux_amd64,
so Terraform running on another platform will fail to install these
providers.
To calculate additional checksums for another platform, run:
terraform providers lock -platform=linux_amd64
(where linux_amd64 is the platform to generate)
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Terraform 1.3.0
data.coder_workspace.me: Refreshing...
data.coder_workspace.me: Refresh complete after 0s [id=03c744e4-e924-4214-b422-06cd7556814c]
coder_agent.dev: Plan to create
coder_app.novnc[0]: Plan to create
coder_app.code-server: Plan to create
docker_volume.home_volume: Plan to create
docker_image.workspace_image: Plan to create
docker_container.workspace[0]: Plan to create
Plan: 6 to add, 0 to change, 0 to destroy.
docker_volume.home_volume: Creating...
coder_agent.dev: Creating...
docker_image.workspace_image: Creating...
coder_agent.dev: Creation complete after 0s [id=978ef762-a4ed-4349-8449-de7139524e92]
coder_app.novnc[0]: Creating...
coder_app.code-server: Creating...
coder_app.novnc[0]: Creation complete after 0s [id=7677e148-29f1-40a2-8cdb-b43a9ea07c03]
coder_app.code-server: Creation complete after 0s [id=8d2e3337-6606-473f-9e9a-1da771f61220]
docker_volume.home_volume: Creation complete after 1s [id=coder-phorcys-testworkspace-root]
docker_image.workspace_image: Creation errored after 2s

17 replies

CCoder.com

•Created by Phorcys on 8/18/2022 in #help

[code-servers] VSCode Insiders channel

I might've asked that already but is there a way for me to use the insiders channel ?

15 replies

Gaming

Programming