buildah | A tool that facilitates building OCI images | Continuous Deployment library

I recently started using podman and realized that images pulled via docker doesn't become available for use to podman and vice-versa. For example:-

If I pull the image using docker CLI, as shown below

i have installed python 3 ..

when i do :

In docker I can just boot the server (WebSphere) as a build step and start configuring it via it's jython SOAP API.

I'm trying convert my Dockerfile into a shell script using buildah to create the container instead of docker build. Is there an easy way to achieve this same behaviour? (It's not working so far)

Things I tried so far:

• buildah run $container /opt/../startServer.sh server1

  result: timeout

• chroot $mountpoint bash -c "/opt/../startServer.sh server1"

  result: error: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or director

edit 1:

• Also tried running buildah build-using-dockerfile with a working Dockerfile when using docker itself but it fails with buildah.

OCI containers are a convenient way to package suitable toolchain for a project so that the development environments are consistent and new project members can start quickly by simply checking out the project and pulling the relevant containers.

• Of course I am not talking about projects that simply need a C++ compiler or Node.JS. I am talking about projects that need specific compiler packages that don't work with newer than Fedora 22, projects with special tools that need to be installed manually into strange places, working on multiple projects that have tools that are not co-installable and such. For this kind of things it is easier to have a container than follow twenty installation steps and then pray the bits left from previous project don't break things for you.

However, starting a container with compiler to build a project requires quite a few options on the docker (or podman) command-line. Besides the image name, usually:

• mount of the project working directory
• user id (because the container should access the mounted files as the user running it)
• if the tool needs access to some network resources, it might also need
  • some credentials, via environment or otherwise
  • ssh agent socket (mount and environment variable)
• if the build process involves building docker containers
  • docker socket (mount); buildah may work without special setup though
• and if is a graphic tool (e.g. IDE)
  • X socket mount and environment variable
  • --ipc host to make shared memory work

And then it can get more complicated by other factors. E.g. if the developers are in different departments and don't have access to the same docker repository, their images may be called differently, because docker does not support symbolic names of repositories (podman does though).

Is there some standard(ish) way to handle these options or is everybody just using ad-hoc wrapper scripts?

I want to build a tiny container image from scratch using Buildah to run a Go app. Apart from the app itself, what other libraries etc need to be included. I am thinking that glibc is needed - is there anything else?

So in summary, I think I am asking "what are all the external dependencies that a compiled Go app needs on Linux?"

There is almost no disk space left in my home directory but I have a lot of disk space in the directory /scratch/tmpexperiment. That directory is now empty.

I would like to try out the commands podman and buildah (just to experiment and learn). After the experiment I would like to erase the directory /scratch/tmpexperiment.

Is it possible to instruct podman and buildah to only create and write files under /scratch/tmpexperiment?

Preferably my home directory should remain untouched during the experiment (or at least modified as little as possible).

My user does not have sudo permissions. This question is regarding non-root (rootless) use of podman and buildah. The installed software versions are podman 1.4.0 and 1.9.0-dev.

With buildah I am trying to build a container image that should only contain the program cowsay and its dependencies. I am doing this on a Fedora 29 computer where I don't have root permissions. Instead of using a Dockerfile and the command buildah build-using-dockerfile (aka buildah bud) I would like to

1. Create an empty container.
2. Mount its file system.
3. Use /usr/bin/dnf on my host system to install packages directly into the file system under the mount point.
4. Create the container image from the file system.

The command buildah from scratch creates an empty container but when I try to mount the file system I get an error

Using buildah, I can find out the date my image was built at with this call: