Official docker image

Please configure docker image creation in CI/build machine after which it upload the official image to docker hub for each release.

Our current option is some unofficial/unmaintained channel docker run -it jprjr/sabotagelinux sh and nothing work in that box (butch update && butch install curl fails).

https://hub.docker.com/r/jprjr/sabotagelinux/

while official one can go under https://hub.docker.com/r/library/

Why would people want to run sabotage linux in docker? Sabotage doesn't have any release cycle.
Its made with self-hosting in mind, which is what people ususally dont want inside docker containers.

Judging from the description, jprjr/docker-misc is an personal experiment and shouldn't be used in production, probably.

@nero, that makes the build system guys lives easier. For example you can build and test your binaries on multiple musl-based systems without paying the cost of setting up an extra VM/physical hardware.

Docker is one command away and you can spin up [m]any distros, build bins, run tests and shut it down. You can even hook it up in TravisCI without paying cost of setting up your own CI server, using Jenkins for example.

cc @rofl0r

[rofl0r]

i can see it being useful. we recently had a generous donor sponsoring a second build server so i may dedicate some of its cycles to building a docker image.
@kasper3 please provide info on how to make an "official" image and getting upstreamed.

https://docs.docker.com/docker-hub/official_repos/#how-do-i-create-a-new-official-repository

@rofl0r, it will require sending PR to https://github.com/docker-library/official-images
Example of Alpine, https://github.com/gliderlabs/docker-alpine which produces https://github.com/docker-library/official-images/blob/master/library/alpine.

[rofl0r]

if i provide a rootfs tarball, can you help out in getting the docker scripts ?

Sure i will give it a shot 👍

Can we seek sponsorship from fastly like https://github.com/gliderlabs/docker-alpine#sponsors?

[rofl0r]

well, maybe if you ask nicely ? but i guess we should first getting step one done...

I tried to build it:

mkdir sabotage-build ; cd $_
curl -o rootfs.tar.xz http://ftp.barfooze.de/pub/sabotage/sabotage-1.1.14-x86_64-rootfs-core-2f51c8d0.tar.xz

cat > Dockerfile <<-"EOF"
FROM scratch
ADD rootfs.tar.xz /
CMD ["/bin/sh"]
EOF

docker build -t sabotage-builder .
docker run -it sabotage-builder

build succeeds, but docker run throws:

Error response from daemon: OCI runtime create failed: container_linux.go:296: starting container process caused "exec: "/bin/sh": stat /bin/sh: no such file or directory": unknown.

any ideas how to produce the working docker image from rootfs tarball?

cc @tianon, @andyshinn for help :)

[andyshinn]

The tarball has an extra path at root:

$ tar tf rootfs.tar.xz | head -n 5
sabotage-1.1.14-rootfs-core-2f51c8d0/
sabotage-1.1.14-rootfs-core-2f51c8d0/sbin
sabotage-1.1.14-rootfs-core-2f51c8d0/etc/
sabotage-1.1.14-rootfs-core-2f51c8d0/etc/crypttab
sabotage-1.1.14-rootfs-core-2f51c8d0/etc/wpa_supplicant.conf

You likely want to go into sabotage-1.1.14-rootfs-core-2f51c8d0 before tar like:

tar -cJf mytarfile.tar.xz -C sabotage-1.1.14-rootfs-core-2f51c8d0 .

@andyshinn, thanks. I am getting:

tar: can't change directory to 'sabotage-1.1.14-rootfs-core-2f51c8d0': No such file or directory

I tried with more selfcontained approach

cat > Dockerfile <<-"EOF"
FROM scratch
ADD http://foss.aueb.gr/mirrors/linux/sabotage/sabotage-1.1.14-x86_64-rootfs-core-2f51c8d0.tar.xz /
CMD ["/bin/sh"]
EOF

docker build -t sabotage-builder .
docker run -it sabotage-builder

and

cat > Dockerfile <<-"EOF"
FROM scratch
ADD http://foss.aueb.gr/mirrors/linux/sabotage/sabotage-1.1.14-x86_64-rootfs-core-2f51c8d0.tar.xz /
CMD ["/sabotage-1.1.14-rootfs-core-2f51c8d0/bin/sh"]
EOF

docker build -t sabotage-builder .
docker run -it sabotage-builder

same error. :(

[andyshinn]

The tarball is built wrong. It needs to be rebuilt without the sabotage-1.1.14-rootfs-core-2f51c8d0 prefix. If you extract it, then you can rebuild it with my previous command, then use that new tarball with the ADD.

man tar -> http://xkcd.com/1168/

[rofl0r]

the tarball is not "built wrong", it was built for general purpose, i.e. not specifically for docker.
i doubt docker is so inflexible it doesnt allow you to mv a directory's contents before booting it...