The Docker Quick Experience seems to be not done or removed

[DYCSchool]

Hi! Thanks for the great project.

I noticed that the document mentioned Docker Quick Experience ( https://zread.ai/DangoSys/buckyball/5-docker-quick-experience ).

However, I couldn't find the corresponding Docker file, image address or related instructions in the README and files of the current repository.

I'm not quite sure if this is because this part has not been completed yet or has already been removed/migrated. Please confirm this part of the content and supplement the current status and correct entry in the README or document.

[shirohasuki]

Hi DYCSchool, thanks for the interest in Buckyball!

Good catch — we did have Docker support previously, but it was removed in PR #22, where we migrated our entire build system to Nix. The old Docker environment was no longer compatible after the migration.

The good news is that the Nix-based setup is actually much simpler now. You can get up and running with just a few commands:

git clone https://github.com/DangoSys/buckyball.git
cd buckyball
./scripts/nix/build-all.sh

We'll update the docs to reflect this change and remove the stale Docker references. Thanks for flagging it!

If you're trying to build a new docker with our Nix-based workflow, feel free to open issues if you run into anything — we're happy to help. We do recognise that Docker support is important for lowering the barrier to entry — not everyone is familiar with Nix, and a simple docker run is still the fastest way for people to try things out. Re-introducing Docker support based on our current Nix environment is on our roadmap.

[DYCSchool]

Hi DYCSchool, thanks for the interest in Buckyball!

Good catch — we did have Docker support previously, but it was removed in PR #22, where we migrated our entire build system to Nix. The old Docker environment was no longer compatible after the migration.

The good news is that the Nix-based setup is actually much simpler now. You can get up and running with just a few commands:

git clone https://github.com/DangoSys/buckyball.git
cd buckyball
./scripts/nix/build-all.sh

We'll update the docs to reflect this change and remove the stale Docker references. Thanks for flagging it!

If you're trying to build a new docker with our Nix-based workflow, feel free to open issues if you run into anything — we're happy to help. We do recognise that Docker support is important for lowering the barrier to entry — not everyone is familiar with Nix, and a simple docker run is still the fastest way for people to try things out. Re-introducing Docker support based on our current Nix environment is on our roadmap.

Thanks for the clarification!

I’m quite interested in the Docker side of the project and would like to try working on a Docker image based on the current Nix workflow.

May I ask if there’s any existing progress or ongoing work related to reintroducing Docker support? I’d love to know the current status.

I’ve been studying this project for the past few weeks and have been going through its structure and build system, and I’m really interested in getting more involved and contributing to the development.

Please let me know if there are any guidelines, preferred approaches, or areas where help is needed.

Thanks again!

[shirohasuki]

@DYCSchool Thanks for your interest and for spending time studying buckyball! It’s great to hear that you’re willing to help reintroduce Docker support.

The project recently migrated to Nix to ensure build reproducibility and environment isolation. Regarding the Docker side, our ideal path is to use Nix's native dockerTools to generate a lightweight, layered image directly from the Nix derivation. This would keep the Docker environment perfectly synced with our development environment.

We haven't started the actual implementation of this part yet, so your contribution would be extremely timely. If you're interested, you could:

• Explore using pkgs.dockerTools.buildLayeredImage in the existing Nix workflow.

• Start with a minimal image that can run in one-clike successfully.

Feel free to open a Draft PR or share your thoughts here. I’d be happy to discuss the technical details as you go!

[shirohasuki]

Would you like to take the lead on this? I can assign the issue to you. Don't worry about doing it all alone—I’ll be right here to collaborate with you.

[DYCSchool]

Thank you so much for your help and guidance!

I’ve now successfully gotten Buckyball running inside Docker on my side, so your suggestions were really helpful.

I’d be very happy to take part in this work and contribute to develop Docker support.

[shirohasuki]

Thank you so much for your help and guidance!

I’ve now successfully gotten Buckyball running inside Docker on my side, so your suggestions were really helpful.

I’d be very happy to take part in this work and contribute to develop Docker support.

Impressive progress! Assignee: @DYCSchool