Terrasque

Just a small detail, docker containers aren’t vm’s and not running their own os. They run inside a jail under the host kernel. Docker containers are very lightweight.

When you run it, do you use unsloth’s recommended settings for coding?

https://unsloth.ai/docs/models/qwen3.6

Also have preserve thinking on, it helps it stay consistent in multi turn work.

Which model version you’re using can also affect results, usually unsloth’s ones are good.

With all that said, it’s of course a small model so it’s not a super coder. The 27b is better (I’d guess 25-35% better), but of course still a small model so…

So it’ll maybe not be good enough still, but should give it the chance to let it do the best it can :)

Try qwen3.6-35b-a3b with a lightweight harness like pi.dev

Having it be able to run commands and try to compile or run the code and see the output helps especially on the “doesn’t compile” part of things

uh… So that’s it, the apache server version? That’s all? I looked at the critical cve’s for that version, and honestly, they’d require a pretty specific setup to be abused if I understood them correctly. Most of them were various DoS with no information disclosure, and the only spooky one I saw require the server to have scripts the server is allowed to execute, but outside of the normal url mapping. Which then would have to be disclosing some info or doing something spooky. The rest seem to require the attacker to control the app behind the apache2 server.

Would be better to upgrade, of course, but it looks nowhere near as bad as the blog author makes it sound.