Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

visual glitch when running docker command #10719

Open
sean1604 opened this issue Feb 19, 2025 · 0 comments
Open

visual glitch when running docker command #10719

sean1604 opened this issue Feb 19, 2025 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers

Comments

@sean1604
Copy link

Type: Bug

When running a docker compose up command multiple "phatom" entries appear. I believed it to be an issue with my linux lxc container or an issue within the code however today I have confirmed the issue is not present whilst using mobaxterm whilst ssh'd in to the same server.

It doesn't seem to happen all the time however an example of what can be

shown on the terminal can be found here:

https://pastebin.com/BYqvx61U

Image

Extension version: 0.117.1
VS Code version: Code 1.97.2 (e54c774e0add60467559eb0d1e229c6452cf8447, 2025-02-12T23:20:35.343Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 6.8.12-8-pve

System Info
Item Value
CPUs Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 x 3310)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.98GB (0.36GB free)
Process Argv --crash-reporter-id 3f6a2671-8a6d-4a59-9658-e0121866d6da
Screen Reader no
VM 0%
Item Value
Remote SSH: 192.168.1.240
OS Linux x64 6.8.12-8-pve
CPUs Intel(R) Core(TM) i5-14600K (6 x 5300)
Memory (System) 16.00GB (14.65GB free)
VM 0%
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31238123
hdaa2157:31222309
copilot_t_ci:31222730
jda6j935:31233686
copilothoveroff:31240707

@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Feb 19, 2025
@chrmarti chrmarti added the bug Issue identified by VS Code Team member as probable bug label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

2 participants