containers / containers/toolbox

SSH X11 forwarding not working in toolbox.

Open
#1,343 2 comments 1 reaction 0 assignees View on GitHub
1. Bug
Dominant language
Go
Stars
3.5k
Forks
262
Avg merge
3d 1h
Merged PRs (30d)
1

Description

**Describe the bug**
I have a Silverblue machine I want to access via SSH and start X11 applications on for local display.

X11 forwarding works fine in the main shell, but when I `toolbox enter` it doesn't work.

**Steps how to reproduce the behaviour**
1. Log in via SSH to a Sliverblue machine with X11 forwarding enabled.
2. Run `firefox`. Observe that the Firefox window appears on the local machine.
3. Do `toolbox enter`
4. `sudo dnf install firefox` (to get it installed in the toolbox)
5. Run `firefox`.
6. Get
`PuTTY X11 proxy: Unsupported authorisation protocol`
`Error: cannot open display: localhost:10.0`

**Expected behaviour**
`firefox` and other X11 applications should work inside the toolbox in the same way that the work outside.

**Actual behaviour**
`PuTTY X11 proxy: Unsupported authorisation protocol`
`Error: cannot open display: localhost:10.0`

**Output of `toolbox --version` (v0.0.90+)**
`toolbox version 0.0.99.4`

**Toolbox package info (`rpm -q toolbox`)**
`toolbox-0.0.99.4-1.fc38.x86_64`

**Output of `podman version`**
e.g.,
```
Client: Podman Engine
Version: 4.5.1
API Version: 4.5.1
Go Version: go1.20.4
Built: Fri May 26 18:58:48 2023
OS/Arch: linux/amd64
```

**Podman package info (`rpm -q podman`)**
`podman-4.5.1-1.fc38.x86_64`

**Info about your OS**
Fedora Silverblue 38

**Additional context**
Might be related to https://github.com/containers/toolbox/issues/1290

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the SSH X11 forwarding flow outside and inside `toolbox enter`, then inspect the entry point that starts the toolbox and how X11 authorization is passed into it. Done means Firefox and other X11 applications launched inside the toolbox display on the SSH client's local machine without the reported authorization or display errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
cli, desktop-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.