haskell / haskell/docker-haskell

Can't start because X11 isn't present?

Open
#138 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Dockerfile
Stars
71
Forks
36
Avg merge
17h 26m
Merged PRs (30d)
2

Description

I'm trying to get an interactive session with GHC on my virtual machine hosting FreeBSD 14.1. I'm using `sysutils/podman-suite` from FreeBSD's ports to run OCI containers, and the Haskell images is the first to cause any problem. There's no problem running Debian slim, so there's something in the Dockerfile here that's causing the problem.

The following terminal (manual) transcript is from my FreeBSD VM running on Hyper-V
```
# podman run -it --rm --os=linux docker.io/haskell:9.10-slim-bullseye
[Usual blob fetching]
Error: copying system image from manifest list: writing blob: adding layer with blob "sha256:79c0c33664058[...]": ApplyLayer stdout: stderr: faccessat /etc/X11: invalid argument exit status 1

# podman run -it --rm --os=linux docker.io/debian:bullseye-slim /bin/echo "Hello from Debian"
[Usual blob fetching]
Hello from Debian
```

And there's no problem getting GHCi up and running on my NixOS 24.04 system in a container

```
# podman run -it --rm docker.io/haskell:9.10-slim-bullseye
[Blobs, manifests, etc.]
GHCi, version 9.10.1: https://www.haskell.org/ghc/ :? for help
ghci>
```

I'm running Podman as root on both systems.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.