ibeam Docker 镜像下载 - 轩辕镜像
ibeam 镜像详细信息和使用指南
ibeam 镜像标签列表和版本信息
ibeam 镜像拉取命令和加速下载
ibeam 镜像使用说明和配置指南
Docker 镜像加速服务 - 轩辕镜像平台
国内开发者首选的 Docker 镜像加速平台
极速拉取 Docker 镜像服务
相关 Docker 镜像推荐
热门 Docker 镜像下载
ibeam 镜像详细信息
ibeam 镜像标签列表
ibeam 镜像使用说明
ibeam 镜像拉取命令
Docker 镜像加速服务
轩辕镜像平台优势
镜像下载指南
相关 Docker 镜像推荐
ibeam 镜像详细说明
ibeam 使用指南
ibeam 配置说明
ibeam 官方文档
This library is currently being beta-tested. See something that's broken? Did we get something wrong? Create an issue and let us know!
IBeam on GitHub
IBeam is an authentication and maintenance tool used for the Interactive Brokers Client Portal Web API Gateway.
Features:
-
Facilitates continuous headless run of the Gateway.
-
No physical display required - virtual display buffer can be used instead.
-
No interaction from the user required - automated injection of IBKR credentials into the authentication page used by the Gateway.
-
TLS certificate support - you can provide your own certificates.
-
Containerised using Docker - it's a plug and play image, although IBeam can be used as standalone too.
-
Not so secure - Yupp, you'll need to store the credentials somewhere, and that's a risk. Read more about it in Security.
Documentation:
- Setup
- Advanced
- More
Quick start
Installation
Docker Image (Recommended):
poshdocker pull voyz/ibeam
Standalone:
poshpip install ibeam
Startup
Docker Image (Recommended):
poshdocker run --env IBEAM_ACCOUNT=your_account123 --env IBEAM_PASSWORD=your_password123 -p 5000:5000 voyz/ibeam
docker-compose:
Create a docker-compose.yml file with the following contents:
yamlversion: "2.1" services: ibeam: image: voyz/ibeam container_name: ibeam env_file: - env.list ports: - 5000:5000 network_mode: bridge # Required due to clientportal.gw IP whitelist restart: 'no' # Prevents IBEAM_MAX_FAILED_AUTH from being exceeded
Create an env.list file in the same directory with the following contents:
poshIBEAM_ACCOUNT=your_account123 IBEAM_PASSWORD=your_password123
Run the following command:
poshdocker-compose up -d
Standalone:
poshpython ibeam_starter.py
Once started, verify the Gateway is running by calling:
poshcurl -X GET "https://localhost:5000/v1/api/one/user" -k
Read more in Installation and Startup.
How does IBeam work?
In a standard startup IBeam performs the following:
- Copy inputs from the Inputs Directory to Gateway's
rootfolder (if provided). - Ensure the Gateway is running by calling the tickle endpoint. If not:
- Start the Gateway in a new shell.
- Ensure the Gateway has an active session that is authenticated by calling the tickle endpoint. If not:
- Create a new Chrome Driver instance using
selenium. - Start a virtual display using
pyvirtualdisplay. - Access the Gateway's authentication website.
- Once loaded, input username and password and submit the form.
- Wait for the login confirmation and quit the website.
- Verify once again if Gateway is running and authenticated.
- Create a new Chrome Driver instance using
- Start the maintenance, attempting to keep the Gateway alive and authenticated. Will repeat login if finds no active session or the session is not authenticated.
Security
Please feel free to suggest improvements to the security risks currently present in IBeam and the Gateway by opening an issue on GitHub.
Credentials
The Gateway requires credentials to be provided on a regular basis. The only way to avoid manually having to input them every time is to store the credentials somewhere. This alone is a security risk.
Currently, IBeam expects the credentials to be available as environment variables during runtime. Whether running IBeam in a container or directly on a host machine, an unwanted user may gain access to these credentials. If your setup is exposed to a risk of someone unauthorised reading the credentials, you may want to look for other solutions than IBeam or use the Gateway standalone and authenticate manually each time.
We considered providing a possibility to read the credentials from an external credentials store, such as GCP Secrets, yet that would require some authentication credentials too, which brings back the same issue it was to solve.
Roadmap
IBeam was built by traders just like you. We made it open source in order to collectively build a reliable solution. If you enjoy using IBeam, we encourage you to attempt implementing one of the following tasks:
Include TLS certificates.Two Factor Authentictaion.- Remove necessity to install Java.
Remove necessity to install Chrome or find a lighter replacement.- Add usage examples.
- Full test coverage.
- Improve the security issues.
- Find a lighter replacement to using Chromium
Read the CONTRIBUTING guideline to get started.
Licence
See LICENSE
Disclaimer
IBeam is not built, maintained, or endorsed by the Interactive Brokers.
Use at own discretion. IBeam and its authors give no guarantee of uninterrupted run of and access to the Interactive Brokers Client Portal Web API Gateway. You should prepare for breaks in connectivity to IBKR servers and should not depend on continuous uninterrupted run of the Gateway. IBeam requires your private credentials to be exposed to a security risk, potentially resulting in, although not limited to interruptions, loss of capital and loss of access to your account. To partially reduce the potential risk use Paper Account credentials.
IBeam is provided on an AS IS and AS AVAILABLE basis without any representation or endorsement made and without warranty of any kind whether express or implied, including but not limited to the implied warranties of satisfactory quality, fitness for a particular purpose, non-infringement, compatibility, security and accuracy. To the extent permitted by law, IBeam's authors will not be liable for any indirect or consequential loss or damage whatever (including without limitation loss of business, opportunity, data, profits) arising out of or in connection with the use of IBeam. IBeam's authors make no warranty that the functionality of IBeam will be uninterrupted or error free, that defects will be corrected or that IBeam or the server that makes it available are free of viruses or anything else which may be harmful or destructive.
Built by Voy
Hi! Thanks for checking out and using this library. If you are interested in discussing your project, require mentorship, consider hiring me, or just wanna chat - I'm happy to talk.
You can send me an email to get in touch: ***
Or if you'd just want to give something back, I've got a Buy Me A Coffee account:
Thanks and have an awesome day 👋
用户好评
来自真实用户的反馈,见证轩辕镜像的优质服务
常见问题
免费版仅支持 Docker Hub 加速,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
免费版仅支持 docker.io;专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
轩辕镜像下载加速使用手册
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
登录仓库拉取
通过 Docker 登录认证访问私有仓库
Linux
在 Linux 系统配置镜像加速服务
Windows/Mac
在 Docker Desktop 配置镜像加速
Docker Compose
Docker Compose 项目配置加速
K8s Containerd
Kubernetes 集群配置 Containerd
宝塔面板
在宝塔面板一键配置镜像加速
群晖
Synology 群晖 NAS 配置加速
飞牛
飞牛 fnOS 系统配置镜像加速
极空间
极空间 NAS 系统配置加速服务
爱快路由
爱快 iKuai 路由系统配置加速
绿联
绿联 NAS 系统配置镜像加速
威联通
QNAP 威联通 NAS 配置加速
Podman
Podman 容器引擎配置加速
Singularity/Apptainer
HPC 科学计算容器配置加速
其他仓库配置
ghcr、Quay、nvcr 等镜像仓库
专属域名拉取
无需登录使用专属域名加速
需要其他帮助?请查看我们的 常见问题 或 官方QQ群: 13763429