Release_Engineering/Docker
Colin Finck 27108f1a28
Fix Illegal Instruction in Docker image by not using -march=native (#2)
`RosBE-Builder.sh` defaults to using `-march=native`. Images built on the latest CPUs (as the GitHub Actions CI machines have) will then fail on older build machines.

These flags are already used for the Debian package: aff79fe611/RosBE-Unix/Base-i386_debian/rules
2024-08-30 23:46:05 +02:00
..
Dockerfile Fix Illegal Instruction in Docker image by not using -march=native (#2) 2024-08-30 23:46:05 +02:00
README.md Add Dockerfile and github docker workflow pushing to ghcr.io (#1) 2024-08-15 16:38:49 +02:00

RosBE-Unix on Ubuntu with Release Engineering scripts

Normally this docker container can be used from ghcr.io

Below steps outline the process of running it locally.

Building the container

  • Create an image named reactos-base:
    • docker build --pull --rm -f "Dockerfile" -t reactos-base "."
  • Create a container named reactos-builder from the reactos-base image
    • docker run --name reactos-builder -it reactos-base
    • exit to close the container

Running the container

  • Run the reactos-builder:
    • docker start reactos-builder
  • Show all docker containers:
    • docker ps
  • Attach to the running reactos-builder:
    • docker attach 03e11af06800 (where 03e11af06800 is the CONTAINER ID from the running container)

Building a release

Release_Configure
# Answer the prompts
Release_ISOs
Release_Source