LinuxServer提供的grocy镜像,用于部署开源家庭库存管理系统,支持食品库存跟踪、购物清单管理及食谱规划,轻量高效且易于集成。
The https://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:
- https://blog.linuxserver.io - all the things you can do with our containers including How-To guides, opinions and much more!
- https://linuxserver.io/*** - realtime support / chat with the community and the team.
- https://discourse.linuxserver.io - post on our community forum.
- https://github.com/linuxserver - view the source for all of our repositories.
- https://opencollective.com/linuxserver - please *** helping us by either donating or contributing to our budget
https://github.com/linuxserver/docker-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 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: [***]
Supported Architectures
We utilise the docker manifest for multi-platform awareness. More information is available from docker https://distribution.github.io/distribution/spec/manifest-v2-2/#manifest-list and our announcement https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/.
Simply pulling lscr.io/linuxserver/grocy:latest 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 | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ✅ | arm64v8-<version tag> |
Application Setup
Grocy is simple to get running. Configure the container with instructions below, start it, and you can then access it by visiting [***] - once the page loads, you can log in with the default username and password of admin / admin
Upgrading
Following a container upgrade ensure that you visit the root (/) route (click on the logo in the left upper edge) in order to run any necessary database migrations. See https://github.com/grocy/grocy#how-to-update for more details.
Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
[!NOTE] Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.
docker-compose (recommended, https://docs.linuxserver.io/general/docker-compose)
yaml--- services: grocy: image: lscr.io/linuxserver/grocy:latest container_name: grocy environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC volumes: - /path/to/grocy/config:/config ports: - 9283:80 restart: unless-stopped
docker cli (https://docs.docker.com/engine/reference/commandline/cli/)
bashdocker run -d \ --name=grocy \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Etc/UTC \ -p 9283:80 \ -v /path/to/grocy/config:/config \ --restart unless-stopped \ lscr.io/linuxserver/grocy:latest
Parameters
Containers 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 9283: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=Etc/UTC | specify a timezone to use, see this list. |
-v /config | Persistent config files |
Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
bash-e FILE__MYVAR=/run/secrets/mysecretvariable
Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable 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 your_user as below:
bashid your_user
Example output:
textuid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
Docker Mods
We publish various https://github.com/linuxserver/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:
bashdocker exec -it grocy /bin/bash -
To monitor the logs of the container in realtime:
bashdocker logs -f grocy -
Container version number:
bashdocker inspect -f '{{ index .Config.Labels "build_version" }}' grocy -
Image version number:
bashdocker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/grocy:latest
Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), 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:
Via Docker Compose
-
Update images:
-
All images:
bashdocker-compose pull -
Single image:
bashdocker-compose pull grocy
-
-
Update containers:
-
All containers:
bashdocker-compose up -d -
Single container:
bashdocker-compose up -d grocy
-
-
You can also remove the old dangling images:
bashdocker image prune
Via Docker Run
-
Update the image:
bashdocker pull lscr.io/linuxserver/grocy:latest -
Stop the running container:
bashdocker stop grocy -
Delete the container:
bashdocker rm grocy -
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) -
You can also remove the old dangling images:
bashdocker image prune
Image Update Notifications - Diun (Docker Image Update Notifier)
[!TIP] We recommend https://crazymax.dev/diun/ for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:
bashgit clone https://github.com/linuxserver/docker-grocy.git cd docker-grocy docker build \ --no-cache \ --pull \ -t lscr.io/linuxserver/grocy:latest .
The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
bashdocker run --rm --privileged lscr.io/linuxserver/qemu-static --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Versions
- 07.03.26: - Rebase to Alpine 3.23 with php 8.5.
- 02.05.24: - Rebase to Alpine 3.21. Add php-opcache package.
- 30.06.24: - Rebase to Alpine 3.20. Existing users should update their nginx confs to avoid http2 deprecation warnings.
- 29.03.24: - Add
clear_env = notophp-fpmto pass on environment variables to workers threads - 06.03.24: - Existing users should update: site-confs/default.conf - Cleanup default site conf.
- 06.03.24: - Rebase to Alpine 3.19 with php 8.3.
- 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
- 13.04.23: - Move ssl.conf include to default.conf.
- 19.01.23: - Rebase to alpine 3.17 with php8.1.
- 20.08.22: - Rebasing to alpine 3.15 with php8. Restructure nginx configs (https://info.linuxserver.io/issues/2022-08-20-nginx-base).
- 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.
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
DockerHub 原生拉取命令
用户好评
来自真实用户的反馈,见证轩辕镜像的优质服务