ci: unify local and ci docker workflows

[fmartingr]

This pull request simplifies the CI and container files around to use the same logic locally and in the release process.

• Removed all docker context from the CI, now using the main Dockerfile in the root of the repository
• Refactored the dockerfile to streamline the build process: file is copied and some basics installed to a scratch image
• Removed OpenBSD arm64 test step

Fixes #546
Closes #905

[Monirzadeh]

i don't use docker(i don't want give root access to that) and try to use make buildx with podman instead but shell script not accept alias so i can test that locally.
somehow it is problem in my side but it can be good if script can work with podman too(for local use).
i don't see any problem in code, (but i can't test that because of that problem)

[fmartingr]

i don't use docker(i don't want give root access to that) and try to use make buildx with podman instead but shell script not accept alias so i can test that locally.

somehow it is problem in my side but it can be good if script can work with podman too(for local use).

i don't see any problem in code, (but i can't test that because of that problem)

Does podman support buildx? I can bundle something in the script.

[Monirzadeh]

based on podman documentation here

podman buildx build command is an alias of podman build. Not all buildx build features are available in Podman.

but i am not sure if we use any of those specific feature they mention or not, so we can try.

[fmartingr]

based on podman documentation here

podman buildx build command is an alias of podman build. Not all buildx build features are available in Podman.

but i am not sure if we use any of those specific feature they mention or not, so we can try.

You can try it locally running:

make buildx-local CONTAINER_RUNTIME=podman

I prepared it for other container runtimes but didn't test it. This command worked on my linux machine.

[Monirzadeh]

Hi i test that and work fine :+1
just one things :
when it create image left type=docker directory in root of project
if it possible (not needed that anymore) automatic remove them or move that to tmp directory.
if you want to keep that not bad if move that to dev-data and add to git ignore too.

[fmartingr]

Hi i test that and work fine :+1 just one things : when it create image left type=docker directory in root of project if it possible (not needed that anymore) automatic remove them or move that to tmp directory. if you want to keep that not bad if move that to dev-data and add to git ignore too.

Ummm, the container options specify -t shiori:localdev --output type=docker. Are you saying that this creates a folder in the root path for podman? With docker what this does is create the image directly into the docker daemon. Let me test that on my laptop.

[Monirzadeh]

yes in root of project i have type=docker that contain files and folders that use for creating images

ls ./type=docker 
etc  shiori  usr

[fmartingr]

yes in root of project i have type=docker that contain files and folders that use for creating images

ls ./type=docker 
etc  shiori  usr

Yeah just checked, it seems that podman does not support storing it directly as an image, so you would need to customize the CONTAINER_BUILDX_OPTIONS to your needs too.

I'd say that's out of scope for this PR, but if you find a way of doing so feel free to send a PR with customizations for podman as well.

[Monirzadeh]

so temporary we can add that directory to gitignore to find a solution for that later

# Exclude podman file
/type=docker*