The LinuxServer.io team brings you another container release featuring :-
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- Podcast - on hiatus. Coming back soon (late 2018).
- Open Collective - please consider helping us by either donating or contributing to our budget
Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling linuxserver/grocy should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
|---|---|
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
Here are some example snippets to help you get started creating a container.
docker create \
--name=grocy \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=<your timezone, eg Europe/London> \
-p 9283:80 \
-v <path to data>:/config \
--restart unless-stopped \
zebardy/barcodebuddy
Compatible with docker-compose v2 schemas.
---
version: "2"
services:
grocy:
image: zebardy/barcodebuddy
container_name: barcodebuddy
environment:
- PUID=1000
- PGID=1000
- TZ=<your timezone, eg Europe/London>
volumes:
- <path to data>:/config
ports:
- 9283:80
restart: unless-stopped
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 80 |
will map the container's port 80 to port 9283 on the host |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=<your timezone, eg Europe/London> |
for specifying your timezone |
-v /config |
this will store any uploaded data on the docker host |
When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id user as below:
$ id username
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
Grocy is simple to get running. Configure the container with the above instructions, start it, and you can then access it by visiting http://your.ip:9283 - once the page loads, you can log in with the default username and password of admin / admin
- Shell access whilst the container is running:
docker exec -it grocy /bin/bash - To monitor the logs of the container in realtime:
docker logs -f barcodebuddy - container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' barcodebuddy
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' zebardy/barcodebuddy
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
- Update the image:
docker pull zebardy/barcodebuddy - Stop the running container:
docker stop barcodebuddy - Delete the container:
docker rm barcodebuddy - Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - Start the new container:
docker start barcodebuddy - You can also remove the old dangling images:
docker image prune
- Update all images:
docker-compose pull- or update a single image:
docker-compose pull barcodebuddy
- or update a single image:
- Let compose update all containers as necessary:
docker-compose up -d- or update a single container:
docker-compose up -d barcodebuddy
- or update a single container:
- You can also remove the old dangling images:
docker image prune
- Pull the latest image at its tag and replace it with the same env variables in one run:
docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ containrrr/watchtower \ --run-once barcodebuddy
Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
- You can also remove the old dangling images:
docker image prune
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/zebardy/docker-barcodebuddy.git
cd docker-barcodebuddy
docker build \
--no-cache \
--pull \
-t zebardy/barcodebuddy:latest .
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static:register --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.