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

Can't start because X11 isn't present? #138

Open
a12l opened this issue Sep 15, 2024 · 0 comments
Open

Can't start because X11 isn't present? #138

a12l opened this issue Sep 15, 2024 · 0 comments

Comments

@a12l
Copy link

a12l commented Sep 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant