docker issueshttps://gitlab.alpinelinux.org/groups/alpine/infra/docker/-/issues2023-12-04T20:38:58Zhttps://gitlab.alpinelinux.org/alpine/infra/docker/secfixes-tracker/-/issues/1Migrate from NVD feeds to API2023-12-04T20:38:58ZKevin DaudtMigrate from NVD feeds to API[NVD - Data Feeds](https://nvd.nist.gov/vuln/data-feeds):
> On December 15th, 2023, the NVD plans to retire all legacy data feeds while guiding any remaining data feed users to updated application-programming interfaces (APIs). APIs have...[NVD - Data Feeds](https://nvd.nist.gov/vuln/data-feeds):
> On December 15th, 2023, the NVD plans to retire all legacy data feeds while guiding any remaining data feed users to updated application-programming interfaces (APIs). APIs have many benefits over data feeds and have been the proven and preferred approach to web-based automation for over a decade. For additional information on the NVD API, please visit the developers pages. Click here for more information on the NVD timeline.
Instead of downloading the feeds as json archives, we need to use the API to obtain information about CVEs.
The API is described [here](https://nvd.nist.gov/developers/start-here).
The API documentation does include the following clause:
> however services which utilize or access the NVD are asked to display the following notice prominently within the application: "This product uses data from the NVD API but is not endorsed or certified by the NVD."
So we probably should add that statement to the secfixes tracker.
NVD has an option to [request an API key](https://nvd.nist.gov/developers/request-an-api-key). Without one, a rate-limit of 5 requests per 30 second applies. With an API key, it's increased to 50 requests.Kevin DaudtKevin Daudt2023-12-15https://gitlab.alpinelinux.org/alpine/infra/docker/alpine/-/issues/3Azure defender reported a false positive that a GDB file is a Wacatac trojan2024-01-29T21:43:11ZThuyen LamAzure defender reported a false positive that a GDB file is a Wacatac trojanhttps://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator/-/issues/6asgen-config-generator doesn't include unreleased alpine versions where binar...2023-12-05T16:02:19ZOliver Smithasgen-config-generator doesn't include unreleased alpine versions where binary packages are already availableAs of writing, Alpine 3.19 is in rc3 state. Binary packages are available, but the version is not released yet.
The asgen-config-generator uses https://alpinelinux.org/releases.json to determine which releases to build appstream data fo...As of writing, Alpine 3.19 is in rc3 state. Binary packages are available, but the version is not released yet.
The asgen-config-generator uses https://alpinelinux.org/releases.json to determine which releases to build appstream data for, and so there currently is no appstream data for 3.19.
This isn't ideal for testing 3.19, alpine-appstream-downloader gets a 404 error when trying to fetch the appstream data files. I wrote a patch to make it try edge in that situation (https://gitlab.com/pabloyoyoista/alpine-appstream-downloader/-/merge_requests/2), but it will still hit the 404 once per run.
Maybe a releases_wip.json or something could be added, that includes the unreleased versions? Not sure what the best path to implement this would be, or if getting the 404 from everybody running alpine-appstream-downloader once is a problem at all. Documenting this for future reference.Pablo Correa GomezPablo Correa Gomezhttps://gitlab.alpinelinux.org/alpine/infra/docker/alpine/-/issues/2Update 3.18.4 image to fix new CVE CVE-2023-53632023-11-19T20:18:46ZArtem YakimenkoUpdate 3.18.4 image to fix new CVE CVE-2023-5363Mirroring [GitHub issue](https://github.com/alpinelinux/docker-alpine/issues/352) to source of truth here.
```
Trivy scan of 3.18.4 official image:
$ trivy image alpine:latest
2023-11-06T02:06:07.665Z INFO Vulnerability scann...Mirroring [GitHub issue](https://github.com/alpinelinux/docker-alpine/issues/352) to source of truth here.
```
Trivy scan of 3.18.4 official image:
$ trivy image alpine:latest
2023-11-06T02:06:07.665Z INFO Vulnerability scanning is enabled
2023-11-06T02:06:07.665Z INFO Secret scanning is enabled
2023-11-06T02:06:07.665Z INFO If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2023-11-06T02:06:07.665Z INFO Please see also https://aquasecurity.github.io/trivy/v0.45/docs/scanner/secret/#recommendation for faster secret detection
2023-11-06T02:06:15.026Z INFO Detected OS: alpine
2023-11-06T02:06:15.026Z INFO Detecting Alpine vulnerabilities...
2023-11-06T02:06:15.028Z INFO Number of language-specific files: 0
alpine:latest (alpine 3.18.4)
Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 2, HIGH: 0, CRITICAL: 0)
┌────────────┬───────────────┬──────────┬────────┬───────────────────┬───────────────┬───────────────────────────────────────────────┐
│ Library │ Vulnerability │ Severity │ Status │ Installed Version │ Fixed Version │ Title │
├────────────┼───────────────┼──────────┼────────┼───────────────────┼───────────────┼───────────────────────────────────────────────┤
│ libcrypto3 │ CVE-2023-5363 │ MEDIUM │ fixed │ 3.1.3-r0 │ 3.1.4-r0 │ Incorrect cipher key and IV length processing │
│ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2023-5363 │
├────────────┤ │ │ │ │ │ │
│ libssl3 │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
└────────────┴───────────────┴──────────┴────────┴───────────────────┴───────────────┴───────────────────────────────────────────────┘
In a 3.18.4 based Dockerfile, doing this fixes this issue:
RUN apk update && apk upgrade --no-cache libcrypto3 libssl3
```
Is it possible to push out a fresh image? Thank you :pray:https://gitlab.alpinelinux.org/alpine/infra/docker/build-base/-/issues/4xtensa-lx106-elf-g++ file not found but it actually exists2023-10-11T17:47:16ZSurya prakashlokulaxtensa-lx106-elf-g++ file not found but it actually exists![e565af8c39aa8f5134e41d561a49efb0066e8f9f.jpg](/uploads/23a5b94c807e053a2c78a6cf966d2191/e565af8c39aa8f5134e41d561a49efb0066e8f9f.jpg){width=458 height=150}
after a deep understanding it look like this file `/root/.arduino15/packages/e...![e565af8c39aa8f5134e41d561a49efb0066e8f9f.jpg](/uploads/23a5b94c807e053a2c78a6cf966d2191/e565af8c39aa8f5134e41d561a49efb0066e8f9f.jpg){width=458 height=150}
after a deep understanding it look like this file `/root/.arduino15/packages/esp8266/hardware/esp8266/3.1.2 Error during build: fork/exec /root/.arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/3.1.0-gcc10.3-e5f9fec/bin/xtensa-lx106-elf-g++` is not missing but `fork/exec` is missing
what is fork/exec and how to solve this issuehttps://gitlab.alpinelinux.org/alpine/infra/docker/apkbuild-lint-tools/-/issues/3False-positive for "volatile source"2023-08-13T21:25:22ZHugo BarreraFalse-positive for "volatile source"The following source is detected as volatile:
https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux/-/commit/1ef6079679acc455f75057dd7097b5b494a241dc.patch
See this CI run for an example: https://gitlab.alpinelinux.org/WhyNotHug...The following source is detected as volatile:
https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux/-/commit/1ef6079679acc455f75057dd7097b5b494a241dc.patch
See this CI run for an example: https://gitlab.alpinelinux.org/WhyNotHugo/aports/-/jobs/1084168
However, this link includes a specific commit's hash, and is therefore immutable.https://gitlab.alpinelinux.org/alpine/infra/docker/gitlab/-/issues/8"ERROR: no such image: alpinelinux/gitlab-shell:: invalid reference format" w...2023-07-12T17:53:24ZJonathan Dobson"ERROR: no such image: alpinelinux/gitlab-shell:: invalid reference format" when running docker-compose up -d## Setting up
Hi. It's my first time using this repo. I am following the README guide.
### I first cloned the repo with
```shell
git clone git@gitlab.alpinelinux.org:alpine/infra/docker/gitlab.git
```
### Then I created a `.env` and I...## Setting up
Hi. It's my first time using this repo. I am following the README guide.
### I first cloned the repo with
```shell
git clone git@gitlab.alpinelinux.org:alpine/infra/docker/gitlab.git
```
### Then I created a `.env` and I added the four variables, added an `=` and a value after each.
The `.env` contents example:
```shell
GITLAB_HOSTNAME=git
GITLAB_ROOT_PASSWORD=gitlabroot
POSTGRES_PASSWORD=password
POSTGRES_USER=postgres
```
## Running
### Next, I run `docker-compose up -d`
this is my error output:
``` shell
server:~/gitlab$ docker-compose up -d
WARNING: The GITLAB_VERSION variable is not set. Defaulting to a blank string.
WARNING: The GITALY_SERVER_VERSION variable is not set. Defaulting to a blank string.
WARNING: The GITLAB_SHELL_VERSION variable is not set. Defaulting to a blank string.
ERROR: no such image: alpinelinux/gitlab-shell:: invalid reference format
```
## Troubleshooting
### Checked and found that no containers are running.
```shell
server:~/gitlab$ docker-compose ps
Name Command State Ports
------------------------------
```
### Made sure the `.env` file is created.
```shell
server:~/gitlab$ ls -a
. .git Dockerfile Taskfile.yml build-args.env gitlab-shell
.. .gitignore LICENSE VERSIONS docker-compose.yml lib
.env .gitlab-ci.yml README.md build gitaly overlay
```
I check if the containers are running with `docker-compose ps` and noticed nothing up.https://gitlab.alpinelinux.org/alpine/infra/docker/alpine/-/issues/1Size be bigger2023-06-14T04:04:15ZChuokeSize be biggerHi, I made an image based on Alpine 3.18.
Previously built images were small, but now rebuilt and made much larger.
previously:
![image](https://github.com/alpinelinux/docker-alpine/assets/17611457/0bd1f2ec-130f-4690-a628-697f32fc4fd2)
...Hi, I made an image based on Alpine 3.18.
Previously built images were small, but now rebuilt and made much larger.
previously:
![image](https://github.com/alpinelinux/docker-alpine/assets/17611457/0bd1f2ec-130f-4690-a628-697f32fc4fd2)
now:
![image](https://github.com/alpinelinux/docker-alpine/assets/17611457/7abab51f-ef86-490e-98b6-b2bdacf0dead)
Is this normal? What am I missing?https://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator/-/issues/5Latest version seems to go through all disk space2022-08-17T04:26:13ZKevin DaudtLatest version seems to go through all disk spaceWhen the appstream-generator `run-generator` job runs, it seems to go through all diskspace, fail, and then returning all the diskspace again.
There is about ~75GB free on that server, which gets consumed in about an hour.
![image](/up...When the appstream-generator `run-generator` job runs, it seems to go through all diskspace, fail, and then returning all the diskspace again.
There is about ~75GB free on that server, which gets consumed in about an hour.
![image](/uploads/38df192e4c0c9e80384ef4ad2e9b3ac2/image.png)
```
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.downloadInternal(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bbbe0]
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.download(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bc730]
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.downloadInternal(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bbbe0]
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.download(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bc730]
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.downloadInternal(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bbbe0]
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.download(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bc730]
??:? @trusted immutable(std.typecons.Nullable!(std.datetime.systime.SysTime).Nullable) asgen.downloader.Downloader.downloadInternal(const(immutable(char)[]), ref std.stdio.File, const(uint)) [0x561ca22bbbe0]
??:? @trusted void asgen.downloader.Downloader.downloadFile(const(immutable(char)[]), const(immutable(char)[]), const(uint)) [0x561ca22bce00]
??:? @property immutable(char)[] asgen.backends.alpinelinux.apkpkg.AlpinePackage.getFilename() [0x561ca23bffa0]
??:? @property immutable(char)[][] asgen.backends.alpinelinux.apkpkg.AlpinePackage.contents() [0x561ca23c0270]
??:? /usr/bin/appstream-generator [0x561ca22e1c50]
??:? void std.parallelism.ParallelForeach!(asgen.backends.interfaces.Package[]).ParallelForeach.opApply(scope int delegate(ref asgen.backends.interfaces.Package)).doIt() [0x561ca22ec560]
??:? void std.parallelism.TaskPool.executeWorkLoop() [0x7f9021733bd0]
??:? thread_entryPoint [0x7f9021437d60]
asgen.downloader.DownloadException@../src/asgen/downloader.d(151): Wrote 0 instead of 10108 objects of type ubyte to file `/cache/cache/tmp/asgen-AOZbcv06/buildkit-0.10.3-r1_aarch64/buildkit-0.10.3-r1.apk' (No space left on device)
```Pablo Correa GomezPablo Correa Gomezhttps://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator/-/issues/4Use releales.json2022-08-16T21:00:17ZKevin DaudtUse releales.jsonInstead of manually having to update the asgen-config.json for the latest Alpine Linux releases, consider using [releases.json](https://alpinelinux.org/releases.json), which gets updated after every release.Instead of manually having to update the asgen-config.json for the latest Alpine Linux releases, consider using [releases.json](https://alpinelinux.org/releases.json), which gets updated after every release.Pablo Correa GomezPablo Correa Gomezhttps://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator/-/issues/3Logs not being rotated2022-08-16T21:16:26ZPablo Correa GomezLogs not being rotatedIt seems that logs aren't being rotated: https://appstream.alpinelinux.org/logs/
I believe the logrotate crontab should have been installed together with logrotate package, and provide automatic log rotation together with the configurat...It seems that logs aren't being rotated: https://appstream.alpinelinux.org/logs/
I believe the logrotate crontab should have been installed together with logrotate package, and provide automatic log rotation together with the configuration file. These seem to be working in my personal server, so maybe there are some paths or something that are different? Or maybe the logrotate crontab is being somewhat removed/ignored? I can see it if I build and start the container form this repo, though. Any help would be greatly appreciated.https://gitlab.alpinelinux.org/alpine/infra/docker/alpine-www/-/issues/1Cannot apk install: "temporary error (try again later)"2022-02-15T15:45:35ZMalcolm CrumCannot apk install: "temporary error (try again later)"Forgive me, I don't know what project to file this under. I think alpinelinux is experiencing an outage:
```
docker run --rm alpine:3.15.0 apk add openssh-client
fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/main/x86_64/APKINDEX.ta...Forgive me, I don't know what project to file this under. I think alpinelinux is experiencing an outage:
```
docker run --rm alpine:3.15.0 apk add openssh-client
fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.15/community/x86_64/APKINDEX.tar.gz
ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.15/main: temporary error (try again later)
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.15/main: No such file or directory
ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.15/community: temporary error (try again later)
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.15/community: No such file or directory
ERROR: unable to select packages:
openssh-client (no such package):
required by: world[openssh-client]
```
```
❯ curl https://www.alpinelinux.org
curl: (28) Failed to connect to www.alpinelinux.org port 443: Operation timed out
```https://gitlab.alpinelinux.org/alpine/infra/docker/appstream-generator/-/issues/2Make generator logs available in a public endpoint2022-02-25T12:04:50ZPablo Correa GomezMake generator logs available in a public endpointI took this [from Debian](https://salsa.debian.org/pkgutopia-team/debian-asgen-config/-/blob/master/scripts/update-metadata.sh). Would be pretty useful in case there is some issues in the generator, which otherwise basically only the inf...I took this [from Debian](https://salsa.debian.org/pkgutopia-team/debian-asgen-config/-/blob/master/scripts/update-metadata.sh). Would be pretty useful in case there is some issues in the generator, which otherwise basically only the infrastructure maintainer can troubleshoot.Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.devhttps://gitlab.alpinelinux.org/alpine/infra/docker/build-base/-/issues/3Make image reusable2021-08-30T07:00:42ZAndy PostnikovMake image reusableTrying to re-use CI images locally I got problem running shell inside of it.
The same happens for `alpinelinux/alpine-gitlab-ci:latest-armv7` image (other arches also brings the same)
Basically any command "cuts the first argument" so ...Trying to re-use CI images locally I got problem running shell inside of it.
The same happens for `alpinelinux/alpine-gitlab-ci:latest-armv7` image (other arches also brings the same)
Basically any command "cuts the first argument" so to run `apk upgrade` I need to type `apk whatever upgrade`
This breaks `abuild`
```
/mnt/main/icu # abuild - deps
ash: gid=0(root): unknown operand
/usr/bin/abuild: .: line 2782: can't open '': No such file or directory
```
Steps to reproduce
```
$ docker run --rm -u 0:0 alpinelinux/build-base:latest-armv7 apk - upgrade
WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/armv7/APKINDEX.tar.gz
(1/2) Upgrading busybox (1.33.1-r5 -> 1.34.0-r0)
Executing busybox-1.34.0-r0.post-upgrade
/bin/sh: can't open '1.34.0-r0': No such file or directory
ERROR: busybox-1.34.0-r0.post-upgrade: script exited with error 2
(2/2) Upgrading ssl_client (1.33.1-r5 -> 1.34.0-r0)
Executing busybox-1.34.0-r0.trigger
1 error; 150 MiB in 60 packages
...
$ docker run --rm -u 0:0 alpinelinux/build-base:latest-armv7 apk upgrade
WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested
apk-tools 2.12.7, compiled for armv7.
usage: apk [<OPTIONS>...] COMMAND [<ARGUMENTS>...]
```
Host details (Ubuntu 21.10)
```
$ docker version
Client: Docker Engine - Community
Version: 20.10.8
API version: 1.41
Go version: go1.16.6
Git commit: 3967b7d
Built: Fri Jul 30 19:53:57 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.8
API version: 1.41 (minimum version 1.12)
Go version: go1.16.6
Git commit: 75249d8
Built: Fri Jul 30 19:52:06 2021
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.4.9
GitCommit: e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version: 1.0.1
GitCommit: v1.0.1-0-g4144b63
docker-init:
Version: 0.19.0
GitCommit: de40ad0
```https://gitlab.alpinelinux.org/alpine/infra/docker/apkbuild-lint-tools/-/issues/2Shellcheck 0.7.22022-02-13T19:33:14ZAKorezinShellcheck 0.7.2In edge repo shellcheck was updated. \
Now it supports `SC30*` options. \
I checked code samples from wiki. \
All available `SC` can be found here https://gist.github.com/eggplants/9fbe03453c3f3fd03295e88def6a1324#file-_shellcheck-md.
I...In edge repo shellcheck was updated. \
Now it supports `SC30*` options. \
I checked code samples from wiki. \
All available `SC` can be found here https://gist.github.com/eggplants/9fbe03453c3f3fd03295e88def6a1324#file-_shellcheck-md.
I don't know if this work:
- https://github.com/koalaman/shellcheck/wiki/SC3025
Not working with `ash`:
- https://github.com/koalaman/shellcheck/wiki/SC3001
- https://github.com/koalaman/shellcheck/wiki/SC3002
- https://github.com/koalaman/shellcheck/wiki/SC3006
- https://github.com/koalaman/shellcheck/wiki/SC3017
- https://github.com/koalaman/shellcheck/wiki/SC3022
- https://github.com/koalaman/shellcheck/wiki/SC3024
- https://github.com/koalaman/shellcheck/wiki/SC3028
- https://github.com/koalaman/shellcheck/wiki/SC3031
- https://github.com/koalaman/shellcheck/wiki/SC3034
- https://github.com/koalaman/shellcheck/wiki/SC3035
- https://github.com/koalaman/shellcheck/wiki/SC3038
- https://github.com/koalaman/shellcheck/wiki/SC3044
- https://github.com/koalaman/shellcheck/wiki/SC3045
- https://github.com/koalaman/shellcheck/wiki/SC3047
- https://github.com/koalaman/shellcheck/wiki/SC3050
- https://github.com/koalaman/shellcheck/wiki/SC3053
- https://github.com/koalaman/shellcheck/wiki/SC3054
- https://github.com/koalaman/shellcheck/wiki/SC3055
- https://github.com/koalaman/shellcheck/wiki/SC3056
This exceptions could be added:
- https://github.com/koalaman/shellcheck/wiki/SC3003
- https://github.com/koalaman/shellcheck/wiki/SC3012
- https://github.com/koalaman/shellcheck/wiki/SC3013
- https://github.com/koalaman/shellcheck/wiki/SC3014
- https://github.com/koalaman/shellcheck/wiki/SC3018
- https://github.com/koalaman/shellcheck/wiki/SC3019
- https://github.com/koalaman/shellcheck/wiki/SC3020
- https://github.com/koalaman/shellcheck/wiki/SC3021
- https://github.com/koalaman/shellcheck/wiki/SC3023
- https://github.com/koalaman/shellcheck/wiki/SC3026
- https://github.com/koalaman/shellcheck/wiki/SC3037
- https://github.com/koalaman/shellcheck/wiki/SC3039
- https://github.com/koalaman/shellcheck/wiki/SC3043
- https://github.com/koalaman/shellcheck/wiki/SC3046
- https://github.com/koalaman/shellcheck/wiki/SC3048
- https://github.com/koalaman/shellcheck/wiki/SC3049
- https://github.com/koalaman/shellcheck/wiki/SC3057
- https://github.com/koalaman/shellcheck/wiki/SC3060https://gitlab.alpinelinux.org/alpine/infra/docker/apkbuild-lint-tools/-/issues/1License2021-05-27T18:35:05ZAKorezinLicenseWhat is the license for this repo? \
Can I use this code as part of my project?
I'd like to use the sources of this repo in my own container image, \
because I use renovate bot to monitor versions of the packages.
I use AGPLv3+ license...What is the license for this repo? \
Can I use this code as part of my project?
I'd like to use the sources of this repo in my own container image, \
because I use renovate bot to monitor versions of the packages.
I use AGPLv3+ license for [my own project](https://gitlab.com/akontainers/apkbuild-tools).https://gitlab.alpinelinux.org/alpine/infra/docker/gitlab/-/issues/7Use 'bundle config set without' instead of '--without'2021-07-10T19:10:56ZKevin DaudtUse 'bundle config set without' instead of '--without'During setup:
```
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set without 'devel...During setup:
```
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set without 'development test mysql aws
kerberos'`, and stop using this flag
```https://gitlab.alpinelinux.org/alpine/infra/docker/aports-build/-/issues/4docker-engine does not have dependency on ip6tables - iptables rules don't ge...2022-02-15T15:25:17Z[diablo]docker-engine does not have dependency on ip6tables - iptables rules don't get deleted when stopping containerI found that if you start a container and map a port to it, when you stop the container (and even delete it) the IPtables rule remains.
The docker-engine has a dependency upon iptables, but not ip6tables.
When you install ip6tables and...I found that if you start a container and map a port to it, when you stop the container (and even delete it) the IPtables rule remains.
The docker-engine has a dependency upon iptables, but not ip6tables.
When you install ip6tables and restart docker daemon, it works as expected.
You will see when debugging docker daemon the following warning:
WARN[0000] Failed to find ip6tables: exec: "ip6tables": executable file not found in $PATH
But there is no mention of it being referenced when starting or stopping containers.
This fix has been tested three times, and proven to work.https://gitlab.alpinelinux.org/alpine/infra/docker/gitlab/-/issues/6Move /etc/nginx/conf.d/* to /etc/nginx/http.d/*2022-02-26T20:43:54ZKevin DaudtMove /etc/nginx/conf.d/* to /etc/nginx/http.d/*The nginx package [changed](383ba9c0a200ed1f4b11d7db74207526ad90bbe3) the default location for vhosts from conf.d/ to http.d.
We install the vhost config in the [entrypoint](https://gitlab.alpinelinux.org/alpine/infra/docker/gitlab/-/bl...The nginx package [changed](383ba9c0a200ed1f4b11d7db74207526ad90bbe3) the default location for vhosts from conf.d/ to http.d.
We install the vhost config in the [entrypoint](https://gitlab.alpinelinux.org/alpine/infra/docker/gitlab/-/blob/13.7-stable/overlay/usr/local/bin/entrypoint.sh#L48)https://gitlab.alpinelinux.org/alpine/infra/docker/alpine-gitlab-ci/-/issues/1CI does not fail on shell syntax errors in APKBUILDs2022-07-23T04:49:27ZNatanael CopaCI does not fail on shell syntax errors in APKBUILDsthe CI gives success without building anything if one of the modified APKBUILDs has invalid shell syntax.
Something like this should fix it:
```diff
diff --git a/overlay/usr/local/bin/build.sh b/overlay/usr/local/bin/build.sh
index 378a...the CI gives success without building anything if one of the modified APKBUILDs has invalid shell syntax.
Something like this should fix it:
```diff
diff --git a/overlay/usr/local/bin/build.sh b/overlay/usr/local/bin/build.sh
index 378a2d5..ea69e23 100755
--- a/overlay/usr/local/bin/build.sh
+++ b/overlay/usr/local/bin/build.sh
@@ -103,6 +103,11 @@ changed_aports() {
aports=$(git diff --name-only --diff-filter=ACMR --relative="$repo" \
"$BASEBRANCH"...HEAD -- "*/APKBUILD" | xargs -I% dirname %)
+
+ for aports in $aports; do
+ ( cd $repo/$aport && . ./APKBUILD) || die "Failed to parse $aport"
+ done
+
# $aports should remain unquoted
# shellcheck disable=2086
ap builddirs -d "$APORTSDIR/$repo" $aports 2>/dev/null | xargs -I% basename % | xargs
```Kevin DaudtKevin Daudt