@adityak74 does this work for you ? I don't believe it would easily work as the cwd that is defined in the ~/.Claude/projects jsonl filesa is the absolute path for the host. So the docker image needs to have the exact same path available for it to work.

@viper151 - Yeah it does work as I have the root .claude directory mounted inside the docker image here.

Popped in here to see if anyone was working on Docker support, and here it is! Can't wait. Let me know if you are looking for an outside set of eyes on the implementation.

@aslaker I wasn't able to verify yet if it's working on not. Only thing I'm concerned about is the ability to work on local folders given the project relies on the cwd of the .claude/projects/[project]/session.jsonl files. And that cwd would be usually the host one while claude code would run inside the container.

Would be great if you could test that.
@adityak74 can you also check the environment variables you have with the ports? Just curious why do we also offer the ability to change PORT and VITE_PORT given we already allow mapping of the ports

@adityak74 @viper151 waiting for this PR to get merged . Happy to help with testing once its done. Do tag me once its ready. Thanks

@adityak74
projects.js:187

• Extracts actual project directories from session files
  These paths point to host directories that don't exist in the container the way I see it and in
  claude-cli.js:31 the spawned Claude process uses these host paths as working directories
  This is not the only dependency though

Not sure if it's related (could be an issue with my setup) but I could not create projects inside claude code UI, says path /app/[project-name] does not exist.