[](https://microbadger.com/images/linuxserver/grocy "Get your own version badge on microbadger.com")
[](https://microbadger.com/images/linuxserver/grocy "Get your own version badge on microbadger.com")
[Grocy](https://github.com/grocy/grocy) is an ERP system for your kitchen! Cut down on food waste, and manage your chores with this brilliant utulity.
Keep track of your purchaes, 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](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).
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 | arm32v6-latest |
## Usage
Here are some example snippets to help you get started creating a container from this image.
### docker
```
docker create \
--name=grocy \
-e PUID=1001 \
-e PGID=1001 \
-e TZ=<yourtimezone,egEurope/London> \
-p 9283:80 \
-v <pathtodata>:/config \
--restart unless-stopped \
linuxserver/grocy
```
### docker-compose
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2"
services:
grocy:
image: linuxserver/grocy
container_name: grocy
environment:
- PUID=1001
- PGID=1001
- TZ=<yourtimezone,egEurope/London>
volumes:
-<pathtodata>:/config
ports:
- 9283:80
mem_limit: 4096m
restart: unless-stopped
```
## 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=1001` | for UserID - see below for explanation |
| `PGID=1001` | for GroupID - see below for explanation |
| `TZ=<your timezone, eg Europe/London>` | for specifying your timezone |
### Volume Mappings (`-v`)
| Volume | Function |
| :----: | --- |
| `/config` | this will store any uploaded data on the docker host |
## 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=1001` and `PGID=1001`, to find yours use `id user` as below:
