Mike Beckerle created DAFFODIL-3061:
---------------------------------------
Summary: Unable to make daffodil-site work under podman
Key: DAFFODIL-3061
URL: https://issues.apache.org/jira/browse/DAFFODIL-3061
Project: Daffodil
Issue Type: Bug
Components: Website
Affects Versions: 4.1.0
Reporter: Mike Beckerle
This is not a bug necessarily, but I am blocked on it.
I am suddenly unable to build the daffodil-site with podman to test it.
Help please!
I've tried backing out to much earlier commits that I know work, but nothing
works.
Here's the output I get:
```
podman run -it --rm \
--publish 127.0.0.1:4000:4000 \
--volume="$PWD:/srv/jekyll" \
--env JEKYLL_ROOTLESS=1 \
docker.io/jekyll/jekyll:4.2.2 \
jekyll serve --watch --source site
ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x86_64-linux-musl]
/usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/definition.rb:507:in
`materialize': Could not find jekyll-asciidoc-3.0.1,
asciidoctor-diagram-3.0.0, asciidoctor-diagram-plantuml-1.2025.2,
asciidoctor-diagram-ditaamini-1.0.3, webrick-1.9.1, addressable-2.8.7,
i18n-1.14.7, kramdown-2.5.1, liquid-4.0.4, asciidoctor-2.0.23, rexml-3.4.1,
asciidoctor-diagram-batik-1.17, public_suffix-6.0.2, concurrent-ruby-1.3.5,
listen-3.9.0, ffi-1.17.2-x86_64-linux-musl, rb-inotify-0.11.1 in locally
installed gems (Bundler::GemNotFound)
from
/usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/definition.rb:187:in
`specs'
from
/usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/definition.rb:244:in
`specs_for'
from
/usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler/runtime.rb:18:in
`setup'
from /usr/local/lib/ruby/gems/3.1.0/gems/bundler-2.3.25/lib/bundler.rb:161:in
`setup'
from /usr/gem/gems/jekyll-4.2.2/lib/jekyll/plugin_manager.rb:52:in
`require_from_bundler'
from /usr/gem/gems/jekyll-4.2.2/exe/jekyll:11:in `<top (required)>'
from /usr/gem/bin/jekyll:25:in `load'
from /usr/gem/bin/jekyll:25:in `<main>'
```
This is clearly something environmental on my workstation, but I've not run
updates on it since last time I did this successfully (which was perhaps a week
ago.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
