I don't know if there is a tier-1 target that supports AtomicU128 right off the top of my head, but you can configure docs.rs to build for a different tier-1 target than x86_64-unknown-linux-gnu in your Cargo.toml.
You also might wish to suppress compile time errors by annotating your crate with [cfg(target_has_atomic = "128")] where appropriate. I.e. I think your whole crate only makes sense on targets with AtomicU128 support, so you could add a #![cfg(target_has_atomic = "128")] as the first line in your crate's root file to make it build on targets that don't support AtomicU128 as well. That wouldn't really be a fix for docs.rs though, as docs.rs would simply render your documentation as if your crate is empty (which it would be on targets without AtomicU128).