diff --git a/docs/contributor/container.md b/docs/contributor/container.md
index dd44b31bfe96994ed54e3eca8610e7d8778f5261..9c542f411c81f4237e69ffaf63d4686eeac204e4 100644
--- a/docs/contributor/container.md
+++ b/docs/contributor/container.md
@@ -16,7 +16,7 @@ Parity builds and publishes a container image that can be found as `docker.io/pa
 ## Parity CI image
 
 Parity maintains and uses internally a generic "CI" image that can be used as a base to build binaries: [Parity CI
-container image](https://github.com/paritytech/scripts/tree/master/dockerfiles/ci-linux):
+container image](https://github.com/paritytech/scripts/tree/master/dockerfiles/ci-unified):
 
 The command below allows building a Linux binary without having to even install Rust or any dependency locally:
 
@@ -24,14 +24,11 @@ The command below allows building a Linux binary without having to even install
 docker run --rm -it \
     -w /polkadot-sdk \
     -v $(pwd):/polkadot-sdk \
-    paritytech/ci-linux:production \
+    paritytech/ci-unified:bullseye-1.75.0-2024-01-22-v20240222 \
     cargo build --release --locked -p polkadot-parachain-bin --bin polkadot-parachain
 sudo chown -R $(id -u):$(id -g) target/
 ```
 
-If you want to reproduce other steps of CI process you can use the following
-[guide](https://github.com/paritytech/scripts#gitlab-ci-for-building-docker-images).
-
 ## Injected image
 
 Injecting a binary inside a base image is the quickest option to get a working container image. This only works if you