aboutsummaryrefslogtreecommitdiffstats
path: root/tools/docker/old-env/Dockerfile
Commit message (Collapse)AuthorAgeFilesLines
* tools/docker: golang toolchain is autoupdated since 1.21Taras Madan2025-02-061-0/+2
| | | | "go mod go@1.23" updates go.mod to the latest 1.23.*.
* tools/docker: update Go in the containersAleksandr Nogikh2024-09-101-1/+1
| | | | Use 1.22.7.
* tools/docker/old-env: switch to Ubuntu 20.04Dmitry Vyukov2024-06-031-11/+22
| | | | | | | | | 16.04 has extremly old gcc (5.4), which don't support C++17. Switch to 20.04 (gcc 9). Split apt commands to separate lines to improve docker caching, otherwise it's takes lots of time to iterate on package set and unclear what exact package causes problems.
* tools/docker: update old-env to Go 1.21Dmitry Vyukov2024-04-261-1/+1
| | | | | | | | | | Go 1.22 is already released. We try to support up 2 latest Go releases, so we can switch to 1.21 for old-env. Go 1.21 has a number of useful things like new slices/maps/cmp/slog packages, min/max builtin functions, PGO builds.
* go: update to 1.20.11 and 1.21.4Taras Madan2023-11-281-1/+1
| | | | 1.22 release is expected in Feb 2024. We'll go 1.21 - 1.22 then.
* tools/docker: use go1.19.6 and go1.20.1Taras Madan2023-02-241-1/+1
| | | | | env and syzbot containers will use go1.20.1 big-env and old-env containers will use go1.19.6
* tools/docker/old-env: update to Go 1.16Dmitry Vyukov2022-01-191-1/+1
| | | | | | | Our policy is to support 2 latest releases of Go. Currently this is Go 1.16 and 1.17. So update the old-env to the oldest release. This will allow us to use lots of goodness available in the latest versions.
* tools/docker: update clang to version 12Dmitry Vyukov2022-01-191-4/+4
| | | | | | Clang 12 is the latest version supported for Ubuntu 12.04. Update to this version. There is no pressing need, but clang 10 is quite old, so update to the latest version.
* tools/docker/old-env: don't use --allow-releaseinfo-changeDmitry Vyukov2022-01-191-2/+2
| | | | | | | | | | | | This flag is needed for Bullseye that we use in env/syzbot containers. I proactively added it to old-env as well assuming it's version-independent flag. But Ubuntu 16.04 does not like this flag: E: Command line option --allow-releaseinfo-change is not understood in combination with the other options The command '/bin/sh -c apt-get update --allow-releaseinfo-change' returned a non-zero code: 100 Remove it from old-env.
* tools/docker: use apt-get update --allow-releaseinfo-changeDmitry Vyukov2021-09-301-2/+2
| | | | | | | | | Without this flag I am getting: D: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable' Error: Process completed with exit code 100.
* .github/workflows: switch fuzzit to syz-old-envDmitry Vyukov2020-10-271-4/+12
| | | | | | Use syz-old-env because it contains Go 1.14. syz-env contains Go 1.15 and go-fuzz is broken with Go 1.15: https://github.com/dvyukov/go-fuzz/issues/294
* tools/docker: mirror images on githubDmitry Vyukov2020-09-121-13/+1
| | | | | Some users don't have access to the gcr.io registry. Mirror images on github as well.
* tools/docker: add old-envDmitry Vyukov2020-08-221-0/+51
old-env is based on Ubuntu 16.04 and allows to test executor build on older distributions. Fixes #2055
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-12 11:05:25 +0000