Skip to content

Commit

Permalink
feat: deleted travis CI and added github action support
Browse files Browse the repository at this point in the history
* feat: deleted travis CI and added github action to test pull request

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* fix(ci): fixed passing build-args

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* fix: fixed CI file

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* fix: fixed artifact conflict

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* chore: reduced matrix value for fast fail

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* Revert "chore: reduced matrix value for fast fail"

This reverts commit 163f4a4.

* chore: limited platform support to amd64 & arm64 for now

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* fix: fixed merge job

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* feat(ci): limit some steps to non pr event

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* fix(ci): fixed docker push error

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* feat: add support for alpine-3.21 and removed support for alpine-3.17

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

* feat: updated README

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>

---------

Signed-off-by: MD Maksudur Rahman Khan <[email protected]>
  • Loading branch information
maateen authored Jan 7, 2025
1 parent de7c3ec commit 841c00e
Show file tree
Hide file tree
Showing 5 changed files with 168 additions and 138 deletions.
116 changes: 116 additions & 0 deletions .github/workflows/docker-push.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,116 @@
name: Docker Image Push

on:
push:
branches: [main]
pull_request:
branches: [main]

jobs:
build:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
alpine_version: ["3.18", "3.19", "3.20", "3.21"]
beanstalkd_version: ["v1.8", "v1.9", "v1.10", "v1.11", "v1.12", "v1.13"]
platform: ["linux/amd64", "linux/arm64"]
steps:
- name: Checkout repository
uses: actions/checkout@v4

- name: Prepare
run: |
platform=${{ matrix.platform }}
echo "PLATFORM_PAIR=${platform//\//-}" >> $GITHUB_ENV
- name: Set up QEMU
uses: docker/setup-qemu-action@v3

- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3

- name: Docker meta
id: meta
uses: docker/metadata-action@v5
with:
images: ${{ github.repository }}

- name: Login to Docker Hub
if: github.event_name != 'pull_request'
uses: docker/login-action@v3
with:
username: ${{ github.repository_owner }}
password: ${{ secrets.DOCKERHUB_TOKEN }}

- name: Build and push by digest
id: build
uses: docker/build-push-action@v6
with:
annotations: ${{ steps.meta.outputs.annotations }}
build-args: |
ALPINE_VERSION=${{ matrix.alpine_version }}
BEANSTALKD_VERSION=${{ matrix.beanstalkd_version }}
context: .
labels: ${{ steps.meta.outputs.labels }}
platforms: ${{ matrix.platform }}
outputs: type=image,name=${{ github.repository }},push-by-digest=true,name-canonical=true,push=${{ github.event_name != 'pull_request' }}

- name: Export digest
if: github.event_name != 'pull_request'
run: |
mkdir -p /tmp/digests/${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}
digest="${{ steps.build.outputs.digest }}"
touch "/tmp/digests/${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}/${digest#sha256:}"
- name: Upload digest
if: github.event_name != 'pull_request'
uses: actions/upload-artifact@v4
with:
name: digests-${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}-${{ env.PLATFORM_PAIR }}
path: /tmp/digests/${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}/*
if-no-files-found: error
retention-days: 1

merge:
runs-on: ubuntu-latest
if: github.event_name != 'pull_request'
needs:
- build
strategy:
fail-fast: false
matrix:
alpine_version: ["3.17", "3.18", "3.19", "3.20"]
beanstalkd_version: ["v1.8", "v1.9", "v1.10", "v1.11", "v1.12", "v1.13"]
steps:
- name: Download digests
uses: actions/download-artifact@v4
with:
path: /tmp/digests/${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}
pattern: digests-${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}-*
merge-multiple: true

- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3

- name: Docker meta
id: meta
uses: docker/metadata-action@v5
with:
images: ${{ github.repository }}

- name: Login to Docker Hub
uses: docker/login-action@v3
with:
username: ${{ github.repository_owner }}
password: ${{ secrets.DOCKERHUB_TOKEN }}

- name: Create manifest list and push
working-directory: /tmp/digests/${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}
run: |
docker buildx imagetools create -t ${{ github.repository }}:${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }} \
$(printf '${{ github.repository }}@sha256:%s ' *)
- name: Inspect image
run: |
docker buildx imagetools inspect ${{ github.repository }}:${{ matrix.beanstalkd_version }}-alpine-${{ matrix.alpine_version }}
19 changes: 0 additions & 19 deletions .travis.yml

This file was deleted.

44 changes: 16 additions & 28 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
ARG ALPINE_VERSION=edge
ARG ALPINE_VERSION="latest"

FROM alpine:${ALPINE_VERSION} AS builder
FROM public.ecr.aws/docker/library/alpine:${ALPINE_VERSION} AS builder

ARG BEANSTALKD_VERSION=master
ARG BEANSTALKD_VERSION="v1.13"

# install dependencies
RUN apk update --quiet --no-cache && \
Expand All @@ -11,11 +11,8 @@ RUN apk update --quiet --no-cache && \
WORKDIR /build

# build from source
RUN git clone https://github.com/kr/beanstalkd.git && \
RUN git clone --depth 1 --branch $BEANSTALKD_VERSION https://github.com/beanstalkd/beanstalkd.git && \
cd beanstalkd && \
if [ "${BEANSTALKD_VERSION}" != "master" ] ; then \
git checkout tags/v${BEANSTALKD_VERSION}; \
fi && \
if [ -f "sd-daemon.c" ]; then \
sed -i 's,sys/fcntl.h,fcntl.h,' sd-daemon.c; \
fi && \
Expand All @@ -25,27 +22,18 @@ RUN git clone https://github.com/kr/beanstalkd.git && \
###############
# Final Build #
###############
ARG ALPINE_VERSION=edge

FROM alpine:${ALPINE_VERSION}

ARG BEANSTALKD_VERSION=master

ARG BUILD_DATE
ARG VCS_REF
LABEL version=$BEANSTALKD_VERSION \
maintainer="Maksudur Rahman Maateen <[email protected]>" \
org.label-schema.build-date=$BUILD_DATE \
org.label-schema.name="maateen/docker-beanstalkd" \
org.label-schema.description="A Docker container for beanstalkd, a simple and fast general purpose work queue." \
org.label-schema.url="https://beanstalkd.github.io/" \
org.label-schema.vcs-ref=$VCS_REF \
org.label-schema.vcs-url="https://github.com/maateen/docker-beanstalkd" \
org.label-schema.vendor="Maksudur Rahman Maateen" \
org.label-schema.version=$BEANSTALKD_VERSION \
org.label-schema.schema-version="1.0" \
com.microscaling.docker.dockerfile="/Dockerfile" \
com.microscaling.license="GPL-3.0"
FROM public.ecr.aws/docker/library/alpine:${ALPINE_VERSION}

LABEL org.opencontainers.image.authors="Maksudur Rahman Maateen <[email protected]>"
LABEL org.opencontainers.image.created="${BUILD_DATE}"

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
LABEL org.opencontainers.image.description="A Docker container for beanstalkd, a simple and fast general purpose work queue."
LABEL org.opencontainers.image.documentation="https://github.com/maateen/docker-beanstalkd"
LABEL org.opencontainers.image.licenses="GPL-3.0"
LABEL org.opencontainers.image.source="https://beanstalkd.github.io/"
LABEL org.opencontainers.image.title="maateen/docker-beanstalkd"
LABEL org.opencontainers.image.url="https://github.com/maateen/docker-beanstalkd"
LABEL org.opencontainers.image.vendor="Maksudur Rahman Maateen <[email protected]>"
LABEL org.opencontainers.image.version="${BEANSTALKD_VERSION}"

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/amd64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Check warning on line 36 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/arm64)

Variables should be defined before their use

UndefinedVar: Usage of undefined variable '$BEANSTALKD_VERSION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

ENV PV_DIR /var/cache/beanstalkd

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 38 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
ENV FSYNC_INTERVAL 1000

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.18, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.19, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.10, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.11, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/amd64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.12, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.13, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.20, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.8, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Check warning on line 39 in Dockerfile

View workflow job for this annotation

GitHub Actions / build (3.21, v1.9, linux/arm64)

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Expand Down
90 changes: 36 additions & 54 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,84 +1,66 @@
# docker-beanstalkd

A Docker container for beanstalkd, a simple and fast general purpose work queue.
![Docker Pulls](https://img.shields.io/docker/pulls/maateen/docker-beanstalkd)
![Docker Stars](https://img.shields.io/docker/stars/maateen/docker-beanstalkd)
![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/maateen/docker-beanstalkd/docker-image-push.yml)
![License](https://img.shields.io/github/license/maateen/docker-beanstalkd)

[![Build Status](https://travis-ci.com/maateen/docker-beanstalkd.svg?branch=master)](https://travis-ci.com/maateen/docker-beanstalkd)
[![Docker Cloud Build Status](https://img.shields.io/docker/cloud/build/maateen/docker-beanstalkd)](https://hub.docker.com/r/maateen/docker-beanstalkd/builds)
[![Docker Cloud Automated build](https://img.shields.io/docker/cloud/automated/maateen/docker-beanstalkd)](https://hub.docker.com/r/maateen/docker-beanstalkd/builds)
[![Docker Image Size (tag)](https://img.shields.io/docker/image-size/maateen/docker-beanstalkd/latest)](https://hub.docker.com/repository/docker/maateen/docker-beanstalkd/tags)
[![MicroBadger Layers](https://img.shields.io/microbadger/layers/maateen/docker-beanstalkd)](https://microbadger.com/images/maateen/docker-beanstalkd "Get your own image badge on microbadger.com")
[![](https://images.microbadger.com/badges/license/maateen/docker-beanstalkd.svg)](https://microbadger.com/images/maateen/docker-beanstalkd "Get your own license badge on microbadger.com")
A Docker container for Beanstalkd, a simple and fast general-purpose work queue.

## Quick reference
## Quick Reference

- **Where to file issues**: https://github.com/maateen/docker-beanstalkd/issues
- **Where to get help**: https://github.com/maateen/docker-beanstalkd/issues
- **Image updates**: https://github.com/maateen/docker-beanstalkd/pulls
- **Where to file issues**: [GitHub Issues](https://github.com/maateen/docker-beanstalkd/issues)
- **Where to get help**: [GitHub Issues](https://github.com/maateen/docker-beanstalkd/issues)
- **Image updates**: [GitHub Pull Requests](https://github.com/maateen/docker-beanstalkd/pulls)

## Supported tags
## Supported Tags

- `latest` (regular build, unstable)
- `master-alpine-edge`, `master-alpine-latest`, `master-alpine-3.13`, `master-alpine-3.12`, `master-alpine-3.11`, `master-alpine-3.10`, `master-alpine-3.9` (regular builds, unstable)
- `1.12-alpine-edge`, `1.12-alpine-latest` (**stable**), `1.12-alpine-3.13`, `1.12-alpine-3.12`, `1.12-alpine-3.11`, `1.12-alpine-3.10`, `1.12-alpine-3.9`
- `1.11-alpine-edge`, `1.11-alpine-latest`, `1.11-alpine-3.13`, `1.11-alpine-3.12`, `1.11-alpine-3.11`, `1.11-alpine-3.10`, `1.11-alpine-3.9`
- `1.10-alpine-edge`, `1.10-alpine-latest`, `1.10-alpine-3.13`, `1.10-alpine-3.12`, `1.10-alpine-3.11`, `1.10-alpine-3.10`, `1.10-alpine-3.9`
- `1.9-alpine-edge`, `1.9-alpine-latest`, `1.9-alpine-3.13`, `1.9-alpine-3.12`, `1.9-alpine-3.11`, `1.9-alpine-3.10`, `1.9-alpine-3.9`
- `1.8-alpine-edge`, `1.8-alpine-latest`, `1.8-alpine-3.13`, `1.8-alpine-3.12`, `1.8-alpine-3.11`, `1.8-alpine-3.10`, `1.8-alpine-3.9`
- `v1.13-alpine-3.21`, `v1.13-alpine-3.20`, `v1.13-alpine-3.19`, `v1.13-alpine-3.18`
- `v1.12-alpine-3.21`, `v1.12-alpine-3.20`, `v1.12-alpine-3.19`, `v1.12-alpine-3.18`
- `v1.11-alpine-3.21`, `v1.11-alpine-3.20`, `v1.11-alpine-3.19`, `v1.11-alpine-3.18`
- `v1.10-alpine-3.21`, `v1.10-alpine-3.20`, `v1.10-alpine-3.19`, `v1.10-alpine-3.18`
- `v1.9-alpine-3.21`, `v1.9-alpine-3.20`, `v1.9-alpine-3.19`, `v1.9-alpine-3.18`
- `v1.8-alpine-3.21`, `v1.8-alpine-3.20`, `v1.8-alpine-3.19`, `v1.8-alpine-3.18`

## What is beanstalkd?
These tags represent the supported combinations of Beanstalkd and Alpine Linux versions, providing flexibility for various deployment environments.

It is a simple, fast work queue. Its interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.
## What is Beanstalkd?

For more information and related downloads for beanstalkd, please visit [beanstalkd.github.io](https://beanstalkd.github.io/).
Beanstalkd is a simple, fast work queue. Its interface is generic but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously. For more information and related downloads for Beanstalkd, please visit [beanstalkd.github.io](https://beanstalkd.github.io/).

## How to use this image
## How to Use This Image

### start a beanstalkd instance
### Start a Beanstalkd Instance

```
$ docker run --name some-beanstalkd -d maateen/docker-beanstalkd
```bash
docker run --name some-beanstalkd -d maateen/docker-beanstalkd
```

### start with persistent storage
### Start with Persistent Storage

```
$ docker run --name some-beanstalkd -v $(pwd):/var/cache/beanstalkd -d maateen/docker-beanstalkd
```bash
docker run --name some-beanstalkd -v $(pwd):/var/cache/beanstalkd -d maateen/docker-beanstalkd
```

### exposing external port
### Exposing External Port

```
$ docker run --name some-beanstalkd -d -p 11300:11300 maateen/docker-beanstalkd
```bash
docker run --name some-beanstalkd -d -p 11300:11300 maateen/docker-beanstalkd
```

## Environment Variables

### `PV_DIR`

Use a binlog to keep jobs on persistent storage in directory `PV_DIR`. Upon startup, **beanstalkd** will recover any binlog that is present in `PV_DIR`, then, during normal operation, append new jobs and changes in state to the binlog.

### `FSYNC_INTERVAL`

Call [fsync](https://www.systutorials.com/docs/linux/man/2-fsync/)(2) at most once every `FSYNC_INTERVAL` milliseconds. Larger values for `FSYNC_INTERVAL` reduce disk activity and improve speed at the cost of safety. A power failure could result in the loss of up to `FSYNC_INTERVAL` milliseconds of history.

A `FSYNC_INTERVAL` value of 0 will cause **beanstalkd** to call fsync every time it writes to the binlog.
- **PV_DIR**: Use a binlog to keep jobs on persistent storage in directory PV_DIR. Upon startup, Beanstalkd will recover any binlog that is present in PV_DIR, then, during normal operation, append new jobs and changes in state to the binlog.
- **FSYNC_INTERVAL**: Call `fsync(2)` at most once every FSYNC_INTERVAL milliseconds. Larger values for FSYNC_INTERVAL reduce disk activity and improve speed at the cost of safety. A power failure could result in the loss of up to FSYNC_INTERVAL milliseconds of history. A FSYNC_INTERVAL value of 0 will cause Beanstalkd to call fsync every time it writes to the binlog.

## Image Variants

The `beanstalkd` images come in many flavors, each designed for a specific use case.

### `maateen/docker-beanstalkd:<beanstalkd_version>-alpine-<alpine_version>`

This image is based on the popular [Alpine Linux project](http://alpinelinux.org/), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
The Beanstalkd images are based on [Alpine Linux](https://alpinelinux.org/) and are available for multiple architectures:
- linux/amd64
- linux/arm64

### Tagging confusion?

- `master` means the [master](https://github.com/beanstalkd/beanstalkd/tree/master) branch of **beanstalkd** project. New changes are always coming here, not so much stable.
- `alpine-edge` means current [development tree](https://wiki.alpinelinux.org/wiki/Aports_tree "Aports tree") of Alpine Linux. It consists of a APK repository called "edge" and contains the latest build of all available Alpine Linux packages. Those packages are updated on a regular basis. *"edge" is under constant development so be careful using it in production. It is possible that bugs in "edge" could cause data loss or could break your system.*
- `alpine-latest` means the [latest stable version](https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases) of Alpine Linux.
Each variant is built with different Alpine Linux versions (3.18 to 3.21) and Beanstalkd versions (1.8 to 1.13), allowing you to choose the most appropriate combination for your needs.

## License

View [license information](https://github.com/beanstalkd/beanstalkd/blob/master/LICENSE) for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
View [license information](https://github.com/maateen/docker-beanstalkd/blob/main/LICENSE) for the software contained in this image. As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc., from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
37 changes: 0 additions & 37 deletions buildnpush.sh

This file was deleted.

0 comments on commit 841c00e

Please sign in to comment.