Following is my Docker compose file. I have used the Jenkins images to install Jenkins. Within the same file,I have defined another container from which I can SSH and connect with the Jenkins server.

Docker Compose File

version: '3'
services:
  jenkins:
    container_name: jenkins
    image: jenkins/jenkins
    ports:
      - "8080:8080"
    volumes:
      - "$PWD/jenkins_home:/var/jenkins_home"
    networks:
      - net
  remote_host:
    container_name: remote-host
    image: remote-host
    build:
      context: centos
    networks:
      - net
networks:
  net:
Created another folder name Centos and created Dockerfile within it.

FROM centos:7

RUN yum -y install openssh-server

RUN useradd remote_user && \
    echo remote_user:1234 | chpasswd && \
    mkdir /home/remote_user/.ssh && \
    chmod 700 /home/remote_user/.ssh

COPY remote-key.pub /home/remote_user/.ssh/authorized-key

RUN chown remote_user:remote_user -R /home/remote_user/.ssh && \
    chmod 600 /home/remote_user/.ssh/authorized-key

RUN /usr/sbin/sshd-keygen

CMD /usr/sbin/ssh -D
I ran following command docker-compose build

Output

=> [internal] load build definition from Dockerfile                                                                                                        0.0s
=> => transferring dockerfile: 32B                                                                                                                          0.0s
=> [internal] load .dockerignore                                                                                                                            0.0s
=> => transferring context: 2B                                                                                                                              0.0s
=> [internal] load metadata for docker.io/library/centos:7                                                                                                  0.7s
=> [1/6] FROM docker.io/library/centos:7@sha256:c73f515d06b0fa07bb18d8202035e739a494ce760aa73129f60f4bf2bd22b407                                            0.0s
=> [internal] load build context                                                                                                                            0.0s
=> => transferring context: 36B                                                                                                                            0.0s
=> CACHED [2/6] RUN yum -y install openssh-server                                                                                                          0.0s
=> CACHED [3/6] RUN useradd remote_user &&    echo remote_user:1234 | chpasswd &&    mkdir /home/remote_user/.ssh &&    chmod 700 /home/remote_user/.ss  0.0s
=> CACHED [4/6] COPY remote-key.pub /home/remote_user/.ssh/authorized-key                                                                                  0.0s
=> CACHED [5/6] RUN chown remote_user:remote_user -R /home/remote_user/.ssh &&    chmod 600 /home/remote_user/.ssh/authorized-key                          0.0s
=> CACHED [6/6] RUN /usr/sbin/sshd-keygen                                                                                                                  0.0s
=> exporting to image                                                                                                                                      0.0s
=> => exporting layers                                                                                                                                      0.0s
=> => writing image sha256:fcaaebf103d6674134a68c23f92e2946b9395e2a970b3c2e78c59b9a18fec8be                                                                0.0s
=> => naming to docker.io/library/remote-host
then I ran following command docker-compose up -d

Output

[+] Running 2/2
⠿ Container jenkins      Running                                                                                                                            0.0s
⠿ Container remote-host  Started 
When I run docker images, I can see remote-host

REPOSITORY        TAG      IMAGE ID      CREATED        SIZE
remote-host      latest    fcaaebf103d6  25 hours ago  367MB
jenkins/jenkins  latest    97d23cbbfa56  5 days ago    463MB
but when I run docker ps, I do not see the running container.

CONTAINER ID  IMAGE            COMMAND                  CREATED        STATUS        PORTS                              NAMES
06aa0ceabb18  jenkins/jenkins  "/sbin/tini -- /usr/…"  39 hours ago  Up 37 hours  0.0.0.0:8080->8080/tcp, 50000/tcp  jenkins
docker ps -a

CONTAINER ID  IMAGE            COMMAND                  CREATED          STATUS                      PORTS                              NAMES
dbd2c2b9cecb  jenkins/jenkins  "/sbin/tini -- /usr/…"  30 minutes ago  Up 30 minutes                0.0.0.0:8080->8080/tcp, 50000/tcp  jenkins
812216a3c8e9  remote-host      "/bin/sh -c '/usr/sb…"  30 minutes ago  Exited (127) 7 minutes ago 
Can someone tell me where did I make mistake?

I had Manjaro-phosh beta 22 with operating SMS, MMS, phone calls (send and receive), and audio working and was getting optimistic.  I did a pacman system update hoping for more improvement but now after a large update it won't boot.  Went from working pretty well to not booting.

Upon press of power button, it just shows the "big M" and has the balls spinning around like windows and hangs there.  Never fully boots.  I did a reboot holding down the RE button.  No improvement.

I will load manjaro-phosh beta 23 (https://github.com/manjaro-pinephone/phosh/releases) to SD card and try again.

I'd like to know if others had working system that was upset by recent update (about 100 packages).  Also, if anyone found a successful reboot procedure.

thanks,      tom kosvic

Hello there,

if someone already asked this, I'm sorry for not finding the clue:

Is it possible to make the Phosh app grid transparent to let the desktop background be visible?

I tried to point to a transparent png file according to this Mobian wiki entry

https://wiki.mobian-project.org/doku.php...r-app-grid

and changed all the RGBA values to zero, but it didn't work - still the black menu background.

I also tried to point to the original background picture - which works - but opening and closing of the menu becomes laggy due to the large picture size.

Thanks for ideas!

Cheers!

Discussion of ARM laptops online: https://www.makeuseof.com/arm-laptop-linux/

Hello there,

has someone tested the new version (20220227) of the Mobian Installer for the PinephonePro?

https://images.mobian-project.org/pineph...er/weekly/

I tried FDE installation from SDcard on eMMC and SDcard and both are not working. Choosing the eMMC, it's aborting with an error message while installing. Choosing installation on the SDcard is going through, but the phone is not booting.

Any ideas?

Cheers!

I don't know if anyone else has problems with the terminal on the Pinephone.

For me, when it wraps a line, if I then backspace to correct that line then it gets very garbled so that I have to Ctrl-C and rewrite the whole line from the beginning.

I have tried several different terminals, but they all seem to do the same thing.

Any suggestions?

Hello,

I have a Pinephone Manjaro edition and I discovered that I don't know the passcode to log into the phone anymore. Any suggestions?

Thanks

For me, and probably for a small minority of other Pinephone users out there, the arrival of the clamshell keyboard allowed me to convert my Pinephone into the thing I had been dreaming about for years: a tiny palmtop computer. However some googling on how to do this was not super helpful. So I'm writing up what I figured out, both as an archive of my process and maybe to help others who want to do this get past sticky points.

There's two big categories of what I tried: First, I experimented with using Plasma Mobile as a desktop, but turned on its side to landscape by default. This worked more or less fine, but I soon got the hankering for being able to have multiple windows open on a screen, and being able to alt-tab between applications. (Why doesn't that work on Plasma Mobile? Seems like there's no reason it shouldn't! But it didn't.) So after a week of using Plasma Mobile in landscape mode, I installed Awesome windows manager and never looked back.

I really want to spend more time using and less time configuring, so while I _could_ do this on Arch or some other more experimental Pinephone OS, I really wanted to make everything work on default Manjaro. Thankfully this turned out to not be too difficult.

So first up: configurations to Plasma Mobile to make it more like a desktop now that you've got the clamshell keyboard going (this stuff is pretty basic, but I had trouble finding it):

1. Landscape mode: Just use the settings to turn on auto-rotate and roll the screen to landscape mode. I found it annoying to auto-rotate so once it was in landscape I turned auto-rotate off.
   
   
2. The most important thing is to disable the soft keyboard. This is done by adding the keyboard control widget to the desktop and then disabling the soft keyboard, see:
   https://forum.pine64.org/showthread.php?...#pid105077
   (I wish I had seen this post. I had to figure it out for myself. Tip: if you haven't seen the Pine64 wiki page on the keyboard it is full of useful information:
   https://wiki.pine64.org/wiki/PinePhone_(Pro)_Keyboard
   ...And surprisingly difficult to google.)
   
   
3. That's pretty much it for Plasma Mobile. Because poking and swiping sucks, I recommend just getting used to using the keyboard shortcuts for your software, but those are all the same as shortcuts you've probably been using for your full-sized laptop/desktop for years. With the soft keyboard disabled the Plasma Mobile Terminal works nicely. Install a terminal-based text editor and start writing or coding! Firefox rocks as a browser, particularly if you install the Vim Vixen extension and go to an all-keyboard interaction with your browser.
   

1. Install Awesome or any other windows manager you want to run with pacman. Nothing fancy here, you should already know how to do this as part of basic system maintenance and management. I didn't try IceWM or any other more conventional windows manager. I don't see any reason why you can't run whatever you like most. I would suggest though that a tiling windows manager like Awesome or DWM where everything can be controlled by keyboard shortcuts will be more useful. Poking tiny menus on the Pinephone touchscreen isn't super easy. I'd also suggest that -- at least with regular Pinephone -- keeping your windows manager lightweight is going to help.
   
   
2. Now to launch the windows manager you want to use you need to change the display/login manager. The factory-installed setup on the Pinephone is sddm (KDE's display manager) which kicks you automatically into Plasma-mobile windows manager. (All running on top of Manjaro Linux of course.) The sweetest thing would be if sddm let you choose which windows manager you wanted to use on login. This is how most Linux desktops are set up. So normally all you have to do is install the windows manager you want (mine = Awesome as I said) and then you can choose it at the login screen.
   
   On the Pinephone, sddm has been modified for poking in a number to unlock the screen/log in. Nowhere is there an option to choose your windows manager (or 'session' as many call it). I could not figure out how to change the settings of sddm to give you the option to choose your windows manager (even though regular desktop sddm has this normally). After messing with it for a while, I decided it would be easier to just switch display/login managers.
   • The first thing I tried was switching to LightDM, a common enough choice for display managers. This was just a matter of installing it with pacman, and then enabling it as a service:
     
     Code:

     sudo systemctl enable lightdm.service
     But LightDM was crashing on startup for some reason. Gave up on that.
     
   • Then I tried ly display manager -- super minimal, non-graphical, ncurses-like. I love it on my full-sized laptop. I compiled it and installed it from the AUR:
     https://aur.archlinux.org/ly.git
     That one seemed to be starting fine, but wasn't coming up on the console when it started. So I gave up on that one too.
     
   • Finally I decided minimalism was the way to go, and compiled and installed emptty:
     https://aur.archlinux.org/emptty.git
     Emptty is nothing but a command-line login that then lets you choose which windows manager to start. (Note: it required installing the pacman package go to compile it.) It worked perfectly. Remember you need to enable the service:
     
     Code:

     sudo systemctl enable emptty
     
     
   • You may also need to disable sddm:
     
     Code:

     sudo systemctl disable sddm.service
     
     
3. Now you've got the display manager going but since emptty is running on the console it is in portrait mode and rotated from your landscape keyboard setting. You'll want to rotate the console so you can read it.
   As root, edit /boot/boot.txt. To the setenv bootargs line, add:
   
   Code:

   fbcon=rotate:1
   
   Then run:
   
   Code:

   mkimage -A arm -O linux -T script -C none -n "U-Boot boot script" -d boot.txt boot.scr
   
   This will set your console to boot in landscape mode. Just remember that if you want to run your phone _without_ your keyboard, you'll need to use systemctl to enable sddm and disable emptty because without the keyboard there's no way to input anything on the console! In that case you will need to go back to the sddm poking-in-a-number display manager.
   
   
4. More on configuring Awesome ('Awesome' has got to be one of the single most ungoogle-able pieces of software in the linux world! It's not the smartest name.) Obviously if you are using a different windows manager, you can skip this. Though I think a few of the concepts will be relevant to other windows managers, and you may find them useful.
   • Screen rotation: Awesome is going to default to portrait mode. You'll want to rotate it once you are running by opening a terminal and using xrandr:
     
     Code:

     xrandr --output DSI-1 --rotate right
     
     
   • Pointer rotation: You also need to rotate your pointer input or your x will be on your y axis and visa versa. This took my _forever_ to figure out how to do. You use xinput to do the same thing xrandr did for the screen:
     
     Code:

     xinput set-prop 8 --type=float "Coordinate Transformation Matrix"  0 1 0 -1 0 1 0 0 1
     
     
   • Set these automatically on login: You can probably do this in Awesome, but I like to control it in the .xinitrc file in my home directory. This is the file that is read if you use 'startx' to start your windows manager from the command line. But you can also use it if you start your windows manager with a display/login manager like we are doing. To do so, you need to install the xinit-session package from AUR:
     https://aur.archlinux.org/xinit-xsession.git
     After install xinit will be one of your session options in emptty, and you can start Awesome by reading from .xinitrc. I added these lines to the end of my ~/.xinitrc:
     
     Code:

     exec xrandr --output DSI-1 --rotate right &
exec xinput set-prop 8 --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1 &
awesome  # Needs to NOT have a &
     
     Big NOTE: you need to make your .xinitrc file _executable_ for xinit to work as a session:
     
     Code:

     chmod 755 ~/.xinitrc
   • Configuring Awesome itself: Awesome is configured in the ~/.config/awesome/rc.lua file. It is not entirely simple or straightforward, and you'll want to read the documentation on Awesome if you really want to get into this. However, here's a few tips:
     • Mod4 is the Pinecone key. Might as well put that to work!
       
     • I like to go through the rc.lua and disable the stuff I don't use. I can only hold so many key commands in my head anyway.
       
     • I like to put system commands on keyboard combinations in the rc.lua,like:
       
     • put 'systemctl suspend' on meta-z
       
     • put 'firefox' on meta-f or something.
       
     • put a terminal launch command on meta-Enter
       
     • put 'xbacklight -dec 10' and 'xbacklight -inc 10' on meta--(minus) and meta-+ respectively so you can control screen brightness. This will require installing the xbacklight or the acpilight packages. And it only works if your windows manager uses X11, not wayland.
       
     • You can do something similar to control sound using pamixer (or some other command-line volume control) to control sound volume.
       
       
5. Poking the screen: At this point you can do _almost_ everything from the keyboard. But you'll find you still need to occasionally poke the screen to select something. The touchscreen is accurate enough that you can very very carefully select a tiny link in a browser, or software menu. But you can't really select things for copy-pasting. And there's no right-click. (Though I see some packages that implement a long-hold as a right-click. I haven't tried them yet.)
   

Good day,

i just received my PinePhone with convergence package.



On first boot, the screen flipped to horizontal mode, and can't return to vertical mode (unsuccessfully tried to turn phone in any direction, rebooted several times but nothing changed).



I can't fill the textbox because the onscreen keyboard pop up and cover some textboxes; i am able to skip a few page form, until "choose username and password" form, which can't be filled or skipped; so i got stuck there... (At first, i feared a defective gyroscope also...)



Does anyone had this issue? Please give some advice, i'm actually blocked...
thanks

About a month ago, I purchased a pinephone pro, I just was notified that it shipped today. The problem is, is I did not read the text at the bottom about purchasing a battery. Does this mean it does not ship with a battery, and if so, are there any batteries from say amazon that will fit in the phone?