Skip to content

[Bug]: Creating workspaces hang when using uppercase workspace name #1471

Open

Description

@DarkGhostHunter

Before submitting

  • I have searched existing issues to confirm this is not a duplicate
  • I am running the latest version of Devsy

What happened?

Creating a workspaces stays in "creating".

What did you expect to happen instead?

To create the workspace

Steps to reproduce

  1. Create Docker Provider
  2. Create Workspace using local /var/home/dev/Projects/Backend with .devcontainer.json/.
  3. All defaults
  4. Hangs on creating.

devcontainer.json

Error output / logs

No logs.

How often does this happen?

Every time

Operating system

Linux

Linux distribution (if applicable)

Fedora 55 (Bluefin, Atomic)

Architecture

AMD64

Desktop app or CLI?

Desktop app

Devsy version

v1.23.2

Devsy provider

Docker

Provider version

v1.0.0

Screenshots

Image

Anything else?

  • Happens with both Docker and Podman
  • Works when the container is running (?).
  • All of this on Flatpak and AppImage

Activity

  1. DarkGhostHunter commented on Oct 12, 2026

    @DarkGhostHunter
    Author

    I just deleted everything and tried again, downloaded the release from GitHub v1.23.2, and it worked.

  2. DarkGhostHunter commented on Oct 18, 2026

    @DarkGhostHunter
    Author

    Seems that there is a problem with the workspace naming. The moment I try something uppercase, the "Launching workspace" hangs.

  3. changed the title [-][Bug]: Creating workspaces hang[/-] [+][Bug]: Creating workspaces hang when using uppercase workspace name[/+] on Oct 18, 2026
  4. skevetter commented on Oct 18, 2026

    @skevetter
    Contributor

    I see. Do you have any logs related to this just to help me understand what's happening better on your end? And you said this only happens on a workspace with the uppercase name?

  5. DarkGhostHunter commented on Oct 19, 2026

    @DarkGhostHunter
    Author

    Devsy v1.24.0, Fedora 44, GNOME 50. No logs since the container doesn't even build or shows logs at all (Waiting for input on log tab).

    Image

    Then, it get stuck:

    Image

    I change the name to lowercase...

    Image

    And it works!

    Image

    My guess is that naming becomes invalid since it's not domain mapeable, but be my guest. Surely it won't work if I had something like special characters or emojis (didn't test this)

  6. skevetter commented on Oct 19, 2026

    @skevetter
    Contributor

    I'm still working on some user interface improvements, but could I get you to go to the settings panel and on the general section for desktop application logging and CLI capture logging. Can you set both of those values to debug?

  7. DarkGhostHunter commented on Oct 19, 2026

    @DarkGhostHunter
    Author

    Yeah, but were are the logs?

  8. DarkGhostHunter commented on Oct 19, 2026

    @DarkGhostHunter
    Author

    BTW, doing the same, show the logs resolving workspace with ide="none" launch="auto" and stays there.

  9. skevetter commented on Oct 19, 2026

    @skevetter
    Contributor

    They should show right below the launch activity in the launching workspace.

  10. skevetter commented on Oct 19, 2026

    @skevetter
    Contributor

    I'm going to try to reproduce on my end, but I need to set up Podman.

  11. rkl110 commented on Oct 21, 2026

    @rkl110

    Same problem here on macOS. It looks like the input validation for the name isn’t working. Adding a “.” to the name also prevents it from starting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions