Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Docker compose files on EXAMPLES.md are out of date

未关闭 适合新手
  • 哪里不对？
#730 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
半天
新手友好度
78/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
冷清
技术栈
docker-compose
领域
documentation

调研方向

更新 EXAMPLES.md 中的 Docker Compose 示例，先从 Issue 中链接的 standalone 示例开始，然后检查其他 Compose 代码片段是否存在相同的过时设置。确认这些示例包含必需的 Splunk 条款接受和当前的 Compose 语法，使用清晰的服务名称，并提供可正常工作的本地启动路径。

由索引模型根据 Issue 内容生成。

描述

Heya! I was happy to find an easy way to throw up a local splunk instance via the examples page - thanks.

However, if you use the compose file as is:

version: "3.6"

services:
  so1:
    image: ${SPLUNK_IMAGE:-splunk/splunk:latest}
    container_name: so1
    environment:
      - SPLUNK_START_ARGS=--accept-license
      - SPLUNK_PASSWORD
    ports:
      - 8000:8000

There's a couple issues:

  • most importantly you need to add - SPLUNK_GENERAL_TERMS=--accept-sgt-current-at-splunk-com or else it won't start. Thank you for the very helpful error though!! (so1 | For example: docker run -e SPLUNK_GENERAL_TERMS=--accept-sgt-current-at-splunk-com -e SPLUNK_START_ARGS=--accept-license -e SPLUNK_PASSWORD splunk/splunk). This causes it fatally stop so should be fixed
  • you don't need container_name: so1 - it will use the service name above
  • i suggest renaming so1 to be splunk . I know there's lots more uses of this service name in the example doc, but so1 isn't useful when you do docker ps - especially if you have a couple dozen containers running like i do. Later on you can even rename uf1 to splunk-forwarder. We've got the power to have nice names ...yes!!
  • version: "3.6" can be removed - docker even complains ``version is obsolete, it will be ignored, please remove it to avoid potential confusion
  • make it a happy path and just put a janky default password in there. If you want to get fancy, you can use an .env file that has a random password in it like these fine docs here do - one copy and paste your secure!

Here's what I ended up with that worked:

services:
  splunk:
    image: ${SPLUNK_IMAGE:-splunk/splunk:latest}
    environment:
      - SPLUNK_START_ARGS=--accept-license
      - SPLUNK_PASSWORD=${SPLUNK_PASSWORD:-password123}
      - SPLUNK_GENERAL_TERMS=--accept-sgt-current-at-splunk-com
    ports:
      - 8000:8000

sprinkle these changes through out the whole doc and keep up the good work!

主要语言
Python
星标
551
派生
279
平均合并
23 小时 25 分钟
30 天内合并 PR
1

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

splunk/docker-splunk 的其他 Issue

查看 splunk/docker-splunk 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。