Emacs native-comp branch convenience c ode

native-comp-convenience.org

Emacs native-comp Recipes

For lack of a better term.

Update Docker image

1. Update Andrea’s image.

   docker pull andreacorallo/emacs-nativecomp:latest
       

1. Tangle my Dockerfile.

   FROM andreacorallo/emacs-nativecomp:latest
   
   RUN adduser --quiet --uid 1000 --disabled-password me
   RUN apt-get update
   RUN apt-get install -y git install-info texinfo
   
   ENV DISPLAY=:0
   USER me:me
       

2. Rebuild my image.

   docker build -t ap/emacs-native-comp .
       

Run Docker container

• Notes
  • Run xhost + to enable GUI sessions.
    • That disables all X session security, AFAIK. Is there a better way?
• Command

  docker run -v /home/me:/home/me -v /tmp/.X11-unix/:/tmp/.X11-unix --env=DISPLAY=:0 --dns=8.8.8.8 -u me -i -t ap/emacs-native-comp:latest
      

• Script

  docker run --rm=true -v /home/me:/home/me -v /tmp/.X11-unix/:/tmp/.X11-unix --env=DISPLAY=:0 --dns=8.8.8.8 -u me -i -t ap/emacs-native-comp:latest bash -c 'cd ~; ~/.bin/emacs-sandbox -d ~/tmp/src/emacs/native-comp/.emacs.d'
      

Fair enough. I assumed by the steps that you meant to update it. Otherwise, the initial docker pull step is unnecessary, since it will be pulled at the build step.
And for the Docker pull problem, I don't have any clue about the cause. My guess would be to check your docker version, since it looks like it might be trying to use a deprecated endpoint. Image registry API has evolved several time to accomodate new features, and some upgrades were breaking changes. HTH.

@pataquets FYI, you're right that the problem was the Docker version. According to the Docker Hub documentation, my version of Docker was supported, but as best I could figure out, Andrea updated his Dockerfile with syntax that my version of Docker didn't support (but rather than giving some kind of "unrecognized Dockerfile keyword" error, Docker gave that useless message). Since then, I've switched to using GNU Guix to build/install a version of Emacs 28 into my user profile, which is working well. (It's also simpler, as it doesn't require bind-mounting directories and special files, dealing with network bridges to the container, X permissions, etc.)

Good to know such weird message. Great to know you've gone the Guix way, since I'm on Bionic also considering going for it or switching to Arch to use AUR. Ditto for Nyxt, btw.
Thanks for sharing all that info, @alphapapa.