検索

一些有趣且实用的 Docker 项目推荐,涵盖开发工具、自托管服务、娱乐应用等,适合不同场景的需求
### 1. 开发 & 效率工具
- Code-Server
- 描述:将 VS Code 搬到浏览器中,支持远程开发。
- 镜像:codercom/code-server - 特点:支持插件、终端和多语言开发,适合云端编程。 - 项目地址:https://github.com/coder/code-server

- Jupyter Notebook
- 描述:交互式数据科学和机器学习开发环境。
- 镜像:jupyter/datascience-notebook
- 特点:支持 Python、R 和 Julia,适合数据分析。

- Portainer
- 描述:图形化管理 Docker 容器的工具。
- 镜像:portainer/portainer-ce - 特点:简化容器、镜像和卷的管理。 - 项目地址:https://github.com/portainer/portainer

---

### 2. 自托管服务
- Nextcloud
- 描述:私有云盘,替代 Google Drive/Dropbox。
- 镜像:nextcloud - 特点:支持文件同步、日历、笔记和协作。 - 项目地址:https://github.com/nextcloud/docker

- Home Assistant
- 描述:智能家居自动化平台。
- 镜像:homeassistant/home-assistant
- 特点:支持 1000+ 种设备集成,本地化控制。

- Bitwarden
- 描述:开源密码管理器(自托管版)。
- 镜像:vaultwarden/server(轻量版)
- 特点:支持跨设备同步,安全性高。

---

### 3. 媒体 & 娱乐
- Plex/Jellyfin
- 描述:媒体服务器,管理本地电影/音乐库。
- 镜像:plexinc/pms-docker 或 jellyfin/jellyfin
- 特点:自动刮削元数据,支持多端播放。

- Spotifyd
- 描述:Spotify 的轻量级客户端(命令行)。
- 镜像:ggogel/spotifyd-docker
- 适合:在服务器后台播放音乐。

- Minecraft Server
- 描述:快速部署 Minecraft 服务器。
- 镜像:itzg/minecraft-server
- 特点:支持 Mod 和插件,一键开服。

---

### 4. 网络 & 安全
- Nginx Proxy Manager
- 描述:图形化 Nginx 反向代理工具。
- 镜像:jc21/nginx-proxy-manager
- 特点:轻松配置 SSL 证书和域名转发。

- AdGuard Home
- 描述:去广告和隐私保护的 DNS 服务器。
- 镜像:adguard/adguardhome
- 特点:屏蔽广告、跟踪器,支持家长控制。

- WireGuard
- 描述:轻量级 VPN 服务。
- 镜像:linuxserver/wireguard
- 适合:安全远程访问家庭网络。

---

### 5. 有趣的小工具
- ASCII Movie
- 描述:将电影实时转换为 ASCII 艺术播放。
- 镜像:ghcr.io/benjamimgois/go-ascii-movie
- 玩法:docker run -it --rm ghcr.io/benjamimgois/go-ascii-movie --movie=THE_MATRIX

- Cow Say
- 描述:让牛牛说出你的话(经典 Linux 小工具)。
- 镜像:ubuntu + apt-get install cowsay
- 示例:echo "Hello Docker" | cowsay

- Doom in Docker
- 描述:在容器里运行经典游戏《DOOM》。
- 镜像:jamesnetherton/docker-doom
- 启动:docker run -it --rm -e DISPLAY=$DISPLAY jamesnetherton/docker-doom

---

### 如何运行?
以 Portainer 为例:
bash
docker run -d -p 9000:9000 --name portainer \
  -v /var/run/docker.sock:/var/run/docker.sock \
  portainer/portainer-ce

访问 http://localhost:9000 即可管理 Docker。 --- 这些项目覆盖了从生产力到娱乐的多种场景,你可以根据兴趣选择尝试! #docker #docker
返信 0 · Renote 0
这是一个简洁的 Docker Compose 常用命令 🐳 Docker Compose 快捷命令 🚀 #docker #compose #devops

🔹 启动服务: docker-compose up -d
🔹 停止服务: docker-compose down
🔹 查看日志: docker-compose logs -f
🔹 构建镜像: docker-compose build
🔹 列出容器: docker-compose ps
🔹 执行命令: docker-compose exec [服务名] [命令]
🔹 重启服务: docker-compose restart
🔹 查看进程: docker-compose top

💡 加 -d 后台运行,加 --build 重建镜像

简洁实用!收藏备用⭐️
返信 0 · Renote 0
Do you work with #containers (in #k8s, #docker, or #ECS)?

I'm trying to grasp what % of container users understand a particular point about how containers work.

First, some rough definitions:

The 'host' is the machine where your containers run.

The 'base image', typically a Linux distro, is the operating system of the container, ('FROM:' in the Dockerfile).

With your current understanding, does the host OS and/or distro need to match the base image?

(Excluding Win containers 😉)

投票

  • Yes! Both need to match for containers to work.: 0票
  • No! The host OS is not a concern for the container: 0票
  • I use containers, but I don't know the terms above: 0票
  • I don't use containers, so this is nonsense to me.: 0票
返信 2 · Renote 0

返信元:

But since the project is a container image, most people don't visit a website or repo after they've implemented the container, so there's a pretty solid chance that posting a statement of "Hey, we're going to retire this thing - use this thing instead" isn't going to be seen and current end-users will end up sticking with a stale, unmaintained version that isn't good for them and doesn't reflect well on us, either. It also doesn't seem great to up and delete it and break stuff for others.
返信 1 · Renote 0
This all makes it so much easier to understand why #DockerHub is littered with massive numbers of stale, insecure images and other than maybe making analytics available to everyone, I don't see any obvious way for how #Docker could make this better without being massively disruptive.
返信 1 · Renote 0

返信元:

I have an interesting problem at work. We aren't using one of our #opensource projects any more, but metrics seem to indicate that others are. But since we don't track end users in any way whatsoever, we have no way of reaching out to whoever they are to see how disruptive it would be for us to pull the plug or even if it's used within our own org! It's not much overhead to keep going at this point, but it's not zero.
返信 1 · Renote 0
One interesting point here is that #DockerHub doesn't give you pull analytics with regular paid tiers (there are two special programs that get it). You can query current amount of pulls with an API call, but if you haven't been doing that all along because you didn't know you needed that, then you don't get that info, so I can see it has a high number of pulls and the last time it was pulled, but I don't know how many unique IPs or regularity. #Docker #opensource
返信 1 · Renote 0
#OxiTraffic, a self-hosted, simple and privacy respecting website traffic tracker 🌐 ➡️ Demo: https://oxitraffic.mo8it.com I just published version 0.6 with a #Docker image! 📦️ (You don't have to use Docker though) Do you have a #blog? I can host it for you if you want to test it with your website :blobcatheart: Of course, it is written in #Rust 🦀 Check out the README, I spent a lot of time on it 😇 https://codeberg.org/mo8it/oxitraffic Boost? 🔃🥰 #SelfHosted #IndieWeb #FOSS #Analytics #Traffic #RustLang #Axum
  • b4434e86151eb9b0.png
返信 0 · Renote 0