Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make a Docker build #15

Open
ashaikh opened this issue Dec 8, 2020 · 11 comments
Open

Make a Docker build #15

ashaikh opened this issue Dec 8, 2020 · 11 comments
Labels
enhancement New feature or request

Comments

@ashaikh
Copy link

ashaikh commented Dec 8, 2020

Hi - This is a really interesting project and I was wondering if this is something that would run on docker on Unraid? You may be able to help people with extra older devices in the house if you consider building a docker container for unraid.

@atauenis atauenis added the enhancement New feature or request label Dec 8, 2020
@atauenis atauenis changed the title Suggestion Make a Docker build Dec 8, 2020
@atauenis
Copy link
Owner

atauenis commented Dec 8, 2020

This is an interesting idea, but I haven't used docker at all, so don't know when learn it and make a container for it.

@hb9fxq
Copy link

hb9fxq commented Jan 9, 2021

Working with default config (x64): https://gist.github.com/hb9fxq/312001b0f220f6241a6e63361c3d7914 but needs rework to allow configs etc. but maybe a quick-win!?

@zefie
Copy link

zefie commented Jan 11, 2022

Some notes from my experience:

  • if using with docker-compose, add stop_signal: SIGKILL, as .NET does not behave most of the time, and since this is not a critical process no data should be corrupted by a SIGKILL

  • Sometimes WebOne and/or .NET will just crash. Even with restart: always, the container tends to just vanish from my compose with an Exited status. A workaround is to make your entry CMD point to a shell script that is a simple while (true); do /usr/local/bin/webone; done wrapper.

  • Codepages are wonky. The built in override examples (DOS, Apple, etc) seem to work but anything from MSDN does not, including iso-8859-1, which is listed as available on the /!codepages/ page. Warning: Unknown codepage iso-8859-1, using AsIs. See MSDN 'Encoding.GetEncodings Method' article for list of valid encodings. I am not sure what is up with that. I even tried installing locales and doing locale-gen in my Dockerfile but it did not help. But even so, it also says
    Current Output Encoding: (whatever is set)
    Current Output Encoding: same as source
    for some reason, so even if the codepage is acknowledged, I am unsure if it is working, since it is reporting two different things at the same time.

@atauenis
Copy link
Owner

atauenis commented Sep 7, 2022

#67 (comment)

@atauenis
Copy link
Owner

Canonical has been released Docker packages with Ubuntu & .NET6. Probably, they may be used as base for correct WebOne docker images.
https://ubuntu.com/blog/install-dotnet-on-ubuntu
https://devblogs.microsoft.com/dotnet/dotnet-6-is-now-in-ubuntu-2204/

@way5
Copy link
Contributor

way5 commented Sep 12, 2022

Ubuntu based image would be certainly more bulky than Alpine based.
What do you mean "...correct WebOne docker images" ?

@atauenis
Copy link
Owner

I am meaning that made from deb package, not from sources. The sources are always latest, but not always stable.
Currently I don't know any utilities to make Alpine package on Windows/Visual Studio (like one I'm using for deb/rpm). So stable releases are currently only in deb/rpm formats.

@aptonline
Copy link

Just found this WebOne after reading this toot https://oldbytes.space/@smallsco/109333356506212028

Certainly interested in a docker image and agree Ubuntu see a little top heavy.

@nefarius
Copy link

nefarius commented Dec 3, 2023

Made one (#108) and finding this issue afterwards 😅 feel free to test and give me feedback, cheers!

@kyzima-spb
Copy link

The sources are always latest

If I take the sources from the archive in releases, then don't I get a stable version?

@atauenis
Copy link
Owner

atauenis commented Aug 1, 2024

Now (since v0.17.1) the development has split to master and dev branches. The master is equal to latest stable release (identical to the source code that can be downloaded from Releases). And dev is the top of development process.

Previously master contained everything latest, in most case newer than published release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants