You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had some requests of providing a server-based docker image as well in addition to the standalone one.
To handle this use-case we need to use make some changes to the Dockerfile (will use different build context as well).
My idea was to have two directories for each Dockerfile in the same repo:
unoserver-docker/cli/Dockerfile
unoserver-docker/server/Dockerfile
And then use context in the github action to create the two images.
However, do I need to totally separate github workflows or can I when using the action use it twice and the following jobs (signing the image) will still work?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm the main contributor to https://github.com/unoconv/unoserver-docker.
We've had some requests of providing a server-based docker image as well in addition to the standalone one.
To handle this use-case we need to use make some changes to the Dockerfile (will use different build context as well).
My idea was to have two directories for each Dockerfile in the same repo:
And then use context in the github action to create the two images.
However, do I need to totally separate github workflows or can I when using the action use it twice and the following jobs (signing the image) will still work?
For reference: https://github.com/unoconv/unoserver-docker/blob/main/.github/workflows/docker-publish..yml
Beta Was this translation helpful? Give feedback.
All reactions