linuxserver/grocy

​​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​ ​
​​
​Grocy is an ERP system for your kitchen! Cut down on food waste, and manage your chores with this brilliant utility.
Keep track of your purchases, how much food you are wasting, what chores need doing and what batteries need charging with this proudly Open Source tool
For more information on grocy visit their website and check it out: https://grocy.info​
Supported Architectures
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 lscr.io/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
Application Setup
Grocy is simple to get running. Configure the container with instructions below, 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
Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)
1
---
2
version: "2.1"
3
services:
4
  grocy:
5
    image: lscr.io/linuxserver/grocy
6
    container_name: grocy
7
    environment:
8
      - PUID=1000
9
      - PGID=1000
10
      - TZ=Europe/London
11
    volumes:
12
      - /path/to/data:/config
13
    ports:
14
      - 9283:80
15
    restart: unless-stopped
Copied!
docker cli (click here for more info)
1
docker run -d \
2
  --name=grocy \
3
  -e PUID=1000 \
4
  -e PGID=1000 \
5
  -e TZ=Europe/London \
6
  -p 9283:80 \
7
  -v /path/to/data:/config \
8
  --restart unless-stopped \
9
  lscr.io/linuxserver/grocy
Copied!
Parameters
Docker 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.
Ports (-p)
Parameter
Function
80
will map the container's port 80 to port 9283 on the host
Environment Variables (-e)
Env
Function
PUID=1000
for UserID - see below for explanation
PGID=1000
for GroupID - see below for explanation
TZ=Europe/London
for specifying your timezone
Volume Mappings (-v)
Volume
Function
/config
this will store any uploaded data on the docker host
Miscellaneous Options
Parameter
Function
Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
1
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Copied!
Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.
Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
User / Group Identifiers
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:
1
  $ id username
2
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
Copied!
Docker Mods
​​
​ ​
​​
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Support Info
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 grocy
Container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' grocy
Image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/grocy
Versions
22.08.21: - Rebase to Alpine 3.14 and PHP 8.
25.07.21: - Add 'int','json' and 'zlib' PHP extensions.
10.05.21: - Reduce image size.
08.04.21: - Update docs to reflect jenkins builder changes.
17.02.21: - Rebasing to alpine 3.13.
26.01.21: - Add 'ldap' PHP extension.
22.12.20: - Add 'ctype' PHP extension.
01.06.20: - Rebasing to alpine 3.12.
19.12.19: - Rebasing to alpine 3.11.
22.09.19: - Add 'gd' PHP extension.
28.06.19: - Rebasing to alpine 3.10.
23.03.19: - Switching to new Base images, shift to arm32v7 tag.
22.02.19: - Rebasing to alpine 3.9.
27.12.18: - Initial Release.